loop-reconcile

# Loop: reconcile Goal end-state: every deliverable chunk the run can scope exists as issues, awaiting `ready-for-agent`, and one report explains whatever it could not scope. This is the autonomous half of the reconciliation loop. When launched from a session, run it in a background agent. It runs headless: never ask the user a question mid-run. Every ambiguity resolves to a report, never to something plausible. Every report reads standalone on GitHub and never depends on chat context. All work state lives in the GitHub repository itself: issues, labels, and milestones. No project board. Every issue this skill files carries two labels: `loop-reconcile`, the mark that the loop owns it, and a scope label `loop:<doc-stem>` naming its source doc — `loop:people` for `docs/northstars/people.md`. A report is an issue too, and it carries `loop-complete` or `loop-needs-discussion` on top of those two. If a label is missing from the repository, create it. Args: an ideal-state doc under `docs/northstars/`, and optionally a repository milestone. - Given a milestone, reconcile against the milestone description. First check that the doc still backs every milestone statement: if one contradicts the doc, or the doc no longer asks for it at all, file a `loop-needs-discussion` report and stop. The doc wins on intent, and a milestone that fell behind it needs a session, not work. - Given no milestone, reconcile against the doc's Statements section and file issues attached to no milestone. ...