reconcilelisted

Reconcile an idea's recorded truth with product reality. Load `method-rules` first, **then read the `method-rules-maintenance-rules` skill in full** — it is the law here and it is not in the default bundle (method-rules §10), so loading it is this skill's own first step; this skill is only the procedure. Works at ANY drift distance (a week of small changes or 80% of the MVP rewritten) and never requires that Claude built anything: session memory is not a source. Idea slug = $0 (if missing, infer from `ideas/*/state.json` with LOCK passed or a locked cycle; ask if ambiguous). Read `state.json` first. If no cycle has reached LOCK, stop: pre-LOCK corrections are pivots (stage skills + decision-log), not reconciliation. ## Step 0 — Open the transaction 1. Allocate `reconcile_id` (lowercase `r-YYYYMMDD-NN`, next unused). Set `maintenance.active_reconcile`; create draft dir `reconcile/<reconcile_id>/`. 2. If a prior `active_reconcile` exists, resume it idempotently (same id, re-verify its draft) — never two in flight. 3. Hash-verify the current head baseline and its manifest (if any) BEFORE reading further; mismatch = surface to user as tampering/corruption finding, do not proceed silently. ## Step 1 — Reality intake (reality declares first; docs stay closed) 1. Read `maintenance.reality_sources`. If empty, elicit sources from the user (repo path, deploy URL, changelog, billing/analytics) and register them (journal `source-registry-change`; new sources ONLY via user approval —