AF1: specs/claw/recipes.t27 -- the CI healing recipe table as data #9282

One row per verified healing recipe, as data, in the shape of T1 specs/claw/gates.t27 (parallel arrays + tests that pin the table).

Columns

• GATES[i] -- which gate the recipe heals (must exist in the gates inventory)
• KINDS[i] -- short slug (types-ledger-bless, dupe-bodies-bless, ...)
• CMDS[i] -- the fix command (the one the loops run by hand today)
• CONDS[i] -- preconditions that MUST hold before running (wave quiet >= 30 min, re-scan after reset, restore _why_entries_rose, never regen when the compiler emits uncompilable bytes, ...)
• CLASSES[i] -- R_AUTO (run + PR + auto-merge) / R_OWNER (report the keystroke, never execute)

Seed set (all verified by the loops 2026-10-06..10-12)

types ledger bless; types classified verdicts; dupe bodies bless; assertionless bless; elab baseline update (known-debt class only); seal gen-drift re-save; seal staleness re-seal; suite expectations bless; gate-topology classify (foreign net-zero rule); L2 stale-gen regen (compiler guard); update-branch / local merge-commit route; W628 cap raise + audit note; GraphQL 504 retry; owner-approved-foreign label (OWNER, always the owner's click); gates.rs dead include_str test (OWNER until the policy PR merges).

Tests

Census by class; gate+kind uniqueness; every row has command and non-empty conditions; class mapping pins (label = OWNER, always); the types gate carries TWO recipes (bless AND verdicts -- the #9145 lesson: a bless alone leaves the classified gate red).

Contract consumer: AF2 (engine), AF3 (tri claw autofix). Part of #9271.