gate-criticlisted

# /gate-critic — structural validator, then critic (applier-verifies) Design Section 5.3 (`/gate-critic`) + Section 9.4 (typed artifacts + gates + applier-verifies) + Section 12 M10 row. The state machine is `draft -> submitted -> gated -> union_applied -> registered` (or `-> failed` on a FAIL verdict); `register_artifact` itself refuses a gated-type artifact that hasn't reached `union_applied` — there is no way around this loop for a gated template. 1. **Confirm the artifact is actually gate-eligible** before doing anything else — only a `template.gated=1` type_key requires this path; `trialerror artifact show --id <ART-id>` tells you the type and current status. If it's `draft` and ungated, `trialerror artifact register` alone is the right tool, not this skill. 2. **Open + submit the gate**, once the artifact itself is finished and ready for review (never open a gate on a half-written draft to "hold a place in line"): ``` trialerror gate open --artifact-id <ART-id> trialerror gate submit --id <CR-id> --by-launch <your launch_id> [--evidence '{"...":"..."}'] ``` 3. **Tier 1 — structural validator.** Mechanical, deterministic: does the artifact conform to its `template` type's required sections/fields? Every citation marker (`[[cite:ANC-...]]`) resolvable? Run `trialerror verify citecheck <artifact_id> --by-launch <id>` as part of this tier — a structural failure here should be fixed and RE-submitted, not carried into tier 2 f