skill-vetting-hardening-archaeologylisted

# skill-vetting hardening — failure archaeology Dead ends from the PR #83 campaign (branch `workstream-b-skill-vetting-2026-07-25`, merged `7cd2af6` 2026-07-26). Most were caught PRE-MERGE by cross-family review, so the residue is in commit history and in-code comments, not `revert`s. Read the disposition tag first — it says what kind of corpse this is. **What to DO at any tripwire below (the Done for every entry).** When a tripwire fires: (1) STOP the proposed mechanism/idea; (2) read the entry's disposition tag, standing rule, and residue; (3) load the owning skill the entry names, or — most entries name none — the skill that owns the affected surface (a live invariant → `skill-vetting-security-invariants`; the harness/evidence → `mutation-matrix-evidence-discipline`; neither → follow the fallback); (4) either satisfy that skill's Done-check for the real change, or record the item unresolved and escalate. **Done:** no dead mechanism survives in the plan or diff, AND either a named owning-rule check passes or the item is recorded unresolved with its disposition. An entry with no explicit **Residue** line has none tracked — treat that absence as "no residue recorded", not "nothing to check". **Owner map (each dead end → the installed rule that owns its current surface):** quoting → `skill-vetting-security-invariants` INV-7; normpath & dot-path → INV-4; transient/steady-state ordering → INV-3 (`partial`/`skip_baseline`); unreachable/ equivalent → `mutation-matrix-evidence-d