backlog-reconcilelisted

# Backlog reconcile ## Scope and triggers Also fires on "check board rows against their specs", or when a scheduled run asks for the backlog-reconcile audit of a repo. NOT for filing new items onto the board means board-registration tooling, e.g. an adopter's own intake skill. This kit's own `docs/FEATURES.md`/`docs/workflow-paths.md` pair is `topology-drift`'s territory, maintainer-only, never this skill's. ## Overview Audit a repo's git-tracked `_meta/BACKLOG.md` Active queue against reality and ship the fixes as a PR. This is the backlog-reconcile instance of `docs/patterns/audit-loop.md` (the pattern doc's own "Backlog reconcile" SDLC-instances row): every adopter repo gets this schema via `/kit:adopt`, so this instance is general-purpose, not maintainer-only like `topology-drift`. ## The four slots (per the audit-loop pattern) | Slot | This instance | |---|---| | Item set | every row of the target repo's `_meta/BACKLOG.md` Active queue, enumerated via `lib/board/backlog.sh board` (id/title/status) plus a raw read of the file for each row's `Target artifact` cell | | Contract | a row's `Status` matches reality: (a) a `shipped` row not exempted by a `_meta/megagoals/` target artifact must have already dropped off the queue; (b) a `Target artifact` naming `SPEC-NNN` must point at a real file whose own `Status:` header agrees with the board's `Status`; (c) a `(tiny, no spec)` row's `executing`/`shipped` claim must have a git-log match | | Evidence class | Tier 1: mecha