Finding (wiki-audit 2026-08-05, axis: routing)
15-scenario routing probe (plans/wiki-audit/findings/routing.md): 11/13 in-charter probes route UNIQUE; 2 AMBIGUOUS — two concerns are claimed verbatim by two domains each:
- Doc-verification gates: testing/quality (spec-artifact-checks, checks-that-cannot-pass, schema-additions-under-a-golden-gate, harness-reverse-controls) vs qa/document-verification (spec-document-gates, editing-a-gated-document). Both claim "automated checks that decide whether a spec document meets requirements". 6 pages, one concern, two domains.
- Flaky tests: testing/flaky/diagnosing-flaky-tests ("fails intermittently … on retry, in CI only") vs debugging/concurrency/intermittent-failures ("passes on retry, fails under load, fails only in CI, flaky test") — same situation, verbatim, in both triggers.
Minor: backend INDEX line says "LLM completion validation & context budgeting" — a weak attractor for ML-training queries (probe 15); "consuming LLM APIs" would repel them at the root. Also databases/index.md lacks a cross-pointer to infrastructure/data/backup-and-restore.
Proposed fix
Give each pair disjoint trigger scopes + mutual cross-pointers (e.g. "authoring the check code → testing; release-gate policy → qa" / "suite-local diagnosis+policy → testing; general intermittent failures incl. prod → debugging"). Wiki-layer edits, mechanical once scopes are agreed.
Finding (wiki-audit 2026-08-05, axis: routing)
15-scenario routing probe (plans/wiki-audit/findings/routing.md): 11/13 in-charter probes route UNIQUE; 2 AMBIGUOUS — two concerns are claimed verbatim by two domains each:
Minor: backend INDEX line says "LLM completion validation & context budgeting" — a weak attractor for ML-training queries (probe 15); "consuming LLM APIs" would repel them at the root. Also databases/index.md lacks a cross-pointer to infrastructure/data/backup-and-restore.
Proposed fix
Give each pair disjoint trigger scopes + mutual cross-pointers (e.g. "authoring the check code → testing; release-gate policy → qa" / "suite-local diagnosis+policy → testing; general intermittent failures incl. prod → debugging"). Wiki-layer edits, mechanical once scopes are agreed.