vgxness 1.3.0 → 1.4.0

package/dist/verification/verification-plan-service.js

@@ -21,7 +21,7 @@ const templates = {
     },
     cli: {
         rationale: ['CLI changes affect TypeScript dispatch/rendering paths and user-visible behavior.', 'Only typecheck is currently allowlisted; CLI execution remains manual/copy-only.'],
-        recommendations: [typecheckRecommendation(), manualRecommendation('manual-cli-smoke', 'Smoke-test CLI command manually', 'Use npm run cli -- <command> as copy-only text for an operator-selected CLI scenario.', 'npm run cli -- <command>')],
+        recommendations: [typecheckRecommendation(), manualRecommendation('manual-cli-smoke', 'Smoke-test CLI command manually', 'Use bun run cli:bun -- <command> as copy-only text for an operator-selected CLI scenario.', 'bun run cli:bun -- <command>')],
         manualChecks: [manualCheck('review-cli-output', 'Review CLI output shape', 'Confirm human output is concise and JSON output remains structured where applicable.')],
     },
     mcp: {

package/docs/architecture.md

@@ -30,7 +30,7 @@ Human operator                     AI coding tool / agent
       │                                      │
       ├───────────────┐                      │
       ▼               ▼                      ▼
- CLI (`vgx`)          TUI (`vgx`)       MCP server (`vgx mcp start`)
+ CLI (`vgxness`)      TUI (`vgxness`)   MCP server (`vgxness mcp start`)
       │               │                      │
       └───────────────┴──────────┬───────────┘
                                  ▼
@@ -142,7 +142,7 @@ Current service API:
 
 Artifact read/list surfaces use the full-content `artifacts` table in the selected local SQLite memory store. They do **not** read Engram search previews, and they do **not** create or modify `openspec/` paths.
 
-The CLI exposes the same boundary through `npm run cli -- sdd status|ready|save-artifact|get-artifact|list-artifacts`. These commands do **not** execute providers, continue phases automatically, create `openspec/`, or write `.opencode/`, `.claude/`, or user/global provider config.
+The CLI exposes the same boundary through `vgxness sdd status|ready|save-artifact|get-artifact|list-artifacts`. These commands do **not** execute providers, continue phases automatically, create `openspec/`, or write `.opencode/`, `.claude/`, or user/global provider config.
 
 ### Target architecture
 
@@ -187,7 +187,7 @@ This plane should remain separate from runtime execution. Rendering OpenCode, Cl
 The CLI exposes this through:
 
 ```bash
-npm run cli -- orchestrator preview --project vgxness --intent "..." [--change <id>] [--db <path>]
+vgxness orchestrator preview --project vgxness --intent "..." [--change <id>] [--db <path>]
 ```
 
 This seam is intentionally non-executing. It may read SDD status/next context for a supplied change from the selected local SQLite store, but it does not call providers, invoke run preflight, edit code, write provider config, create run records, install global memory, or create `openspec/`. Future live orchestration must build on this explicit preview contract instead of bypassing it with prompt-only routing.
@@ -199,9 +199,9 @@ The MCP server is the agent-facing control plane. It should expose typed, narrow
 Current MCP operator verification uses two short-lived CLI commands before connecting a client:
 
 ```bash
-npm run cli -- mcp setup --preview --provider opencode --db <path>
-npm run cli -- mcp setup --preview --provider claude --db <path>
-npm run cli -- mcp doctor --db <path> --project vgxness --change manual-smoke
+vgxness mcp setup --preview --provider opencode --db <path>
+vgxness mcp setup --preview --provider claude --db <path>
+vgxness mcp doctor --db <path> --project vgxness --change manual-smoke
 ```
 
 `mcp setup --preview` returns copyable stdio client snippets only. It is read-only and must not write `.opencode/`, `.claude/`, or provider config. `mcp doctor` verifies local readiness with JSON checks and may prepare/use the selected SQLite DB, but it does not mutate provider configuration.
@@ -223,15 +223,15 @@ The CLI is the scriptable operator surface. It should be predictable, dry-run fr
 Command shape should stay verb-first and grouped by product concept:
 
 ```bash
-vgx init
-vgx doctor
-vgx status
-vgx mcp install opencode
-vgx mcp status
-vgx sdd status <change>
-vgx sdd next <change>
-vgx profiles list
-vgx profiles set apply <model>
+vgxness init
+vgxness doctor
+vgxness status
+vgxness mcp install opencode
+vgxness mcp status
+vgxness sdd status <change>
+vgxness sdd next <change>
+vgxness profiles list
+vgxness profiles set apply <model>
 ```
 
 ### TUI boundary
@@ -324,7 +324,7 @@ Harness tools expose the same registry through `createAgentRegistryToolHandlers(
 | `getAgent({ id })` / `getAgentByName({ project, scope, name })` | Read full definitions for execution or adapter rendering. |
 | `listAgents(filters)` / `listSubagents({ parentAgentId })` | Discover available agents and parent-child relationships. |
 
-The minimal CLI exposes this same registry for local terminal use through `npm run cli -- agents register|list|get` and `npm run cli -- subagents register|list|get`. It stays thin: flag/JSON-file parsing, SQLite opening, and JSON formatting only; registry rules remain in the service/tool boundary.
+The minimal CLI exposes this same registry for local terminal use through `vgxness agents register|list|get` and `vgxness subagents register|list|get`. It stays thin: flag/JSON-file parsing, SQLite opening, and JSON formatting only; registry rules remain in the service/tool boundary.
 
 Current agent resolution v1 is provider-agnostic, deterministic, and rule-based. It accepts project/scope, task text or intent, desired capabilities, workflow/phase, provider adapter, and optional `agent`/`subagent` mode. Resolution reads existing agent definitions only, then scores compatible candidates with transparent reasons:
 
@@ -338,8 +338,8 @@ Current agent resolution v1 is provider-agnostic, deterministic, and rule-based.
 Incompatible definitions are returned under `skipped` with reasons such as project/scope mismatch, mode mismatch, provider adapter mismatch, workflow mismatch, or capability mismatch. Ties are stable: higher score first, then top-level agents before subagents, then agent name/id.
 
 ```bash
-npm run cli -- agents resolve --project vgxness --capabilities implementation,typescript --workflow sdd --phase apply --provider opencode --task "Implement the next SDD apply slice"
-npm run cli -- agents resolve --project vgxness --mode subagent --capabilities review --workflow sdd --phase verify
+vgxness agents resolve --project vgxness --capabilities implementation,typescript --workflow sdd --phase apply --provider opencode --task "Implement the next SDD apply slice"
+vgxness agents resolve --project vgxness --mode subagent --capabilities review --workflow sdd --phase verify
 ```
 
 Resolution v1 does **not** call an AI/model ranker, execute agents, mutate provider config, install tools, choose a model dynamically, or create/update provider files. Future orchestration can use these ranked candidates as one explicit input, but current behavior is explainable metadata matching only.
@@ -375,15 +375,15 @@ Skill improvement proposals are the current controlled foundation for self-impro
 CLI examples:
 
 ```bash
-npm run cli -- skills register --project vgxness --name sdd-apply --description "Applies SDD tasks"
-npm run cli -- skills add-version --project vgxness --name sdd-apply --version 1.0.0 --source-kind path --source-path .config/opencode/skills/sdd-apply/SKILL.md --activate
-npm run cli -- skills attach --project vgxness --name sdd-apply --target-type workflow-phase --target-key sdd:apply
-npm run cli -- skills resolve --agent apply-agent --project vgxness --workflow sdd --phase apply --provider opencode
-npm run cli -- skills payload --agent apply-agent --project vgxness --workflow sdd --phase apply --provider opencode
-npm run cli -- skills propose --project vgxness --name sdd-apply --proposed-version 1.1.0 --source-kind inline --inline-metadata '{"content":"Updated skill"}' --rationale "Repeated correction from trace"
-npm run cli -- skills submit-proposal --proposal <proposal-id> --actor uziel
-npm run cli -- skills approve-proposal --proposal <proposal-id> --actor uziel --reason "Reviewed diff"
-npm run cli -- skills apply-proposal --proposal <proposal-id> --actor uziel
+vgxness skills register --project vgxness --name sdd-apply --description "Applies SDD tasks"
+vgxness skills add-version --project vgxness --name sdd-apply --version 1.0.0 --source-kind path --source-path .config/opencode/skills/sdd-apply/SKILL.md --activate
+vgxness skills attach --project vgxness --name sdd-apply --target-type workflow-phase --target-key sdd:apply
+vgxness skills resolve --agent apply-agent --project vgxness --workflow sdd --phase apply --provider opencode
+vgxness skills payload --agent apply-agent --project vgxness --workflow sdd --phase apply --provider opencode
+vgxness skills propose --project vgxness --name sdd-apply --proposed-version 1.1.0 --source-kind inline --inline-metadata '{"content":"Updated skill"}' --rationale "Repeated correction from trace"
+vgxness skills submit-proposal --proposal <proposal-id> --actor uziel
+vgxness skills approve-proposal --proposal <proposal-id> --actor uziel --reason "Reviewed diff"
+vgxness skills apply-proposal --proposal <proposal-id> --actor uziel
 ```
 
 V1 does **not** autonomously detect trace patterns, mutate skill files, activate autonomous updates, evaluate proposed quality, or write external skill/provider configuration. Proposal creation is reviewable, and activation is gated by explicit approval plus explicit apply.
@@ -428,8 +428,8 @@ Renderers currently include:
 | `opencode` | `rendered/opencode/<project>/<scope>/<agent>/opencode.json` | Single config preview with `$schema` and `agent` object. Top-level agents default to `primary`; subagents render as `subagent`. |
 
 ```bash
-npm run cli -- agents render --provider json --project vgxness --name apply-agent
-npm run cli -- agents render --provider opencode --project vgxness --name apply-agent
+vgxness agents render --provider json --project vgxness --name apply-agent
+vgxness agents render --provider opencode --project vgxness --name apply-agent
 ```
 
 Rendering is intentionally read-only: it returns generated content in the CLI response. It does **not** write `.opencode/`, `.claude/`, or any user/global provider config.
@@ -442,7 +442,7 @@ Claude Code rendering remains follow-up work after its exact install-safe artifa
 The current OpenCode integration also exposes a preview-only composition seam through `OpenCodeInjectionPreviewService` and the thin CLI command:
 
 ```bash
-npm run cli -- opencode preview --provider opencode --agent apply-agent --project vgxness --change checkout-flow --phase apply-progress
+vgxness opencode preview --provider opencode --agent apply-agent --project vgxness --change checkout-flow --phase apply-progress
 ```
 
 This preview lives in the provider adapter/preview layer, not in provider-agnostic core services. It composes existing read-only outputs:
@@ -620,16 +620,17 @@ Agent and subagent registry definitions keep neutral `permissions` such as `{ "s
 
 ## Future interface surface
 
-Candidate future CLI surface beyond the current minimal local CLI documented in `docs/cli.md`:
+Current and near-term CLI surface should build on the plural domain commands documented in `docs/cli.md`. Future shortcuts can be added later, but they should not imply separate singular command families:
 
 ```bash
-vgx init
-vgx memory search|get|save|update
-vgx agent list|add|validate|render
-vgx skill list|add|propose|approve|reject
-vgx sdd new|continue|status|archive
-vgx run list|show|resume
-vgx adapter doctor|render
+vgxness init
+vgxness memory search|get|save|update
+vgxness agents list|register|get|resolve|render
+vgxness skills list|register|propose|approve-proposal|apply-proposal
+vgxness sdd status|next|ready|save-artifact|accept-artifact|list-artifacts
+vgxness runs list|get|timeline|debug|resume-inspect|resume-gate
+vgxness mcp doctor|install
+vgxness opencode preview
 ```
 
 Representative MCP tools mirror the same core services for agent use. For the current exact tool names, use `SUPPORTED_VGX_MCP_TOOL_NAMES`: