> For the complete documentation index, see [llms.txt](https://faction-os.gitbook.io/faction-os-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://faction-os.gitbook.io/faction-os-docs/.spec_system/archive/sessions/phase02-session07-product-surface-validation-and-documentation-closeout/tasks.md). # Task Checklist **Session ID**: `phase02-session07-product-surface-validation-and-documentation-closeout` **Total Tasks**: 18 **Estimated Duration**: 3-4 hours **Created**: 2026-05-29 *** ## Legend * `[x]` = Completed * `[ ]` = Pending * `[P]` = Parallelizable (can run with other \[P] tasks) * `[SNNMM]` = Session reference (NN=phase number, MM=session number) * `TNNN` = Task ID *** ## Progress Summary | Category | Total | Done | Remaining | | -------------- | ------ | ------ | --------- | | Setup | 3 | 3 | 0 | | Foundation | 4 | 4 | 0 | | Implementation | 7 | 7 | 0 | | Testing | 4 | 4 | 0 | | **Total** | **18** | **18** | **0** | *** ## Setup (3 tasks) Initial verification and evidence plan. ### Cross-cutting * [x] T001 \[S0207] Verify Sessions 01-06 prerequisites, Session 07 gap-matrix rows, and current browser validation coverage (`.spec_system/PRD/phase_02/session_07_product_surface_validation_and_documentation_closeout.md`) * [x] T002 \[S0207] Create implementation notes with baseline commands, browser evidence plan, quality gate list, blocker policy, and remaining-gap template (`.spec_system/specs/phase02-session07-product-surface-validation-and-documentation-closeout/implementation-notes.md`) * [x] T003 \[S0207] Audit stable README and docs before validation for shipped, deferred, excluded, and evidence-only language (`README.md`, `docs/README_docs.md`, `docs/ARCHITECTURE.md`, `docs/privacy-and-security.md`, `docs/release.md`) *** ## Foundation (4 tasks) Browser and documentation closeout foundations. ### tests/e2e * [x] T004 \[S0207] \[P] Review app e2e coverage and extend only if needed for screenshot evidence, console/page-error guards, failed request checks, battlefield dimensions, and fallback states with explicit loading, empty, error, and offline states (`tests/e2e/app.e2e.ts`) * [x] T005 \[S0207] \[P] Review public demo e2e coverage and extend only if needed for splash entry, battlefield interaction, limitation copy, service-worker scope, offline reload, and asset guard evidence with explicit loading, empty, error, and offline states (`tests/e2e/public-demo.e2e.ts`) * [x] T006 \[S0207] \[P] Tighten browser guard diagnostics only if validation needs clearer console, page-error, failed local request, or failed asset request reporting with explicit error mapping (`tests/e2e/support/browserGuards.ts`) ### docs * [x] T007 \[S0207] \[P] Build a documentation closeout matrix mapping PRD, UX PRD, gap-matrix rows, README files, and stable docs to shipped/deferred/excluded status (`.spec_system/specs/phase02-session07-product-surface-validation-and-documentation-closeout/implementation-notes.md`) *** ## Implementation (7 tasks) Browser validation, documentation updates, and closeout records. ### Browser validation * [x] T008 \[S0207] Run app desktop and mobile Playwright validation, capture screenshots, console/page-error guard results, failed request checks, battlefield nonzero dimensions, and overlap observations (`tests/e2e/app.e2e.ts`) * [x] T009 \[S0207] Run public demo desktop and mobile Playwright validation, capture screenshots, asset guard results, service-worker readiness, offline reload evidence, and limitation-copy observations (`tests/e2e/public-demo.e2e.ts`) ### docs * [x] T010 \[S0207] Update root, web, and public-demo README files with final Phase 02 shipped behavior, validation references, and deferred boundary language (`README.md`, `apps/web/README_web.md`, `public-demo/README_public-demo.md`) * [x] T011 \[S0207] Update stable architecture, docs index, battlefield, public-demo sharing, public-demo validation, privacy, and release docs with Phase 02 closeout evidence and remaining release risks (`docs/ARCHITECTURE.md`, `docs/README_docs.md`, `docs/battlefield.md`, `docs/public-demo-code-sharing.md`, `public-demo/docs_public-demo/validation.md`, `docs/privacy-and-security.md`, `docs/release.md`) * [x] T012 \[S0207] Update PRD, UX PRD, Phase 02 PRD, and gap matrix acceptance notes with validation-backed shipped/deferred/excluded status without marking future phases as shipped (`.spec_system/PRD/PRD.md`, `.spec_system/PRD/PRD_UX.md`, `.spec_system/PRD/phase_02/PRD_phase_02.md`, `.spec_system/PRD/phase_02/product_surface_gap_matrix.md`) * [x] T013 \[S0207] Update legacy-consolidation retained-value notes for Phase 02 product surface closeout without copying raw historical content or approving Phase 08 deletion (`docs/legacy-consolidation.md`) ### spec system * [x] T014 \[S0207] Produce security and privacy closeout covering local-first posture, redaction, replay/export/scan/browser storage, public demo synthetic-data boundaries, War Room deferral, and release risks (`.spec_system/specs/phase02-session07-product-surface-validation-and-documentation-closeout/security-compliance.md`) *** ## Testing (4 tasks) Quality gates and final closeout artifacts. ### Cross-cutting * [x] T015 \[S0207] Run root quality gates for format check, lint, typecheck, Vitest, battlefield asset parity, and `git diff --check`, or document explicit blockers with reproduction evidence (`package.json`) * [x] T016 \[S0207] Run ASCII and LF validation for spec-system outputs and touched docs, then record failures or fixes (`.spec_system/specs/phase02-session07-product-surface-validation-and-documentation-closeout/implementation-notes.md`) * [x] T017 \[S0207] Produce final validation report with task completion, deliverables, browser evidence, quality gate results, blockers, security posture, and behavioral quality spot-checks (`.spec_system/specs/phase02-session07-product-surface-validation-and-documentation-closeout/validation.md`) * [x] T018 \[S0207] Produce implementation summary and remaining-gap handoff for Phase 03 and later phases, then confirm readiness for the validate workflow step (`.spec_system/specs/phase02-session07-product-surface-validation-and-documentation-closeout/IMPLEMENTATION_SUMMARY.md`) *** ## Completion Checklist Before marking session complete: * [x] All tasks marked `[x]` * [x] All tests passing or blockers documented with evidence * [x] All files ASCII-encoded where required by spec-system output rules * [x] `implementation-notes.md` updated * [x] `security-compliance.md` updated * [x] `validation.md` ready for validate workflow review * [x] `IMPLEMENTATION_SUMMARY.md` updated * [x] Ready for the validate workflow step *** ## Next Steps Run the implement workflow step to begin AI-led implementation. --- # 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://faction-os.gitbook.io/faction-os-docs/.spec_system/archive/sessions/phase02-session07-product-surface-validation-and-documentation-closeout/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.