Skip to content

v1.2.0

Latest

Choose a tag to compare

@jcarlosrodicio jcarlosrodicio released this 26 Oct 09:56
· 6 commits to master since this release
8335f09

v1.2.0 - Safe lifecycle and canonical release identity

This minor release ports three process changes from norma, OAK's sibling
harness, and clears the production dependency audit. The final review now
works in bounded rounds and treats a bar lowered to get to green as a
defect, developers get a policy for which tests to write, and nine
transitive advisories in the shipped OpenCode tool dependencies are fixed
with exact overrides.

Highlights

  • A weakened bar is a review finding. oak-adversarial-review has
    eleven dimensions. Dimension 10 covers a test made easier, a checker
    silenced, a threshold moved or unfinished work: each one blocks unless the
    task artifacts name it and quote the requirement behind it. Dimension 11
    reports a test that only re-proves an existing one as should fix.
  • Review rounds. A later round reads the previous report first, closes
    each of its findings as resolved, still open or dismissed, and does not
    raise them again. A finding names its class and every instance. A third
    round that still blocks ends as blocked, and /autonomous treats it as
    stop reason 6. The state-sync step appends each round to the review report
    instead of overwriting it.
  • Pre-existing findings are reported apart and never block or count as
    blocking or unresolved. The review run event carries round= and
    pre_existing=.
  • Which Tests to Write. test-driven-development gains a test policy:
    search before writing, one test per rule at the cheapest layer, one
    representative case plus the edges that differ, a list of what not to
    test, at most one regression test per bug, and the guarantees that are
    always kept. A project's own policy in AGENTS.md wins. The developer's
    Strict TDD rule points at it.
  • Clean dependency audit. npm audit --omit=dev on opencode/ reported
    nine advisories (four critical, five high). Exact overrides fix them
    without moving the pinned @opencode-ai/plugin 1.14.41, @opentui/solid
    0.2.5 or solid-js 1.9.12: brace-expansion 5.0.12, seroval and
    seroval-plugins 1.6.8, toml 5.0.1 and zod 4.6.7. The supply-chain
    contract and docs/supply-chain.md carry the new pins.
  • The OpenCode 2 type workspace pins @babel/core 7.29.7, the same version
    the shipped opencode/package.json already overrides.

Installation or upgrade

Install or upgrade the published CLI package:

npm install --global opencode-agent-orchestration-kit@1.2.0
oak version
oak upgrade --dry-run
oak upgrade

The npm installation exposes the CLIs but does not mutate OpenCode
configuration. oak install and oak upgrade remain separate, explicit
operations.

Migration

No migration is required. Existing harness configuration remains compatible.
oak upgrade refreshes the agent, command and skill files that changed. A
preserved target opencode/package.json or package-lock.json keeps its own
resolutions: merge the new overrides into it to get the audit fixes.

Validation performed

The public contract check, unit and script suite, typechecks for OpenCode 1
and OpenCode 2, compatibility and supply-chain checks, the production and
signature dependency audits, installation smoke and package smoke passed.
GitHub Actions Check and the OpenCode 1 and OpenCode 2 compatibility smokes
were green on the merged pull request before the release tag.

Public safety boundary

The public release excludes private OpenCode and Pi configuration, local
providers and MCP wiring, credentials, authentication files, provider URLs,
raw transcripts, private evidence, absolute machine-local paths, and runtime
state.

Boundary statement: no private config, no credentials, no provider URLs, no
raw transcripts, no machine-local paths.