Deployment evidence requires at least 1 real non-sample listing.
CL
ClearLah
Deploy command for Cloudflare Pages
Deploy only when the public marketplace can be verified.
One operator surface for Cloudflare Pages package, project guard, direct upload, live URL verification, deployment evidence, and customer beta recheck.
Deployment Evidence Gate
Checking buyer-visible public inventory before deployment evidence.
Only deploy and record evidence for the locked `clearlah` Pages project.
Run `record:deployment -- --verify` after live URL and listings pass.
Fastest Safe Deploy Flow
Keep preview uploads separate from customer beta evidence.
Build Pages package
Use this to upload an internal preview zip. It does not prove customer beta readiness while inventory or notifications are blocked.
Build strict package
This must pass before real user traffic. It fails when listings, payments, notifications, or package checks are incomplete.
Verify Cloudflare scope
Confirm the CLI account and Pages project before any upload, especially when multiple Cloudflare projects exist.
Deploy to Pages
Use Wrangler only after strict checks pass. Dashboard Direct Upload can use the same zip and handoff notes.
Record verified URL
The verifier checks homepage, trust pages, JS contact config, and real listings before writing evidence.
Recheck readiness
Customer beta remains blocked until real supply, notifications, strict package, and deployment evidence pass together.
Copy Commands
These commands are ordered so deployment evidence cannot bypass real marketplace readiness.
Preview package
Creates the Cloudflare Pages zip for internal preview and package inspection.
npm run package:pages
Strict package
Use before customer beta or production traffic.
npm run package:pages:strict
Cloudflare scope checks
Confirms authentication and project availability before upload.
npx wrangler whoami npx wrangler pages project list
Dashboard handoff
Writes the latest package, blockers, URL probe, and post-deploy command into an artifact.
npm run deploy:handoff -- --url=https://clearlah.pages.dev
Wrangler deploy
Runs the guarded deploy command for the locked `clearlah` Pages project.
npm run deploy:pages
Direct upload fallback
Use this zip in Cloudflare Dashboard if CLI deployment is unavailable.
Upload artifacts/clearlah-pages-dist.zip to the Cloudflare Pages project named clearlah.
Record evidence
Writes `docs/deployment-evidence.json` only after live verification passes.
npm run record:deployment -- --url=https://clearlah.pages.dev --method="Cloudflare Pages Direct Upload" --project=clearlah --verify
URL guard smoke
Protects the evidence gate from local, private, placeholder, or wrong-project URLs.
npm run test:deployment-url
Customer beta recheck
Run after supply, notifications, package, and deployment evidence are all in place.
npm run check:customer-beta
Operator Links
Deployment depends on real supply, notifications, admin review, and platform readiness together.
Deploy Guardrails
These prevent a public URL from being mistaken for a ready marketplace.
No wrong project
Only the Cloudflare Pages project named `clearlah` can be used for deployment evidence.
No empty feed evidence
Do not record deployment evidence while `/data/listings.json` has zero real buyer-visible listings.
No local URL
Deployment evidence must use a public HTTPS URL, not localhost, private IP, or a placeholder domain.
No skipped verify
Use `record:deployment -- --verify`; manual notes are not enough for customer beta.