Skip to content

Releases: osovv/vv-opencode

v1.0.0

Choose a tag to compare

@github-actions github-actions released this 03 Jul 19:28
b19260a

1.0.0 (2026-07-03)

Summary

vv-opencode reaches version 1.0, establishing a daily-driver baseline for the curated OpenCode workflow. The release formalizes a stability posture where setup commands, managed skill names, public package exports, schema v3, and the spec artifact layout are treated as compatibility surfaces, meaning breaking changes to these areas will be explicitly documented in future release notes. User-owned config is never silently clobbered, and invalid config continues to fail loudly. This marks the transition from iterative development to a practical, documented baseline for real project use.

  • docs: declare 1.0 stability posture (8a3e590)

v0.35.33

Choose a tag to compare

@github-actions github-actions released this 26 Jun 12:10
7834e28

0.35.33 (2026-06-26)

Summary

This release removes the harmful RTK (rtk-ai/rtk) recommendation from the interactive vvoc init outro and the README, because RTK proxies developer commands and distorts their output shape, causing automated sessions to receive unexpected responses and work around RTK instead of completing the intended work. Users will now see a clean init success message and no longer be directed to install a proxy that interferes with standard command output.

  • fix(init): drop harmful RTK recommendation that distorted command output (cd5c12a)

v0.35.32

Choose a tag to compare

@github-actions github-actions released this 26 Jun 11:01
835e3fc

0.35.32 (2026-06-26)

Summary

Workflow result preservation is now implemented: when a tracked subagent returns BLOCKED or NEEDS_CONTEXT, the controller receives the actual explanation in the error and can inspect it later through work_item_list, significantly improving recovery after hard stops. Protocol parsing now extracts the freeform result body after the required blank line, and if a subagent forgets that blank line, the error provides an actionable diagnostic with a corrected format example instead of a confusing generic message. The repair system also gains missing-blank-line guidance, increasing the chance of automatic format recovery without changing the subagent's outcome. All excerpts are bounded and explicitly truncated to prevent unbounded storage in persisted workflow state.

  • docs(grace): add workflow result preservation spec and plan (c4f05fa)
  • docs(grace): archive workflow result preservation change (6efdc37)
  • feat(workflow): preserve tracked result context (078e926)

v0.35.31

Choose a tag to compare

@github-actions github-actions released this 25 Jun 13:08
579d345

0.35.31 (2026-06-25)

Summary

This release adds the vv-handoff managed skill, a lightweight end-of-session tool that writes a project-local XML handoff note from already-visible session context—recording the original request, completed work, current state and decisions, important files, known command results, blockers, and the next safe step—without running shell commands or collecting fresh evidence, and with automatic secret redaction and collision-safe directory naming. The vv-spec skill documentation was also clarified to ensure spec package date prefixes remain date-only, excluding any time or timezone components.

  • docs(grace): add vv-handoff skill spec and plan (490c96e)
  • docs(vv-spec): clarify date-only spec package prefix (cba76f5)
  • feat(skills): add vv-handoff managed skill (a386c5a)

v0.35.30

Choose a tag to compare

@github-actions github-actions released this 24 Jun 12:33
bbde3c7

0.35.30 (2026-06-24)

Summary

Spec packages created by the vv-spec skill now use date-prefixed directory names (YYYY-MM-DD-slug) so active packages sort by creation date and are easier to identify, with corresponding updates to the vv-spec, vv-plan, and vv-controller skill and agent templates. The project documentation has been fully migrated to the GRACE 4 artifact model, replacing legacy XML sources under docs/ with the current .grace/ directory structure, and all GRACE context artifacts—requirements, technology, principles, deployment, and UX guidelines—have been refined for clarity and accuracy. Legacy GRACE 3 XML documents and superseded workflow plan handoff notes have been removed, and stale migration references have been cleaned up from graph and verification indexes.

  • feat(vv-spec): date-prefix spec packages (0dba659)
  • docs: drop migration report artifact (327812d)
  • docs: finalize GRACE migration cleanup (496236f)
  • docs: migrate project to GRACE 4 (ba3e162)
  • docs: refine GRACE context requirements (73245b1)
  • docs: refine GRACE deployment context (cd2da0f)
  • docs: refine GRACE principles context (ad1b050)
  • docs: refine GRACE technology context (eeff4d2)
  • docs: refine GRACE UX guidelines (09d075a)
  • docs: remove legacy GRACE 3 artifacts (c9b910d)
  • docs: remove stale GRACE migration references (6ad640a)

v0.35.29

Choose a tag to compare

