> 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_12/session_02_release_closeout_and_rollout_readiness.md). # Session 02: Release Closeout And Rollout Readiness **Session ID**: `phase12-session02-release-closeout-and-rollout-readiness` **Status**: Not Started **Estimated Tasks**: \~14-22 **Estimated Duration**: 2-4 hours *** ## Objective Complete final quality, privacy, security, documentation, uninstall, and release-readiness checks for first-class Codex CLI support. *** ## Scope ### In Scope (MVP) * Run final lint, typecheck, focused tests, and any available CI-equivalent checks. * Review privacy, security, docs, and uninstall behavior one final time. * Prepare release notes or changelog entries describing Claude plus Codex support. * Record known limitations, follow-up work, and manual validation evidence. ### Release Closeout Gates * Final lint, typecheck, focused tests, and available CI-equivalent results. * Privacy review for install, hooks, server, web, replay, export, logs, and diagnostics. * Security review for hook trust, permission requests, backups, uninstall, and malformed Codex config handling. * Documentation review confirming Claude and Codex paths are both represented. * Release notes or changelog entries for Claude plus Codex support. * Known limitations and follow-up work. ### Non-Goals To Preserve * No hosted auth, hosted storage, analytics capture, push, tunnel, or remote execution behavior. * No automatic approval of Codex permission requests. * No bypass of Codex hook trust as the default setup path. * No mutation of Codex provider, auth, telemetry, model, profile, or OpenAI API settings. * No custom Codex slash command claims. * No attempt to reconstruct full transcripts from `transcript_path`. * No broad file, git, terminal, Docker, Worker, or hosted executor behavior. ### Open Questions To Close Or Carry Forward * Should the default `factionos init` remain Claude-only for one release, or should it prompt when both Claude and Codex homes are present? * Should `~/.factionos/settings.json` store one default `cli` or an `installedClis` list? * Should project-local `.codex/hooks.json` be supported in the first Codex release, or held until user-level install is proven? * How much Codex MCP detail should FactionOS surface: generic tool-use names only, or allowlisted compact argument labels for specific MCP servers? * Should `PreCompact` and `PostCompact` become visible mission events, or stay diagnostics-only? ### Out of Scope * New feature implementation beyond release-blocking fixes. * Hosted auth, storage, analytics, public replay, push, or remote execution. * Broad refactors unrelated to release readiness. *** ## Prerequisites * [ ] Session 01 complete. * [ ] Packaging decision recorded. * [ ] Phase 11 validation notes available. * [ ] Release gate commands identified. *** ## Deliverables 1. Final release-readiness evidence. 2. Privacy, security, docs, and uninstall review notes. 3. Release notes or changelog entries for Claude plus Codex support. 4. Known limitations and follow-up work list. *** ## Success Criteria * [ ] The Codex integration is ready to release as first-class local hook support. * [ ] Remaining limitations are documented and do not block the definition of done. * [ ] Final validation does not expose raw prompts, patches, terminal output, transcripts, MCP args, paths, tokens, or provider credentials. --- # 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_12/session_02_release_closeout_and_rollout_readiness.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.