Four red gates, one cause
PR #3664 adds one skill and four checks went red. They are not four problems. Each gate asks for a different piece of the same checklist that adding a user-invocable skill triggers. Click a gate to see what it actually wanted.
The one that is not a wiring oversight
MAX_USER_INVOCABLE_SKILLS=35 is a deliberate cap on the size of the
/ork: menu, and paired-probe is the 36th. That is a design decision, not
a defect: the limit did its job by forcing the question. It was raised to 36 with the
reason recorded in the file's own running history, and the debt was named rather than
hidden, because the same comment counsels funding additions by demoting a zero-use
skill chosen from analytics. Eighteen such candidates remain outstanding.
Why verify is the right chain parent
The island gate needs one automated reach. /ork:verify grades work and
returns a merge verdict, so it is exactly where a check that cannot disagree does the
most damage: it converts an unearned PASS into a shipped change. The reference lives
under a heading that states the failure, not the tool.
| Gate | Wanted | Now |
|---|---|---|
| Manifests | an activation channel | chained from verify |
| Compliance | an eval spec | paired-probe.eval.yaml |
| Performance | room under the cap | 35 → 36, reason recorded |
| CI Summary | the other three | aggregates green |