@rnbsolucoes/axion-code 0.1.32 → 0.1.33

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
@@ -287,7 +287,9 @@ MCP import files use the same JSON array shape as `%USERPROFILE%\.axion\mcp-serv
287
287
 
288
288
  `axion mcp import <file.json>` merges by `id`, preserves `native` protection for built-ins, writes formatted JSON, and rejects entries without `id` or without the required `command`/`url` for the selected transport. Native MCPs such as `dotcontext` cannot be removed, only disabled.
289
289
 
290
- `axion mcp tools <id> [--json]` starts an enabled stdio MCP server, performs the MCP initialize handshake and returns the exact tools advertised by `tools/list`. This is the recommended smoke test for native MCPs before enabling provider tool calls, for example `axion mcp tools dotcontext --json`.
290
+ `axion mcp tools <id> [--json]` starts an enabled stdio MCP server, performs the MCP initialize handshake and returns the exact tools advertised by `tools/list`. This is the recommended smoke test for native MCPs before enabling provider tool calls, for example `axion mcp tools axion-dotcontext --json`.
291
+
292
+ The native Dotcontext MCP uses the current official package surface, `npx -y @dotcontext/mcp@latest`. Existing shared Axion homes are migrated from the deprecated `dotcontext` npm package to `@dotcontext/mcp@latest` during bootstrap while preserving local MCP status metadata. Because the native entry points at `@latest`, normal MCP startup pulls upstream Dotcontext server updates; Axion code changes are needed only when Dotcontext changes package names, tool contracts or Axion-specific integration policy.
291
293
 
292
294
  Plugins are read from the same shared Axion Desktop file, `%USERPROFILE%\.axion\plugins.json`. The CLI can list, enable, disable and remove plugin records, but executable plugin installation remains intentionally gated for the next trust-policy cycle.
293
295
 
@@ -345,7 +347,7 @@ axion permission resolve <approval-id> --deny --reason "not needed" --json
345
347
  axion tool run Read "{\"path\":\"README.md\"}" --mode full_permission --json
346
348
  axion tool run Write "{\"path\":\"notes/out.txt\",\"content\":\"approved\"}" --session smoke --turn turn-1 --approval <approval-id> --mode request_permission --json
347
349
  axion tool run Shell "{\"command\":\"echo axion-shell\"}" --session smoke --turn turn-1 --approval <approval-id> --mode request_permission --json
348
- axion mcp tools dotcontext --json
350
+ axion mcp tools axion-dotcontext --json
349
351
  # Shape: replace server/tool with an enabled MCP tool advertised by tools/list.
350
352
  axion tool run mcp__your-server__list_items "{\"query\":\"PREVC\"}" --mode full_permission --json
351
353
  ```
Binary file
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@rnbsolucoes/axion-code",
3
- "version": "0.1.32",
3
+ "version": "0.1.33",
4
4
  "description": "Axion Code CLI harness for the Axion ecosystem.",
5
5
  "type": "module",
6
6
  "repository": {