Skip to content

v2.30.0

Choose a tag to compare

@mrbro-bot mrbro-bot released this 07 Jun 07:16
· 570 commits to main since this release
16270b3

What's new

Features

The docs site now surfaces npx skills as a first-class, portable install path alongside the OpenCode npm plugin. Previously, Systematic's installation story pointed exclusively at @opencode/systematic, which is an OpenCode-specific runtime. Skills themselves are harness-agnostic Markdown content that work in any agent environment — OpenCode, Claude Code, Cursor, Copilot, or any other harness. The npx skills add marcusrbrown/systematic command installs that content directly from this repo, no registry required.

The homepage now presents a dual install-path block with chooser cues to help readers pick fast: "OpenCode, full runtime" for the npm plugin (still the recommended path for the complete OpenCode experience), and "Any harness, skills only" for npx skills. The Installation page gains a dedicated secondary section with a scannable flag table. The README Quick Install section reflects both paths. Every non-deprecated skill reference page now carries a copyable npx skills add marcusrbrown/systematic --skill <name> command, auto-injected by the docs generator — deprecated skills are correctly excluded and the generator change is covered by nine new unit tests.

Documentation

A new best-practices solution doc captures the converter-injected default hardening pattern that emerged across v2.27.0 (agent mode) and v2.29.0 (agent temperature). Both cases followed the same shape: derive a runtime-injected default's resolved value mechanically from the real inference function, write it explicitly into frontmatter, change the runtime to fill-if-absent, and add a content-integrity gate that requires the value to be usable — not merely present.

Two lessons are encoded for future reference. First, zero-behavior-change must be proven mechanically by deriving the expected value for every agent and asserting zero mismatches, not assumed. Second, a presence-only gate is a false lock: the runtime treats present-but-invalid values as absent and falls back anyway, so the gate must verify usability. The doc cross-references the two related overlay and gate best-practices docs.

Also in this release

  • deps: update fro-bot/agent to v0.55.4 (#497)

Compare

v2.29.0...v2.30.0