test: 2.5 orchestration run via local qwen3.8-27b (PASS)

.opencode/state/status.md

@@ -1,14 +1,16 @@
 # Project status
 
-Updated: 2026-10-14 (Phase 1 COMPLETE — quality gate passed)
+Updated: 2026-10-14 (2.5 orchestration run PASS — quality gate + end-to-end run both green)
 
 ## Current phase
 
-Phase 1 done: plugin installs, loads in OpenCode v2.0.29, skills inject, package builds,
-`@haylan/opencode-pocock@0.1.0` published to the Gitea registry (release run 5684), install-from-
-registry verified, nightly workflow proven (dispatch run 5685: github.com reachable, no-change
-early exit). Remaining: Phase 2.5 (manual token-spending orchestration run) and 2.7 (observe a
-week of nightlies).
+Phase 1 done AND 2.5 done: plugin installs, loads in OpenCode v2.0.29, skills inject, package
+builds, `@haylan/opencode-pocock@0.1.0` published to the Gitea registry (release run 5684),
+install-from-registry verified, nightly workflow proven (dispatch run 5685: github.com reachable,
+no-change early exit), and a full manual orchestration run of the `pocock` orchestrator against a
+3-ticket fixture (omniroute/qwen3.8-27b) is **PASS** — all 3 tickets built by parallel workers,
+reviewed, fixed, merged, clean exit, no product bugs. Remaining: 2.7 (observe a week of
+nightlies).
 
 ## Done
 
@@ -41,8 +43,12 @@ week of nightlies).
 
 ## Known gaps / risks
 
-- 2.5 not done: no token-spending end-to-end orchestration run yet (pocock building a fixture
-  spec with parallel workers). Drift/unit/smoke suites cover the deterministic surface.
+- 2.5 DONE (2026-10-14): full orchestration run PASS on omniroute/qwen3.8-27b — see
+  docs/runtime-checks.md § "2.5 orchestration run". Noted env-only quirks: skill id collision
+  resolves `code-review` to the user's global `~/.agents/skills` copy (documented, not a plugin
+  bug); user's codebase-memory "graph-first" rule rejected one orchestrator `glob` (recovered via
+  `find`). Local 27b took ~63 min; reviewer subagents stream output only on completion (looked
+  stalled, was not). No product bugs found.
 - 2.7: nightlies need a week of green runs before "stable" is declared; first scheduled run
   2026-10-15 03:30 UTC.
 - Background subagents in V2 (env-gated in V1) not verified; orchestrator text works either way.
@@ -53,10 +59,10 @@ week of nightlies).
 
 ## Next steps (exact)
 
-1. 2.5: manual orchestration run — fixture project with spec + 3 tickets (2 independent, 1
-   blocked), run `opencode --agent pocock`, verify worktree loop/merges/review/permissions;
-   record in docs/runtime-checks.md.
+1. ~~2.5: manual orchestration run~~ DONE 2026-10-14 (PASS, see docs/runtime-checks.md).
 2. Watch nightly runs for a week (2.7); on upstream release (17 pending changesets), verify the
    full sync→generate→publish→commit-back cycle end-to-end.
 3. Then declare stable and announce; keep classification.json current when upstream promotes
    in-progress skills.
+4. (Optional, owner) Decide whether to fold the 2.5 agent-improvement suggestions (truncated-skill
+   note, non-ff resume reminder) into agents/*.md — they are in the runtime-checks.md report.