queen: a hot file is named and split -- a path that shuts out more than N issues becomes a finding with a split plan #9975

Part of the dispatch roadmap epic #9976. Industry reference and the measured gap are below.

Measured 2026-10-17: 166 issues skipped as fileConflict. In a sample of 12, scripts/tri_loop/t27b.py sat in 5 Boundaries, and bootstrap/src/main.rs, bootstrap/src/compiler.rs and cli/tri/src/main.rs in 4 more. On 2026-10-08 bootstrap/src/compiler.rs alone shut out 105 issues. Nine open PRs touch these four files, some untouched since 2026-10-05.

Industry reference: lock-contention profiling -- a hot lock is split or made finer (striped or per-region locks); trios#1888 already has a merge-side region check behind TRIOS_QUEEN_REGIONS.

User Scenarios

• As the Queen's doctor (specs/queen/self_health.t27), when one path shuts out more than N issues, I report it as a hot file with the count and the holders, every tick, on the board.
• As the owner, I get a split plan for each hot file: region holds for it, or its rules moved into .t27 so the hot file shrinks.

Requirements

• is_hot(blocked_count, threshold) -> bool and hold_granularity(path_kind, blocked_count) -> u8 (whole file or region), the threshold a named constant with its reason.
• A path the only-t27 policy forbids bees to edit by hand (specs/policy/own_language.t27) is not held by a bee task at all: such a task needs the owner label first, and that is its skip reason, not fileConflict.

Success Criteria

• Tests: the 2026-10-08 case (105 blocked) is hot; a path with 2 blocked is not; a forbidden-to-bees path yields the owner-label reason.
• 0 surviving mutants.

Rules for the bee

• Only .t27 is hand-written; the seal is tool-written (t27c seal --save after a fresh release build on the Railway lab). No .py, .rs, .ts, .sh or .yml edits.
• Every rule gets test blocks and at least one invariant; run tri mutate spec on the new file (on the lab) and kill every surviving mutant. The bar is specs/queen/dispatch.t27 in PR test(queen): kill the 39 surviving mutants of specs/queen/dispatch.t27 #9961: 0 survivors, 0 vacuous tests.
• Write the measured numbers that motivate the card into its header comment, as specs/queen/holds.t27 does.
• Wiring into the runtime (gHashTag/trios) is a separate step: it lands as generated code once gen-ts lowers pure function bodies (gen-ts: lower the bodies of pure functions, so a host imports a spec's rule instead of copying it #7871 / PR gen-ts: lower the bodies of pure functions #7872). Do not hand-write TypeScript here.

Boundary

• specs/queen/hot_files.t27
• .trinity/seals/queen_QueenHotFiles.json