Fix 10 CodeRabbit review issues and stale documentation

Resolve all actionable, outside-diff, duplicate, and nitpick issues from
CodeRabbit review on PR #14, plus one discovered consistency issue.

Major: implementer PostToolUse hook (per-Edit) → Stop hook (once at end)
with 120s timeout. Tester Stop hook timeout 30s → 120s. Added cc-orc to
cc-tools discovery. Updated CLAUDE.md directory tree with missing files.
Fixed stale verify-no-regression.py comment. Added MD040 language
specifiers. Clarified orchestrator plan mode delegation scope and added
specialist catalog catch-all.

Author: AnExiledDev

.devcontainer/CHANGELOG.md

@@ -10,11 +10,22 @@
 
 #### Workhorse Agents
 - **`investigator`** — consolidated read-only research agent (sonnet) merging the domains of researcher, explorer, dependency-analyst, git-archaeologist, debug-logs, and perf-profiler; handles codebase search, web research, git forensics, dependency auditing, log analysis, and performance profiling
-- **`implementer`** — consolidated read-write implementation agent (opus, worktree) merging generalist, refactorer, and migrator; handles all code modifications with embedded code standards, execution discipline, and PostToolUse regression testing
+- **`implementer`** — consolidated read-write implementation agent (opus, worktree) merging generalist, refactorer, and migrator; handles all code modifications with embedded code standards, execution discipline, and Stop hook regression testing
 - **`tester`** — enhanced test agent (opus, worktree) with full testing standards, framework-specific guidance, and Stop hook verification; creates and verifies test suites
 - **`documenter`** — consolidated documentation and specification agent (opus) merging doc-writer and spec-writer; handles README, API docs, docstrings, and the full spec lifecycle (create, refine, build, review, update, check)
 - **Question Surfacing Protocol** — all 4 workhorse agents carry an identical protocol requiring them to STOP and return `## BLOCKED: Questions` sections when hitting ambiguities, ensuring no assumptions are made without user input
 
+### Fixed
+
+#### CodeRabbit Review Fixes
+- **`implementer.md`** — changed PostToolUse hook (fires every Edit) to Stop hook (fires once at task end) with 120s timeout; prevents redundant test runs during multi-file tasks
+- **`tester.md`** — increased Stop hook timeout from 30s to 120s to accommodate larger test suites
+- **`setup-aliases.sh`** — added `cc-orc` to `cc-tools` discovery loop so it appears in tool audit
+- **`CLAUDE.md`** — added missing `keybindings.json`, `orchestrator-system-prompt.md`, and `writing-system-prompt.md` to directory structure tree
+- **`agent-system/README.md`** — updated `verify-no-regression.py` comment to list both consumers (implementer, refactorer); hyphenated "question-surfacing protocol"
+- **`orchestrator-system-prompt.md`** — clarified plan mode allows investigator delegation for research; added catch-all entry in selection criteria pointing to the full specialist catalog
+- **MD040 compliance** — added `text` language specifiers to 7 fenced code blocks across `investigator.md`, `tester.md`, and `documenter.md`
+
 ### Changed
 
 #### Agent System

.devcontainer/CLAUDE.md

@@ -12,7 +12,10 @@ CodeForge devcontainer for AI-assisted development with Claude Code.
 │   ├── file-manifest.json     # Declarative config file deployment
 │   └── defaults/              # Source files deployed on start via file-manifest
 │       ├── settings.json      # Model, permissions, plugins, env vars
+│       ├── keybindings.json   # Keyboard shortcuts
 │       ├── main-system-prompt.md
+│       ├── orchestrator-system-prompt.md
+│       ├── writing-system-prompt.md
 │       ├── ccstatusline-settings.json  # Status bar widget layout
 │       └── rules/             # Deployed to .claude/rules/
 ├── features/                  # Custom devcontainer features

.devcontainer/config/defaults/orchestrator-system-prompt.md

@@ -147,6 +147,7 @@ Selection criteria:
 - Is it a targeted security review? → security-auditor
 - Is it a complex architecture decision? → architect
 - Is it a simple command to run? → bash-exec
+- Does the task require a specialist not listed above? → consult the agent-system README for the full 17-agent specialist catalog
 </agent_catalog>
 
 <question_surfacing>
@@ -219,7 +220,7 @@ If ANY condition is not met, the change is NOT trivial.
 <planmode_rules>
 Plan mode behavior (read-only tools only: `Read`, `Glob`, `Grep`):
 - No code modifications (`Edit`, `Write` forbidden — and you never use these anyway)
-- No agent delegation for implementation
+- No agent delegation for implementation (investigator delegation for research is permitted)
 - No commits, PRs, or refactors
 
 Plan contents MUST include:

.devcontainer/plugins/devs-marketplace/plugins/agent-system/README.md

@@ -8,7 +8,7 @@ Replaces Claude Code's built-in agents with enhanced custom agents that carry do
 
 ### Workhorse Agents
 
-General-purpose agents designed for orchestrator mode (`cc-orc`). Each covers a broad domain, carrying detailed execution discipline, code standards, and a question surfacing protocol. Most tasks need only 2-3 of these.
+General-purpose agents designed for orchestrator mode (`cc-orc`). Each covers a broad domain, carrying detailed execution discipline, code standards, and a question-surfacing protocol. Most tasks need only 2-3 of these.
 
 | Agent | Domain | Access | Model |
 |-------|--------|--------|-------|
@@ -200,7 +200,7 @@ agent-system/
 |   +-- redirect-builtin-agents.py   # Built-in agent redirection
 |   +-- task-completed-check.py      # Test suite quality gate
 |   +-- teammate-idle-check.py       # Incomplete task checker
-|   +-- verify-no-regression.py      # Post-edit regression tests (refactorer)
+|   +-- verify-no-regression.py      # Post-edit regression tests (implementer, refactorer)
 |   +-- verify-tests-pass.py         # Test verification (test-writer)
 +-- skills/
 |   +-- debug/

.devcontainer/plugins/devs-marketplace/plugins/agent-system/agents/documenter.md

@@ -130,7 +130,7 @@ offset = len(header) + 1  # add one to header length
 
 ### Spec Directory Structure
 
-```
+```text
 .specs/
 ├── MILESTONES.md           # Current milestone scope
 ├── BACKLOG.md              # Priority-graded feature backlog

.devcontainer/plugins/devs-marketplace/plugins/agent-system/agents/implementer.md

@@ -19,16 +19,15 @@ skills:
   - migration-patterns
   - spec-update
 hooks:
-  PostToolUse:
-    - matcher: Edit
-      type: command
+  Stop:
+    - type: command
       command: "python3 ${CLAUDE_PLUGIN_ROOT}/scripts/verify-no-regression.py"
-      timeout: 30
+      timeout: 120
 ---
 
 # Implementer Agent
 
-You are a **senior software engineer** who handles all code modifications — writing new features, fixing bugs, refactoring for quality, and migrating between frameworks or versions. You are methodical, scope-disciplined, and thorough — you do what was asked, verify it works, and report clearly. You treat every edit as consequential and verify after every change.
+You are a **senior software engineer** who handles all code modifications — writing new features, fixing bugs, refactoring for quality, and migrating between frameworks or versions. You are methodical, scope-disciplined, and thorough — you do what was asked, verify it works, and report clearly. You treat every edit as consequential.
 
 ## Project Context Discovery
 
@@ -189,7 +188,7 @@ Hard to reverse (stop and report):
 - **NEVER** create helpers, utilities, or abstractions for one-time operations.
 - **NEVER** add docstrings, comments, or type annotations to code you did not change.
 - Read files before modifying them. Understand existing code before changing it.
-- The PostToolUse hook runs tests after every `Edit` call. If tests fail, analyze the failure and fix the issue or try a different approach.
+- The Stop hook runs tests when you finish. If tests fail, analyze the failure and fix the issue or try a different approach before completing.
 
 ## Working Strategy
 
@@ -218,8 +217,8 @@ Before starting any task, classify it:
 2. **Run the test suite** to establish a green baseline. If tests fail, stop and report.
 3. **Plan the transformation** — describe what and why before editing.
 4. **Execute smallest safe steps** — one atomic transformation at a time.
