> 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/phase33-session02-freeze-public-fixtures/tasks.md). # Task Checklist **Session ID**: `phase33-session02-freeze-public-fixtures` **Total Tasks**: 18 **Estimated Duration**: 3-4 hours **Created**: 2026-06-25 *** Legend: `[x]` completed; `[ ]` pending; `[P]` parallelizable; `[SNNMM]` session ref; `TNNN` task ID. *** ## Progress Summary | Metric | Value | | --------------- | ------- | | Tasks Completed | 18 / 18 | | Tasks Remaining | 0 | | Last Completed | T018 | *** ## Setup (3 tasks) * [x] T001 \[S3302] Verify Phase 33 Session 02 prerequisites, Session 01 completion evidence, and static fixture boundary (`.spec_system/PRD/phase_33/session_02_freeze_public_fixtures.md`) * [x] T002 \[S3302] Create implementation notes sections for commands, input counts, dry-run results, fixture writes, output counts, privacy scans, caveats, and static-boundary evidence (`.spec_system/specs/phase33-session02-freeze-public-fixtures/implementation-notes.md`) * [x] T003 \[S3302] Verify snapshot, build, and scan command separation before fixture work (`package.json`) *** ## Foundation (4 tasks) * [x] T004 \[S3302] Record selected local input counts for Trend Finder, Engine Replay, advanced artifacts, and Dream without copying raw payload bodies (`src/data/live-data.json`) * [x] T005 \[S3302] Record current committed public snapshot counts and existing gaps for Trend Finder, Engine Replay, advanced artifacts, and Dream (`demo-website/public/demo/live-data.snapshot.json`) * [x] T006 \[S3302] Add minimal manifest count summary and Dream field policy metadata with schema-valid values and privacy-scan-safe labels (`scripts/lib/pages-demo-snapshot.ts`) * [x] T007 \[S3302] Update focused snapshot exporter tests for deterministic manifest metadata, count summary, Dream field policy, and expected write targets (`scripts/lib/__tests__/pages-demo-snapshot.test.ts`) *** ## Implementation (6 tasks) * [x] T008 \[S3302] Run the focused snapshot exporter test file before fixture writes and record the result (`scripts/lib/__tests__/pages-demo-snapshot.test.ts`) * [x] T009 \[S3302] Run `bun run demo:snapshot --dry-run --json` against the selected local input with scan and input-source results recorded (`scripts/demo/export-pages-snapshot.ts`) * [x] T010 \[S3302] Compare dry-run projected data counts against selected input counts using structured inspection and record expected pre-hardening gaps (`scripts/lib/pages-demo-snapshot.ts`) * [x] T011 \[S3302] Run `bun run demo:snapshot` to write only the allowed committed fixture files with dry-run evidence and atomic-write failure handling (`scripts/demo/export-pages-snapshot.ts`) * [x] T012 \[S3302] Review generated `live-data.snapshot.json` for populated Trend Finder data, Dream branch state, provenance labels, and count deltas without raw private payload bodies (`demo-website/public/demo/live-data.snapshot.json`) * [x] T013 \[S3302] Review generated snapshot metadata and manifest for source commit, captured timestamp, route coverage, redaction counts, scan status, count summary, field policies, and no extra committed manifests (`demo-website/snapshot-manifest.json`) *** ## Testing (5 tasks) * [x] T014 \[S3302] Run committed-fixture privacy scan and record scanned file counts and issue count (`scripts/demo/scan-pages-demo.ts`) * [x] T015 \[S3302] Run focused snapshot and fixture privacy tests after generated fixture writes (`scripts/lib/__tests__/pages-demo-privacy-scan.test.ts`) * [x] T016 \[S3302] Confirm Pages build assembly still requires committed fixtures and does not call snapshot authoring, collectors, schedulers, local bridge reads, Dream runtime, uploads, or admin mutations (`scripts/lib/pages-demo-build.ts`) * [x] T017 \[S3302] Validate generated fixture JSON parsing, ASCII encoding, and LF line endings for all touched fixture and session artifacts (`demo-website/public/demo`) * [x] T018 \[S3302] Finalize implementation notes with changed-file list, command outcomes, count deltas, projection caveats, and handoff notes for Sessions 03 and 04 (`.spec_system/specs/phase33-session02-freeze-public-fixtures/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 start the creview -> validate sequence *** ## Next Steps Run the `implement` 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/phase33-session02-freeze-public-fixtures/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.