vgxness 1.9.1 → 1.9.3

package/docs/code-runtime.md

@@ -35,6 +35,7 @@ Common flags across modes:
 | Flag | Effect |
 |---|---|
 | `--save-artifact` | Persist the phase artifact when explicit persistence is intended. |
+| `--draft-run` | Let planning phases use draft prerequisites for planning only; human acceptance is still required and `apply-progress` remains gated. |
 | `--change-id <id>` | Override change id. |
 | `--approval-policy`, `--approval-channel`, `--memory` | Same as the other modes. |
 
@@ -172,6 +173,8 @@ Prompts, reports, checkpoints, transcripts, and memory saves redact secret-like
 
 `vgxness code sdd <change> <phase>` loads existing artifacts for the requested change/phase and exposes phase-appropriate tools. Non-implementation phases stay read/artifact oriented. `apply-progress` may expose edit and shell tools. `verify` may expose verification shell tools. Artifact saves require explicit `--save-artifact` (or the equivalent runtime flag); passing it is the only way persistence is triggered.
 
+Use `vgxness sdd continue --project <project> --change <change>` first when you want the read-only continuation plan. It may suggest `vgxness code sdd ... --draft-run --save-artifact` for planning phases when draft prerequisites exist. `--draft-run` does not accept a value, does not weaken human acceptance, and does not unblock `apply-progress`; it only lets planning phases produce or revise draft artifacts before a human accepts them.
+
 ## Project detection
 
 `detectProject()` (in `src/code/runtime/project-detection.ts`) reports repository root, stack hints, config files, and verification presets such as `npm run typecheck` or `npm run test` when package scripts exist. The fake provider is deterministic for local tests.

package/docs/contributing.md

@@ -69,7 +69,7 @@ The configurator/setup plane (rendering/installing provider config) is separate
 
 These rules are non-negotiable. The harness is loaded with capability; do not remove these guards.
 
-- Read-only/preview commands must stay non-mutating. Setup plans, MCP setup previews, OpenCode previews, workflow previews, and status views must not write provider config or call providers.
+- Read-only/preview commands must not mutate provider config or external tool state. Setup plans, MCP setup previews, OpenCode previews, workflow previews, and status views must not write provider config or call providers. Local VGXNESS store initialization may occur when a command needs the selected SQLite store.
 - Provider config writes require explicit consent (`--yes` or equivalent confirmed flow) plus backup/rollback behavior.
 - Do not create or write `openspec/`. SDD artifacts are stored through the local SQLite artifact service under canonical topic keys `sdd/{change}/{phase}`.
 - Human acceptance is distinct from artifact presence. Do not infer acceptance from generated content or saved drafts. The runtime rejects `acceptedBy.type !== 'human'`.

package/docs/glossary.md

@@ -64,7 +64,7 @@ A permission resolution: `allow`, `ask`, or `deny`. For SDD-phase gating the mat
 
 ## Dry-run
 
-A read-only preview. Setup plans, MCP setup previews, OpenCode previews, workflow previews, and status views are dry-runs by contract — they must not write provider config or call providers.
+A read-only preview. Setup plans, MCP setup previews, OpenCode previews, workflow previews, and status views are dry-runs by contract for provider config and external tools: they must not write provider config or call providers. Local VGXNESS store initialization may occur when a command needs the selected SQLite store.
 
 ## Eval target
 
@@ -80,7 +80,7 @@ A redacted, structured report over SDD state, runs, and approvals. Surfaced thro
 
 ## MCP
 
-Model Context Protocol. The agent-facing transport. VGXNESS exposes 38 typed tools over stdio through `vgxness mcp start`. The tool list lives in `SUPPORTED_VGX_MCP_TOOL_NAMES` (`src/mcp/schema.ts`) and is documented in [MCP tools](./mcp.md).
+Model Context Protocol. The agent-facing transport. VGXNESS exposes 41 typed tools over stdio through `vgxness mcp start`. The tool list lives in `SUPPORTED_VGX_MCP_TOOL_NAMES` (`src/mcp/schema.ts`) and is documented in [MCP tools](./mcp.md).
 
 ## Memory observation
 

package/docs/mcp.md

@@ -1,6 +1,6 @@
 # MCP tools
 
