declare-driftlisted

Cheap, incremental drift declaration — the counterpart to the full `reconcile` skill. Load `method-rules` **and then the `method-rules-maintenance-rules` skill** (§6 governs this skill) — it is deliberately NOT in the default bundle, so post-LOCK skills load it themselves. Never nag: declaring drift is good news for the system, not a debt. Idea slug = $0; free-text change description = rest of arguments (elicit if empty: what changed, roughly when, how they know — shipped code? config? pricing page?). ## `--release` mode (v1.5.0 — controlled MVP release declaration) Reuses this skill's existing "something happened in the world, tell the pipeline" entry point rather than inventing a new one — a controlled release is exactly that kind of event. Invoked as `declare-drift <idea-slug> --release`. 1. Preconditions: the operating cycle has reached `LOCK` (same "pre-LOCK changes are pivots, not drift" boundary as the ordinary flow below — a controlled MVP release cannot happen before the MVP itself was locked and built), and `gates.V1.status === "deferred"` with `state.post_launch_validation` present. If V1 was never deferred, there is nothing to release into — say so and stop (this mode is not a generic "we shipped" announcement; that is the ordinary drift-declaration flow below). 2. Confirm with the founder, briefly, that this MVP release is the controlled release the deferral ceremony anticipated (not an unrelated ship). No AskUserQuestion ceremony required —