@osovv/vv-opencode 0.35.33 → 1.0.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (4) hide show
  1. package/CHANGELOG.md +8 -0
  2. package/README.md +15 -0
  3. package/package.json +1 -1
  4. package/schemas/vvoc/v3.json +1 -1
package/CHANGELOG.md CHANGED
@@ -1,3 +1,11 @@
1
+ ## 1.0.0 (2026-07-03)
2
+
3
+ ### Summary
4
+
5
+ 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.
6
+
7
+ * docs: declare 1.0 stability posture ([8a3e590](https://github.com/osovv/vv-opencode/commit/8a3e590))
8
+
1
9
  ## <small>0.35.33 (2026-06-26)</small>
2
10
 
3
11
  ### Summary
package/README.md CHANGED
@@ -35,6 +35,21 @@ Project scope writes only to `./.opencode/` and `./.vvoc/`. A normal `opencode`
35
35
 
36
36
  ---
37
37
 
38
+ ## 1.0 Stability Posture
39
+
40
+ `vv-opencode` 1.0 marks the workflow as a daily-driver baseline: a hand-picked, curated OpenCode setup that packages the agent routing, managed skills, model-role indirection, safer editing, review loops, and release discipline used in real projects.
41
+
42
+ The stable user-facing surface is intentionally practical:
43
+
44
+ - `vvoc install` / `vvoc sync` / `vvoc launch` remain the primary setup and refresh path.
45
+ - `vv-spec`, `vv-plan`, and `vv-execute` remain the canonical spec-to-code path for larger work.
46
+ - `vv-review`, `vv-reflect`, and `vv-handoff` remain the auxiliary review, durable-learning, and session-continuity workflows.
47
+ - The published package exports, CLI command names, canonical vvoc schema v3, and date-prefixed `.vvoc/specs/YYYY-MM-DD-<slug>/` artifact layout are treated as compatibility surfaces.
48
+
49
+ The project still prefers conservative, explicit changes over hidden migration magic: user-owned config is not silently clobbered, invalid current config fails loudly, and breaking workflow or config changes must be documented in release notes.
50
+
51
+ ---
52
+
38
53
  ## Spec-to-Code Pipeline
39
54
 
40
55
  vvoc keeps larger agentic work from jumping straight into edits. The process turns a request into explicit artifacts first, then executes the approved plan with bounded implementation and review loops.
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@osovv/vv-opencode",
3
- "version": "0.35.33",
3
+ "version": "1.0.0",
4
4
  "description": "A curated, opinionated set of OpenCode plugins for spec-first, review-driven, safer agentic development.",
5
5
  "type": "module",
6
6
  "main": "./dist/index.js",
package/schemas/vvoc/v3.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "$schema": "https://json-schema.org/draft/2020-12/schema",
3
- "$id": "https://cdn.jsdelivr.net/npm/@osovv/vv-opencode@0.35.33/schemas/vvoc/v3.json",
3
+ "$id": "https://cdn.jsdelivr.net/npm/@osovv/vv-opencode@1.0.0/schemas/vvoc/v3.json",
4
4
  "title": "vvoc config",
5
5
  "description": "Canonical vvoc configuration document.",
6
6
  "type": "object",