-VGXNESS exposes 38 typed MCP tools over stdio through `vgxness mcp start`. The canonical list is the `SUPPORTED_VGX_MCP_TOOL_NAMES` array in `src/mcp/schema.ts` — treat that as the source of truth. The list below mirrors it; if a tool appears here that is not in the array, or vice versa, the array wins.
+VGXNESS exposes 41 typed MCP tools over stdio through `vgxness mcp start`. The canonical list is the `SUPPORTED_VGX_MCP_TOOL_NAMES` array in `src/mcp/schema.ts` — treat that as the source of truth. The list below mirrors it; if a tool appears here that is not in the array, or vice versa, the array wins.
 
 Tools are exposed under the `vgxness_*` prefix. Some MCP hosts strip the prefix and accept the short form (`sdd_status`, `memory_save`, etc.). The schema accepts both.
 
@@ -11,16 +11,18 @@ All tools:
 - Return either a typed result or a `VgxMcpError` with a `code` and `message`.
 - Do not require the agent to import or instantiate anything; pass JSON, get JSON.
 
-## SDD workflow (10)
+## SDD workflow (12)
 
 | Tool | Purpose | Required inputs | Notes |
 |---|---|---|---|
 | `vgxness_sdd_status` | Report per-phase artifact presence and the next ready missing phase. | `project`, `change` | |
 | `vgxness_sdd_next` | Recommend the next phase decision for a change. | `project`, `change` | |
+| `vgxness_sdd_continue` | Build a read-only continuation plan for a blocked or interrupted SDD change. | `project`, `change`; optional `payloadMode` (`compact`/`verbose`) | Complements `vgxness_sdd_next` and `vgxness_sdd_cockpit` with copyable next steps. Does not mutate artifacts or runs, execute providers, write provider config, create `openspec/`, or bypass human acceptance. |
 | `vgxness_sdd_ready` | Check whether a specific phase is ready. | `project`, `change`, `phase`; optional `runId`, `agentId` | Returns structured `SddReadiness` with `blockedPrerequisites`. |
 | `vgxness_sdd_get_readiness` | Same as `ready` with explicit output shape. | same as `ready` | |
 | `vgxness_sdd_save_artifact` | Persist phase content under canonical topic key `sdd/{change}/{phase}`. | `project`, `change`, `phase`, `content` | Saving does not imply acceptance. |
-| `vgxness_sdd_accept_artifact` | Record explicit human acceptance for a phase. | `project`, `change`, `phase`, `acceptedBy` (`{type:"human", id, displayName?}`); optional `acceptedAt`, `note`, `notes`, `rationale`, `runId`, `agentId` | `acceptedBy.type` must be `"human"`. Runtime rejects agent or anonymous acceptance. |
+| `vgxness_sdd_accept_artifact` | Record explicit human acceptance for a phase. | `project`, `change`, `phase`, `acceptedBy` (`{type:"human", id, displayName?}`); optional `acceptedAt`, `note`, `runId`, `agentId` | `acceptedBy.type` must be `"human"`. Runtime rejects agent or anonymous acceptance. Only `note` is accepted; `notes` and `rationale` are rejected as unexpected fields. |
+| `vgxness_sdd_reopen_artifact` | Move a rejected artifact back to draft for revision. | `project`, `change`, `phase`, `reopenedBy` (`{type:"human", id, displayName?}`); optional `reopenedAt`, `note`, `runId`, `agentId` | Human-only recovery path. Does not imply acceptance or bypass downstream gates. |
 | `vgxness_sdd_get_artifact` | Read one full artifact. | `project`, `change`, `phase`; optional `payloadMode` (`compact`/`verbose`) | |
 | `vgxness_sdd_list_artifacts` | List all artifacts for a change in canonical phase order. | `project`, `change`; optional `payloadMode` | |
 | `vgxness_sdd_cockpit` | Aggregate per-phase status, blockers, and recommended next action. | `project`, `change` | Returns `SddCockpit` with `aggregateBlockers` of kinds `missing-topic-key`, `unaccepted-phase`, `legacy-artifact`, `readiness`. |
@@ -64,7 +66,7 @@ All tools:
 | `vgxness_opencode_manager_payload` | Build the OpenCode manager payload envelope. | `OpenCodeManagerPayloadInput` shape (project, scope, agent, workflow/phase, workspaceRoot, maxSourceBytes, payloadMode) | `installable: false`, `readOnly: true`. |
 | `vgxness_opencode_handoff_preview` | Compose a full handoff preview: provider artifacts + skill diagnostics + SDD status + provider status + safety flags. | `project`; optional `scope`, `agentId`, `agentName`, `workspaceRoot`, `maxSourceBytes`, `change`, `phase` | Read-only preview. Does not execute OpenCode, install hooks, or write provider config. |
 
