@visa/cli 5.0.0-rc.411 → 5.0.0-rc.413

package/README.md

@@ -92,16 +92,21 @@ for one) uses the same tools through `visa-tool`, which starts this package's
 MCP server and makes one call:
 
 ```sh
-VISA_RUNTIME_CUSTODY_PROFILE=headless visa connect --no-open --wait 0   # once; the owner approves
-visa-tool --skill    # a skill file for the app to save: recovery after a rebuilt VM, and the rules below
+VISA_CLI_RUNTIME=muse VISA_RUNTIME_CUSTODY_PROFILE=headless visa connect --no-open --wait 0   # once; the owner approves
+visa-tool --skill    # the Visa skill: recovery after a rebuilt VM, and the rules below
 visa-tool --list     # the server's rules and the tools with their inputs (JSON)
 visa-tool status     # one call: the tool's answer as JSON, exit 1 on a refusal
 visa-tool pay '{"target":"https://…","request_id":"order-1"}'   # no max: a price preview, nothing is paid
 ```
 
 On a computer with no keyring, every command needs
-`VISA_RUNTIME_CUSTODY_PROFILE=headless`. The skill reads `visa-tool --list` on
-each use rather than copying it, so an update never leaves it stale.
+`VISA_RUNTIME_CUSTODY_PROFILE=headless`. `VISA_CLI_RUNTIME` names the app, so
+the agent is called by its name (Muse) rather than the app `visa connect` falls
+back to mounting. The skill reads `visa-tool --list` on
+each use rather than copying it, and carries a version: when `--list` reports a
+higher `skill_version`, the app asks its owner for the new text. Muse will not
+save a program's output as a skill, so its owner pastes the same text from the
+Console's Muse message.
 
 ## MCP tools