feat(web): add Cloudflare deployment placeholder

[kapustazh]

Problem and behavior

Cloudflare Workers Builds is connected to the existing oneshot Worker and custom domain, but the repository had no deployable frontend or Wrangler configuration. Every PR therefore reported a failed external deployment.

This adds a static testnet-labelled placeholder and a minimal static-assets wrangler.jsonc. It contains no application logic and will be replaced by the frozen A05 frontend after Gate P4.

Validation

• Format, lint, typecheck, and 439 tests pass.
• wrangler deploy --dry-run reads the placeholder asset and exits successfully with no bindings.
• GitHub checks pass: repository policy, Markdown/Mermaid, ESLint/TypeScript/PostgreSQL, and Workers Builds: oneshot.

Review evidence

• Gate A: PASS — Antigravity / Gemini 3.8 Flash, tree 2dd5a0b955849431ae27a69192b2044937379db3.
• Gate B: PASS — Antigravity / Gemini 3.8 Flash, head c77e9a45b3251951a56a2d96aa5e3c7821aafef5, same tree.

Human merge remains required.

[cloudflare-workers-and-pages]

Deploying with    Cloudflare Workers

The latest updates on your project. Learn more about integrating Git with Workers.

Status	Name	Latest Commit	Updated (UTC)
✅ Deployment successful! View logs	oneshot	c77e9a4	Sep 07 2026, 09:20 PM