meta-reviewlisted

# Meta-Review The deliberate pass that catches what incremental work misses. **Claude is the reasoner; a hook can only surface markers - it cannot decide what is missing or fix it.** Run this; do not delegate the judgment to a script. ## When to run - At a milestone, before a release/cutover, or when the user asks "am I missing anything?", "is this optimized?", "did we only fix the instance?", or "is anything wrong?". - After a stretch of incremental fixes (each fix tends to spawn an unscheduled follow-up). ## The six checks (do each, then act) 1. **Parked-but-unscheduled.** Grep the canonical plan for `PARK|DEFER|TODO|OPTIONAL|candidate|later`. For each: is it in the recommended order with a rationale, or explicitly justified-parked? If neither, schedule it now (priority + one-line why). Standing rule: defer -> schedule in the SAME edit. (The `meta_audit_on_stop` hook in this suite surfaces the mechanical version of this at turn-end.) 2. **Instance-only fixes (the durability check).** For each notable fix in recent history (git log, plan, notes), ask: *did we fix the instance, or install a mechanism so it cannot recur?* A fix that relies on "Claude will remember" is instance-only. Durable forms: an encoded standing rule, a test/regression, a self-checking harness, a small mechanical hook, or a structural change. Convert the real ones; not everything needs a mechanism (judgment calls stay judgment calls). 3. **Optimization (code/structure/perf).**