@rnbsolucoes/axion-code 0.1.43 → 0.1.45

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/README.md CHANGED
@@ -390,15 +390,19 @@ Maestro/workers loop from the new Desktop Nexus provider:
390
390
 
391
391
  ```powershell
392
392
  axion provider nexus status --profile nexus
393
- axion provider nexus set --profile pcp-nexus --engine pcp --judge-kind sakana --judge sakana:fugu --image-model image-default --video-model video-pro --exec3 mock:mock/worker --exec3-instruction "general text worker"
393
+ axion provider nexus set --profile pcp-nexus --engine pcp --judge-kind sakana --judge sakana:fugu --image-provider imagehub --image-model image-default --video-provider videohub --video-model video-pro --exec3 mock:mock/worker --exec3-instruction "general text worker"
394
394
  ```
395
395
 
396
- PCP in the CLI currently supports Maestro tool-calling with text workers
397
- `exec3` and `exec4`. Nexus streams normalized lifecycle telemetry to the TUI
398
- for Fusion and PCP phases; internal PCP worker dispatches stay private and do
399
- not surface as app-level tool approvals. Image/video generative slots are
400
- preserved in the shared schema for Desktop compatibility but are not executed
401
- by the CLI yet.
396
+ PCP in the CLI supports Maestro tool-calling with text workers `exec3` and
397
+ `exec4`, plus image/video slots exposed as internal PCP workers. Nexus streams
398
+ normalized lifecycle telemetry to the TUI for Fusion and PCP phases; internal
399
+ PCP worker dispatches stay private and do not surface as app-level tool
400
+ approvals. Image/video dispatch is refused unless permission mode is `yolo`;
401
+ even in `yolo`, the CLI currently returns a structured "media runtime
402
+ unavailable" tool result until the local media runtime lands. When Axion
403
+ Desktop saves PCP image/video slots as model-only capability references, the CLI
404
+ resolves the provider label from Desktop's `capability_selections` store on a
405
+ best-effort basis for status, audit metadata and worker labels.
402
406
 
403
407
  ## Build
404
408
 
@@ -415,10 +419,10 @@ This is a functional direction MVP, not the full harness:
415
419
 
416
420
  - direct provider streaming exists for OpenAI-compatible chat completions,
417
421
  OpenAI Responses and Anthropic Messages;
418
- - Nexus supports the legacy Fusion engine and the new PCP text-only
419
- Maestro/workers engine with initial stream normalization; richer judge
420
- telemetry, redaction/audit surfacing, TUI Nexus configuration and image/video
421
- workers remain deferred;
422
+ - Nexus supports the legacy Fusion engine and the new PCP Maestro/workers
423
+ engine with stream normalization, redacted audit surfacing, TUI Nexus
424
+ configuration, text workers and permission-gated image/video worker
425
+ placeholders; real CLI media generation remains deferred;
422
426
  - terminal logo uses Sixel when available and falls back to width-bounded ANSI/block rendering;
423
427
  - initial chat splash shows the Axion logo and system name until the first interaction;
424
428
  - guarded dispatcher execution is limited to workspace-local `Read`, `Glob`,
Binary file
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@rnbsolucoes/axion-code",
3
- "version": "0.1.43",
3
+ "version": "0.1.45",
4
4
  "description": "Axion Code CLI harness for the Axion ecosystem.",
5
5
  "type": "module",
6
6
  "repository": {