-## Runs (8)
+## Runs (9)
 
 | Tool | Purpose | Required inputs | Notes |
 |---|---|---|---|
@@ -74,6 +76,7 @@ All tools:
 | `vgxness_run_checkpoint` | Append a resumable JSON state. | `AppendRunCheckpointInput` shape | |
 | `vgxness_run_finalize` | Finalize a run with `outcome` and `outcomeReason`. | `FinalizeRunInput` shape | `outcome` must match a terminal `status`. Re-finalization is rejected. |
 | `vgxness_run_preflight` | Run policy evaluation and return the decision + planned execution isolation strategy. | `PreflightRunOperationInput` shape | May create a pending approval when the decision is `ask`. Does not invoke an executor. |
+| `vgxness_run_resume_candidates` | List recent interrupted runs for a project when the run id is unknown. | `project`; optional `limit` (1-100, default 5) | Returns failed, blocked, and needs-human candidates with `inspectInput` for `run_resume_inspect`. Does not retry, resume, mutate runs, create sandboxes/worktrees, invoke providers, or write artifacts/config. |
 | `vgxness_run_resume_inspect` | Plan-only resume advisory. | `runId` | Returns `RunResumeOrchestrationPlan` with blockers and `nextAction` (`resolve-approval`/`inspect-run`/`retry-check`/`manual-recovery`/`no-action`). |
 | `vgxness_run_resume_gate` | Evaluate retry policy for an approval without executing. | `approvalId`; optional `policy` | Default policy is `never`. See [Safety model](./safety.md) for the policy table. |
 
@@ -107,17 +110,18 @@ Inspecting SDD before doing any work:
 
 ```text
 vgxness_sdd_cockpit    { project: "vgxness", change: "new-flow" }
+vgxness_sdd_continue   { project: "vgxness", change: "new-flow" }
 vgxness_sdd_get_readiness { project: "vgxness", change: "new-flow", phase: "proposal" }
 ```
 
-The cockpit returns `aggregateBlockers`; if any are `unaccepted-phase`, the agent should not run the next phase until a human accepts the prerequisite.
+The cockpit returns `aggregateBlockers`; if any are `unaccepted-phase`, the agent should not run the next phase until a human accepts the prerequisite. `vgxness_sdd_continue` uses the same SDD state to explain how to continue; it is advisory only.
 
 Recording a phase with explicit human acceptance:
 
 ```text
 vgxness_sdd_save_artifact    { project, change, phase: "proposal", content: "..." }
 # human opens the harness and runs:
-vgxness_sdd_accept_artifact  { project, change, phase: "proposal", acceptedBy: { type: "human", id: "uziel" }, rationale: "Reviewed proposal." }
+vgxness_sdd_accept_artifact  { project, change, phase: "proposal", acceptedBy: { type: "human", id: "uziel" }, note: "Reviewed proposal." }
 ```
 
 Running a planned operation:
