docs: standardize verification handoffs and lane claims

.config/opencode/skills/verification-before-completion/SKILL.md

@@ -19,15 +19,25 @@ Use this skill before declaring work done, handing off, or approving readiness.
 
 ## Evidence Standard
 
-- Include exact commands run.
-- Include pass/fail outcomes and key output.
-- Tie evidence to each acceptance condition.
+Use the compact verification summary shape for every evidence entry:
+
+- **Goal** – what is being verified
+- **Mode** – `smoke` (intermediate checkpoints) or `full` (final completion)
+- **Command/Check** – exact command or manual check performed
+- **Result** – `pass`, `fail`, `blocked`, or `not_run`
+- **Key Evidence** – concise proof (output snippet, hash, assertion count)
+- **Artifacts** – paths to logs/screenshots, or `none`
+- **Residual Risk** – known gaps, or `none`
+
+Keep raw logs out of primary context by default. When a check fails, summarize the failure first and then point to the raw evidence. Include full output only when explicitly requested.
+
+Tie each evidence entry to an acceptance condition from the plan.
 
 ## Role Expectations
 
-- Builder and tester: no completion claim without concrete verification evidence.
-- Reviewer: reject completion claims that are not evidence-backed.
-- Coder: point to verification evidence from assigned lane before signaling done.
+- Builder and tester: no completion claim without verification evidence in the compact shape above.
+- Reviewer: reject completion claims that lack structured evidence or lane-ownership boundaries.
+- Coder: include compact-shape verification evidence from the assigned lane before signaling done.
 
 ## If Verification Fails