> 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-session06-scan-build-and-deploy/tasks.md).

# Task Checklist

**Session ID**: `phase33-session06-scan-build-and-deploy` **Total Tasks**: 19 **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 | 19 / 19  |
| Current Task    | Complete |
| Blockers        | 0        |

***

## Setup (3 tasks)

* [x] T001 \[S3306] Verify Phase 33 Session 01 through Session 05 validation evidence and Session 06 release-gate scope (`.spec_system/PRD/phase_33/session_06_scan_build_and_deploy.md`)
* [x] T002 \[S3306] Create implementation notes for command evidence, fixture deltas, scan results, build output, budget totals, route smoke, deploy dry-run, and caveats (`.spec_system/specs/phase33-session06-scan-build-and-deploy/implementation-notes.md`)
* [x] T003 \[S3306] Verify Cloudflare deploy prerequisites by checking project-name handling and local env-var presence without printing secret values (`scripts/lib/pages-demo-deploy.ts`)

***

## Foundation (4 tasks)

* [x] T004 \[S3306] Run `bun run demo:snapshot --dry-run --json` and record source commit, capture metadata, input sources, redaction counts, route coverage, and scan status (`scripts/demo/export-pages-snapshot.ts`)
* [x] T005 \[S3306] Review current committed public fixtures and manifest before final writes for Trend Finder, Dream Review, graph fixtures, route coverage, and private-data absence (`demo-website/public/demo/live-data.snapshot.json`)
* [x] T006 \[S3306] Run `bun run demo:snapshot` after dry-run review to refresh or confirm committed public fixtures with atomic-write behavior (`demo-website/public/demo/live-data.snapshot.json`)
* [x] T007 \[S3306] Review generated snapshot metadata and manifest after final snapshot for source commit, captured timestamp, redaction counts, count summaries, field policies, and route coverage (`demo-website/snapshot-manifest.json`)

***

## Implementation (7 tasks)

* [x] T008 \[S3306] Run `bun run demo:build:pages` and verify the required static Pages output files are assembled from committed fixtures (`demo-website/dist/index.html`)
* [x] T009 \[S3306] Verify generated Pages output has `_headers`, `_redirects`, `/demo/*` fixtures, no top-level `404.html`, no `_worker.js`, and no Pages Functions entrypoint (`demo-website/dist`)
* [x] T010 \[S3306] \[P] Run `bun run demo:scan:pages` against committed fixtures and generated dist and record scanned file counts plus issue count (`scripts/demo/scan-pages-demo.ts`)
* [x] T011 \[S3306] \[P] Run `bun run demo:budget:pages` and record Pages JS/CSS budget totals against `demo-website/dist/assets` (`scripts/check-bundle-budget.sh`)
* [x] T012 \[S3306] \[P] Run focused unit tests for snapshot, privacy scan, build, deploy helper, route matrix, public demo copy, endpoint selection, Trend Finder public demo states, Engine Replay, Dream transforms, and Dream public-demo controls (`scripts/lib/__tests__/pages-demo-snapshot.test.ts`)
* [x] T013 \[S3306] Serve `demo-website/dist` through Wrangler Pages dev and run desktop/mobile Pages route smoke with no `/__*` bridge requests (`tests/e2e/pages-demo-routes.spec.ts`)
* [x] T014 \[S3306] Spot-check static preview HTTP status and product surfaces for `/`, Trend Finder Trends, Engine Replay, Hidden Gems, Sources, Watchlist, and Brief (`.spec_system/specs/phase33-session06-scan-build-and-deploy/deployment-verification.md`)

***

## Testing (5 tasks)

* [x] T015 \[S3306] Run deploy dry-run with the real operator-supplied project name and `--branch main`, then record the reviewed Wrangler command without secret values (`scripts/demo/deploy-pages-demo.ts`)
* [x] T016 \[S3306] Run deploy execute with the same real project name and `--branch main --execute` when Cloudflare env vars are available locally, with command exit status recorded (`scripts/demo/deploy-pages-demo.ts`)
* [x] T017 \[S3306] Verify hosted route HTTP status, no local bridge or mutation requests, final Pages URL, branch, and source commit when upload execution succeeds (`.spec_system/specs/phase33-session06-scan-build-and-deploy/deployment-verification.md`)
* [x] T018 \[S3306] Run final JSON parse, ASCII, LF, and privacy string spot-checks over changed fixtures, generated dist evidence, and session artifacts (`demo-website/public/demo`)
* [x] T019 \[S3306] Finalize implementation notes with changed-file list, command outcomes, deploy status, manual review findings, static-only boundary evidence, and handoff notes (`.spec_system/specs/phase33-session06-scan-build-and-deploy/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] deployment-verification.md updated
* [x] Ready for `creview` to review and repair uncommitted release-gate changes

***

## 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-session06-scan-build-and-deploy/tasks.md?ask=<question>&goal=<endgoal>
```

`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.