claw-code/rust/crates/rusty-claude-cli/tests
Yeachan-Heo 8f53524bd3 Make backlog-scan lanes say what they actually selected
The next repo-local sweep target was ROADMAP #65: backlog-scanning
lanes could stop with prose-only summaries naming roadmap items, but
there was no machine-readable record of which items were chosen,
which were skipped, or whether the lane intended to execute, review,
or no-op. The fix teaches completed lane persistence to extract a
structured selection outcome while preserving the existing quality-
floor and review-verdict behavior for other lanes.

Constraint: Keep selection-outcome extraction on the existing `lane.finished` metadata path instead of inventing a separate event stream
Rejected: Add a dedicated selection event type first | unnecessary for this focused closeout because `lane.finished` already persists structured data downstream can read
Confidence: high
Scope-risk: narrow
Reversibility: clean
Directive: If backlog-scan summary conventions change later, update `extract_selection_outcome`, its regression test, and the ROADMAP closeout wording together
Tested: cargo fmt --all --check; cargo clippy --workspace --all-targets -- -D warnings; cargo test --workspace; architect review APPROVE after roadmap closeout update
Not-tested: Downstream consumers that may still ignore `lane.finished.data.selectionOutcome`
2026-04-12 09:54:37 +00:00
..
cli_flags_and_config_defaults.rs Prevent cross-worktree session bleed during managed session resume/load 2026-04-11 16:08:28 +00:00
compact_output.rs feat: b5-git-aware — batch 5 upstream parity 2026-04-07 14:51:26 +09:00
mock_parity_harness.rs fix(cli): 6 cascading test regressions hidden behind client_integration gate 2026-04-08 14:54:10 +09:00
output_format_contract.rs Make the CLI point users at the real install source 2026-04-12 04:50:03 +00:00
resume_slash_commands.rs Make backlog-scan lanes say what they actually selected 2026-04-12 09:54:37 +00:00