@rnbsolucoes/axion-code 0.1.31 → 0.1.33

package/README.md

@@ -287,7 +287,9 @@ MCP import files use the same JSON array shape as `%USERPROFILE%\.axion\mcp-serv
 
 `axion mcp import <file.json>` merges by `id`, preserves `native` protection for built-ins, writes formatted JSON, and rejects entries without `id` or without the required `command`/`url` for the selected transport. Native MCPs such as `dotcontext` cannot be removed, only disabled.
 
-`axion mcp tools <id> [--json]` starts an enabled stdio MCP server, performs the MCP initialize handshake and returns the exact tools advertised by `tools/list`. This is the recommended smoke test for native MCPs before enabling provider tool calls, for example `axion mcp tools dotcontext --json`.
+`axion mcp tools <id> [--json]` starts an enabled stdio MCP server, performs the MCP initialize handshake and returns the exact tools advertised by `tools/list`. This is the recommended smoke test for native MCPs before enabling provider tool calls, for example `axion mcp tools axion-dotcontext --json`.
+
+The native Dotcontext MCP uses the current official package surface, `npx -y @dotcontext/mcp@latest`. Existing shared Axion homes are migrated from the deprecated `dotcontext` npm package to `@dotcontext/mcp@latest` during bootstrap while preserving local MCP status metadata. Because the native entry points at `@latest`, normal MCP startup pulls upstream Dotcontext server updates; Axion code changes are needed only when Dotcontext changes package names, tool contracts or Axion-specific integration policy.
 
 Plugins are read from the same shared Axion Desktop file, `%USERPROFILE%\.axion\plugins.json`. The CLI can list, enable, disable and remove plugin records, but executable plugin installation remains intentionally gated for the next trust-policy cycle.
 
@@ -345,7 +347,7 @@ axion permission resolve <approval-id> --deny --reason "not needed" --json
 axion tool run Read "{\"path\":\"README.md\"}" --mode full_permission --json
 axion tool run Write "{\"path\":\"notes/out.txt\",\"content\":\"approved\"}" --session smoke --turn turn-1 --approval <approval-id> --mode request_permission --json
 axion tool run Shell "{\"command\":\"echo axion-shell\"}" --session smoke --turn turn-1 --approval <approval-id> --mode request_permission --json
-axion mcp tools dotcontext --json
+axion mcp tools axion-dotcontext --json
 # Shape: replace server/tool with an enabled MCP tool advertised by tools/list.
 axion tool run mcp__your-server__list_items "{\"query\":\"PREVC\"}" --mode full_permission --json
 ```
@@ -392,8 +394,11 @@ axion provider nexus set --profile pcp-nexus --engine pcp --judge-kind sakana --
 ```
 
 PCP in the CLI currently supports Maestro tool-calling with text workers
-`exec3` and `exec4`. Image/video generative slots are preserved in the shared
-schema for Desktop compatibility but are not executed by the CLI yet.
+`exec3` and `exec4`. Nexus streams normalized lifecycle telemetry to the TUI
+for Fusion and PCP phases; internal PCP worker dispatches stay private and do
+not surface as app-level tool approvals. Image/video generative slots are
+preserved in the shared schema for Desktop compatibility but are not executed
+by the CLI yet.
 
 ## Build
 
@@ -411,8 +416,9 @@ This is a functional direction MVP, not the full harness:
 - direct provider streaming exists for OpenAI-compatible chat completions,
   OpenAI Responses and Anthropic Messages;
 - Nexus supports the legacy Fusion engine and the new PCP text-only
-  Maestro/workers engine; Nexus streaming normalization, judge telemetry,
-  redaction/audit surfacing and image/video workers remain deferred;
+  Maestro/workers engine with initial stream normalization; richer judge
+  telemetry, redaction/audit surfacing, TUI Nexus configuration and image/video
+  workers remain deferred;
 - terminal logo uses Sixel when available and falls back to width-bounded ANSI/block rendering;
 - initial chat splash shows the Axion logo and system name until the first interaction;
 - guarded dispatcher execution is limited to workspace-local `Read`, `Glob`,

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@rnbsolucoes/axion-code",
-  "version": "0.1.31",
+  "version": "0.1.33",
   "description": "Axion Code CLI harness for the Axion ecosystem.",
   "type": "module",
   "repository": {