🤖 Guidance pass C: rewrite steering sentences with counterweights

plugins/spire/skills/implementation/references/run-log.md

@@ -31,14 +31,16 @@ Rules:
 
 ## Handoff note (one per block, written by the block's owner)
 
+A few lines per block: findings, not narration. "none" is the normal answer for deviations and flags, and a real deviation or doubt is never left out.
+
 ```markdown
 ### Block <N.M> — <title>
 
 - Model: <exact id>
 - Start / end: <`date` output> / <`date` output>
-- Done: <what changed, in a few lines>
-- Deviations from plan: <what, and why> — or "none"
-- Flagged for review: <anything the reviewer should look at, e.g. a semantic you were unsure of>
+- Done: <what changed, in one or two lines>
+- Deviations from plan: <what, and why, including size well over the plan's estimate> — or "none"
+- Flagged for review: <a point you are unsure of, e.g. a semantic the plan left open> — or "none"
 - Left for later: <work deferred to a later block or phase>
 - Expected broken: <areas that do not build or pass yet, and which block fixes them>
 - Commits: <hashes>
@@ -51,8 +53,8 @@ Rules:
 
 - Gate: <command> — <result>
 - Tests: <command> — <result> (fallout fixed in block <N.M>)
-- Flags for the reviewer: every deviation and every "flagged for review" line above, one per bullet, with its block.
-- Not run / untested: <anything the tests do not cover>
+- Flags for the reviewer: the deviations and flags from the block notes above, one line each with its block — or "none" when the notes have none.
+- Not run / untested: <behaviour the plan names that no test or gate ran> — or "none"
 - Status: provisional until review, fix pass and re-check close.
 ```