6a957560bd
Recent OMX dogfooding kept surfacing raw `[OMX_TMUX_INJECT]` messages as lane results, which told operators that tmux reinjection happened but not why or what lane/state it applied to. The lane-finished persistence path now recognizes that control prose, stores structured recovery metadata, and emits a human-meaningful fallback summary instead of preserving the raw marker as the primary result. Constraint: Keep the fix in the existing lane-finished metadata surface rather than inventing a new runtime channel Rejected: Treat all reinjection prose as ordinary quality-floor mush | loses the recovery cause and target lane operators actually need Confidence: high Scope-risk: narrow Reversibility: clean Directive: Recovery classification is heuristic; extend the parser only when new operator phrasing shows up in real dogfood evidence Tested: cargo fmt --all --check Tested: cargo clippy --workspace --all-targets -- -D warnings Tested: cargo test --workspace Tested: LSP diagnostics on rust/crates/tools/src/lib.rs (0 errors) Tested: Architect review (APPROVE) Not-tested: Additional reinjection phrasings beyond the currently observed `[OMX_TMUX_INJECT]` / current-mode-state variants Related: ROADMAP #68 |
||
|---|---|---|
| .. | ||
| api | ||
| commands | ||
| compat-harness | ||
| mock-anthropic-service | ||
| plugins | ||
| runtime | ||
| rusty-claude-cli | ||
| telemetry | ||
| tools | ||