-5. **Verify after each step** — PostToolUse hook runs tests automatically.
-6. **If tests fail after an edit**: revert, analyze, try a different approach.
+5. **Verify before finishing** — the Stop hook runs tests automatically when you complete.
+6. **If tests fail**: analyze the failure, fix the issue, and try again before finishing.
 
 ### For Multi-Step Tasks
 

.devcontainer/plugins/devs-marketplace/plugins/agent-system/agents/investigator.md

@@ -40,7 +40,7 @@ Before starting work, read project-specific instructions:
 
 1. **Rules**: `Glob: .claude/rules/*.md` — read all files found. These are mandatory constraints.
 2. **CLAUDE.md files**: Starting from your working directory, read CLAUDE.md files walking up to the workspace root:
-   ```
+   ```text
    Glob: **/CLAUDE.md (within the project directory)
    ```
 3. **Apply**: Follow discovered conventions for naming, frameworks, architecture boundaries, and workflow rules. CLAUDE.md instructions take precedence over your defaults when they conflict.
@@ -121,7 +121,7 @@ Follow a disciplined codebase-first, web-second approach. Local evidence is more
 
 **Phase 2 — Codebase investigation**: Start with the local codebase. Even for general questions, the project context shapes the answer.
 
-```
+```text
 # Discover project structure
 Glob: **/*.{py,ts,js,go,rs,java}
 Glob: **/package.json, **/pyproject.toml, **/Cargo.toml, **/go.mod
@@ -141,7 +141,7 @@ When investigating how something works:
 
 **Phase 3 — Web research** (when needed): Fill gaps the codebase cannot answer.
 
-```
+```text
 # Search for documentation
 WebSearch: "<library> documentation <specific topic>"
 

.devcontainer/plugins/devs-marketplace/plugins/agent-system/agents/tester.md

@@ -22,7 +22,7 @@ hooks:
   Stop:
     - type: command
       command: "python3 ${CLAUDE_PLUGIN_ROOT}/scripts/verify-tests-pass.py"
-      timeout: 30
+      timeout: 120
 ---
 
 # Tester Agent
@@ -35,7 +35,7 @@ Before starting any task, check for project-specific instructions:
 
 1. **Rules**: `Glob: .claude/rules/*.md` — read all files found. These are mandatory constraints.
 2. **CLAUDE.md files**: Starting from your working directory, read CLAUDE.md files walking up to the workspace root:
-   ```
+   ```text
    Glob: **/CLAUDE.md (within the project directory)
    ```
 3. **Apply**: Follow discovered conventions for naming, nesting limits, framework choices, architecture boundaries, and workflow rules. CLAUDE.md instructions take precedence over your defaults.
@@ -171,7 +171,7 @@ When uncertain, investigate first — read the code, check the docs — rather t
 
 ### Step 1: Detect the Test Framework
 
-```
+```text
 # Python
 Glob: **/pytest.ini, **/pyproject.toml, **/setup.cfg, **/conftest.py
 Grep in pyproject.toml/setup.cfg: "pytest", "unittest"
@@ -203,7 +203,7 @@ Read 2-3 existing test files for:
 
 ### Step 3: Identify Untested Code
 
-```
+```text
 # Compare source files to test files
 # Check coverage reports if available
 Glob: **/coverage/**, **/.coverage, **/htmlcov/**

.devcontainer/scripts/setup-aliases.sh

@@ -101,7 +101,7 @@ cc-tools() {
   echo "━━━━━━━━━━━━━━━━━━━━━━━━"
   printf "  %-20s %s\n" "COMMAND" "STATUS"
   echo "  ────────────────────────────────────"
-  for cmd in claude cc ccw ccraw ccusage ccburn claude-monitor \\
+  for cmd in claude cc ccw ccraw cc-orc ccusage ccburn claude-monitor \\
              ccms ct cargo ruff biome dprint shfmt shellcheck hadolint \\
              ast-grep tree-sitter pyright typescript-language-server \\
              agent-browser gh docker git jq tmux bun go infocmp; do