From 34cb089c9c68e3b6bdd32a5002f15ec857cf145b Mon Sep 17 00:00:00 2001 From: Thomas Camlong Date: Sat, 24 Oct 2026 19:53:07 +0200 Subject: [PATCH] fix(release): verify canonical Pages domain and publication evidence --- .github/workflows/ci.yml | 2 +- .scratch/rewrite/issues/27-demo-deployment.md | 16 +++++++++++++++- .scratch/rewrite/map.md | 15 +++++++++++++++ .scratch/rewrite/spec.md | 6 ++++-- .scratch/v3-release/notes.md | 10 ++++------ .scratch/v3-release/spec.md | 10 +++++++--- .scratch/v3-release/validation.md | 13 +++++++++++++ README.md | 6 +++--- docs/agents/architecture.md | 6 ++++-- docs/features.md | 2 +- 10 files changed, 67 insertions(+), 19 deletions(-) diff --git a/.github/workflows/ci.yml b/.github/workflows/ci.yml index 449bffa..d93ef5c 100644 --- a/.github/workflows/ci.yml +++ b/.github/workflows/ci.yml @@ -54,7 +54,7 @@ jobs: cancel-in-progress: false environment: name: demo - url: https://sub.ajnart.dev + url: https://subs.ajnart.dev steps: - uses: actions/checkout@v7.0.1 - uses: oven-sh/setup-bun@v2 diff --git a/.scratch/rewrite/issues/27-demo-deployment.md b/.scratch/rewrite/issues/27-demo-deployment.md index ea62a02..9fa4971 100644 --- a/.scratch/rewrite/issues/27-demo-deployment.md +++ b/.scratch/rewrite/issues/27-demo-deployment.md @@ -5,9 +5,11 @@ Progress: claimed Type: task Blocked by: 23, 24, 26 +Current blocker: scoped Cloudflare Pages Edit Actions token. Domain access and manual publication are verified; automatic publication is not yet proven. + ## Outcome -Publish the validated static demo at sub.ajnart.dev, retain subs.ajnart.dev as a compatibility alias, and show the current app in a concise README. +Publish the validated static demo at subs.ajnart.dev as its only canonical hostname, and show the current app in a concise README. ## Acceptance criteria @@ -19,6 +21,8 @@ Publish the validated static demo at sub.ajnart.dev, retain subs.ajnart.dev as a ## Evidence +Latest Pages evidence: `subs.ajnart.dev` is the only canonical hostname. Renewed MCP authentication enabled its verified cutover from the old Worker binding to proxied CNAME `subs-demo.pages.dev`. Pages reports the domain active, verification active and validation active; valid HTTPS and all static entry assets match the tested build. Live batch/persistence/export/import/reset and PIN-free/zero-backend checks pass. The mistaken singular Pages registration was removed. Earlier Worker/domain/authentication evidence below is retained as history; the only remaining deployment blocker is the scoped Actions token. + October 24, 2026: Wrangler published the final static artifact to https://subs.ajnart.dev, version `b8d6886a-02ed-442c-8037-a6a6c97fc1d2`. HTTPS with a valid certificate returns 200, and the published JS/CSS names match the final local build. Public DNS answers are present; the local machine required explicit resolution while its negative cache caught up. README is concise and uses three refreshed real screenshots with the correct active count and no transient toasts. Final local lint/typecheck, all 27 existing tests, both builds, Docker and Compose validation pass. CI checks both targets and Docker, then deploys successful `main` builds or an explicit manual request with Wrangler. Repository Actions secrets were empty at verification: automatic deployment remains blocked until the Operator adds a scoped `CLOUDFLARE_API_TOKEN`; local OAuth is deliberately not copied into CI. The user has been notified without requesting a secret in chat. This ticket is not marked resolved while automatic deployment remains unproven. @@ -32,3 +36,13 @@ The final development browser confirms Inter loads with HTTP 200 and no backend Subsequent user steering requests the singular primary hostname and a major release. `.scratch/v3-release/spec.md` tracks that publication. The earlier deployment URLs and version IDs above are historical evidence, not proof of the new release or automatic deployment. The credential blocker remains open until an actual Actions deployment succeeds. PR #50 merged at `63dbaaf3cc8ff55c15e83742fbc2de07031fb63c`; fresh PR checks passed all 27 existing tests and Docker. Main application and Docker checks also passed, but the deploy job failed at the expected absent-token preflight in run `40112683090`, before upload. The user subsequently selected real Cloudflare Pages, not a Worker-hosted static application. The scoped CI credential now needs Account → Cloudflare Pages → Edit; custom-domain DNS access is separate. The existing plural Worker binding is retained until the primary Pages hostname is verified. + +### Historical pre-cutover follow-up + +Latest user correction supersedes the earlier singular-primary request: only `subs.ajnart.dev` is canonical, not a compatibility alias. Main `328902e` is live on Pages at https://subs-demo.pages.dev (deployment https://b2da0cfb.subs-demo.pages.dev), with nine cards, PIN-free access, zero API requests, batch creation, persistence, and reset verified. Main multiarch GHCR publication succeeded in 2m9s; all 27 existing tests, both builds, lint, and typecheck passed. The plural custom domain still points to the old Worker; no Pages cutover is complete. Reauthenticated MCP still fails with `requires login before it can register a client`, even after reconnecting and activating the credential. The scoped CI token remains absent, so automatic deployment is still unproven and this ticket remains claimed. + +### Current canonical Pages verification + +MCP authentication now works and verified account `71a8e70b7b1e301fca750fd6c6ae1f1d`, project `subs-demo`, main `328902e`, and deployment `b2da0cfb` returning HTTP 200. The Pages domain was registered, only its old Worker binding was detached, and a proxied CNAME with TTL 1 now points `subs.ajnart.dev` to `subs-demo.pages.dev`. Canonical HTTPS has a valid certificate; HTML, favicon, JS, CSS, and adapter bytes match the tested build. The browser showed nine cards, no PIN, and zero API requests. Adding two plans priced at zero and 12.34 produced eleven cards, and reload preserved them. + +The 17:46 pending-validation snapshot is superseded: Pages domain status, verification and validation are now all active, with live HTTPS verified. Repository Actions secrets remain empty: manual Pages publication is verified, while automated deployment remains blocked by the absent scoped token. This ticket remains claimed only for that automation requirement; the user requested `v3.0.0` publication after the final PR merges. diff --git a/.scratch/rewrite/map.md b/.scratch/rewrite/map.md index f4d5a33..e330333 100644 --- a/.scratch/rewrite/map.md +++ b/.scratch/rewrite/map.md @@ -31,6 +31,7 @@ The coordinator claims this release through completion. GPT-6.1 Sol implementati - Latest user scope adds Hallmark-led UI polish, purposeful Magic UI/Aceternity components, lazy link previews, and a browser-only static demo deployed with Wrangler at subs.ajnart.dev. The private Docker target remains separate and protected by default. - Subsequent release steering selects `sub.ajnart.dev` as primary and retains the plural hostname as a compatibility alias. Publish a new major, `v3.0.0`, because v2 already exists; stop obsolete Vercel Git deployments without deleting the external project. Current release work and validation are tracked in `.scratch/v3-release/spec.md`. - The user then explicitly selected Cloudflare Pages for the PIN-free static DEMO_MODE build, authorized full existing-test and Docker verification, and requested concise Markdown feature docs without a website. PR #50 is merged; the focused Pages/container follow-up must also merge before the final v3 release. This supersedes the prior Worker-hosting choice, not the private-server boundary. +- Latest hostname correction supersedes the earlier singular-primary/compatibility-alias steering above: `subs.ajnart.dev` is the only canonical hostname. The singular hostname is not a target or alias. The initial constraint was to preserve the old plural Worker deployment until the Pages custom-domain cutover was verified; current cutover evidence follows below. ## Execution order @@ -111,3 +112,17 @@ Future exploratory candidates, not release commitments: provider price monitorin - [25 — Visual polish](issues/25-visual-polish.md): all three P2 review findings plus footer nit fixed and recaptured; Hallmark static exceptions remain explicit. - [26 — Static demo](issues/26-static-demo.md): API-blocked persistence, isolated reset/corrupt recovery and static build pass. - [27 — Deployment/screenshots](issues/27-demo-deployment.md): final demo published and HTTPS assets verified. GitHub application and Docker checks passed for implementation commit `aa70c37` on push and PR #50; automatic production deployment remains blocked on the scoped Actions secret. + +### Historical pre-cutover Pages release follow-up + +- Main `328902e` is live at https://subs-demo.pages.dev (deployment https://b2da0cfb.subs-demo.pages.dev). Nine cards, PIN-free access, zero API requests, batch creation, persistence, and reset were verified. +- Main multiarch GHCR publication succeeded in 2m9s; all 27 existing tests, both builds, lint, and typecheck passed. +- Only `subs.ajnart.dev` is canonical. It still points to the old Worker and has not been cut over to Pages. Reauthenticated MCP still fails with `requires login before it can register a client`, even after reconnecting and activating the credential. The scoped CI token remains absent; neither custom-domain activation nor automatic deployment is complete. + +### MCP authentication resolved and canonical Pages HTTPS verified + +- The user was correct: MCP authentication works. Account `71a8e70b7b1e301fca750fd6c6ae1f1d`, Pages project `subs-demo`, main `328902e`, and deployment `b2da0cfb` returning HTTP 200 were verified. The preceding MCP errors and old-Worker state are historical, not current blockers. +- Registered `subs.ajnart.dev` as a Pages domain (ID prefix `9dfced2f`), detached only its old Worker custom-domain binding (ID prefix `3a37d7`), and created the CNAME (record ID prefix `4877c624`) to `subs-demo.pages.dev`, proxied with TTL 1. Unrelated Worker resources were not removed. +- https://subs.ajnart.dev is live with a valid certificate. HTML, favicon, JS, CSS, and adapter bytes match the tested build. The live browser showed nine cards, no PIN, and zero API requests; adding two plans priced at zero and 12.34 produced eleven cards and persisted after reload. +- The earlier 17:46 pending-validation snapshot is superseded: Pages domain status, verification and validation are all active; canonical HTTPS and the published artifact are verified. +- Repository Actions secrets remain `[]`. Manual Pages publication is verified; automated Pages CI remains blocked on the scoped token. Publish the requested `v3.0.0` against the exact merged commit after the final PR merges, without claiming automatic deployment. diff --git a/.scratch/rewrite/spec.md b/.scratch/rewrite/spec.md index 4530539..ff5aa9a 100644 --- a/.scratch/rewrite/spec.md +++ b/.scratch/rewrite/spec.md @@ -80,7 +80,7 @@ Replace the running application with a responsive, service-centered Subs experie 66. As a user, I want the previous interactive link-preview experience restored, so that I can inspect a public Service link on demand. 67. As a visitor, I want a working public demo without a PIN or backend, so that I can try Subs immediately. 68. As a demo user, I want local edits, import/export, and an explicit reset, so that I can explore without affecting another visitor or private Installation. -69. As an Operator, I want the static demo deployed automatically to Cloudflare Pages with Wrangler at sub.ajnart.dev, retaining subs.ajnart.dev as a compatibility alias, so that the public version follows successful release builds. +69. As an Operator, I want the static demo deployed automatically to Cloudflare Pages with Wrangler at subs.ajnart.dev as its only canonical hostname, so that the public version follows successful release builds. 70. As a contributor, I want current application screenshots and a short README, so that setup and the product are clear without excessive documentation. ## Implementation Decisions @@ -136,7 +136,7 @@ Replace the running application with a responsive, service-centered Subs experie - Restore lazy, user-activated link previews for safe public HTTP(S) URLs. Never request previews on page mount, preview local/private addresses, or add server-side arbitrary URL fetching. - The static demo reuses the app UI with isolated browser persistence and clearly identified sample data. No API, database, PIN, or live exchange-rate service is required. Demo rates are explicitly illustrative, not current market rates. - Private Docker installations still start empty with authentication enabled. Demo flags must not change the private runtime's defaults or include server modules and secrets in static assets. -- Build and validate both targets. Deploy the static artifact to Cloudflare Pages using Wrangler at sub.ajnart.dev after successful checks, retaining subs.ajnart.dev as a compatibility alias after primary-domain verification; do not make ordinary local builds or Docker builds publish remotely. Keep automated deployment credentials scoped and outside the repository. Pages serves no backend, Functions or PIN challenge; private Docker installations retain PIN protection by default. +- Build and validate both targets. Deploy the static artifact to Cloudflare Pages using Wrangler at subs.ajnart.dev as its only canonical hostname after successful checks; limit custom-domain cutover changes to its old Worker binding and Pages/DNS records. Distinguish verified HTTPS serving from Pages control-plane validation. Do not make ordinary local builds or Docker builds publish remotely. Keep automated deployment credentials scoped and outside the repository. Pages serves no backend, Functions or PIN challenge; private Docker installations retain PIN protection by default. - Refresh real application screenshots and keep the public README short. Detailed release evidence belongs in these internal tickets rather than lengthy product copy. ## Testing Decisions @@ -160,4 +160,6 @@ Replace the running application with a responsive, service-centered Subs experie This document specifies the target release; ready-for-agent is triage readiness, not evidence anything has shipped. Completion and deferral evidence belong in the execution map and individual tickets. Exploratory candidates such as provider price monitoring, notifications, offline writes, multi-Collection support, or a future FX feed remain proposals requiring a separate decision and do not appear as functioning controls or release promises. +The Pages demo is live at https://subs.ajnart.dev with verified HTTPS, matching build assets, no PIN or API requests, and batch persistence after reload. MCP authentication works. Pages domain status, verification and validation are all active, superseding the earlier 17:46 pending snapshot. Manual publication is verified, while automated Pages deployment remains blocked by the absent scoped Actions token. The requested `v3.0.0` publication follows the final PR merge. + The authoritative supporting sources are TanStack Start's official overview and hosting guidance, Nitro's current v3 documentation, shadcn's official TanStack installation guide, and the supplied Bold Wikipedia registry theme. Source links, repository-local skill provenance, and restore instructions are maintained in the agent documentation. diff --git a/.scratch/v3-release/notes.md b/.scratch/v3-release/notes.md index 2889f36..e655124 100644 --- a/.scratch/v3-release/notes.md +++ b/.scratch/v3-release/notes.md @@ -1,9 +1,7 @@ -## Subs v3.0.0 (draft) +## Subs v3.0.0 A new private Collection runtime, a simpler subscription-first home, and a browser-only public demo. -Subs 2 is already released; this is the next major version. v3 publication and the Pages custom-domain cutover are pending final verification. - ### Highlights - Home opens directly to your subscriptions. Collection tools reveals totals, filters, sorting, table layout, bulk actions and upcoming renewals when needed. @@ -18,11 +16,11 @@ See the [feature overview, shortcuts, and limits](https://github.com/ajnart/subs ### Demo and deployment -The primary demo target is [sub.ajnart.dev](https://sub.ajnart.dev), with [subs.ajnart.dev](https://subs.ajnart.dev) intended to remain a compatibility alias after verified cutover. Pages publication and custom-domain HTTPS are not yet verified. Browser data is separate for each hostname; export/import a backup to move demo edits between them. +Try the verified Cloudflare Pages demo at [subs.ajnart.dev](https://subs.ajnart.dev), its only canonical hostname. HTTPS and published assets match the tested build; the demo opens without a PIN or backend requests, and batch creation and persistence after reload are verified. Browser data is separate for each hostname; export/import a backup to move demo edits. -This PIN-free demo is a separate `DEMO_MODE` browser build, not a private installation with `DISABLE_AUTH`. `bun run deploy:demo` builds `dist/demo` and uses `wrangler pages deploy --branch main`; it needs no Pages Functions, backend, or bindings. Ordinary local and Docker builds never publish. +This PIN-free demo is a separate `DEMO_MODE` browser build, not a private installation with `DISABLE_AUTH`. It needs no Pages Functions, backend, or bindings. Ordinary local and Docker builds never publish. -The Checks workflow gates `main`/manual Pages deployments on application and Docker checks. Automatic deployment remains blocked: the `CLOUDFLARE_API_TOKEN` Actions secret was absent at release preflight. Missing credentials fail explicitly before publishing. CI needs **Account → Cloudflare Pages → Edit** permission scoped to the configured account; local OAuth is not a CI credential. +Manual Pages publication is verified. Automated Pages deployment remains blocked because repository Actions secrets are empty; CI requires a scoped `CLOUDFLARE_API_TOKEN` with **Account → Cloudflare Pages → Edit** permission. Working local OAuth or MCP authentication does not supply that CI credential. ### Upgrade from Subs 2 diff --git a/.scratch/v3-release/spec.md b/.scratch/v3-release/spec.md index ed64683..3ba2f08 100644 --- a/.scratch/v3-release/spec.md +++ b/.scratch/v3-release/spec.md @@ -6,20 +6,24 @@ Type: task ## Outcome -Publish the completed improvements as `v3.0.0`, validate the static demo on Cloudflare Pages using Wrangler, and make `https://sub.ajnart.dev` its primary address. Stop obsolete Vercel Git deployments. `v2.0.0` already exists; do not overwrite it. +Publish the completed improvements as `v3.0.0`, validate the static demo on Cloudflare Pages using Wrangler, and make `https://subs.ajnart.dev` its only canonical address. Stop obsolete Vercel Git deployments. `v2.0.0` already exists; do not overwrite it. ## Constraints - Preserve the accepted simple home, wider dialogs, atomic multi-service setup, safe custom icons, keyboard interactions and authoritative theme. - Keep the private PIN-protected, single-container SQLite target separate from the PIN-free browser-only DEMO_MODE build. Publish only static assets to Cloudflare Pages, without Pages Functions, a Worker application, API, database or server bindings. Ordinary local and Docker builds never publish. -- Retain `subs.ajnart.dev` as a compatibility alias after the primary Pages domain is verified; document the singular hostname as primary. Browser storage is origin-specific and is not silently transferred between hostnames. Do not interrupt the old alias before the new primary works or claim custom-domain completion while DNS/certificates remain pending. +- Use only `subs.ajnart.dev` as the canonical Pages domain; the singular hostname is not a target or alias. Browser storage is origin-specific and is not silently transferred between hostnames. Limit the cutover to this domain's old Worker binding and Pages/DNS records; preserve unrelated resources. Verify both live HTTPS and Pages control-plane activation. - Preserve `vercel.json` with Git deployments disabled and bring it to main through PR #50. Do not delete the external Vercel project or unrelated integrations. - Use only legitimately authorized Cloudflare credentials for the configured account/Worker. Local OAuth may deploy locally; CI requires a separate scoped `CLOUDFLARE_API_TOKEN` secret. Never print, commit or copy broad credentials into CI. - Verify lint/typecheck, all existing regressions, both release builds, Pages static serving and real-browser demo flows with no backend requests or PIN. Validate Docker health, protection and SQLite persistence on amd64 and arm64; ensure the build-stage platform optimization copies no build-host-native runtime dependencies. Add no speculative unit-test files or dependencies. - Keep supported feature documentation concise in README and Markdown under docs, with no docs website. Explicitly separate private Installation protection from the public demo and describe limitations honestly. - Push conventional commits through the existing feature PR, await fresh CI, and merge through GitHub. No direct push to main, force push, retagging or destructive Git operations. -- Publish the major release against the exact merged commit after live HTTPS/asset/demo verification. Watch workflows to completion and report credential or external-access blockers honestly. +- Publish the major release against the exact merged commit after the final PR merges and live HTTPS/asset/demo verification. Watch workflows to completion and report credential or external-access blockers honestly. The missing Pages CI credential blocks automation, not the verified manual publication or the user's requested release after merge. ## Completion evidence PR #50 merged the accepted feature tree into main at `63dbaaf3cc8ff55c15e83742fbc2de07031fb63c`. The subsequent user request selects Pages and full Docker validation; this follow-up proceeds through its own focused PR before the final release. Accepted feature evidence is `.scratch/quick-setup/validation.md` and `.scratch/simple-home/validation.md`; release evidence is recorded alongside this specification and appended publicly to the PR/release after publication. Automatic deployment remains tracked by `.scratch/rewrite/issues/27-demo-deployment.md` until its credential path is proven. + +Latest correction: the user selected only `subs.ajnart.dev`, not the singular hostname. Main `328902e` is deployed at https://subs-demo.pages.dev (deployment https://b2da0cfb.subs-demo.pages.dev), with nine cards, no PIN or API requests, batch creation, persistence, and reset verified. Main multiarch GHCR publication succeeded in 2m9s; all 27 existing tests, both builds, lint, and typecheck passed. + +Cloudflare MCP authentication works for account `71a8e70b7b1e301fca750fd6c6ae1f1d`. Only the old Worker domain binding was detached; proxied CNAME `subs.ajnart.dev` now points to `subs-demo.pages.dev`, TTL 1. Pages domain status, verification and validation are all active, superseding the earlier 17:46 pending snapshot. Valid canonical HTTPS and HTML/favicon/JS/CSS/adapter bytes match the tested build. Live batch prices zero and 12.34, reload persistence, real export/import/reset, no PIN or API requests and mobile fit are verified. Repository Actions secrets remain empty; automatic Pages deployment is independently blocked by the scoped token. Publish `v3.0.0` after the final PR merges, as requested. diff --git a/.scratch/v3-release/validation.md b/.scratch/v3-release/validation.md index cc133c2..a380a9f 100644 --- a/.scratch/v3-release/validation.md +++ b/.scratch/v3-release/validation.md @@ -46,3 +46,16 @@ Remote CI, live domain attachment and release publication remain pending. Earlie - Both ARM64 and AMD64 images build successfully with the native build-stage fix. On each architecture: health 200, anonymous Collection read 401, native target Bun/SQLite available, a 12.34-price record and session persist through restart and container replacement with the same volume. All 90 runtime artifact files were inspected by path, with no native extensions or executable/bin payloads; both real architecture runtimes execute the portable server successfully. - Pages local serving verifies nine sample cards with no PIN; zero-cost batch saves survive reload, reset returns nine samples, API requests are blocked and none captured. Mobile 390px has no overflow. An initial browser probe reloaded before save acknowledgement; repeating with the committed-save condition passes. - `sub.ajnart.dev` is registered on Pages but pending DNS verification. Local OAuth cannot edit DNS and the dashboard is signed out. The Operator was asked to add CNAME `sub` → `subs-demo.pages.dev` and a scoped Pages Edit Actions token, without sharing secrets in chat. The old plural Worker domain is not detached while primary verification is pending. + +### Canonical Pages cutover + +The user clarified that only `subs.ajnart.dev` is intended; the singular hostname is not a target or alias. Renewed Cloudflare MCP access now reaches the correct account and zone. The earlier authentication/DNS blockers above are historical and resolved. + +- Verified Pages project `subs-demo` production branch main, deployment `b2da0cfb-a282-445e-84bd-27bfa467bb4a` from merged `328902e7b166337a2978d35871a4512627e78a16`, before touching the existing hostname. +- Registered `subs.ajnart.dev` on Pages, detached only the old Worker custom-domain binding, then created proxied CNAME `subs.ajnart.dev` → `subs-demo.pages.dev`, TTL 1. No Worker project or unrelated DNS record was deleted. +- Pages now reports domain, verification and validation all `active`. Valid-certificate HTTPS returns 200. HTML, favicon, entry JS/CSS and browser adapter match the tested artifact byte for byte. +- Live canonical browser: nine sample cards, no PIN fields and zero `/api/` resources; two-plan batch saves zero and 12.34 prices, eleven cards survive reload. Real downloaded JSON contains eleven records; reset restores nine, import preview reports nine duplicates, explicit confirmation imports two, and final reset restores nine. No page errors; mobile 390px has no horizontal overflow. Automation was synchronized with completed navigation/save acknowledgements rather than transient intermediate views. +- Removed only the unused singular Pages registration after canonical verification; no singular DNS record was created. +- Both focused Pages follow-up PR workflows passed; PR #51 is merged. Main multi-platform image publication succeeded in 2m9s, replacing the stalled emulated build. Main application and Docker checks pass; automatic Pages upload still fails only because the scoped Actions secret is absent. + +The final hostname/documentation commit and v3 release will record their workflow and publication links in the final PR/release evidence. Live domain completion does not imply CI credentials were installed. diff --git a/README.md b/README.md index 1b44367..5f70d0c 100644 --- a/README.md +++ b/README.md @@ -2,7 +2,7 @@ Track subscriptions, renewals, and recurring costs. -[Try the demo](https://sub.ajnart.dev) · [Self-host](#docker) +[Try the demo](https://subs.ajnart.dev) · [Self-host](#docker) ![Subs overview](docs/screenshots/overview-dark.png) @@ -79,9 +79,9 @@ Preview the built static site with Wrangler Pages at http://127.0.0.1:4174. Use `bun run deploy:demo` builds the demo and directly uploads `dist/demo` to Cloudflare Pages with `--branch main`. Root `wrangler.jsonc` sets `pages_build_output_dir`; there are no Pages Functions, backend, or bindings. Ordinary local and Docker builds never publish. -`sub.ajnart.dev` is the primary target, with `subs.ajnart.dev` intended to remain a compatibility alias. The Pages custom-domain cutover is pending live verification. Browser data is separate for each hostname; export/import a backup to move demo edits. +The Cloudflare Pages demo is live at [subs.ajnart.dev](https://subs.ajnart.dev), its only canonical hostname, with verified HTTPS and no PIN or backend. It is also available at [subs-demo.pages.dev](https://subs-demo.pages.dev). Browser data is separate for each hostname; export/import a backup to move demo edits. -The Checks workflow gates `main` and explicit manual Pages deployments on application and Docker checks. It requires a `CLOUDFLARE_API_TOKEN` Actions secret scoped to the configured account with **Account → Cloudflare Pages → Edit** permission. That secret was absent at release preflight: automatic deployment remains blocked, and missing credentials fail before publishing. Local Wrangler OAuth does not enable CI deployment. +The Checks workflow gates `main` and explicit manual Pages deployments on application and Docker checks. It requires a `CLOUDFLARE_API_TOKEN` Actions secret scoped to the configured account with **Account → Cloudflare Pages → Edit** permission. Manual Pages publication is verified, but repository Actions secrets remain empty: automatic deployment is blocked, and missing credentials fail before publishing. Local Wrangler OAuth and authenticated MCP access do not enable CI deployment. ## Configuration diff --git a/docs/agents/architecture.md b/docs/agents/architecture.md index e0f83e2..428b79f 100644 --- a/docs/agents/architecture.md +++ b/docs/agents/architecture.md @@ -44,9 +44,11 @@ The separate `vite.demo.config.ts` builds `demo/main.tsx` with React and Tailwin `bun run deploy:demo` first builds the browser demo, then uses `wrangler pages deploy --branch main` for direct upload to the `subs-demo` Pages project. Default root `wrangler.jsonc` selects the project and `pages_build_output_dir: ./dist/demo`; the deploy script pins the account through `CLOUDFLARE_ACCOUNT_ID`. Explicit `main` targets production rather than inferring a local feature branch. The demo has no Pages Functions, Worker entrypoint, backend, or bindings. Do not carry over Worker `assets`, `routes`, `workers_dev`, `preview_urls`, or custom `build`/`main` fields. -`sub.ajnart.dev` is the primary Pages target; retain `subs.ajnart.dev` as a compatibility alias only through a verified cutover. Attach custom domains to the Pages project and configure DNS for its actual returned `pages.dev` hostname, not Worker routes or an assumed project subdomain. Preserve the old plural deployment until primary HTTPS is proven. Pages/domain publication is pending live verification; configuration alone is not evidence of a working hostname. Browser data remains isolated per hostname. +`subs.ajnart.dev` is the only canonical Pages hostname; the singular hostname is not a target or alias. The verified Pages deployment of main `328902e` is live at https://subs.ajnart.dev and https://subs-demo.pages.dev (deployment https://b2da0cfb.subs-demo.pages.dev). The domain is registered on `subs-demo`; only its old Worker custom-domain binding was detached, and a proxied CNAME now targets `subs-demo.pages.dev` with TTL 1. Canonical HTTPS has a valid certificate; HTML, favicon, JS, CSS, and adapter bytes match the tested build. Browser verification confirmed nine cards, no PIN or API requests, and a two-plan batch priced at zero and 12.34 that produced eleven cards and persisted after reload. Browser data remains isolated per hostname. -The Checks workflow gates Pages direct upload on both application checks and Docker validation, for `main` or an explicit manual request. CI requires a scoped `CLOUDFLARE_API_TOKEN` secret with **Account → Cloudflare Pages → Edit** for the configured account. The last main run stopped at the missing-token preflight before any deployment; automatic publication remains blocked until a credentialed Actions run succeeds. Local Wrangler OAuth is not a durable CI credential. +The Checks workflow gates Pages direct upload on both application checks and Docker validation, for `main` or an explicit manual request. CI requires a scoped `CLOUDFLARE_API_TOKEN` secret with **Account → Cloudflare Pages → Edit** for the configured account. Manual Pages publication is verified, but repository Actions secrets remain `[]`; automatic publication is blocked until a credentialed Actions run succeeds. Local Wrangler OAuth and authenticated MCP access are not durable CI credentials. + +Cloudflare MCP authentication works for the configured account. Pages reports `subs.ajnart.dev` active, with verification and validation both active. The unused singular-domain registration was removed after the canonical hostname passed verification. `vercel.json` disables the legacy Vercel Git auto-deployment: neither the persistent Bun/SQLite installation nor the Cloudflare demo targets Vercel. The external project is not deleted. Demo development keeps Vite filesystem restrictions enabled and adds only the resolved font package directory alongside the workspace, so linked Bun installs can serve their fonts without exposing the entire package cache. diff --git a/docs/features.md b/docs/features.md index 0b2e62c..b02d3a9 100644 --- a/docs/features.md +++ b/docs/features.md @@ -37,6 +37,6 @@ The speaker button controls TIKS interaction sounds on this device. **Settings ## Private installation and public demo - **Private:** one Bun Docker process and writable SQLite volume, initially empty and protected by a six-digit PIN. An Operator setup token authorizes first-use PIN setup; the same private Collection is available across devices. Use HTTPS and protect full-volume snapshots for complete recovery. -- **Demo:** a separate browser-only `DEMO_MODE` build targeting [sub.ajnart.dev](https://sub.ajnart.dev), with sample data, illustrative rates, local edits/import/export/reset, and no backend or PIN. This is not private-server `DISABLE_AUTH`; browser data is isolated by hostname and is not synced between devices. The Pages domain cutover is still pending live verification. +- **Demo:** a separate browser-only `DEMO_MODE` build live on Cloudflare Pages at [subs.ajnart.dev](https://subs.ajnart.dev), its only canonical hostname, with verified HTTPS, sample data, illustrative rates, local edits/import/export/reset, and no backend or PIN. This is not private-server `DISABLE_AUTH`; browser data is isolated by hostname and is not synced between devices. It is also available at [subs-demo.pages.dev](https://subs-demo.pages.dev). Subs does not connect to banks, execute payments or provider cancellations, monitor provider pricing, or provide background sync/closed-browser alarms.