@lotics/cli 0.96.3 → 0.96.4

package/README.md

@@ -72,6 +72,8 @@ lotics org use acme                 # switch active org by name (or org id)
 lotics org use "Acme Corp"          # names are case-insensitive
 ```
 
+The org **id** is the identity; the name is a label cached when the key was saved. Rename an org in the app and the cached label goes stale — the old name still works, the new one matches nothing — until `lotics auth whoami` refreshes it. A name matching two saved orgs is refused rather than guessed; use the id.
+
 ### Working in parallel (worktrees)
 
 Pin a directory to its own org/workspace so a global `org use` elsewhere never disturbs it. The pin is a pointer — the key still comes from the global store, so there's nothing to paste:

package/dist/src/cli.js

@@ -91630,6 +91630,11 @@ async function main() {
       const info = await client2.whoami();
       const existing = loadGlobalConfig() ?? {};
       saveGlobalConfig({ ...existing, email: info.email });
+      const cached2 = existing.profiles?.[info.organization_id];
+      if (cached2 && cached2.org_name !== info.organization_name) {
+        upsertProfile(info.organization_id, { api_key: cached2.api_key, org_name: info.organization_name });
+        console.error(`Renamed since this key was saved: "${cached2.org_name}" \u2192 "${info.organization_name}" (updated locally)`);
+      }
       const viewAs = flags.viewAs ?? process.env.LOTICS_VIEW_AS;
       if (flags.json) {
         console.log(JSON.stringify({ ...info, workspace_id: ctx2.workspaceId ?? null, source: ctx2.source, view_as: viewAs ?? null }, null, 2));

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@lotics/cli",
-  "version": "0.96.3",
+  "version": "0.96.4",
   "description": "Lotics SDK and CLI for AI agents",
   "type": "module",
   "bin": {