> 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/phases/phase_21/session_07_final_regression_and_documentation.md). # Session 07: Final Regression And Documentation **Session ID**: `phase21-session07-final-regression-and-documentation` **Package**: apps/web **Status**: Not Started **Estimated Tasks**: \~12-18 **Estimated Duration**: 2-4 hours *** ## Objective Close the phase with targeted regression coverage and updated project documentation. *** ## Scope ### In Scope (MVP) * Run focused shell, panel, shortcut, accessibility, and typecheck targets. * Repair regressions introduced by the expansion work. * Update documentation that describes where Campaigns and other Orchestration surfaces live. * Record any remaining limitations or follow-up decisions in the ongoing project note or stable product docs. * Confirm the final delivered behavior proves the user outcome end to end in the product. ### Out of Scope * New feature work beyond regression repairs. * Hosted production validation. * Formal legal/privacy approval changes. *** ## Prerequisites * [ ] Sessions 01 through 06 completed. * [ ] Focused test list from the folded Phase 21 source findings reviewed. * [ ] Stable docs needing Campaigns/Orchestration entry-path updates identified. *** ## Deliverables 1. Passing focused test and typecheck evidence, or documented pre-existing failures with proof. 2. Updated docs that match the implemented bottom-rail expansion model. 3. Final phase handoff notes preserving remaining no-claim or follow-up items. *** ## Folded Source Details This session owns final proof that the old planning note can be deleted without losing planning detail. The canonical source is now the Phase 21 PRD plus these session stubs. Verification targets preserved from the source plan: * `npm test -- apps/web/tests/CockpitShell.test.tsx apps/web/tests/MobileAccessibility.test.tsx` * `npm test -- apps/web/tests/OrchestrationPanel.test.tsx apps/web/tests/QuestBoard.test.tsx apps/web/tests/WarRoomPanel.test.tsx` * `npm test -- apps/web/tests/keyboardShortcuts.test.ts apps/web/tests/commandCenterShortcuts.test.ts apps/web/tests/KeyboardShortcutsModal.test.tsx` * `npm run typecheck --workspace @factionos/web` * After implementation, run a browser pass at a small viewport and a desktop viewport to verify the fixed expanded surface is not clipped by the cockpit grid and that the bottom rail remains usable when no panel is expanded. Documentation details to preserve: * Update any docs that tell users where Campaigns and other Orchestration surfaces live. * Documentation must not imply the summary/details popup is the primary place to use Campaigns, Queue, File/Git, terminal runtime controls, or other Command Center workbenches. * Any retained summary/details inspectors should be documented, if at all, as secondary inspectors or diagnostics rather than as the primary working surface. * Preserve no-claim language for unrelated hosted production validation, formal certification, hosted identity, trusted erasure, or backend execution surfaces not touched by Phase 21. End-to-end delivery bar for this session: * The phase is complete only after the shipped product path proves open, use, visible result, close/recover, and state-preservation behavior for the focused bottom-rail surfaces. * Passing scaffolding tests is not enough; validation must include real component behavior and browser-visible evidence for the implemented UI. * Any pre-existing test or typecheck failure must be documented with evidence and separated from Phase 21 regressions. *** ## Success Criteria * [ ] `npm test -- apps/web/tests/CockpitShell.test.tsx apps/web/tests/MobileAccessibility.test.tsx` passes. * [ ] `npm test -- apps/web/tests/OrchestrationPanel.test.tsx apps/web/tests/QuestBoard.test.tsx apps/web/tests/WarRoomPanel.test.tsx` passes. * [ ] `npm test -- apps/web/tests/keyboardShortcuts.test.ts apps/web/tests/commandCenterShortcuts.test.ts apps/web/tests/KeyboardShortcutsModal.test.tsx` passes. * [ ] `npm run typecheck --workspace @factionos/web` passes, or any failure is documented as pre-existing with evidence. * [ ] Documentation no longer implies the summary/details popup is the primary place to use Campaigns or other Orchestration workbenches. --- # 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/phases/phase_21/session_07_final_regression_and_documentation.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.