feat: implement company pipeline orchestration with user commands for full, quick, and skip modes

CLAUDE.md

@@ -77,6 +77,18 @@ Controller (key input → Action) → Event Loop → LLM stream → Tool executi
 - **Tools** — `trait Tool { fn name() -> &str, fn run() -> Result<String> }`, 28 impls, gated by `Harness`.
 - **Shell safety** — `tool/shell_filter/` blocks credential leaks and destructive git commands.
 
+### Company Pipeline (Division Architecture)
+
+- **5 divisions** in `src/app/subagent/division.rs`: Strategy, Engineering, Quality, Security, Documentation.
+- **Pipeline orchestrator** in `src/app/workflow/company.rs`: two modes:
+  - `run_company_pipeline()` — full 5-division pipeline
+  - `run_company_pipeline_quick()` — 3-division (Strategy → Engineering → Quality)
+- **Auto-CEO trigger** in `run_agent_turn()` (`actions/mod.rs`): detects complex requests via `is_complex_request()` heuristics, auto-delegates to pipeline.
+- **Override** via `/pipeline full|quick|skip` sets `MiscState::pipeline_override`, consumed on next turn.
+- **Live division progress** in TUI panel (`view/workflow.rs`): shows division name + current tool via `AgentStatus::progress`.
+- **Auto inline review** after each edit: `src/app/subagent/auto.rs` — `spawn_quick_review()` injects verdict back into LLM conversation.
+- **Background subagents** (test-gen, arch-review, security-review) fire asynchronously at turn end via `TurnEvent::SystemNote`.
+
 ## Code Documentation
 
 Every function, struct, enum, trait, module, and significant code block must have a doc comment (`///` or `//!`) that explains: