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/_shared/review-pipeline-phases.md

@@ -41,11 +41,6 @@ in `_shared/gitea-write-patterns.md`.
 
 **Orchestrator actions**:
 
-0. **Move the source issue to the `review` column** on the Pipeline Stages
-   board per `_shared/gitea-write-patterns.md` Pattern 7.5. Skip if no
-   source issue exists. The review stage is a single board column covering
-   all review targets (DAG single gate / code review / audit-process).
-
 0.5. **Initialize the review-status file** (round 1 only). The Orchestrator
    creates `<runs-root>/{slug}/reviews/{stage}/status.json` before dispatching
    round 1, with the full schema-required field set
@@ -111,6 +106,13 @@ in `_shared/gitea-write-patterns.md`.
      `core/skills/_shared/review-orchestrator-rules.md` — Default
      Explorer Permissions).
    - Temperature: 0.1 (deterministic output).
+   - StructuredOutput mount ([org-internal #5658]): pass `format: { type:
+     "json_schema", schema: <the reviewer-output.schema.json contents you
+     read at prompt build time> }` on the task dispatch — the reviewer's
+     final emission is schema-enforced (malformed verdict/severity/summary
+     args are rejected with field-path repair feedback inside the reviewer's
+     own loop). The findings FILE remains the canonical Tier-1 artifact; the
+     structured output mirrors it as a self-check.
 
 4. Wait for all {REVIEWER_OR_AUDITOR}s to complete. Each reviewer writes its
    dimension result to the skill's configured findings sink:
@@ -171,6 +173,11 @@ in `_shared/gitea-write-patterns.md`.
      `tier1-local` skills; `/tmp/octopus/...` for `tier2-comment` skills)
    - `permissions`: read + write + edit + bash + glob + grep (all allow)
    - `temperature`: 0.1
+   - `format` ([org-internal #5658]): `{ type: "json_schema", schema: <the
+     synthesis.schema.json contents you read> }` — the Synthesizer's final
+     emission is schema-enforced (malformed verdict/dimension args rejected
+     with field-path repair feedback in-loop). The posted fenced JSON block
+     remains the canonical artifact; the structured output mirrors it.
    - Foreground (the Orchestrator waits for completion).
 
 3. The Synthesizer: