> 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/phase12-session02-release-closeout-and-rollout-readiness/tasks.md). # Task Checklist **Session ID**: `phase12-session02-release-closeout-and-rollout-readiness` **Total Tasks**: 22 **Estimated Duration**: 3-4 hours **Created**: 2026-05-31 *** ## Legend * `[x]` = Completed * `[ ]` = Pending * `[P]` = Parallelizable (can run with other \[P] tasks) * `[S1202]` = Session reference (12=phase number, 02=session number) * `TNNN` = Task ID *** ## Progress Summary | Category | Total | Done | Remaining | | -------------- | ------ | ------ | --------- | | Setup | 4 | 4 | 0 | | Foundation | 5 | 5 | 0 | | Implementation | 9 | 9 | 0 | | Testing | 4 | 4 | 0 | | **Total** | **22** | **22** | **0** | *** ## Setup (4 tasks) Initial state confirmation, evidence scope, and release-gate planning. ### Cross-package * [x] T001 \[S1202] Verify Phase 12 Session 02 prerequisites, completed Session 01 packaging decision, and cross-cutting release scope (`.spec_system/PRD/phase_12/session_02_release_closeout_and_rollout_readiness.md`) * [x] T002 \[S1202] Review Phase 11 e2e validation, Session 01 plugin deferral, and release-guide command requirements (`.spec_system/specs/phase12-session01-codex-plugin-packaging/codex-plugin-packaging-decision.md`) * [x] T003 \[S1202] Identify current worktree, local environment constraints, available hosted smoke mode, and release-blocking fix boundaries (`.spec_system/specs/phase12-session02-release-closeout-and-rollout-readiness/implementation-notes.md`) * [x] T004 \[S1202] Map required release gates, focused Codex checks, prior-evidence citations, and unavailable/no-claim outcomes (`.spec_system/specs/phase12-session02-release-closeout-and-rollout-readiness/release-readiness-evidence.md`) *** ## Foundation (5 tasks) Create release closeout artifacts before running or recording gates. ### Cross-package * [x] T005 \[S1202] \[P] Create release-readiness evidence matrix for gate status, commands, owners, exceptions, and remediation notes (`.spec_system/specs/phase12-session02-release-closeout-and-rollout-readiness/release-readiness-evidence.md`) * [x] T006 \[S1202] \[P] Create privacy and security review matrix for install, hooks, server, web, replay, export, logs, diagnostics, backups, and uninstall boundaries (`.spec_system/specs/phase12-session02-release-closeout-and-rollout-readiness/privacy-security-release-review.md`) * [x] T007 \[S1202] \[P] Create documentation review matrix for root README, docs, package READMEs, release guide, deployment guide, and API docs (`.spec_system/specs/phase12-session02-release-closeout-and-rollout-readiness/docs-release-review.md`) * [x] T008 \[S1202] \[P] Create release notes and known-limitations skeletons with plugin deferral, `/hooks` review, and no-hosted-claim sections (`.spec_system/specs/phase12-session02-release-closeout-and-rollout-readiness/codex-release-notes.md`) * [x] T009 \[S1202] \[P] Create rollout readiness checklist for install, status, doctor, uninstall, rollback, docs, and operator handoff (`.spec_system/specs/phase12-session02-release-closeout-and-rollout-readiness/rollout-readiness-checklist.md`) *** ## Implementation (9 tasks) Run closeout checks, record evidence, and apply only release-blocking documentation or source fixes. ### apps/cli and apps/hooks * [x] T010 \[S1202] Run focused Codex installer and hook-map tests, then record direct-hook baseline status and any release-blocking remediation (`.spec_system/specs/phase12-session02-release-closeout-and-rollout-readiness/release-readiness-evidence.md`) * [x] T011 \[S1202] Review direct install, `/hooks` trust guidance, status, doctor, uninstall, backup, user-owned hook preservation, and rollback posture (`.spec_system/specs/phase12-session02-release-closeout-and-rollout-readiness/rollout-readiness-checklist.md`) ### Cross-package gates * [x] T012 \[S1202] Run or record final format, lint, workspace typecheck, focused tests, full tests, and workspace build outcomes with failure remediation paths (`.spec_system/specs/phase12-session02-release-closeout-and-rollout-readiness/release-readiness-evidence.md`) * [x] T013 \[S1202] Run or record media, battlefield, no-network hosted smoke, secret scan, and diff-check outcomes with unavailable/no-claim handling (`.spec_system/specs/phase12-session02-release-closeout-and-rollout-readiness/release-readiness-evidence.md`) * [x] T014 \[S1202] Record prior-evidence citations for live Codex trust review, fixture replay, browser validation, plugin N/A status, and any gate that cannot be safely rerun (`.spec_system/specs/phase12-session02-release-closeout-and-rollout-readiness/release-readiness-evidence.md`) ### Documentation and release artifacts * [x] T015 \[S1202] Complete boundary-specific privacy and security review with explicit no-claim status for plugin, hosted, production, remote execution, and trusted erasure surfaces (`.spec_system/specs/phase12-session02-release-closeout-and-rollout-readiness/privacy-security-release-review.md`) * [x] T016 \[S1202] Complete stable docs review and apply release-blocking docs updates for Codex support, plugin deferral, trust review, and limitations (`.spec_system/specs/phase12-session02-release-closeout-and-rollout-readiness/docs-release-review.md`) * [x] T017 \[S1202] Draft release notes or changelog-ready entries for Claude Code plus Codex CLI support, direct hook setup, plugin deferral, and validation posture (`.spec_system/specs/phase12-session02-release-closeout-and-rollout-readiness/codex-release-notes.md`) * [x] T018 \[S1202] Record known limitations, closed open questions, carried-forward follow-ups, and release note exclusions (`.spec_system/specs/phase12-session02-release-closeout-and-rollout-readiness/known-limitations-and-followups.md`) *** ## Testing (4 tasks) Validate artifacts, no-overclaim posture, and workflow handoff. ### Cross-package * [x] T019 \[S1202] Review all Session 02 artifacts for ASCII-only content, Unix LF line endings, sensitive-string leakage, and broad local path leakage (`.spec_system/specs/phase12-session02-release-closeout-and-rollout-readiness/release-readiness-evidence.md`) * [x] T020 \[S1202] Verify release notes and docs do not claim plugin install, plugin cache refresh, plugin trust, trust bypass, project-local trusted `.codex`, hosted telemetry, production-hosted validation, remote execution, or broad trusted erasure (`.spec_system/specs/phase12-session02-release-closeout-and-rollout-readiness/docs-release-review.md`) * [x] T021 \[S1202] Finalize implementation notes with command results, failures, fixes, evidence links, residual risks, and validate workflow handoff (`.spec_system/specs/phase12-session02-release-closeout-and-rollout-readiness/implementation-notes.md`) * [x] T022 \[S1202] Reconcile task checklist, completion checklist, and release handoff so the session is ready for the validate workflow (`.spec_system/specs/phase12-session02-release-closeout-and-rollout-readiness/tasks.md`) *** ## Completion Checklist Before marking session complete: * [x] All tasks marked `[x]` * [x] All tests passing or source-backed exceptions recorded * [x] All files ASCII-encoded * [x] `implementation-notes.md` updated * [x] Release-readiness evidence completed * [x] Privacy and security release review completed * [x] Release notes or changelog-ready entries completed * [x] Known limitations and follow-up work recorded * [x] Ready for the validate workflow step *** ## Next Steps Run the validate workflow step to verify session completeness. --- # 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/phase12-session02-release-closeout-and-rollout-readiness/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.