cc-os/plugins/os-backlog/lib/backlog.rb

require_relative "backlog/board_spec"
require_relative "backlog/board_ensurer"
require_relative "backlog/config"
require_relative "backlog/resolver"
os-backlog: plugin scaffold + board-ensure (refs #10) Idempotent board-ensure over the installed planka-api gem: uniform lists (Backlog/Next/Doing/Waiting/Review/Done), uniform label set (P0-P3, hitl, semi, afk-ready) with per-label color-candidate fallback since Planka's color whitelist isn't documented, the archived--<name> rename convention (activate/archive primitives; ensure never archives automatically), and the bot-created-project visibility fix (shared-type project + explicit project-manager add + null ownerProjectManagerId). Unit tests stub the client layer entirely — no live API calls. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01XknQRvihHDpYE47RTmUR4N 2026-07-10 17:35:18 +00:00			`require_relative "backlog/board_spec"`
			`require_relative "backlog/board_ensurer"`
os-backlog: routing resolver CLI (refs #12) 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 2026-07-10 17:36:08 +00:00			`require_relative "backlog/config"`
			`require_relative "backlog/resolver"`