[snarkipus]

Release complete — owner-approved stable 2.0.0

• Prepare 2.0.0 / v2.0.0 for stable npm latest, GitHub prerelease=false. Keep next at its historical beta.5 value; existing exact 1.x/beta pins remain available.
• Reconcile current onboarding, migration, changelog, qualification status and metadata assertions. OpenCode must be upgraded before changing the plugin pin; new admission remains >=2.2.6 <2.3, Beads minimum 1.3.1.
• All 28 runtime and packaged guidance files are byte-identical to qualified a6146d7; no runtime or asset changes, no repeat live-model campaign.
• The existing project activation configuration remains unchanged: 2.0.0 is not yet on npm, and operator activation is outside scope.

Verification

• Full suite: 218 passing tests / 11,892 assertions.
• One prepared archive, all 31 packed files match source; package smoke passed.
• Prepared rehearsal archive SHA-256: 8384377bbbad739fd0338c6bfb5656b7f746bfef3fbb2ccbf3b0d199a72d1d7a.
• Release metadata/channel validation passed for v2.0.0, latest, prerelease=false.
• Strict canonical specs 3/3; diff hygiene passed.
• Final Opus metadata-only recheck: Standards READY / Release metadata READY; accepted source/qualification review is retained. Report: Prepare stable opencode-beads 2.0.0 release #41 (comment).

Gate and limits

Owner approved the exact candidate and publication. PR41 merged as a493652 with the tested/reviewed tree preserved; postmerge CI42621474282 passed. Trusted release42621866460 published v2.0.0 to latest, prerelease=false, leaving next=1.1.0-beta.5. Final release asset and npm tarball are byte-identical SHA256 a9b6cc636c1c3699b89d70c9576cb717aea4fdc0b60e155a8ac80dbce6fc7dad; all31 extracted files match approved source. GitHub attestation and npm registry signature/provenance verified. Fresh exact npm installation/public entrypoint load passed. The rehearsal and final container digests differ, with the complete extracted file bytes unchanged. No operator/Zeus activation, o66 fix or upstream-monitoring work.

Tracker: opencode-beads-vla (one release lifecycle task, closed and synchronized after verification). Links accepted implementation evidence from closed opencode-beads-5rj.

Release: https://github.com/snarkipus/opencode-beads/releases/tag/v2.0.0
Registry: https://www.npmjs.com/package/@snarkipus/opencode-beads/v/2.0.0

[snarkipus]

Final release-metadata gate: READY (publication still held)

Exact candidate: 2321062644937247ca3f426d862139997f07e5e2. CI run42565918071 is successful on that exact head (Linux, Windows, zizmor). Parent verified all28 runtime/assets unchanged, all31 packed files match source, 218 tests/11892 assertions, exact-package smoke, stable release metadata and strict canonical specs.

Actual Claude Opus5.5, medium requested effort, same final source-review session71dc3fce-9fb7-40a3-a7eb-c833ba95d080: Read/Grep/Glob only,13 turns, completed/no error/no denials, unchanged frozen candidate. Standards READY / Release metadata READY. Report below is independent read-only review; test receipts are parent execution, not reviewer execution. Optional historical README wording/description suggestions remain nonblocking and intentionally do not reopen this frozen candidate.

Candidate rehearsal archive SHA256 8384377bbbad739fd0338c6bfb5656b7f746bfef3fbb2ccbf3b0d199a72d1d7a. It is distinct from the original qualified canary and not a published registry artifact. The unchanged trusted workflow builds its final publication archive separately; final attached asset/registry bytes, provenance and fresh exact consumer installation remain post-approval verification.

AWAITING FRESH OWNER APPROVAL: merge PR41, release v2.0.0 with prerelease=false and npm latest, leave next=1.1.0-beta.5 unchanged. No merge, tag, GitHub release, npm publication or dist-tag mutation has occurred. Project activation pin/operator/Zeus remain untouched, o66 unresolved. Beadopencode-beads-vla remains open through the gate.

---

Release-metadata review for exact candidate 2321062 (opencode-beads-vla, PR41, release/2.0.0)

I read release.patch, artifact.json, tracking.json, the current README (concentrating on the changed sections and every remaining beta/channel mention), the current qualification summary and the channel mapping in scripts/release.ts. I ran nothing and wrote nothing. The tests, smoke run, release verify and CI results are the parent's receipts, not my own runs.

Verdicts

• Standards: READY. The delta is metadata, docs and tests only. There is no runtime, guidance-asset or framework change. The release steps in AGENTS.md are covered: package.json version, a CHANGELOG [2.0.0] section with updated [unreleased] and [2.0.0] links, and both README install examples.
• Release metadata: READY. I found no material blocker.

What checks out

• Version and channel line up. package.json is 2.0.0. artifact.json says tag v2.0.0, latest, prerelease:false, which matches the stable branch of releaseChannel (scripts/release.ts:87-94). README line 64 now describes next as a separate historical beta channel and recommends an exact pin. That is consistent with leaving next on beta.5.
• Installation and migration read correctly. The upgrade section says to upgrade OpenCode first, replace the plugin entry rather than add a second one, and check /oc-beads:diagnostics. It says beta.5 stays on >=2.1.1 <2.2, and that 1.0.2 is historical. It covers the change from one Bead per invocation to authorized scope, and keeps the beta.1 status→diagnostics note. These match the owner-recommended 2.0 path, and none of it claims automatic migration.
• Qualification claims are accurate.
  • The compatibility row says "2.2.6 (accepted native and genuine-model qualification)". The text separates admission from tested patches.
  • Beads 1.3.4 is described as the fixture version only, with 1.3.1 still the supported minimum. The table stays at 1.3.1.
  • The summary's "Historical frozen README status" bullet keeps the canary digest 072d9c29… distinct from the new archive, and the SDK contract says the version/README change produces a different archive.
• Known limitations are stated honestly. o66, #57424 and "unresolved" stay in both the README and the CHANGELOG, and nothing claims recovery. The nested-decline/Stop limitation is kept.
• Test assertions match the docs.
  • tests/docs.test.ts checks both table rows by exact text, the upgrade sentence, the pins sentence, and the absence of the old "not passed live host qualification" wording.
  • The version regexes in docs.test.ts and workflows.test.ts now require 2.x.y.

Optional advice (nonblocking)

These two lines are packed README text, so changing them would mean a new archive. If you want them fixed, do it before publication, not after.

1. README.md:178 still says "The beta/next beads-task-agent…" Line 64 now calls next a historical beta channel, so this reads as if the scope-bounded agent applied only to the beta. The Design section and line 49 already describe it as 2.0 behavior, so the impact is low. Changing it to "The beads-task-agent…" fixes it.
2. README.md:132 opens the Beads workflows section with "Published stable 1.0.2 registers no slash commands…" That is historically true, but it now leads a section about the current stable 2.0.0, which registers 30 commands. Marking the sentence as historical, or moving it below the 2.0 description, would read better.
3. The package.json description ("bd prime context injection with a schema-migration guard, and a bounded task agent") leaves out the native tools and the workflow commands. It understates rather than contradicts, so it's cosmetic only.

Scope of these verdicts

The READY verdicts cover release preparation for exact commit 2321062 only. They do not authorize a merge, a tag, a GitHub release, npm publication, latest tag changes or operator/Zeus activation. Those still need fresh owner approval. The trusted workflow will build the publication archive separately, so its bytes and provenance still need their own verification. The earlier source/qualification records (the original REVISE and the later READY) are unaffected.