> 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/docs-release-review.md). # Documentation Release Review **Session ID**: `phase12-session02-release-closeout-and-rollout-readiness` **Package**: Cross-cutting **Date**: 2026-05-31 **Status**: Complete *** ## Review Goal Confirm stable docs describe Claude Code and Codex CLI local hook support without overstating plugin packaging, hook trust, hosted behavior, production validation, remote execution, or trusted erasure. *** ## Required Release Wording Docs may claim: * Claude Code hooks remain the default `factionos init` path. * Codex CLI hooks are supported through explicit provider selection: `factionos init --cli codex` or `factionos init --cli all`. * Codex users review loaded hooks with `/hooks` in a new Codex CLI session. * `status`, `doctor`, and `uninstall` support selected Codex posture and managed-hook cleanup. * Plugin packaging is explicitly deferred for this release. * Hosted and production claims require separate hosted smoke evidence. Docs must not claim: * A Codex plugin package exists or was validated. * Plugin install, cache refresh, plugin trust review, or plugin uninstall passed. * FactionOS bypasses Codex hook trust or creates project-local trusted `.codex` state. * Codex auth, provider, telemetry, model, profile, API key, account settings, or trusted-project settings are mutated. * Hosted telemetry, hosted identity, hosted storage, analytics capture, public replay hosting, production-hosted validation, push/tunnel operation, remote execution, or broad trusted erasure is active. *** ## Stable Docs Matrix | File | Review focus | Initial status | Follow-up | | -------------------------------------- | ------------------------------------------------------------------------------------------------------------------ | -------------- | ------------------------------------------------------------------------------------- | | `README.md` | High-level Codex support, default Claude setup, direct Codex setup, plugin deferral, current shipped capabilities. | Reviewed | Final no-overclaim scan pending. | | `docs/README_docs.md` | Docs routing and stable/historical distinction. | Reviewed | No blocking gap found. | | `docs/release.md` | Release gates, hosted smoke no-claim wording, release note inputs. | Reviewed | Update only if final gate outcomes require it. | | `docs/development.md` | Provider workflow, focused checks, trust review, sensitive evidence rules. | Reviewed | No blocking gap found yet. | | `docs/privacy-and-security.md` | Codex privacy boundary, install/uninstall scope, hosted and erasure no-claims. | Reviewed | No blocking gap found yet. | | `docs/deployment.md` | Production status, hosted smoke mode, deployed validation no-claims. | Reviewed | No blocking gap found yet. | | `docs/environments.md` | `CODEX_HOME`, active/reserved variable ownership, hosted credential boundaries. | Reviewed | No blocking gap found yet. | | `docs/api/README_api.md` | Local API and erasure no-claims; hook source maps. | Updated | Replaced stale "later installer" wording with current direct Codex installer wording. | | `docs/api/event-api-hook-contracts.md` | Codex lifecycle support, plugin deferral, unsupported surfaces. | Reviewed | No blocking gap found yet. | | `apps/cli/README_cli.md` | CLI commands, provider selection, Codex install/status/doctor/uninstall, local erasure. | Reviewed | No blocking gap found yet. | | `apps/hooks/README_hooks.md` | Hook maps, trust review, plugin deferral, redaction, diagnostics. | Reviewed | No blocking gap found yet. | | `apps/server/README_server.md` | Server local-first and API route posture. | Reviewed | No blocking gap found. | | `apps/web/README_web.md` | Web display and replay/export boundaries. | Reviewed | No blocking gap found. | | `packages/protocol/README_protocol.md` | Shared Codex vocabulary and no-hosted claim alignment. | Reviewed | No blocking gap found. | *** ## Package README Matrix | Package | File | Required release check | | -------- | -------------------------------------- | ---------------------------------------------------------------------------------------------------------- | | CLI | `apps/cli/README_cli.md` | Provider selection, isolated direct install, status, doctor, uninstall, and no plugin/trust-bypass claims. | | Hooks | `apps/hooks/README_hooks.md` | Codex source map, redaction, timeout, `/hooks` review, plugin deferral, no hosted telemetry. | | Server | `apps/server/README_server.md` | Local ingest and hosted no-claim boundaries remain aligned with API docs. | | Web | `apps/web/README_web.md` | Codex labels/replay are local cockpit behavior only. | | Protocol | `packages/protocol/README_protocol.md` | `codex-cli` vocabulary is first-class local event vocabulary, not hosted/provider transfer. | | War Room | `apps/warroom/README_warroom.md` | Optional Worker remains separate from Codex local hooks and not hosted identity. | *** ## Release-Blocking Docs Gap Log One release-blocking docs gap was found and fixed: | File | Gap | Resolution | | ------------------------ | ------------------------------------------------------------------------------------------------------------------ | --------------------------------------------------------------------------------------------------------------------------------------------------------------- | | `docs/api/README_api.md` | Described `hooks.codex.json` as source for "later installer" work even though direct Codex install is now shipped. | Updated wording to state that `factionos init --cli codex` and `factionos init --cli all` consume the template for user-level hook install and `/hooks` review. | No other blocking docs gaps were found. *** ## Final No-Overclaim Result The stable-docs scan found expected negative-policy wording only for plugin, trust-bypass, hosted, remote-execution, production-hosted, and trusted-erasure phrases. No reviewed stable doc claims plugin availability, plugin validation, trust bypass, project-local trusted `.codex` setup, hosted telemetry, production-hosted validation, remote execution, or broad trusted erasure for this release. The final scan across release notes, Session 02 artifacts, root docs, package READMEs, and stable docs also found expected negative-policy, deferred, unavailable, no-claim, or N/A wording only. *** ## No-Overclaim Scan Targets The final review must search stable docs and release artifacts for claims around: * Plugin install, cache refresh, plugin trust, or plugin uninstall. * Trust bypass, automatic hook approval, or project-local trusted `.codex` setup. * Hosted telemetry, hosted identity, hosted storage, production-hosted validation, analytics capture, push/tunnel operation, public replay hosting, remote execution, or trusted erasure. Expected negative-policy wording may include those phrases when clearly marked as deferred, unavailable, not claimed, or N/A. --- # 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/docs-release-review.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.