vgxness 1.9.0 → 1.9.2

package/docs/providers.md

@@ -2,7 +2,7 @@
 
 VGXNESS is provider-agnostic at the core: the registry stores provider-neutral definitions and adapters translate them into provider-specific config and runtime behavior. This document covers the two adapter layers: the **control-plane adapter** (OpenCode primary plus supported secondary Claude Code support) and the **code-runtime provider adapter** (OpenAI-compatible + fake).
 
-## Status (v1.6.0)
+## Status (v1.9.1)
 
 | Provider | Control plane | Code runtime | Notes |
 |---|---|---|---|
@@ -44,7 +44,7 @@ vgxness agents render --provider json --project vgxness --name apply-agent
 
 ### Claude Code support
 
-Claude Code is supported as a secondary, non-default control-plane target. Read-only status, doctor, setup plan, and change-plan surfaces can inspect or preview Claude targets without Claude Code installed and without writing files.
+Claude Code is supported as a secondary, non-default control-plane target. Status, doctor, setup plan, and change-plan surfaces can inspect or preview Claude targets without Claude Code installed and without writing provider config. Local VGXNESS store initialization may occur when the selected SQLite store is needed.
 
 Claude scopes are canonicalized to `local`, `project`, and `user`; VGXNESS compatibility aliases `personal` and legacy `global` map to Claude `user` with warnings. MCP registration is represented as structured config/argv, for example `claude mcp add --scope user vgxness -- vgxness mcp start`; no shell strings are generated. For user/global apply, VGXNESS narrowly merges only `mcpServers.vgxness` in `~/.claude.json`, preserves unknown keys, backs up existing files, and does not manage auth/session data. Status/doctor/change-plan are read-only and do not execute Claude Code.
 
@@ -128,13 +128,13 @@ Deterministic, offline. Used by `test/code/` and `bun run smoke:opentui-code` to
 
 Provider install and doctor flows live in `src/mcp/client-install-opencode.ts` and `src/mcp/provider-doctor.ts` and are exposed through the MCP server and the CLI:
 
-- `vgxness mcp install opencode --plan` — read-only plan; never writes config.
+- `vgxness mcp install opencode --plan` — plan that never writes provider config; local VGXNESS store initialization may occur when the selected SQLite store is needed.
 - `vgxness mcp install opencode --yes` — explicit write path; creates a backup first.
 - `vgxness mcp doctor opencode` — JSON report of provider health.
 - `vgxness provider status` / `vgxness provider doctor` (planned CLI) — same shape through the operator surface.
 - `vgxness setup rollback --backup <path>` — restores a previous OpenCode config byte-for-byte after validation.
 
-Writes happen only through `apply` with explicit consent. Plans, status, doctor, change-plan, and previews are read-only by contract.
+Provider config writes happen only through `apply` with explicit consent. Plans, status, doctor, change-plan, and previews do not write provider config; local VGXNESS store initialization may occur when the selected SQLite store is needed.
 
 ## Safety boundary
 

package/docs/safety.md

@@ -132,7 +132,7 @@ Retry policy evaluation is separate from execution. `vgxness_run_resume_gate` ev
 
 ## Safety boundaries (enforced everywhere)
 
-- Read-only/preview commands must stay non-mutating: setup plans, MCP setup previews, OpenCode previews, workflow previews, status views, and the natural-language orchestrator preview never write provider config, call providers, or install global memory.
+- Read-only/preview commands must not mutate provider config or external tool state: setup plans, MCP setup previews, OpenCode previews, workflow previews, status views, and the natural-language orchestrator preview never write provider config, call providers, or install global memory. Local VGXNESS store initialization may occur when a command needs the selected SQLite store.
 - Provider config writes (`opencode.json`, `.opencode/`, `.claude/`, `CLAUDE.md`) require explicit consent (`--yes` or an equivalent confirmed flow) plus backup/rollback behavior.
 - The control plane and the code runtime do not create or write `openspec/`. SDD artifacts are stored through the local SQLite artifact service under canonical topic keys.
 - Human acceptance is distinct from artifact presence: `vgxness_sdd_accept_artifact` records explicit human-only acceptance; saving a draft never implies acceptance.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "vgxness",
-  "version": "1.9.0",
+  "version": "1.9.2",
   "description": "CLI and MCP control plane for guided AI-agent workflows, SDD, memory, and OpenCode setup.",
   "license": "SEE LICENSE IN LICENSE",
   "repository": {