@rnbsolucoes/axion-code 0.1.31 → 0.1.32

package/README.md

@@ -392,8 +392,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 +414,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.32",
   "description": "Axion Code CLI harness for the Axion ecosystem.",
   "type": "module",
   "repository": {