@rnbsolucoes/axion-code 0.1.80 → 0.1.82

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
@@ -40,6 +40,8 @@ axion-code remote-control stop --json
40
40
  axion-code remote-control pair --json < pair.json
41
41
  axion-code remote-control intent --json < intent.json
42
42
  axion-code remote-control events --json
43
+ axion-code remote-control seal --json < payload.json
44
+ axion-code remote-control open --json < secure-frame.json
43
45
  axion-code provider list --json
44
46
  axion-code provider profile init
45
47
  axion-code provider profile list --json
@@ -78,10 +80,16 @@ axion-code hooks status --json
78
80
  axion-code hooks add --event UserPromptSubmit --action inject --name Safety --content "Use trusted hook context only." --enabled
79
81
  axion-code hooks enable
80
82
  axion-code package inspect <path>
81
- axion-code package self-check --json
82
- ```
83
-
84
- ## Install
83
+ axion-code package self-check --json
84
+ ```
85
+
86
+ `remote-control intent --json` validates the active paired lease and enqueues
87
+ accepted mobile intents for the owning TUI session. The TUI remains the executor:
88
+ `user_message` is dispatched as a normal local provider turn, `tool_approval`
89
+ resolves the existing approval queue, and provider/tool execution never moves to
90
+ the mobile client.
91
+
92
+ ## Install
85
93
 
86
94
  Official install, after the package is published to the public npm registry:
87
95
 
Binary file
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@rnbsolucoes/axion-code",
3
- "version": "0.1.80",
3
+ "version": "0.1.82",
4
4
  "description": "Axion Code CLI harness for the Axion ecosystem.",
5
5
  "type": "module",
6
6
  "repository": {