docs(auto-combo): complete the mode pack table and gate what it claims

[maxmad64bis]

Summary

docs/routing/AUTO-COMBO.md documents four mode packs. Six ship. Its numbers are wrong too — it prints 0.14 where modePacks.ts says 0.1333.

The other half is that nothing was watching. Four documents state a scoring-factor count and check:docs-counts covered none of them. Wiring them up turned the gate red on seven real drifts:

✗ ARCHITECTURE.md        — "9-factor"  — code has 15      ✗ ARCHITECTURE.md   — "4 mode packs" — code has 6
✗ REPOSITORY_MAP.md      — "9-factor"  — code has 15      ✗ REPOSITORY_MAP.md — "4 mode packs" — code has 6
✗ RESILIENCE_GUIDE.md    — "13-factor" — code has 15
✗ AUTO-COMBO-GUIDE.md    — "5 factors", "13-factor"       ✗ SKILL.md — "13 factors" — code has 15

ARCHITECTURE.md didn't just have the wrong number — it named nine factors that aren't the engine's, and its four "mode packs" (coding, fast, cheap, smart) are the auto/* request prefixes, not packs.

A product fact fell out of writing the table. No pack sets quality, and applying a pack replaces the weight map wholesale (weights = pack in engine.ts, not a merge). So quality carries 0.03 by default and normalizes to 0 under any pack — pick a mode pack and the observed-quality signal stops voting. Documented, not changed.

The gate reads pack names from the module via the tsx subprocess that already reads every other code-derived count, so there's no hand-rolled TypeScript parser to go quietly wrong. Its count pattern matches the three spellings the docs actually use (6 curated **mode packs**, 6 pre-defined weight profiles, 4 weight profiles) — matching only the first left the other two unguarded, which is how the stale 4 weight profiles line in AUTO-COMBO.md itself surfaced. On the reference document a missing claim now fails rather than passing, so rewording a sentence past the pattern can't silence it.

The dashboard was behind too: four of six packs offered, and the default strategy labelled Rules (6-Factor Scoring). The count is gone from the label rather than corrected — nothing reads selector labels, so a number that's right today goes stale unnoticed. chaos-mode is now offered as Chaos Mode (fault injection — testing); next to "Ship Fast" it would otherwise read as one more routing preference.

Related Issues

• Related to fix(docs): Auto-Combo factor count is read from DEFAULT_WEIGHTS #11545

Validation

• Change type: other (docs + CI gate) / UI
• Focused tests and category gates from the golden path
• npm run lint
• Reconciled with the current active release base; focused checks rerun afterward
• Production-code changes include a new or updated automated test in this PR

The gate output above is the pre-fix run with the new checks wired in; after the corrections check:docs-counts exits 0. The dashboard test failed on two counts before the change — the missing packs, and the factor count in the label.

npm run lint exits 2 here and on an untouched checkout of the base alike (suppressions left that do not occur anymore, zero reported errors).

Tests Added Or Updated

• tests/unit/check-docs-counts-sync.test.ts (extended: pack-name validator, token-boundary matching, the three count spellings, required-claim behaviour)
• tests/unit/dashboard/intelligent-routing-options.test.ts (new: every shipped pack is offered, no strategy label states a factor count, the fault-injection pack says so)

Coverage Notes

Nothing in src/, open-sse/, electron/ or bin/ changes behaviour: the only code touched is a selector option list and two labels, both covered by the new dashboard test. The gate script's added functions are pure and unit-tested.

Reviewer Notes

• The pack-name check uses a token boundary, not includes. ship-fast is a substring of ship-fast-v2, and a doc shouldn't pass by naming a pack that doesn't ship.
• REPOSITORY_MAP.md shows 18 changed lines for a one-cell edit: the cell grew by a character and lint-staged reformatted the table. Same for AUTO-COMBO-GUIDE.md, which wasn't prettier-clean on the base.
• Each pack sums to 0.9999 at four decimals, not exactly 1.0. The text says so rather than rounding the claim.
• chaos-mode and reliability-first were already reachable through auto/chaos and the engine; this only makes them selectable from the panel that claims to list the packs.