> 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-session01-documentation-and-privacy-sync/tasks.md). # Task Checklist **Session ID**: `phase11-session01-documentation-and-privacy-sync` **Total Tasks**: 22 **Estimated Duration**: 3-4 hours **Created**: 2026-05-31 *** ## Legend * `[x]` = Completed * `[ ]` = Pending * `[P]` = Parallelizable (can run with other \[P] tasks) * `[S1101]` = Session reference (11=phase number, 01=session number) * `TNNN` = Task ID *** ## Progress Summary | Category | Total | Done | Remaining | | -------------- | ------ | ------ | --------- | | Setup | 3 | 3 | 0 | | Foundation | 5 | 5 | 0 | | Implementation | 11 | 11 | 0 | | Testing | 3 | 3 | 0 | | **Total** | **22** | **22** | **0** | *** ## Setup (3 tasks) Initial state confirmation and source review. ### Cross-package * [x] T001 \[S1101] Verify Phase 11 Session 01 prerequisites, completed Phase 10 state, and cross-cutting documentation scope (`.spec_system/PRD/phase_11/session_01_documentation_and_privacy_sync.md`) * [x] T002 \[S1101] Review existing stable docs for Claude-only wording, Phase 09 readiness language, Codex trust guidance gaps, and package metadata claims (`README.md`) * [x] T003 \[S1101] \[P] Review CLI and hooks package READMEs plus package metadata for current `--cli claude|codex|all`, `CODEX_HOME`, `/hooks`, and provider-map wording (`apps/cli/README_cli.md`) *** ## Foundation (5 tasks) Shared documentation vocabulary, source-backed setup wording, and privacy boundaries. ### Cross-package * [x] T004 \[S1101] Define consistent provider terminology and no-overclaim wording for `Claude Code`, `Codex CLI`, `--cli claude|codex|all`, `CODEX_HOME`, `FACTIONOS_CLI=codex-cli`, and `/hooks` trust review (`docs/README_docs.md`) * [x] T005 \[S1101] \[P] Establish Codex setup source notes for user-level hooks, backup-first install/uninstall, default Claude behavior, and Phase 12 plugin deferral (`apps/cli/README_cli.md`) * [x] T006 \[S1101] \[P] Establish Codex hook runtime source notes for `hooks.json`, `hooks.claude.json`, `hooks.codex.json`, managed hook entries, and user-owned hook preservation (`apps/hooks/README_hooks.md`) * [x] T007 \[S1101] \[P] Establish Codex privacy source notes for prompts, transcripts, MCP arguments, `apply_patch`, command previews, terminal output, token-like values, and broad paths (`docs/privacy-and-security.md`) * [x] T008 \[S1101] Review current package descriptions and keywords to identify source-backed Codex metadata updates without implying plugin packaging or hosted telemetry (`package.json`) *** ## Implementation (11 tasks) Stable docs and metadata synchronization. ### Root and metadata * [x] T009 \[S1101] Update root quick start with parallel Claude and Codex local hook setup paths, explicit `/hooks` trust review, and unchanged default Claude behavior (`README.md`) * [x] T010 \[S1101] Update root workspace capability and limitation wording so Phase 10 Codex support is source-backed while Phase 11 validation, Phase 12 plugin packaging, hosted identity, trusted erasure, and production-hosted validation remain no-claim (`README.md`) * [x] T011 \[S1101] Update root and relevant package metadata descriptions or keywords for source-backed Codex hook support without adding unsupported plugin, hosted, or telemetry claims (`package.json`) ### docs * [x] T012 \[S1101] Add a Codex CLI local session onboarding path with install, start/open, `/hooks` trust review, expected cockpit behavior, and troubleshooting entry points (`docs/onboarding.md`) * [x] T013 \[S1101] Document Codex install/test workflows, status, doctor, uninstall, `~/.codex` or `CODEX_HOME`, and local FactionOS state for contributors (`docs/development.md`) * [x] T014 \[S1101] Document optional `CODEX_HOME` and installer-managed `FACTIONOS_CLI=codex-cli` behavior in environment references without telling users to export hook-managed values manually (`docs/environments.md`) * [x] T015 \[S1101] Add Codex hook trust, transcript, MCP, `apply_patch`, prompt, command preview, path, token, and local-state privacy guidance while preserving hosted no-claim and trusted-erasure limitations (`docs/privacy-and-security.md`) * [x] T016 \[S1101] Split API hook contract guidance into provider-specific Claude Code and Codex CLI sections with Codex event names, hook map source, timeout/post behavior, redaction limits, and no hosted telemetry claims (`docs/api/event-api-hook-contracts.md`) * [x] T017 \[S1101] Update the docs index so active Codex support routes readers to root, CLI, hooks, server/web/API docs, and Phase 11 validation scope without duplicating obsolete Phase 09 readiness language (`docs/README_docs.md`) ### Package READMEs * [x] T018 \[S1101] Refresh CLI README provider-routing guidance for default Claude setup, `--cli codex`, `--cli all`, `/hooks` trust review, status, doctor, uninstall, and unsupported plugin/project-local trust behavior (`apps/cli/README_cli.md`) * [x] T019 \[S1101] Refresh hooks README shared-runtime guidance for Claude and Codex provider maps, user-level Codex hook install, managed-entry preservation, `/hooks` trust review, and payload minimization (`apps/hooks/README_hooks.md`) *** ## Testing (4 tasks) Documentation review, metadata validation, and repository hygiene. ### Cross-package * [x] T020 \[S1101] Review changed docs for provider terminology consistency, valid links, default Claude behavior preservation, `/hooks` trust guidance, and absence of normal-path trust bypass recommendations (`docs/README_docs.md`) * [x] T021 \[S1101] Validate modified package metadata JSON and run focused formatting checks for JSON metadata files (`package.json`) * [x] T022 \[S1101] Run `git diff --check`, ASCII/LF validation, and a targeted sensitive-string review for planned docs to ensure no raw prompts, patch bodies, transcript contents, terminal output, MCP argument bodies, tokens, or broad local paths were added (`docs/privacy-and-security.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] 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-session01-documentation-and-privacy-sync/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.