Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion .github/workflows/ci.yml
Original file line number Diff line number Diff line change
Expand Up @@ -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
Expand Down
16 changes: 15 additions & 1 deletion .scratch/rewrite/issues/27-demo-deployment.md
Original file line number Diff line number Diff line change
Expand Up @@ -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

Expand All @@ -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.
Expand All @@ -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.
15 changes: 15 additions & 0 deletions .scratch/rewrite/map.md
Original file line number Diff line number Diff line change
Expand Up @@ -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

Expand Down Expand Up @@ -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.
6 changes: 4 additions & 2 deletions .scratch/rewrite/spec.md
Original file line number Diff line number Diff line change
Expand Up @@ -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
Expand Down Expand Up @@ -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
Expand All @@ -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.
10 changes: 4 additions & 6 deletions .scratch/v3-release/notes.md
Original file line number Diff line number Diff line change
@@ -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.
Expand All @@ -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

Expand Down
Loading
Loading