> For the complete documentation index, see [llms.txt](https://ai-os-and-trend-finder.gitbook.io/ai-os-and-trend-finder-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://ai-os-and-trend-finder.gitbook.io/ai-os-and-trend-finder-docs/.spec_system/archive/sessions/phase31-session07-release-polish-and-documentation/tasks.md). # Task Checklist **Session ID**: `phase31-session07-release-polish-and-documentation` **Total Tasks**: 18 **Estimated Duration**: 3-4 hours **Created**: 2026-06-24 *** ## Progress Summary | Metric | Value | | --------------- | ---------------- | | Tasks Completed | 18 / 18 | | Remaining Tasks | 0 | | Last Updated | 2026-06-24 15:11 | *** Legend: `[x]` completed; `[ ]` pending; `[P]` parallelizable; `[SNNMM]` session ref; `TNNN` task ID. *** ## Setup (3 tasks) * [x] T001 \[S3107] Verify Phase 31 Session 07 prerequisites, Session 06 validation evidence, and release-polish scope (`.spec_system/PRD/phase_31/session_07_release_polish_and_documentation.md`, `.spec_system/specs/phase31-session06-demo-qa-and-privacy-verification/validation.md`) * [x] T002 \[S3107] Reconcile current route matrix with committed snapshot metadata route coverage (`scripts/lib/pages-demo-routes.ts`, `demo-website/public/demo/snapshot-metadata.json`) * [x] T003 \[S3107] Verify Pages build, scan, preview, budget, and direct-upload command baselines before changing scripts (`package.json`, `scripts/check-bundle-budget.sh`, `demo-website/README.md`) *** ## Foundation (5 tasks) * [x] T004 \[S3107] Create public demo metadata parser and fetch view model with explicit loading, empty, error, and offline states (`src/lib/public-demo-metadata.ts`) * [x] T005 \[S3107] Create reusable public demo provenance UI with product-facing copy, accessible labels, and responsive compact states (`src/components/public-demo-provenance.tsx`) * [x] T006 \[S3107] \[P] Add unit coverage for public demo metadata and provenance rendering states (`src/components/__tests__/public-demo-provenance.test.tsx`) * [x] T007 \[S3107] Make the bundle budget checker accept a configurable asset directory and add a Pages budget script (`scripts/check-bundle-budget.sh`, `package.json`) * [x] T008 \[S3107] \[P] Add direct-upload command modeling with project-name validation and explicit error mapping (`scripts/lib/pages-demo-deploy.ts`, `scripts/demo/deploy-pages-demo.ts`, `scripts/lib/__tests__/pages-demo-deploy.test.ts`) *** ## Implementation (5 tasks) * [x] T009 \[S3107] Wire the provenance component into the app top bar without crowding mobile or weakening Trend Finder route state (`src/routes/__root.tsx`) * [x] T010 \[S3107] Tune public-demo unavailable copy for local refresh, setup, agent status, Knowledge Graph, Trend Finder, scheduler, source setup, and AI Rogue states (`src/lib/public-demo.ts`) * [x] T011 \[S3107] Refresh public snapshot content, manifest, and metadata route coverage through the browser-safe projection boundary (`scripts/lib/pages-demo-snapshot.ts`, `demo-website/public/demo/live-data.snapshot.json`, `demo-website/public/demo/snapshot-metadata.json`, `demo-website/snapshot-manifest.json`) * [x] T012 \[S3107] Apply responsive public-demo polish for route matrix surfaces with platform-appropriate accessibility labels, focus management, and input support (`src/routes/__root.tsx`, `src/styles.css`, `scripts/lib/pages-demo-routes.ts`) * [x] T013 \[S3107] Update Pages deployment docs, demo README, changelog, and release gate notes with Workers/Pages separation preserved (`docs/deployment.md`, `demo-website/README.md`, `docs/CHANGELOG.md`, `.spec_system/specs/phase31-session07-release-polish-and-documentation/implementation-notes.md`) *** ## Testing (5 tasks) * [x] T014 \[S3107] Add mobile Pages route smoke coverage with no `/__*` request assertion and document-overflow checks (`tests/e2e/pages-demo-mobile.spec.ts`) * [x] T015 \[S3107] Extend static route smoke checks to assert visible provenance while preserving product-surface and no-bridge assertions (`tests/e2e/pages-demo-routes.spec.ts`, `scripts/lib/pages-demo-routes.ts`) * [x] T016 \[S3107] Run focused unit suites for metadata, provenance, budget, deploy helper, snapshot, and route behavior (`src/components/__tests__/public-demo-provenance.test.tsx`, `scripts/lib/__tests__/pages-demo-deploy.test.ts`, `scripts/lib/__tests__/pages-demo-snapshot.test.ts`, `scripts/lib/__tests__/pages-demo-routes.test.ts`) * [x] T017 \[S3107] Run required automated release checks (`bun run typecheck`, `bun run typecheck:scripts`, `bun run lint`, `bun run demo:build:pages`, `bun run demo:scan:pages`, `bun run demo:budget:pages`) * [x] T018 \[S3107] Run static preview desktop/mobile smoke, verify direct-upload helper or documented project-name constraint, validate ASCII/LF, and record bundled release gate evidence (`tests/e2e/pages-demo-routes.spec.ts`, `tests/e2e/pages-demo-mobile.spec.ts`, `.spec_system/specs/phase31-session07-release-polish-and-documentation/implementation-notes.md`) *** ## Completion Checklist * [x] All tasks marked `[x]` * [x] All tests and checks passing * [x] All files ASCII-encoded with LF line endings * [x] implementation-notes.md updated * [x] Ready for `creview` to continue the implement -> creview -> validate sequence *** ## Next Steps Run the `creview` workflow step. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://ai-os-and-trend-finder.gitbook.io/ai-os-and-trend-finder-docs/.spec_system/archive/sessions/phase31-session07-release-polish-and-documentation/tasks.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.