@mathismeadows/roamer-device-auth 1.5.1 → 1.5.2

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@mathismeadows/roamer-device-auth",
-  "version": "1.5.1",
+  "version": "1.5.2",
   "private": false,
   "mcpName": "com.mathismeadows/roamer-mcp",
   "type": "module",

package/roamer-device-auth.mjs

@@ -197,8 +197,20 @@ async function listKnownClientSlugs() {
   for (const entry of entries) {
     // Safe to split on "__" without ambiguity: neither a client slug (clientSlugFromInitializeLine)
     // nor an identity key (identityKeyFromTokens) can contain an underscore post-sanitization.
-    const match = entry.match(/^roamer_(?:tokens|loopback_tokens)__([^_]+)__/);
-    if (match) slugs.add(match[1]);
+    const withIdentity = entry.match(/^roamer_(?:tokens|loopback_tokens)__([^_]+)__/);
+    if (withIdentity) {
+      slugs.add(withIdentity[1]);
+      continue;
+    }
+    // BUG (found live 2026-09-08, caused a real cross-session logout): a slug that has never
+    // reconnected since AUTH-54 shipped only has the pre-AUTH-54 legacy file — no identity
+    // segment at all — and was invisible here. login/logout's own "if status lists exactly one
+    // slug, there's no ambiguity" reasoning then wrongly treated a real, actively-used client as
+    // nonexistent, silently acting on a *different* session's slug instead because it was the
+    // only one that happened to already be migrated. A legacy-only slug must still count as a
+    // real, known candidate even though it has no identity cached under the new scheme yet.
+    const legacy = entry.match(/^roamer_(?:tokens|loopback_tokens)__([^_]+)\.json$/);
+    if (legacy) slugs.add(legacy[1]);
   }
   return [...slugs].sort();
 }