@github-actions github-actions released this 22 Jun 07:06
03ca5d0

0.35.29 (2026-06-22)

Summary

This release adds the vv-osovv-cheap preset, which provides a more cost-effective set of model role assignments by combining deepseek, stepfun, minimax, and zai models, and updates the project documentation to clarify vvoc's role as a curated, opinionated plugin set that adds a structured spec-to-code process layer for safer, more portable agentic development—including formalized trajectories, review-driven execution, and long-run safety features.

  • feat(preset): add vv-osovv-cheap preset with zai smart and deepseek reviewer (dfe1efe)
  • docs: clarify vvoc process positioning (3d78927)
  • docs: explain plugin user benefits (baf716b)
  • docs: update project positioning (7af2865)

v0.35.28

Choose a tag to compare

@github-actions github-actions released this 21 Jun 20:53
8464151

0.35.28 (2026-06-21)

Summary

This release completes the strict cutover from legacy behavior: vvoc config parsing now rigidly enforces canonical schema v3 with the plugins section as required, rejecting old, incomplete, or malformed vvoc.json files instead of silently migrating or repairing them; vvoc status and vvoc doctor report parse errors without mutating the file, and vvoc upgrade treats a failed post-install sync as a reported partial upgrade requiring manual config fix. Runtime compatibility fallbacks have been removed — Guardian permission replies use only the current OpenCode permission API or HTTP reply, Hashline edit anchors accept only current hashing algorithms, and vvoc sync no longer deletes old managed-agent names or managed command entries, leaving them untouched while writing current registrations. Users with existing v1/v2 configs must manually update to schema v3 before any sync, install, or plugin runtime will proceed.

  • docs: complete launch polish pass (b026a79)
  • docs: document strict legacy cutover (cf99ccf)
  • feat(config): enforce strict vvoc config parsing (299a398)
  • feat(upgrade): report partial sync failures (fad286c)
  • refactor(runtime): remove legacy compatibility fallbacks (7517d0d)

v0.35.27

Choose a tag to compare

@github-actions github-actions released this 20 Jun 20:40
b059943

0.35.27 (2026-06-20)

Summary

Runtime plugins now load the effective vvoc configuration once during startup and share an immutable snapshot for the lifetime of the process, replacing the previous pattern where each plugin independently discovered and loaded the config. This internal refactor ensures all plugins see the same configuration values, eliminates redundant filesystem reads, and makes plugin toggle checks a pure operation on the already-loaded config object. Users should restart OpenCode after changing vvoc.json — there is no live reload — but otherwise no behavioral changes are expected; this change primarily improves consistency and startup efficiency across Guardian, Hashline Edit, Model Roles, Secrets Redaction, System Context Injection, and Workflow plugins.

  • refactor(config): load vvoc runtime config once (04e414e)

v0.35.26

Choose a tag to compare

@github-actions github-actions released this 19 Jun 21:25
d09507c

0.35.26 (2026-06-19)

Summary

This release memoizes config resolution to eliminate a 5–10 second startup delay on slow filesystems, and introduces explicit intent review rounds in the WorkflowPlugin, giving users deterministic control over implementation and review-only pipelines—work items now require a mode and requiredReviewers set, reviewers launch in parallel with collect-all round aggregation, and review-only failures are treated as completed findings rather than routing back to the implementer. It also restores the OpenAI patch‑preset context limit to 1.05M after a brief compliance adjustment.

  • chore: bump version from 0.35.24 to 0.35.25 with changelog (70854dc)
  • perf(config): memoize loadEffectiveVvocConfigForRuntime to fix startup regression (a83c73c)

v0.35.24

Choose a tag to compare

@github-actions github-actions released this 18 Jun 21:25
91ad85a

0.35.24 (2026-06-18)

Summary

This release restores the 1.05M context limit for the openai patch-preset after a brief adjustment to 400K for ChatGPT Pro plan compliance, and introduces explicit intent review rounds to the WorkflowPlugin: work items now require mode (implementation or review_only) and requiredReviewers (spec, code, or both), reviewers are launched and tracked in parallel, results are collected into a full review round before deciding the next lifecycle state, and review-only mode treats reviewer FAIL as a completed finding without routing to the implementer—giving users more deterministic and flexible pipeline control.

  • fix: restore 1.05M openai patch-preset limits (9d5df8a)
  • fix: set openai patch-preset context to 400K for ChatGPT Pro plan compliance (0177f03)
  • fix: use 400K context limit for openai patch-preset (ChatGPT Pro plan) (84c6029)
  • feat(workflow): add explicit intent review rounds (f02e784)