v0.1.6: sync 2026-10-03..10-15 core corpus — kanban practice fully retired (#5745), review-artifact schema validation wiring (#5656 N-04/N-06), review-code batching (#4386) + worktree codegraph preamble (#4187), gitea adapter slimming, roles yaml first-line fix (octopus main-repo commits 86047c51d..de16e8704)

core/skills/verify/SKILL.md

@@ -196,10 +196,6 @@ each missing item.
 <!-- section:phase-1 -->
 ## Phase 1 — Load Verification Context
 
-> **Pipeline stage**: if the source issue exists, move it to the `verify`
-> column on the Pipeline Stages board per `_shared/gitea-write-patterns.md`
-> Pattern 7.5. Skip if no source issue exists.
-
 Read the upstream artifacts. DAG task/milestone mode (the live path — see
 the DAG branch below for its read map):
 
@@ -310,6 +306,20 @@ gate fingerprint is keyed on the working tree (SHA + uncommitted state +
 untracked), so it covers pre-push/headless states the same-SHA CI clauses
 cannot.
 
+### 2.0b — Gate Records as Deterministic Inputs ([org-internal #5656] N-04)
+
+Mechanical checks MUST be grounded in gate records (`gate` tool result
+metadata), never in a model's transcription of command output:
+
+- Cite `exit_code` verbatim — canonical block from
+  `packages/octopus/src/gate/consume.ts`: `gate <id> (<tier>):
+  exit_code=<n> -> green|red`, plus `duration_ms` / `ci_run_id` when present.
+- `exit_code === null` (timeout/abort) is NO verdict — rerun required; a
+  pass claim cannot stand on it.
+- A green verdict-cache hit (`metadata.verdict_cache.key`) satisfies the
+  check the same as a fresh run (content-addressed, same fingerprint).
+- Narration drift (claim != record) is itself a verification finding.
+
 ### 2.1 Full Test Suite
 
 ```bash
@@ -1203,10 +1213,7 @@ If the user confirms, invoke the commit workflow per
 
 An iteration is NOT Done until all code is committed in git history.
 
-After the commit gate passes, move the source issue to the `done` column on
-the Pipeline Stages board per `_shared/gitea-write-patterns.md` Pattern 7.5.
-Skip if no source issue exists. `done` is a stage column marker; issue
-closing follows the lifecycle per `issue-checklist-sync.md` 归档动作.
+Issue closing follows the lifecycle per `issue-checklist-sync.md` 归档动作.
 
 To notify workflow completion, call the `signal_stage_done` tool.