gate-checklisted

Run a gate check. Load the `method-rules` skill first, then load the `method-rules-gate-contracts` skill (Skill tool) — the per-gate contract is the law here; do not improvise requirements. **If and only if gate == BP**, also load the `method-rules-gate-contracts-bp` skill: BP's contract is a satellite so that the other nine gates never carry it in working context (v1.7.0, the maintenance-rules §10 precedent). Arguments: idea slug = $0, gate = $1 (if missing, read `state.json` and infer from active work). ## Layer 0 — pre-formal ceremonies (run BEFORE Layer 1, so Layer 1 can verify their output) **Mechanical first step, before any ceremony (v1.13.0).** Two lightweight detectors run before anything else in Layer 0 — both read only `state.json` and tracked artifacts, never session memory (method-rules §1): 1. **Pre-LOCK reconcile** — `node "${CLAUDE_SKILL_DIR}/../../scripts/reconcile-pre-lock.js" <idea-dir> --json`, and **only while no cycle in this idea has reached LOCK** (the mirror-image guard to the `reconcile` skill's own "if no cycle has reached LOCK, stop" rule — this script refuses to run once one has, and says so). It surfaces deterministic divergences (a proposed patch each) and non-deterministic open questions (never a proposed patch — reading artifact prose is a judgment call). Present both to the user; apply a proposed patch, if the user confirms it, via `state-write.js` only — never automatically. Findings append to `decision-log.md` under `type: "pre-lock-rec