@rnbsolucoes/axion-code 0.1.16 → 0.1.17

package/README.md

@@ -280,8 +280,13 @@ guarded dispatcher must use.
 Requests are persisted in the shared session database under
 `%USERPROFILE%\.axion\sessions\axion.db` with the redacted decision, risk class,
 permission mode, impact summary and pending/approved/denied state. This is the
-headless contract that the TUI approval modal and guarded dispatcher will use
-before mutating filesystem, shell or MCP tools are enabled.
+headless contract used by the TUI approval menu and the future guarded
+dispatcher before mutating filesystem, shell or MCP tools are enabled.
+
+Provider stream `tool_call` events now open the TUI approval menu when the
+active permission mode requires review. Approve/Deny records the audited
+decision and returns focus to the chat input. Actual tool execution remains
+blocked until the guarded dispatcher is enabled.
 
 Examples:
 
@@ -341,7 +346,9 @@ This is a functional direction MVP, not the full harness:
   deferred until the Nexus beta handoff;
 - 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;
-- no mutating tool execution yet; the approval/sandbox classification and persisted approval queue contracts are implemented and inspectable;
+- no mutating tool execution yet; the approval/sandbox classification,
+  persisted approval queue and TUI approval menu are implemented and
+  inspectable;
 - no executable Pi RPC bridge yet;
 - no MCP transport execution yet;
 - native subagent execution is prompt-isolated and provider/model-inherited; richer multi-subagent orchestration, streaming and budget telemetry remain next-cycle items.

package/package.json

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