Owner briefs carry the reviewers' standard adversarial checks; dispatch names shared-type owners #5239

Parent Outcome: #5097
Work level: Delivery · Track: Active delivery · Intended Status: In progress

Owner

The Root/fdev skills owner (same owner as #5185).

Done when

From the 2026-11-02 progress report (docs/reports/progressReports/2026-11-02-060416Z-unified-v3-progress.md), process problems 2 and 3. Defects kept being found by independent critics rather than by the authors' own checks: SDD#1158 partial apply, Algorithms#6 A* inadmissible, Algorithms#7 publish route, Game#802 ring contrast, Game#797 sizing regressions. Two parallel owners also built rival Theme types (Game#802, Game#805).

1. pnext-item (both skill roots) gains a short pre-review self-check the owner runs before requesting review:

   • Range: fuzz or property-test across the full range the API accepts, not only typical values.
   • Partial failure: for every multi-step write or effect, ask what happens on failure or kill between steps, and test it.
   • Planted bugs: disable each safety check or guard and confirm a test fails.
   • Reviewer probes: when repairing after a review, re-run all of the reviewer's probes against the new head, and add the reviewer's probe classes to their own tests.
   • Cross-cutting fixes: for a cross-cutting defect (sizing, concurrency, lifecycle), write the invariant first, then the code, not point fixes.

   Keep it concise, about 10 lines; no new gate, no new review chain.

2. Dispatch guidance (work-board-coord and/or intra-repo-parallel-work, both roots): when parallel Deliveries share a type, contract or file, the dispatch brief names the single owner of that shared surface, and the others consume it.

3. Parity and checks: skill-view parity holds and the skill checks pass, with a CHANGELOG entry.

Current deliverable

None.

Next action

Dispatch the skills owner.

Blocked on

Nothing.

Acceptance evidence

None yet.

Refs #5097