@rnbsolucoes/axion-code 0.1.28 → 0.1.31

package/README.md

@@ -42,6 +42,8 @@ axion-code provider profile set or-free
 axion-code provider profile delete or-free
 axion-code provider profile active
 axion-code provider model list openrouter --json
+axion-code provider cost set openrouter --model openai/gpt-5-mini --max-usd 0.25 --input-usd-per-1m 0.25 --output-usd-per-1m 2 --max-output-tokens 4000
+axion-code provider cost status --profile openrouter --model openai/gpt-5-mini --json
 axion-code provider test openrouter google/gemini-2.5-flash-lite
 axion-code permission list --json
 axion-code permission set full_permission
@@ -64,6 +66,7 @@ axion-code agents run bug-hunter "review this login flow"
 axion-code agents run-many bug-hunter,performance-reviewer "review this login flow" --budget-tokens 2000 --stream
 axion-code learn --json
 axion-code package inspect <path>
+axion-code package self-check --json
 ```
 
 ## Install
@@ -103,6 +106,18 @@ current platform into the local Axion Code bin directory and then executes it. I
 a source clone only, if no packaged binary exists, the wrapper can build from Go
 as a development fallback.
 
+To classify the currently executed binary for support or security review, run:
+
+```powershell
+axion package self-check --json
+```
+
+The self-check reports the executable path, real path, runtime version,
+SHA-256, file size, package cache marker when present and a provenance
+classification such as `npm-wrapper-cache`, `npm-package-release`,
+`source-build` or `unknown-local-binary`. It is deterministic local
+provenance, not a replacement for future Authenticode signing.
+
 Requirements:
 
 - Node.js 18+ for the npm wrapper.
@@ -173,10 +188,21 @@ Axion Code selection is isolated:
 %USERPROFILE%\.axion\mcp-servers.json
 %USERPROFILE%\.axion\plugins.json
 %USERPROFILE%\.axion\sub-agents.json
+%USERPROFILE%\.axion\harness\cost-policy.json
 ```
 
 OpenRouter uses `OPENROUTER_API_KEY` from the environment or a `secret:<NAME>` reference stored in `C:\Israel\Pesoal\secrets.env` (override for tests: `AXION_SECRETS_ENV`). Provider profile config stores only references, never the key value.
 
+Provider-specific cost ceilings are stored outside the Desktop profile schema in
+`%USERPROFILE%\.axion\harness\cost-policy.json`. Use `provider cost set` to
+bind a ceiling and token prices to a profile or profile/model pair. The runtime
+blocks a request before provider execution when the estimated input or configured
+maximum output cost would exceed the ceiling. After a response, actual
+input/output usage is converted to cost and surfaced in provider/subagent stream
+telemetry; if actual cost exceeds the ceiling, the turn returns an explicit cost
+ceiling error. A ceiling without token prices is not enforced, because Axion Code
+does not infer provider pricing silently.
+
 For test/dev isolation, set `AXION_HOME` to a temporary folder. In normal use,
 leave it unset so Desktop and CLI share the same provider catalog while keeping
 their active provider/model selections independent.
@@ -355,6 +381,20 @@ axion provider profile set or-free
 axion
 ```
 
+Nexus profiles share the same `%USERPROFILE%\.axion\harness\nexus-config.json`
+used by Axion Desktop. The default `fusion` engine runs the existing
+panel -> judge -> final flow. The `pcp` engine enables the text-only
+Maestro/workers loop from the new Desktop Nexus provider:
+
+```powershell
+axion provider nexus status --profile nexus
+axion provider nexus set --profile pcp-nexus --engine pcp --judge-kind sakana --judge sakana:fugu --exec3 mock:mock/worker --exec3-instruction "general text worker"
+```
+
+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.
+
 ## Build
 
 ```powershell
@@ -369,8 +409,10 @@ If Go is not on PATH, use a verified local Go toolchain and keep generated binar
 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 stream normalization remains
-  deferred until the Nexus beta handoff;
+  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;
 - 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`,
@@ -381,4 +423,4 @@ This is a functional direction MVP, not the full harness:
   `tool_result` continuation turn;
 - remote MCP transports, browser, process and unknown tools remain blocked;
 - no executable Pi RPC bridge yet;
-- native subagent execution is prompt-isolated and provider/model-inherited; `agents run-many` provides parallel fan-out, compact comparison, aggregate usage, a token budget ceiling and streamed lifecycle/telemetry events. Provider-specific cost ceilings remain a next-cycle item.
+- native subagent execution is prompt-isolated and provider/model-inherited; `agents run-many` provides parallel fan-out, compact comparison, aggregate usage, a token budget ceiling and streamed lifecycle/telemetry events. Provider/model cost ceilings are enforced by the shared Axion cost policy.

package/package.json

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