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
..
.claw/sessions	feat(runtime): typed task packet format for structured claw dispatch	2026-04-04 00:40:20 +09:00
src	Keep latest session selection tied to real session recency	2026-04-12 07:49:32 +00:00
tests	Make backlog-scan lanes say what they actually selected	2026-04-12 09:54:37 +00:00
build.rs	Remove the deprecated Claude subscription login path and restore a green Rust workspace	2026-04-11 17:24:44 +00:00
Cargo.toml	Close the clawability backlog with deterministic CLI output and lane lineage	2026-04-05 18:41:02 +00:00