🤖 Guidance pass D2: one home for harness rules in spawning-claude-code

plugins/spire/skills/implementation/SKILL.md

@@ -50,7 +50,7 @@ One option is **trunk and gremlins**. At intake the builder reads the build plan
 
 ## Phase review, fix, stop
 
-- A **fresh** reviewer that did not build the phase, dispatched outside the build, stamps its model id in its report header. A review without a stamped id does not count.
+- A **fresh** reviewer that did not build the phase, dispatched outside the build (by Igor; the `reviewer` agent holds its rules).
 - It is adversarial: it runs the gates, traces concrete scenarios, and **reads every flag in the handoff notes**, answering one only where it changes a finding or a verdict. In the phase's diff it looks for **weakened checks** (loosened assertions, downgraded errors, deleted tests) and **tests that cannot fail**, and reports each one it finds as a finding.
 - It ends with a short **size and unrequested surface** section: size against the plan's estimate, and what was built that no plan box asked for. The reviewer lists; Igor and the user decide, and an unplanned addition may be a good one.
 - **One fix pass** over all findings. Minors are fixed in that pass or logged as follow-ups.
@@ -64,8 +64,7 @@ One option is **trunk and gremlins**. At intake the builder reads the build plan
 
 ## Spawning and models
 
-- Read `references/spawning-claude-code.md` before dispatching. In short: sequential work runs in the foreground; resume agents only from the session root; leaf briefs say "do this yourself; do not dispatch further agents".
-- Every plan, handoff note and review stamps the exact model id the agent ran on.
+- Read `references/spawning-claude-code.md` before dispatching. Its rules of thumb are the home of the harness rules: foreground for sequential work, resume only from the session root, model pins, stamping the model id, leaf briefs.
 - Model traits are in `references/models.md`: dated observations, not law.
 
 ## Writing things down