vgxness 1.2.0 → 1.3.0

package/docs/cli.md

@@ -52,7 +52,7 @@ Recommended user flow after `npm install -g vgxness`:
 
 ```bash
 vgx --help
-vgx                      # operational dashboard in a TTY; static safe guidance in CI/non-TTY
+vgx                      # OpenTUI main menu in a TTY; static safe setup guidance in CI/non-TTY
 vgx init                 # setup wizard in a TTY; read-only plan in CI/non-TTY
 vgx setup plan           # human-readable, read-only plan
 vgx setup status         # human-readable, read-only setup status
@@ -205,23 +205,24 @@ npm run cli -- sdd status --project vgxness --change my-change
 
 `opencode preview` returns a combined, preview-only injection envelope for future OpenCode/MCP/hook callers. It does **not** execute OpenCode, install hooks or MCP servers, create runs, record skill usage, or write provider config.
 
-## Operational dashboard
+## OpenTUI main menu
 
-Use the interactive dashboard for a read-only operational view:
+Use no arguments in a TTY to open the main menu:
 
 ```bash
 npm run cli --
-npm run cli -- dashboard interactive [--project vgxness] [--change my-change]
-npm run cli -- dashboard status --project vgxness [--change my-change]
 ```
 
-The installed `vgxness`/`vgx` binary opens the same operational dashboard as `dashboard interactive` when run with no arguments in a TTY. With no TTY, no-args prints deterministic safe guidance, exits 0, and does not read dashboard status, infer a project, open project state, toggle raw mode, or write provider/config artifacts. Use `vgxness --help` or `vgxness -h` to print command help without starting the dashboard; explicit subcommands keep their normal behavior.
+The installed `vgxness`/`vgx` binary opens the OpenTUI main menu when run with no arguments in a TTY. With no TTY, no-args prints deterministic safe setup guidance, exits 0, and does not infer a project, open project state, toggle raw mode, or write provider/config artifacts. Use `vgxness --help` or `vgxness -h` to print command help without starting the main menu; explicit subcommands keep their normal behavior.
 
-The top-level menu is: **Installation, Status, Agents, Skills, Memory, SDD, Runs, Approvals, Permissions, Settings**. Terminal controls are `1-9`/`0` to switch screens, `r` to refresh, `?` for help, and `q` to quit. `Enter` shows details only; operational actions remain copy-only and must be run outside the TUI.
+The top-level menu is: **Installation, Doctor / recovery, SDD / workflow guidance, Advanced CLI, Exit**. Terminal controls are `↑/↓` or `j/k` to move, `Enter` to open the focused item, `?` for help, and `q` to quit.
 
-`dashboard interactive` can launch without `--project`; it opens Installation/status-oriented guidance while project-scoped checks are deferred rather than failed. Project-scoped screens render recoverable `project-required` states until you relaunch or refresh with a project.
+For scriptable status, use explicit read-only commands:
 
-`dashboard status --project <name>` is the scriptable/read-only renderer. It intentionally remains separate from no-args behavior and validates required project/limit flags.
+```bash
+npm run cli -- setup status --project vgxness
+npm run cli -- sdd status --project vgxness --change my-change
+```
 
 Provider support shown in the Installation surface is:
 
@@ -230,7 +231,7 @@ Provider support shown in the Installation surface is:
 - **Antigravity** — placeholder/coming-soon guidance only.
 - **Custom/future** — extension point with safe manual/default unsupported behavior.
 
-The dashboard displays preview/status data, workflow registry entries, run traces, and approvals/preflights as read-only/copy-only data. It does **not** silently write OpenCode or other provider config, does **not** call provider executables, does **not** run install/apply/doctor/workflow commands, and does **not** approve/reject preflights. Any operational next action is copied for explicit execution outside the TUI.
+Setup and main-menu TUI surfaces do **not** silently write OpenCode or other provider config, do **not** call provider executables, and do **not** approve/reject preflights. Any operational next action is copied for explicit execution outside the TUI.
 
 ## Natural-language orchestrator preview
 

package/docs/funcionamiento-del-sistema.md

@@ -25,7 +25,7 @@ Para resolverlos, el sistema se construye sobre estos bloques:
 | Politica de permisos | Decide si una operacion se permite, se bloquea o requiere aprobacion humana. |
 | MCP server | Expone herramientas para que agentes consulten y actualicen el control plane. |
 | CLI | Permite operar el sistema desde comandos reproducibles. |
-| Dashboard/TUI | Muestra estado local, setup, runs y progreso SDD para humanos. |
+| TUI | Muestra setup y guias operativas locales para humanos. |
 
 ## Que problema resuelve
 
@@ -71,7 +71,7 @@ Humano / operador
       |
       | usa
       v
-CLI / Dashboard / TUI
+CLI / TUI
       |
       | llama servicios locales
       v
@@ -92,7 +92,7 @@ MCP control plane
 Core de vgxness
 ```
 
