8d4b1c7f46
Pure repo -> board decision function (Backlog::Resolver) plus the `resolve` os-backlog subcommand: given repo path, .cc-os/config contents, and a board-name inventory (all passed in — no filesystem or network access in the resolver itself), returns exactly one of "use <board>" / "activate <archived board>" / "stop-and-discuss". An explicit config board takes precedence; otherwise the board name is derived from the repo/client dir basename with project inferred from ~/dev vs ~/clients. Unmapped paths, and configured-but-unmatched boards, both resolve to stop-and-discuss rather than silently falling back. Pure Ruby unit tests, no network. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01XknQRvihHDpYE47RTmUR4N |
||
|---|---|---|
| .. | ||
| os-adr | ||
| os-backlog | ||
| os-doc-hygiene | ||
| os-orchestration | ||
| os-status | ||
| os-vault | ||