@topolo/cli 0.13.13 → 0.13.16

package/package.json

@@ -1,8 +1,8 @@
 {
   "name": "@topolo/cli",
   "packageManager": "pnpm@10.17.1",
-  "version": "0.13.13",
-  "topoloPublishedVersion": "0.13.13",
+  "version": "0.13.16",
+  "topoloPublishedVersion": "0.13.16",
   "description": "Public command-line interface for Topolo customer organizations, developers, and agents.",
   "license": "UNLICENSED",
   "author": "Topolo",
@@ -31,7 +31,7 @@
   },
   "dependencies": {
     "@modelcontextprotocol/sdk": "1.31.0",
-    "@topolo/mcp": "0.14.27",
+    "@topolo/mcp": "0.14.30",
     "@topolo/sdk": "0.23.22",
     "commander": "^12.1.0",
     "undici": "6.29.0"

package/skills/topolo/SKILL.md

@@ -67,8 +67,16 @@ TOPOLO_CONTEXT=org:org_acme topolo --env production whoami --json
 TOPOLO_CONTEXT=org:org_acme topolo --env production actions --service brand --json
 ```
 
-The CLI keeps this pin through credential refresh and never changes the shared
-active context. A missing pinned credential does not select another context.
+`topolo --context <key> <command>` pins one command the same way. The CLI keeps
+this pin through credential refresh and never changes the stored default
+context. A missing pinned credential does not select another context.
+
+There is no implicit default: when several contexts are signed in for an
+environment, any command or MCP without `--context`/`TOPOLO_CONTEXT` refuses
+("the context is no longer safe to assume"). Pin the context; do not run
+`topolo context use` to work around the refusal. `topolo auth login` never moves
+the stored default and prints which user and organization were approved; check
+that line, because the browser may approve a different account than intended.
 
 For concurrent agents or multiple MCP connections, never coordinate by changing
 one shared active context. Register each pinned context through the CLI so it
@@ -79,6 +87,8 @@ topolo setup --name topolo-acme --context org:org_acme --env production
 topolo doctor --name topolo-acme
 ```
 
+Every registration setup writes pins `TOPOLO_ENV` and `TOPOLO_CONTEXT`; without
+`--context` it pins the only signed-in context and refuses when there are several.
 The context selector accepts an
 exact key returned by `topolo context ls --json` (such as `personal` or
 `org:<orgId>`) or a unique stored organization id, slug, or name. Each process
@@ -270,6 +280,13 @@ Local deletion does not revoke the upstream credential; use its published
 revocation action separately when required. Other SDK/remote hosts keep
 redaction unless they explicitly provide a protected store.
 
+The only supported way to put a referenced API key on disk is an
+operator-approved custody file:
+`topolo credentials write-custody <reference> --out <absolute-dir> --app <appId> --api-key-id <id> --confirm --json`
+verifies the key against Auth, writes 0600 `api-key.json` and `custody.json`
+(metadata and a SHA-256 digest only) into a 0700 directory, prints no secret,
+and deletes the local reference without revoking the upstream key.
+
 ## Generic public API escape hatch
 
 Only when public docs provide a complete contract: