> 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/phase21-session07-final-regression-and-documentation/tasks.md). # Task Checklist **Session ID**: `phase21-session07-final-regression-and-documentation` **Total Tasks**: 18 **Estimated Duration**: 3-4 hours **Created**: 2026-06-29 *** Legend: `[x]` completed; `[ ]` pending; `[P]` parallelizable; `[SNNMM]` session ref; `TNNN` task ID. *** ## Setup (3 tasks) * [x] T001 \[S2107] Verify analyzer-selected Session 07 scope, completed Session 01-06 prerequisites, and web package context (`.spec_system/PRD/phase_21/session_07_final_regression_and_documentation.md`) * [x] T002 \[S2107] Audit stable docs for Command Center entry-path, Campaigns location, secondary summary inspector wording, and no-claim language (`.spec_system/specs/phase21-session07-final-regression-and-documentation/documentation-audit.md`) * [x] T003 \[S2107] Create final evidence files for regression commands, browser proof, and Phase 21 handoff (`.spec_system/specs/phase21-session07-final-regression-and-documentation/regression-evidence.md`) *** ## Foundation (4 tasks) * [x] T004 \[S2107] Run focused shell and mobile accessibility regression targets and record exact results (`npm test -- apps/web/tests/CockpitShell.test.tsx apps/web/tests/MobileAccessibility.test.tsx`) * [x] T005 \[S2107] Run focused Orchestration, Quest Board, and War Room panel regression targets and record exact results (`npm test -- apps/web/tests/OrchestrationPanel.test.tsx apps/web/tests/QuestBoard.test.tsx apps/web/tests/WarRoomPanel.test.tsx`) * [x] T006 \[S2107] Run focused shortcut and keyboard modal regression targets and record exact results (`npm test -- apps/web/tests/keyboardShortcuts.test.ts apps/web/tests/commandCenterShortcuts.test.ts apps/web/tests/KeyboardShortcutsModal.test.tsx`) * [x] T007 \[S2107] Run web package typecheck and classify any failure as Phase 21 regression, pre-existing failure, or environment issue (`npm run typecheck --workspace @factionos/web`) *** ## Implementation (7 tasks) * [x] T008 \[S2107] Repair focused host regressions from shell, sizing, Escape, scroll, or focus checks with cleanup on scope exit for all acquired resources (`apps/web/src/components/BottomRailExpansionHost.tsx`) * [x] T009 \[S2107] Repair compact or focused bottom-rail shell wiring regressions with explicit loading, empty, error, and offline states preserved (`apps/web/src/App.tsx`) * [x] T010 \[S2107] Repair Orchestration focused Command Center regressions with one mounted panel instance, nested overlay ordering, and product-facing copy only (`apps/web/src/components/orchestration/OrchestrationShell.tsx`) * [x] T011 \[S2107] Repair Quest Board or War Room focused action regressions with duplicate-trigger prevention while in-flight and state reset or revalidation on re-entry (`apps/web/src/components/QuestBoard.tsx`, `apps/web/src/components/WarRoomPanel.tsx`) * [x] T012 \[S2107] Update the operator quickstart so Campaigns, Queue, File/Git, terminal runtime controls, and other workbenches live under the Orchestration Command Center focused path (`docs/orchestration-quickstart.md`) * [x] T013 \[S2107] \[P] Update the web README bottom-rail contract so compact and focused surfaces share one implementation and retained summaries are secondary inspectors (`apps/web/README_web.md`) * [x] T014 \[S2107] \[P] Update docs routing, architecture, and root product-surface summaries with the Phase 21 focused-surface path and no hosted/certification overclaims (`docs/README_docs.md`, `docs/ARCHITECTURE.md`, `README.md`) *** ## Testing (4 tasks) * [x] T015 \[S2107] Run app desktop and app mobile browser verification for focused bottom-rail surfaces and record final results (`npm run test:e2e -- --project=app-desktop --project=app-mobile tests/e2e/app.e2e.ts`) * [x] T016 \[S2107] Re-run all three focused Vitest groups and web typecheck after any repairs or docs updates (`npm test -- apps/web/tests/CockpitShell.test.tsx apps/web/tests/MobileAccessibility.test.tsx apps/web/tests/OrchestrationPanel.test.tsx apps/web/tests/QuestBoard.test.tsx apps/web/tests/WarRoomPanel.test.tsx apps/web/tests/keyboardShortcuts.test.ts apps/web/tests/commandCenterShortcuts.test.ts apps/web/tests/KeyboardShortcutsModal.test.tsx && npm run typecheck --workspace @factionos/web`) * [x] T017 \[S2107] Validate docs grep, ASCII, LF, whitespace, and privacy/no-claim scans for changed files (`git diff --check`) * [x] T018 \[S2107] Complete final Phase 21 handoff notes with command results, documentation changes, limitations, and updateprd inputs (`.spec_system/specs/phase21-session07-final-regression-and-documentation/phase-handoff.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 `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://faction-os.gitbook.io/faction-os-docs/.spec_system/archive/sessions/phase21-session07-final-regression-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.