feat(homepage): prove the local Cloudflare Worker journey - #14
Conversation
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 3bc26425da
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
|
|
||
| ```sh | ||
| pnpm lint:fix:unsafe | ||
| bun install --frozen-lockfile |
There was a problem hiding this comment.
Install the standalone Alchemy island
On a fresh checkout, this is the only installation instruction, but the root workspace list contains only apps/* and packages/*, while homepage-cli.ts executes infra/alchemy/node_modules/.bin/alchemy. Bun's local install --help confirms that installation uses the current package's manifest and that another package requires --cwd; consequently, every documented plan, deploy, and destroy command fails with ENOENT after following these prerequisites. Add a frozen install for infra/alchemy before the operator commands.
Useful? React with 👍 / 👎.
| const responses = sortEntries(diagnostics.responses); | ||
| const probes = sortEntries(diagnostics.probes); | ||
| writeFileSync( | ||
| join(EVIDENCE_DIR, "network-ledger.json"), |
There was a problem hiding this comment.
Preserve failed-attempt evidence across CI retries
When CI is set, Playwright retains the existing two-retry policy, but every attempt writes to this same fixed ledger path (and likewise to the fixed provenance path). A failing first attempt can therefore be retried successfully and have its forbidden requests, console errors, or page errors overwritten, leaving evidence that represents only the final attempt while the suite reports success. Disable retries for this deterministic evidence journey or write and retain attempt-indexed evidence.
Useful? React with 👍 / 👎.
Design spec
design-specs/0011-cloudflare-homepage-dev-deployment.mdJourney
A maintainer builds and runs the homepage through the accepted local Cloudflare Worker/Alchemy development contract, then exercises the local browser journey and bounded cleanup.
Experience it
Evidence
What is real
The local DEV CONTENT Worker journey is conforming. Provider canary/deploy/destroy, DNS/TLS, persistent
main-dev, and public reachability remain unperformed and require separate operator authority; this PR does not deploy anything.