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/review-code/SKILL.md

@@ -458,7 +458,7 @@ table).
 <!-- section:phase-a -->
 ## Phase A — Parallel Review
 
-> **Canonical mechanics**: `core/skills/_shared/review-pipeline-phases.md` — keep this section in sync with the canonical Phase A–E flow. This section adds review-code-specific constants (10 dimensions, severity definitions, risk tiers, output mode, standalone-bugfix mode). Step 0 (move source issue to `review` column on Pipeline Stages board per Pattern 7.5) is inherited from the shared Phase A orchestrator actions; see `_shared/review-pipeline-phases.md`.
+> **Canonical mechanics**: `core/skills/_shared/review-pipeline-phases.md` — keep this section in sync with the canonical Phase A–E flow. This section adds review-code-specific constants (10 dimensions, severity definitions, risk tiers, output mode, standalone-bugfix mode); orchestrator actions are inherited from the shared Phase A flow.
 
 ### Standalone Bugfix Mode — Orchestrator Dispatch
 
@@ -530,6 +530,13 @@ fallback is retired with the design pipeline, [org-internal #3072] phase 3):
      emits the reviewer's output; it does NOT touch the code under review, so
      rule #7 auditor independence holds.)
    - 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.
 
    **Worktree-path rule (mandatory)**: Every file path in the reviewer prompt
    (`{FILE_SECTIONS}`, design reference paths, artifact paths) MUST be the
@@ -545,6 +552,21 @@ fallback is retired with the design pipeline, [org-internal #3072] phase 3):
    observed in the 2026-07 auto-approve retrospective (5-round convergence,
    67.7% rework fraction).
 
+   **Code-graph availability preamble (worktree sessions, [org-internal #4187])**: the main
+   checkout's `.codegraph/` index does NOT cover a session worktree
+   ([org-internal #2561]/TD-006). Before dispatch, the Orchestrator checks the worktree's
+   own index: run `codegraph_status` against the worktree root, or check for
+   `<worktree-root>/.codegraph/codegraph.db` (a bare `init.log` without the
+   db means the background `session-worktree.sh create` init is still running).
+   Include in each reviewer's dispatch preamble: (a) the worktree index state
+   (ready / building / absent), and (b) when absent or still building, the
+   ABSOLUTE path of the main checkout (which has its own `.codegraph/`) so
+   DGN/COR reviewers can query MAIN-side symbols (design baselines, frozen
+   cross-session contracts) from the main checkout's index and cite them as
+   `main:<path>:<line>`. Reviewers apply rule 6b of
+   `_shared/review-reviewer-prompt.md` (NA + INFO finding) when no index is
+   reachable at all — grep-only structural claims must never pass silently.
+
 4. Wait for all reviewers to complete. Each reviewer writes its finding JSON to
    `<runs-root>/{slug}/reviews/code/round{N}/findings-{DIMENSION_CODE}.json`
     (Tier 1 local, validated by `core/schemas/reviewer-output.schema.json`). After all