> 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/phase11-session03-end-to-end-validation-and-integration-fixes/tasks.md). # Task Checklist **Session ID**: `phase11-session03-end-to-end-validation-and-integration-fixes` **Total Tasks**: 25 **Estimated Duration**: 3-4 hours **Created**: 2026-05-31 *** ## Legend * `[x]` = Completed * `[ ]` = Pending * `[P]` = Parallelizable (can run with other \[P] tasks) * `[S1103]` = Session reference (11=phase number, 03=session number) * `TNNN` = Task ID *** ## Progress Summary | Category | Total | Done | Remaining | | -------------- | ------ | ------ | --------- | | Setup | 4 | 4 | 0 | | Foundation | 5 | 5 | 0 | | Implementation | 13 | 13 | 0 | | Testing | 3 | 3 | 0 | | **Total** | **25** | **25** | **0** | *** ## Setup (4 tasks) Initial state confirmation, environment isolation, and validation route selection. ### Cross-package * [x] T001 \[S1103] Verify Phase 11 Session 03 prerequisites, completed Session 02 state, and cross-package validation scope (`.spec_system/PRD/phase_11/session_03_end_to_end_validation_and_integration_fixes.md`) * [x] T002 \[S1103] Review Session 02 fixture evidence, current Codex docs, and blocker-only fix boundaries (`.spec_system/specs/phase11-session02-test-fixture-hardening/validation.md`) * [x] T003 \[S1103] Prepare isolated validation homes, ports, local auth posture, and user-owned Codex hook seed plan (`.spec_system/specs/phase11-session03-end-to-end-validation-and-integration-fixes/codex-e2e-validation-record.md`) * [x] T004 \[S1103] Link the CLI and record environment preflight, including live Codex availability or fixture-replay fallback (`.spec_system/specs/phase11-session03-end-to-end-validation-and-integration-fixes/implementation-notes.md`) *** ## Foundation (5 tasks) Validation artifacts, fixture replay helpers, and e2e scaffolding. ### Cross-package * [x] T005 \[S1103] \[P] Create validation record skeleton for commands, evidence, exceptions, privacy review, blockers, and final status (`.spec_system/specs/phase11-session03-end-to-end-validation-and-integration-fixes/codex-e2e-validation-record.md`) * [x] T006 \[S1103] \[P] Create redacted Codex e2e fixture helper for lifecycle, Bash, `apply_patch`, MCP, permission, subagent, and Stop payloads with schema-validated input and explicit error mapping (`tests/e2e/support/codexFixtures.ts`) * [x] T007 \[S1103] Add Codex fixture-replayed cockpit e2e coverage with explicit loading, empty, error, offline, connected, and privacy-safe visible states (`tests/e2e/app.e2e.ts`) * [x] T008 \[S1103] Record live-vs-fixture validation decision rules and no-overclaim wording in implementation notes (`.spec_system/specs/phase11-session03-end-to-end-validation-and-integration-fixes/implementation-notes.md`) * [x] T009 \[S1103] Map validation commands to owner packages and identify focused tests for any blocker fixes (`.spec_system/specs/phase11-session03-end-to-end-validation-and-integration-fixes/implementation-notes.md`) *** ## Implementation (13 tasks) End-to-end validation, browser evidence, and blocker-only source fixes. ### apps/cli * [x] T010 \[S1103] Record isolated `factionos init --cli codex --faction orc` evidence with user-owned hook preservation, idempotent rerun coverage, duplicate managed-hook prevention, and no Claude mutation (`.spec_system/specs/phase11-session03-end-to-end-validation-and-integration-fixes/codex-e2e-validation-record.md`) * [x] T011 \[S1103] Record live Codex `/hooks` trust-review outcome or source-backed fixture exception without recommending trust bypasses (`.spec_system/specs/phase11-session03-end-to-end-validation-and-integration-fixes/codex-e2e-validation-record.md`) * [x] T012 \[S1103] Record `factionos status --cli codex` and `factionos doctor --cli codex` evidence with timeout handling, compact labels, counts, and no raw payload output (`.spec_system/specs/phase11-session03-end-to-end-validation-and-integration-fixes/codex-e2e-validation-record.md`) * [x] T013 \[S1103] Record `factionos uninstall --cli codex` evidence with idempotent rerun coverage, user-owned hook preservation, managed-hook removal, and no trusted-erasure overclaim (`.spec_system/specs/phase11-session03-end-to-end-validation-and-integration-fixes/codex-e2e-validation-record.md`) * [x] T014 \[S1103] Validate and, if needed, fix CLI provider/install/status/doctor/uninstall blocker behavior closest to the provider posture boundary (`apps/cli/src/lib/providerPosture.js`) ### apps/server * [x] T015 \[S1103] Validate local runtime startup with `FACTIONOS_MOCK=false`, bounded wait/failure handling, and explicit local server health evidence (`.spec_system/specs/phase11-session03-end-to-end-validation-and-integration-fixes/codex-e2e-validation-record.md`) * [x] T016 \[S1103] Validate Codex `SessionStart`, `UserPromptSubmit`, and `Stop` lifecycle ingest with schema-validated input and explicit error mapping (`tests/e2e/support/codexFixtures.ts`) * [x] T017 \[S1103] Validate and, if needed, fix server ingest blocker behavior for Codex lifecycle, tool, permission, MCP, subagent, unknown, or compaction-safe events (`apps/server/src/lib/eventIngest.ts`) ### apps/hooks * [x] T018 \[S1103] Validate Bash and `apply_patch` observability with bounded metadata, no raw command output, no raw patch bodies, and scoped rollback of any fixture setup (`tests/e2e/support/codexFixtures.ts`) * [x] T019 \[S1103] Validate MCP and permission request observability with allowlisted tool names, no raw argument dumps, no auto-approval, and explicit degraded fallback behavior (`tests/e2e/support/codexFixtures.ts`) * [x] T020 \[S1103] Validate subagent start and stop observability with typed lineage when safe IDs exist and compact degraded events when they do not (`tests/e2e/support/codexFixtures.ts`) ### apps/web * [x] T021 \[S1103] Validate cockpit Codex labels, mission filters, hero detail, tool usage, replay, export-adjacent redaction, and accessible interactive states (`tests/e2e/app.e2e.ts`) * [x] T022 \[S1103] Validate and, if needed, fix web Codex display or redaction blocker behavior using protocol-backed labels and exhaustive private-field handling (`apps/web/src/lib/heroCli.ts`) *** ## Testing (3 tasks) Focused verification and repository hygiene. ### Cross-package * [x] T023 \[S1103] Run focused Playwright app desktop/mobile validation for the Codex replay path and capture browser guard results (`tests/e2e/app.e2e.ts`) * [x] T024 \[S1103] Run focused Vitest suites for touched protocol, hooks, CLI, server, and web code, then run workspace typecheck (`vitest.config.ts`) * [x] T025 \[S1103] Run `npm run format:check`, `npm run lint`, `git diff --check`, ASCII/LF validation, sensitive-string review, and finalize implementation notes (`.spec_system/specs/phase11-session03-end-to-end-validation-and-integration-fixes/implementation-notes.md`) *** ## Completion Checklist Before marking session complete: * [x] All tasks marked `[x]` * [x] All tests passing * [x] All files ASCII-encoded * [x] implementation-notes.md updated * [x] `codex-e2e-validation-record.md` completed * [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/phase11-session03-end-to-end-validation-and-integration-fixes/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.