docs: record 0.1.0 release, registry install verification and nightly proof

.opencode/state/status.md

@@ -1,11 +1,14 @@
 # Project status
 
-Updated: 2026-10-14 (phase 1 implementation, ~90% done)
+Updated: 2026-10-14 (Phase 1 COMPLETE — quality gate passed)
 
 ## Current phase
 
-Phase 1 (plugin package) — implementation complete and runtime-verified locally. Remaining:
-first registry release (1.10) + Gitea secret provisioning, then Phase 2.
+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).
 
 ## Done
 
@@ -38,21 +41,22 @@ first registry release (1.10) + Gitea secret provisioning, then Phase 2.
 
 ## Known gaps / risks
 
-- 1.10 not done: package never published to the Gitea registry yet; npm-name plugin entry
-  (resolving through `exports`) unverified — local directory entry verified instead.
-- `PACKAGE_TOKEN` Gitea secret must be provisioned by the repo admin before nightly can publish
-  or commit back.
-- Nightly runner network access to github.com unverified (fallback: Gitea mirror of upstream).
+- 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.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.
 - Windows-only smoke quirk: fixture temp dir deletion can lag (EPERM warning, harmless); CI is
   Linux.
-- Background subagents in V2 (env-gated in V1) not verified; orchestrator text works either way.
 - `request.body` overlays accepted but not sent by the V2 runner — agents avoid them.
+- Skill id collisions with pre-existing file-based installs resolve to the file copy (silent).
 
 ## Next steps (exact)
 
-1. Run `npm run format`, `npm run check`, `npm test`, `npm run build`; commit workflows/smoke/docs.
-2. Push to origin; ask owner to add `PACKAGE_TOKEN` secret (write:package + write:repository).
-3. 1.10: `node scripts/release.ts` with SERVER_URL/REPOSITORY/SHA/TOKEN env (or dispatch a manual
-   release workflow) → verify `plugins: ["@haylan/opencode-pocock"]` installs from the registry in
-   a clean fixture; record in docs/runtime-checks.md.
-4. Phase 2 per TODO.md (2.2 guardrails already implemented in 1.4 — verify mapping note; 2.4–2.7).
+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.
+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.