docs: propose 0025 CI routing gaps for docs, governance, and tooling

[undergroundrap]

Proposes decision record 0025: two CI-routing gaps and the narrow fixes.

Why

PR #11 measured the status quo: 39m33s, Full profile, success, for two new docs files (validation run 35787826906). Two findings explain the price:

1. Additions/deletions always pay Full. Get-HumCiChangeProfile sends every non-ordinary-modification to Full; both docs: accept 0024 performance north star; seed perf-debt ledger #11 files were additions.
2. Unregistered paths always pay Full. The ownership registry is 309 literal paths (307 compiler, 2 language). docs/decisions/, docs/research/, workorders/, .github/, most of docs/ — and all of tools/ — are unregistered. Every CI-tooling PR, which was most of today, pays Full.

What the record proposes

• (a) Additions/deletions under an already-owned prefix classify by path; renames classify both sides, max rank. Mode and type changes (symlink, gitlink, executable bit) explicitly stay Full.
• (b) Prefix-level ownership for docs, governance, and tooling paths, governed by one verified rule: a path rank must include the checks that consume it. The record cites the verified wiring (Invoke-HumFixedProfile adds the hygiene group unconditionally; hum-dev evidence <profile> dispatches to tools/check_all.ps1 -EvidenceTier <Profile>) and records the split it produces: docs/ and tools/ consumers are already covered at language rank; workorders/ boundary classifier is not, so its implementation must wire it in or keep workorders/ at a higher rank.
• Unknown prefixes explicitly stay Full. If accepted, the AGENTS.md routing ruling changes in the same PR as the policy code (like 0023).
• Exact prefixes/ranks and the workorders/ wiring are the BDFL call; the record proposes the shape, not the table.

Review

Claude pre-issuance review passed at 06a4f85: all four required fixes landed, branch rebased onto current main (f586f7e), diff is exactly the one new file with no deletions. Researcher-owned; no builder-lane files.

Expected CI

Full (~40 min) — by the very rule this record documents. If accepted, the implementation goes to the builder lane, and docs/tooling PRs stop paying Full.