PR Reviews

This PR adds Cloudflare Workers/Pages Wrangler configuration for the static landing page, plus the usual `.wrangler`/`dev.vars`/`env` excludes in `.gitignore`. The diff is clean from a secrets-in-code perspective. The only notable concern is that serving the repository root as the static assets directory will expose configuration files (e.g. `.gitignore`, `wrangler.jsonc`) from the deployed worker. I recommend narrowing `assets.directory` to a dedicated `public/` folder or adding an `assets.not_found_handling`/`exclude` strategy so internal metadata is not served. Not blocking on its own.

This PR adds auto-generated Cloudflare Workers configuration (`wrangler.jsonc`) and standard Wrangler-related ignore rules. The setup is reasonable for a static landing page, but serving the repository root (`"directory": "."`) as the assets directory can publish config files (e.g. `wrangler.jsonc`, `.gitignore`) and any future `.env`/`.dev.vars` files that are only gitignored, not excluded from the asset upload. Consider adding `assets.exclude` patterns (or moving deployable assets into a dedicated `public/` directory). Also, if this becomes the primary hosting target, update `AGENTS.md` to document `wrangler dev` alongside the existing `serve` command.