Skip to content

feat(homepage): prove the local Cloudflare Worker journey - #14

Open
phibkro wants to merge 1 commit into
publish/0012-dashboard-w0from
publish/0011-homepage-local
Open

feat(homepage): prove the local Cloudflare Worker journey#14
phibkro wants to merge 1 commit into
publish/0012-dashboard-w0from
publish/0011-homepage-local

Conversation

@phibkro

@phibkro phibkro commented Aug 12, 2026

Copy link
Copy Markdown
Member

Design spec

design-specs/0011-cloudflare-homepage-dev-deployment.md

Journey

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

  1. Check out this stacked branch.
  2. Run the local build/worker/browser commands in the spec Evidence section.
  3. Exercise the homepage routes and inspect the local health/evidence signals.

Evidence

  • Local Bun/Node build, wrapper, browser, digest, security, and cleanup gates: PASS.
  • Exact accepted 0011 local capsule paths; no dashboard, backend, or SDK source mutation.
  • Frontend journey evidence is recorded in the spec; no provider evidence is implied.

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.

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 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".

Comment thread apps/homepage/README.md

```sh
pnpm lint:fix:unsafe
bun install --frozen-lockfile

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P1 Badge 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"),

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge 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 👍 / 👎.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant