forge-reconcilelisted

# forge-reconcile Work sometimes lands outside the forge loop: a manual hotfix, a teammate's commit, a Claude session that skipped `forge-build`. The code moves, but the tracker, specs, and context files never hear about it — and every later session works from a map that's missing roads. This skill closes that gap: detect the out-of-band (OOB) commits, understand them, and **adopt them back into the process** as first-class history (retro-spec + tracker entry), or consciously dismiss them. Division of labor with the neighbors: `forge-audit` fixes what the context files *say* (docs vs code). `forge-reconcile` fixes what the process *knows* (git history vs tracker/specs). A reconcile often ends by recommending a narrow `forge-audit` pass when the adopted work changed architecture or scope. ## Argument Text after the command narrows the scope (e.g. `/forge-reconcile last 5 commits` or `/forge-reconcile abc1234`) — restrict analysis to the matching commits. No argument → everything the detector reports. ## First: detect Run the deterministic detector (read-only): ```bash bash "${CLAUDE_PLUGIN_ROOT}/skills/forge-reconcile/scripts/detect-oob.sh" ``` Interpret the verdict: - `NO_CONTEXT` — no tracker; nothing to reconcile against. Point the user to `forge-init`. - `NO_EPOCH` — the tracker exists but was never committed, so there is no adoption baseline. Recommend committing the context dir first; offer to do it. - `CLEAN` with `dirty_tree: no` — the process trail is com