-La regla importante es que CLI, MCP y dashboard no deberian tener reglas de negocio duplicadas. Todos deben pasar por los mismos servicios de dominio.
+La regla importante es que CLI, MCP y TUI no deberian tener reglas de negocio duplicadas. Todos deben pasar por los mismos servicios de dominio.
 
 ## Capas del sistema
 
@@ -105,7 +105,7 @@ El sistema tiene varias superficies de uso.
 | CLI | Humano, scripts, smoke tests | `src/cli/dispatcher.ts` | Parsear comandos y llamar servicios. |
 | MCP stdio | Agentes y herramientas IA | `src/mcp/stdio-server.ts` | Exponer herramientas MCP locales. |
 | MCP control plane | Capa interna MCP | `src/mcp/control-plane.ts` | Validar tool calls y despacharlas a servicios. |
-| Dashboard/TUI | Humano local | `src/cli/interactive-dashboard.ts` | Mostrar estado operativo y permitir navegacion local. |
+| TUI | Humano local | `src/cli/tui/` | Mostrar setup y guias operativas locales. |
 
 La CLI es intencionalmente fina. Abre la base local, instancia servicios y devuelve JSON o texto. No deberia contener la logica profunda del producto.
 
@@ -633,7 +633,6 @@ Areas principales vistas en el dispatcher:
 | `sdd` | Estado, readiness y guardado de artefactos SDD. |
 | `orchestrator` | Preview de ruteo desde lenguaje natural hacia direct, plan, sdd o diagnose. |
 | `opencode` | Previews/integracion OpenCode. |
-| `dashboard` | Estado visual o interactivo. |
 | `mcp` | Setup, doctor e instalacion MCP. |
 
 La base se selecciona con la misma regla que el resto del sistema:
@@ -693,7 +692,7 @@ El proyecto ya contiene implementaciones concretas de:
 7. Politica de permisos base.
 8. MCP stdio server y control plane.
 9. CLI para operar los servicios.
-10. Setup status y dashboard local.
+10. Setup status y TUI local.
 11. Integracion inicial con OpenCode.
 12. CLI instalable con memoria global por defecto y compatibilidad explicita con `--db`.
 
