Documentation Review

Name: docs-review
Rating: 92
Author: njbrake

Review all project documentation for accuracy against the current codebase. Fix any outdated, incorrect, or missing information.

Scope

Documentation files to review:

Source code to cross-reference:

•CLI command definitions in src/cli/ (clap structs, subcommands, flags, arguments)
•Configuration structs in src/session/ (config fields, defaults, validation)
•Supported agents and detection logic in src/process/
•TUI key bindings and navigation in src/tui/
•Docker/sandbox configuration in src/docker/
•Git worktree operations in src/git/
•Feature flags and capabilities throughout src/

•
Read every documentation file listed above.
•
For each documentation file, cross-reference its claims against the actual source code:
- •CLI flags and arguments: compare against clap definitions in src/cli/
- •Configuration options: compare against config structs in src/session/
- •Supported agents: compare against agent detection in src/process/
- •Key bindings: compare against input handling in src/tui/
- •Installation steps: verify scripts in scripts/ match documented commands
- •Feature descriptions: verify features exist and work as documented
•
For each discrepancy found:
- •Fix the documentation to match the source code (never the reverse)
- •Keep the fix minimal and precise
- •Preserve the existing writing style and tone of the document
•
Do NOT modify any non-documentation files. Never edit .rs, .toml, .yml, .yaml, .sh, .js, .json, or any other source/config files.
•
After reviewing all files, provide a summary of what was changed and why. If no changes were needed, report that all documentation is accurate.