TRI CLAW autofix: take the CI/CD routine off the user (all healing experience in, all through .t27/t27c/t27b/t27o) #9281

Owner directive 2026-10-12: autofix for TRI CLAW must take the CI/CD routine off the user. All healing experience from every related repo goes INTO TRI CLAW. Everything through .t27 + t27c + t27b + t27o -- no foreign glue.

Scope

• Every red gate that has a known, verified healing recipe gets fixed automatically by TRI CLAW: run the fix, open the PR, arm auto-merge. The user never babysits a ratchet again.
• Fixes that are owner-gated (labels, waivers, route picks) are never executed -- they are reported with the exact one keystroke, per the standing no-person-in-the-loop-escalation rules.
• Safety preconditions are data too (wave quiet windows, re-scan-after-reset, audit-note restoration), because the recipes were learned the hard way -- each one carries the trap it was learned from.
• The whole engine lives in .t27 specs lowered by t27c and executed through t27b/t27o. The GitHub App shell and CLI stay thin I/O.

Sub-issues

• AF1 recipes-as-data spec (specs/claw/recipes.t27)
• AF2 engine (matcher + runner, .t27-native)
• AF3 tri claw autofix wiring
• AF4 experience harvest from all related repos

Part of epic #9271. Builds on T1 specs/claw/gates.t27 (merged) and T2 tri claw (#9277).