@@ -814,7 +813,7 @@ Si todo vive solo en prompts, el sistema depende de disciplina del LLM. Si todo
 ```text
 src/
   agents/        Registro, resolucion, activacion y renderers de agentes.
-  cli/           Dispatcher, dashboard y renderers de salida CLI.
+  cli/           Dispatcher, TUI y renderers de salida CLI.
   export/        Redaccion/export de snapshots.
   harness/       Handlers reutilizables para tools internas.
   mcp/           Servidor stdio, schemas, validacion, doctor e instalacion MCP.

package/docs/prd.md

@@ -190,7 +190,7 @@ TUI state requirements:
 
 - Loading, empty, error, success, blocked, and permission states must be explicit and actionable.
 - Keyboard navigation and visible focus are required.
-- The dashboard TUI is read-only; provider config writes/install/apply are external-only, require explicit confirmation outside the dashboard, and are not run by dashboard flows.
+- TUI status/setup surfaces are read-only; provider config writes/install/apply are external-only, require explicit confirmation outside the TUI, and are not run by preview/status flows.
 
 #### Installation experience
 
@@ -299,7 +299,7 @@ Minimum capabilities:
 - Cloud sync.
 - Multi-user collaboration.
 - Team permissions and governance.
-- Web dashboard.
+- Web console.
 - Hosted memory service.
 - Marketplace for agents.
 - Full provider parity across every AI coding tool.
@@ -332,11 +332,11 @@ After the MVP proves local individual usage, expand toward:
 - Team/shared memory spaces.
 - Permissions, governance, and audit trails.
 - PR and chained-PR coordination.
-- Hosted dashboard for inspection and collaboration.
+- Hosted web console for inspection and collaboration.
 - Additional provider adapters.
 - Import/export between local and cloud memory backends.
 - Distributed agent workers.
-- Hosted observability and evaluation dashboard.
+- Hosted observability and evaluation UI.
 - Skill marketplace or shared skill catalog.
 
 ## Success criteria

package/docs/vgxcode.md

@@ -0,0 +1,76 @@
+# vgxcode OpenTUI root-owned shell
+
+Experimental Bun/OpenTUI coding interface for VGXNESS.
+
+## Why this is root-owned
+
+VGXNESS ships the existing `vgx`/`vgxness` CLI bins while the OpenTUI coding interface remains an internal root-owned surface. The repository root owns `@opentui/core`, the Bun lockfile, and verification.
+
+This keeps the shipped `vgx`/`vgxness` CLI stable while letting us build the OpenTUI experience directly from root source.
+
+## Run
+
+Prerequisite: install Bun.
+
+```bash
+bun src/cli/tui/opentui/code/index.ts
+```
+
+Interactive mode is read-only. Type a task/question and press `Enter`; `vgxcode` runs the root CLI bridge as either:
+
+```bash
+bun run cli:bun -- code inspect "<your prompt>" --events-jsonl
+bun run cli:bun -- code plan "<your prompt>" --events-jsonl
+```
+
+The prompt defaults to `inspect`. Press `Tab` to toggle between `inspect` and `plan`, or prefix a prompt with `/inspect` or `/plan`:
+
+```text
+/plan outline a safe implementation
+/inspect summarize the current architecture
+```
+
+After submit, the prompt input is cleared and the submitted prompt remains visible as `Last submitted`. The UI shows explicit `idle`, `running`, `completed`, and `error` states. It is intentionally mutation-disabled: no `craft`, no SDD writes, and no approval flow lives in this internal shell.
+
+To replay real read-only runtime events without spawning the root CLI, pipe the root Bun CLI JSONL bridge into `vgxcode`:
+
+```bash
+bun run cli:bun -- code inspect "What is this project?" --events-jsonl | bun src/cli/tui/opentui/code/index.ts
+bun run cli:bun -- code plan "Plan a safe change" --events-jsonl | bun src/cli/tui/opentui/code/index.ts
+```
+
+Use `bun run cli:bun -- ...` for OpenTUI-adjacent local testing. `npm run cli -- ...` uses Node/tsx and can fail when a path loads `@opentui/core`.
+
+Press `Ctrl+C` to exit.
+
+## Current scope
+
+The shell reads newline-delimited `CodeRuntimeEvent` JSON from stdin when piped. If stdin has events or parse errors, `vgxcode` renders that stream and does not spawn the root CLI. If stdin is a TTY, the OpenTUI entrypoint opens the interactive prompt and uses read-only `inspect` through the JSONL bridge.
+
+Errors are shown in the Activity panel when JSONL parsing fails, unsupported runtime events appear, npm/lifecycle banners appear in the stream, or the spawned root CLI exits non-zero.
+
+## Checks
+
+```bash
+npm run check:bun-lock          # from the repository root; read-only/advisory
+bun run verify:typecheck
+node --import tsx --test test/cli/tui/opentui-code.test.ts
+bun run smoke:opentui-code
+```
+
+The root `npm run check:bun-lock` command compares root `package.json`
+dependency specifiers with the root `bun.lock` without installing Bun or
+mutating `node_modules`. The root lockfile is the repository dependency
+authority; package evidence is validated by `bun run package:bun:evidence`.
+
+Manual interactive check:
+
+```bash
+bun src/cli/tui/opentui/code/index.ts
+# type: What is this project?
+# press Enter
+```
+
+## Safety rule
+
+`vgxcode` renders state. It must not execute tools, bypass approvals, or own mutation policy. Runtime, approvals, verification, SDD, and memory stay in the VGXNESS core runtime.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "vgxness",
-  "version": "1.2.0",
+  "version": "1.3.0",
   "description": "CLI and MCP control plane for guided AI-agent workflows, SDD, memory, and OpenCode setup.",
   "license": "SEE LICENSE IN LICENSE",
   "repository": {
@@ -21,7 +21,8 @@
   "type": "module",
   "scripts": {
     "cli": "tsx src/cli/index.ts",
-    "build": "tsc -p tsconfig.build.json && node scripts/copy-migrations.mjs",
+    "cli:bun": "bun src/cli/index.ts",
+    "build": "node scripts/clean-dist.mjs && tsc -p tsconfig.build.json && node scripts/copy-migrations.mjs",
     "verify": "bun run verify:typecheck && bun run verify:test && bun run verify:test:bun-storage && bun run verify:bun-sqlite && bun run verify:package",
     "verify:typecheck": "tsc --noEmit",
     "verify:test": "node scripts/run-node-tests.mjs",
@@ -30,11 +31,11 @@
     "verify:bun-sqlite": "bun scripts/probe-bun-sqlite.mjs",
     "ci:bun": "bun run check:bun-lock && bun run verify",
     "check:bun-lock": "node scripts/check-bun-lock.mjs",
-    "check:vgxcode:bun-lock": "node scripts/check-bun-lock.mjs --package-json packages/vgxcode/package.json --bun-lock packages/vgxcode/bun.lock",
     "check:bun:typecheck": "node scripts/run-bun-typecheck.mjs",
     "probe:bun": "node scripts/probe-bun-compat.mjs",
     "probe:bun-runtime": "node scripts/probe-bun-runtime-cli-mcp.mjs",
     "verify:bun-runtime": "node scripts/probe-bun-runtime-cli-mcp.mjs --require-pass",
+    "smoke:opentui-code": "bun src/cli/tui/opentui/code/smoke.ts",
     "package:bun:evidence": "node scripts/probe-bun-package-evidence.mjs",
     "test": "node scripts/run-node-tests.mjs",
     "typecheck": "tsc --noEmit"
@@ -53,13 +54,11 @@
   ],
   "dependencies": {
     "@modelcontextprotocol/sdk": "^1.29.0",
-    "ink": "^7.0.3",
-    "react": "^19.2.6",
+    "@opentui/core": "^0.2.16",
     "zod": "^4.4.3"
   },
   "devDependencies": {
     "@types/node": "^22.15.18",
-    "@types/react": "^19.2.15",
     "tsx": "^4.19.4",
     "typescript": "^5.8.3"
   },