queen: order work by value -- cost of delay over size (WSJF) and the number of issues it unblocks #9971

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

specs/queen/priority.t27 orders issues by label level and aging only. It cannot tell an issue that unblocks 105 others (as bootstrap/src/compiler.rs did on 2026-10-08, see specs/queen/holds.t27) from a leaf task, and it ignores size.

Industry reference: WSJF (cost of delay / job size, Reinertsen); critical-path and HEFT list scheduling put the tasks with the longest dependent chain first.

User Scenarios

• As the Queen choosing among eligible issues, I take first the one whose completion unblocks the most other issues (by held paths and by blocked by #N links), then the best cost of delay per size.
• As the owner, a label still wins: value only orders issues inside one priority level.

Requirements

• unblock_score(n_blocked_by_paths, n_blocked_by_links) -> u32, size_class(boundary_paths, est_lines) -> u8, wsjf(cost_of_delay, size) -> u32.
• outranks_by_value(a, b) is only the tie-break after the level from priority.t27.
• Pure integer math; every weight documented.

Success Criteria

• Tests: an unblocker beats a leaf at the same level; a label level beats any value; equal values fall back to issue age.
• Invariant: the order is irreflexive and transitive on the tested sample.
• 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/value.t27
• .trinity/seals/queen_QueenValue.json