@@ -130,6 +134,16 @@ vgxness_run_checkpoint  { runId, label: "after-step-1", state: {...} }
 vgxness_run_finalize    { runId, outcome: "success", outcomeReason: "..." }
 ```
 
+Finding interrupted runs when the run id is unknown:
+
+```text
+vgxness_run_resume_candidates { project: "vgxness", limit: 5 }
+vgxness_run_resume_inspect    { runId }
+vgxness_run_resume_gate       { approvalId, policy }
+```
+
+`vgxness_run_resume_candidates` is discovery only. It points to `run_resume_inspect` for a selected candidate and does not admit a retry or resume execution; `run_resume_gate` remains the advisory retry-policy check for a known approval id.
+
 ## Safety boundary
 
 MCP tools do not:

package/docs/project-health-audit-v1.9.1.md

@@ -0,0 +1,126 @@
+# Auditoría de salud del proyecto VGXNESS v1.9.1
+
+## Resumen v1.9.1
+
+VGXNESS v1.9.1 fue validado exitosamente como CLI/MCP control plane local-first, con runtime instalado basado en Bun, almacenamiento SQLite local y gobernanza SDD con aceptación humana explícita. Esta auditoría es la fuente canónica para la evidencia v1.9.1; si los conteos o comandos cambian, actualiza este documento en vez de duplicar la matriz en otros docs.
+
+## Evidencia oficial validada
+
+- VGXNESS v1.9.1 validado exitosamente.
+- MCP expone 38 tools tipadas.
+- Inventario de tests: 106 test files.
+- Validación oficial aprobada:
+  - `bun run verify:typecheck`
+  - `bun run verify:test` con 437 pass, 0 fail
+  - `bun run verify:test:bun-storage`
+  - `bun run verify:bun-sqlite`
+  - `bun run package:bun:evidence` con `releaseReadiness: pass`
+
+## Matriz de validación
+
+| Superficie | Evidencia v1.9.1 | Taxonomía | Resultado esperado |
+|---|---|---|---|
+| Typecheck | `bun run verify:typecheck` | `test-run` | TypeScript estricto compila sin errores. |
+| Node tests | `bun run verify:test` | `test-run` | Suite Node pasa; evidencia validada: 437 pass, 0 fail. |
+| Bun storage tests | `bun run verify:test:bun-storage` | `test-run/local-store` | Tests storage-backed pasan vía runner oficial bajo Bun. |
+| Bun SQLite probe | `bun run verify:bun-sqlite` | `test-run/local-store` | `bun:sqlite` aplica migraciones en DB temporal y valida integridad. |
+| Package evidence | `bun run package:bun:evidence` | `package evidence` | Evidencia de paquete sin publicar; `releaseReadiness: pass`. |
+| MCP schema/tools | `docs/mcp.md` + `SUPPORTED_VGX_MCP_TOOL_NAMES` | `governance/read model` | 38 tools documentadas; schema y tabla deben mantenerse sincronizados. |
+| Test inventory | Inventario v1.9.1 | `test-run` | 106 test files como evidencia versionada. |
+| Setup/provider status | `setup plan/status`, provider status/doctor/change-plan | `read-only/no provider writes` | No escriben provider config; pueden leer o inicializar el store local de VGXNESS si hace falta. |
+| Provider previews | MCP setup preview, OpenCode preview, agent render | `read-only/provider-preview` | Preview sin ejecutar proveedores ni escribir `.opencode/`, `.claude/` o config global. |
+| SDD workflow | `sdd status/ready/get/list/next/save/accept` | `governance/read model` | Artefactos en SQLite bajo `sdd/{change}/{phase}`; aceptación humana explícita. |
+| Runs/preflight | `run_start`, `run_preflight`, resume inspect/gate | `guarded apply` | Operaciones riesgosas pasan por preflight/approval antes de ejecución. |
+| Memory/session local state | Memory, sessions, cockpit | `local-store possible` | Estado durable vive en SQLite local; no implica provider config writes. |
+| Workflow executor | Workflow preview/run/execute + allowlist | `requires explicit consent` | Preview no muta; ejecución requiere confirmación y comandos allowlisted. |
+| Package runtime Bun | Bins `vgxness`/`vgx` y MCP instalado | `package evidence` | Runtime instalado usa wrapper Bun y evidencia de paquete sin publicación. |
+
+## Taxonomía de seguridad
+
+- `docs-only`: documentación sin cambios de runtime.
+- `test-run`: verificación local o CI que puede consumir CPU/IO pero no cambia el contrato de producto.
+- `test-run/local-store`: tests/probes que crean o usan storage local temporal.
+- `package evidence`: inspección de artefacto/install smoke sin publicar.
+- `read-only/no provider writes`: no escribe configuración de proveedor, aunque puede abrir o preparar estado local de VGXNESS.
+- `read-only/provider-preview`: produce planes o previews sin instalar hooks, ejecutar proveedores ni escribir provider config.
+- `local-store possible`: puede leer/escribir SQLite local de VGXNESS por diseño del comando.
+- `governance/read model`: estado SDD/runs/memory consultable, con aceptación humana separada de la presencia del artefacto.
+- `guarded apply`: operación mutante detrás de preflight, approval y auditoría.
+- `requires explicit consent`: requiere `--yes`, confirmación equivalente o aprobación humana registrada.
+- `future/not implemented`: documentado como trabajo futuro, no como alcance actual.
+
+## Read-only, provider config y local store
+
+En esta auditoría, “read-only” debe leerse con precisión operacional: una superficie puede ser read-only respecto de proveedor y workspace, pero aun así abrir, leer o preparar el store local de VGXNESS. La regla canónica es:
+
+> No provider config writes; local VGXNESS store initialization may occur.
+
+Esto distingue tres planos:
+
+1. **Provider config**: `.opencode/`, `opencode.json`, `.claude/`, `.mcp.json`, `CLAUDE.md` y archivos equivalentes. Escribirlos requiere consentimiento explícito y backup/rollback cuando aplique.
+2. **Local VGXNESS store**: SQLite local para memoria, sesiones, runs, SDD artifacts, agentes, skills y perfiles. Algunos comandos pueden abrir o inicializar este store.
+3. **Workspace/source**: archivos del repo y artefactos de código. Este cambio es docs-only y no cambia runtime, permisos, approvals, provider setup ni packaging.
+
+## Comandos oficiales de validación
+
+Validación oficial completa para v1.9.1:
+
+```bash
+bun run verify:typecheck
+bun run verify:test
+bun run verify:test:bun-storage
+bun run verify:bun-sqlite
+bun run package:bun:evidence
+```
+
+Para release-readiness, el package evidence debe requerir pase explícito:
+
+```bash
+bun run package:bun:evidence -- --require-pass
+```
+
+## Notas sobre tests storage-backed
+
+Los tests storage-backed no deben documentarse como invocaciones genéricas directas de `node --test`. Usa los runners oficiales porque preparan el runtime correcto, paths temporales y expectativas de Bun/SQLite:
+
+- `bun run verify:test:bun-storage` para tests storage-backed bajo Bun.
+- `bun run verify:bun-sqlite` para el probe SQLite real con `bun:sqlite`.
+
+Node.js sigue siendo tooling de desarrollo/build/test para TypeScript, `node:test` y scripts auxiliares, pero el storage runtime soportado es Bun.
+
+## Riesgos y mitigaciones
+
+| Riesgo | Mitigación |
+|---|---|
+| Duplicar la matriz en README u otros docs y crear drift. | Mantener este archivo como fuente canónica; README solo resume y enlaza. |
+| Prometer “no mutation” absoluta donde puede inicializarse SQLite local. | Usar wording preciso: no provider config writes; local VGXNESS store initialization may occur. |
+| Confundir package evidence con publicación. | Package evidence no publica; publishing requiere proceso humano explícito separado. |
+| Tratar aceptación SDD como presencia de artifact. | Mantener aceptación humana explícita como requisito independiente. |
+| Ejecutar storage tests con runner incorrecto. | Documentar runners oficiales Bun para storage-backed tests. |
+| Expandir esta auditoría hacia refactors P1/P2. | Mantener P1/P2 bajo future work solamente. |
+
+## Fuera de alcance
+
+- Cambios de runtime, approvals, preflight, permisos, SDD acceptance o provider setup.
+- Cambios de package metadata, scripts, packaging o publicación.
+- Escritura de provider config o creación de `.opencode/`, `.claude/` u `openspec/`.
+- Refactors de MCP control-plane, SDD workflow, runs, storage o CLI.
+- Nuevos comandos de health audit o nuevos MCP tools.
+
+## Future work P1/P2
+
+Estos puntos son notas futuras (`future/not implemented`), no alcance de v1.9.1:
+
+- Modularizar MCP control-plane.
+- Separar SDD projections/read models.
+- Unificar lenguaje de guarded apply/Claude.
+- Crear un comando/reporte integrado de health audit.
+
+## Cómo actualizar esta auditoría
+
+1. Revalidar los comandos oficiales y registrar conteos nuevos solo si fueron medidos.
+2. Si cambia el número de MCP tools, actualizar `SUPPORTED_VGX_MCP_TOOL_NAMES` y `docs/mcp.md` en el mismo cambio.
+3. Si cambia el inventario de tests, actualizar esta evidencia versionada y evitar duplicar conteos en README.
+4. Si cambia la semántica de setup/provider preview/status, revisar wording de provider config vs local store.
+5. Si cambian runners o package evidence, actualizar `README.md`, `docs/cli.md` y `docs/contributing.md` según corresponda.
+6. No marcar esta auditoría ni artefactos SDD como aceptados salvo aceptación humana explícita.

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.1",
+  "version": "1.9.3",
   "description": "CLI and MCP control plane for guided AI-agent workflows, SDD, memory, and OpenCode setup.",
   "license": "SEE LICENSE IN LICENSE",
   "repository": {