@catalyst-cloud/cli 0.16.20 → 0.16.22

package/CHANGELOG.md

@@ -1,5 +1,13 @@
 # Changelog
 
+## 0.16.22
+
+A self-hosted Linux machine set up over SSH now keeps updating after you log out, with no `sudo` step. Setup turns on lingering for your user by itself, and says so along with how to undo it (`loginctl disable-linger $USER`). Only when the machine does not allow that does setup name the one `sudo loginctl enable-linger $USER` command, and it says updates stop at logout until you run it. `catalyst runner auto-update status` now says whether updates keep running after you log out. For a machine you already set up, install this version and run `catalyst runner auto-update on`.
+
+## 0.16.21
+
+`catalyst accounts` now leaves out removed AI accounts: ones an admin revoked, or whose paid access ended. They take no work and take no new credential, so they no longer appear as accounts to repair. The list says how many it left out, and `catalyst accounts --all` shows them, marked "removed — kept for history". Setup now names a revoked account as ended instead of asking you to turn it on. Update the Catalyst plugin's skills along with the CLI: setup's account check uses `--all`, which older CLIs do not know.
+
 ## 0.16.20
 
 Setup on Linux now prints every command whole, on its own line, so you can copy it from any terminal width. When this computer still needs the session egress service, setup prints one `sudo` command that checks the installer's fingerprint and installs and starts the service. Run it, then run the same setup command again. When nothing may take work for your workspace yet, setup now names the command that enrolls this computer as a self-hosted machine: `catalyst onboard --runner --team <your team>`.

package/dist/args.js

@@ -331,7 +331,9 @@ export const FLAG_TABLES = {
             help: "skip the published-release check (no network)",
         },
     },
-    accounts: {},
+    accounts: {
+        all: { value: false, help: "also list removed accounts, which are kept for history and take no work" },
+    },
     seat: {
         size: { value: true, help: "model size: big or med" },
         stage: { value: true, help: "sized relay stage; defaults from size" },
@@ -538,7 +540,7 @@ export const VERB_USAGE = {
     write: "write <comment <ticket> --body|--stdin [--parent] [--bookkeeping] [--as-user] | state <ticket> --slot|--state-id|--state-type | label <ticket> --add... --remove... | create --team --title [--description|--stdin] [--label] [--priority] | reaction <ticket>|--comment <id> --emoji <e> | attachment <ticket> --title --url | session <ticket> [--title] [--plan-file] [--activity]>",
     ask: "ask <raise --team --title [--context] [--option]... [--default] --blocks <ticket>...|--nothing-to-block [--ask-key] [--gates-pr <n>... --released-by <letter>... [--gates-label hold|hold:preview]... [--gates-repo <owner/name>]] | accept <askTicket> --answer <commentId> --role <role> | list [--anyone] [--json]>",
     ready: "ready [--onboarding] [--local-sync] [--json] [--offline]",
-    accounts: "accounts [--json]",
+    accounts: "accounts [--all] [--json]",
     seat: "seat checkout --size big|med --harness claude,codex,opencode [--session-id ID] [--stage STAGE] [--key-env NAME]",
     mcp: "mcp <add <name> --url URL <--auth none|--bearer SECRET_NAME|--header NAME=SECRET_NAME...>|list|remove <name>> [--json]",
     team: "team <list|check <KEY>|check --all|map <KEY> [--stage role=StateName]... [--yes --plan-hash H]|adopt <KEY> [--undo] [--yes --plan-hash H]|migrate <KEY> [--choice sourceId=destinationId]... [--retire] [--yes --plan-hash H]|checklist <KEY>> [--json]",

package/dist/execution.js

@@ -311,9 +311,12 @@ export async function cmdQueue(args, ctx) {
     ctx.stdout(args.json ? JSON.stringify(out) : JSON.stringify(out, null, 2));
     return 0;
 }
-/** The five status words `/api/v1/coding-accounts` reports, in the words a customer reads. */
+/** The status words `/api/v1/coding-accounts` reports, in the words a customer reads. */
 export const ACCOUNT_STATUS = {
-    "expired-or-revoked": "expired or revoked — replace its credential on the AI accounts page (Settings → AI accounts → the account → Replace credential) before it can take work",
+    "expired-or-revoked": "credential expired or missing — replace its credential on the AI accounts page (Settings → AI accounts → the account → Replace credential) before it can take work",
+    // CTC-6204: revoked and ended accounts share one history-only end state (Ryan, 2026-10-19).
+    ended: "removed — kept for history, takes no work",
+    "out-of-rotation": "paused — its owner took it out of rotation",
     walled: "walled — the provider's usage limit is spent for now",
     active: "active — observed working",
     attested: "attested — healthy at last check, no work observed since",
@@ -326,12 +329,18 @@ export function accountDisplayName(a) {
             return v.trim();
     return a.accountSlot ?? "?";
 }
+/** CTC-6204: a revoked account, or one whose paid access ended, can never take work again and takes
+ *  no new credential. It is kept for history only. An older cloud still calls a revoked account
+ *  `expired-or-revoked`, so `revokedAtMs` decides as well as the status word. */
+export function historyOnly(a) {
+    return typeof a.revokedAtMs === "number" || a.status === "ended";
+}
 /** One slot as a line a human reads: who it is, what state it is in, and what it is spending on. */
 export function renderAccount(a) {
     const display = accountDisplayName(a);
     const name = display === (a.accountSlot ?? "?") ? display : `${display} (${a.accountSlot ?? "?"})`;
     const harness = a.harness ? `/${a.harness}` : "";
-    const status = a.status ? (ACCOUNT_STATUS[a.status] ?? a.status) : "status unknown";
+    const status = historyOnly(a) ? ACCOUNT_STATUS.ended : a.status ? (ACCOUNT_STATUS[a.status] ?? a.status) : "status unknown";
     const bits = [`${name}  ${a.provider ?? "?"}${harness}  ${status}`];
     // CTC-4199: a cancelled subscription is kept for reporting and not used; never re-credential it (Ryan, 2026-09-29).
     if (a.renewalStatus === "canceled")
@@ -367,17 +376,29 @@ export async function cmdAccounts(args, ctx) {
     if (res.status === 404)
         throw needsNewerCloud("coding-account status", cfg);
     const accounts = Array.isArray(res.body) ? res.body : (res.body?.accounts ?? []);
+    // CTC-6204: removed accounts are history, so they are left out unless --all asks for them. Listed,
+    // they read as accounts to repair, and agents kept trying to revive them.
+    const shown = flagBool(args, "all") ? accounts : accounts.filter((a) => !historyOnly(a));
+    const hidden = accounts.length - shown.length;
     if (args.json) {
-        const named = accounts.map((a) => ({ ...a, displayName: accountDisplayName(a) }));
-        ctx.stdout(JSON.stringify(Array.isArray(res.body) ? named : { ...res.body, accounts: named }));
+        const named = shown.map((a) => ({ ...a, displayName: accountDisplayName(a), removed: historyOnly(a) }));
+        ctx.stdout(JSON.stringify(Array.isArray(res.body) ? named : { ...res.body, accounts: named, removedHidden: hidden }));
         return 0;
     }
+    const addAt = `${normalizeBaseUrl(cfg.baseUrl)}/settings/coding-accounts`;
+    const hiddenLine = `${hidden} removed account${hidden === 1 ? " is" : "s are"} kept for history and take no work; catalyst accounts --all lists ${hidden === 1 ? "it" : "them"}.`;
     if (accounts.length === 0) {
-        ctx.stdout(`No coding accounts are enrolled in this workspace. A workspace owner or admin adds one at ${normalizeBaseUrl(cfg.baseUrl)}/settings/coding-accounts; there is no command for that yet.`);
+        ctx.stdout(`No coding accounts are enrolled in this workspace. A workspace owner or admin adds one at ${addAt}; there is no command for that yet.`);
+        return 0;
+    }
+    if (shown.length === 0) {
+        ctx.stdout(`No AI account in this workspace can take work. A workspace owner or admin adds one at ${addAt}. ${hiddenLine}`);
         return 0;
     }
-    for (const a of accounts)
+    for (const a of shown)
         ctx.stdout(renderAccount(a));
+    if (hidden > 0)
+        ctx.stdout(hiddenLine);
     return 0;
 }
 /**

package/dist/onboard-accounts.js

@@ -97,11 +97,13 @@ async function inventory(ctx, journal, signal) {
  * (the server's isUsableCodingAccount): any provider, any member's account, and a canceled
  * subscription keeps working until its paid access ends. */
 function unusableCause(row, now) {
-    if (row.declaredState !== "active")
-        return "coding_account_inactive";
+    // CTC-6204: ended first. A revoked account is usually also declared inactive, and "turn it on"
+    // is advice it can never take.
     if (row.revokedAtMs !== null ||
         (row.accessEndsAtMs !== null && row.accessEndsAtMs <= now))
         return "coding_account_ended";
+    if (row.declaredState !== "active")
+        return "coding_account_inactive";
     if (row.needsCredential)
         return "coding_account_needs_login";
     if (row.quarantined)

package/dist/runner-auto-update.js

@@ -82,6 +82,21 @@ export function systemdUnits(deps, dir) {
         ].join("\n"),
     };
 }
+/** A user timer runs only while this person's systemd user manager does, and without lingering that
+ *  manager stops when they log out of a headless machine. */
+function lingering(run, uid) {
+    return /Linger=yes/.test(run("loginctl", ["show-user", String(uid), "--property=Linger"]).stdout);
+}
+/** Turn lingering on for this person when it is off. On most distributions polkit lets a user in an
+ *  active session, SSH included, do this without sudo (CTC-6264). --no-ask-password: a refusal must
+ *  come back as an answer, never as a prompt. Returns the state read back afterwards. */
+function ensureLingering(run, uid) {
+    if (lingering(run, uid))
+        return { linger: true, turnedOn: false };
+    run("loginctl", ["--no-ask-password", "enable-linger"]);
+    const linger = lingering(run, uid);
+    return { linger, turnedOn: linger };
+}
 function writeFileAtomic(path, text) {
     mkdirSync(dirname(path), { recursive: true });
     const temp = `${path}.${process.pid}.tmp`;
@@ -103,7 +118,10 @@ export function autoUpdateStatus(deps) {
         if (!existsSync(timer))
             return { state: "off", detail: "no_timer" };
         const enabled = run("systemctl", ["--user", "is-enabled", `${AUTO_UPDATE_UNIT}.timer`]);
-        return enabled.status === 0 ? { state: "on", detail: "timer_enabled", path: timer } : { state: "off", detail: "timer_not_enabled" };
+        if (enabled.status !== 0)
+            return { state: "off", detail: "timer_not_enabled" };
+        const linger = lingering(run, deps.uid ?? process.getuid?.() ?? 0);
+        return { state: "on", detail: linger ? "timer_enabled" : "timer_enabled_without_linger", path: timer, linger };
     }
     return { state: "unsupported", detail: `platform_${platform}` };
 }
@@ -139,13 +157,14 @@ export function enableAutoUpdate(deps, dir) {
         const enabled = run("systemctl", ["--user", "enable", "--now", `${AUTO_UPDATE_UNIT}.timer`]);
         if (enabled.status !== 0)
             return { state: "off", detail: `systemctl_enable_failed:${enabled.stderr.trim().slice(0, 160)}` };
-        // Without lingering, a user timer stops when this person logs out of a headless machine.
-        const linger = run("loginctl", ["show-user", String(deps.uid ?? process.getuid?.() ?? 0), "--property=Linger"]);
-        return { state: "on", detail: /Linger=yes/.test(linger.stdout) ? "timer_enabled" : "timer_enabled_without_linger", path: paths.timer };
+        const { linger, turnedOn } = ensureLingering(run, deps.uid ?? process.getuid?.() ?? 0);
+        return { state: "on", detail: linger ? "timer_enabled" : "timer_enabled_without_linger", path: paths.timer, linger,
+            ...(turnedOn ? { lingerTurnedOn: true } : {}) };
     }
     return { state: "unsupported", detail: `platform_${platform}` };
 }
-/** Stop and remove the schedule's own files. Nothing else. */
+/** Stop and remove the schedule's own files. Nothing else: on Linux it reports lingering but leaves it
+ *  as it is, because it may have been on before setup turned it on. */
 export function disableAutoUpdate(deps) {
     const platform = deps.platform ?? process.platform;
     const run = deps.run ?? defaultRun;
@@ -164,7 +183,7 @@ export function disableAutoUpdate(deps) {
             if (existsSync(path))
                 unlinkSync(path);
         run("systemctl", ["--user", "daemon-reload"]);
-        return { state: "off", detail: "timer_removed" };
+        return { state: "off", detail: "timer_removed", linger: lingering(run, deps.uid ?? process.getuid?.() ?? 0) };
     }
     return { state: "unsupported", detail: `platform_${platform}` };
 }

package/dist/runner-command.js

@@ -14,12 +14,21 @@ function schedulerDeps(ctx, deps) {
     };
 }
 function statusLine(status) {
-    if (status.state === "on")
-        return status.detail === "timer_enabled_without_linger"
-            ? "Automatic runner updates are on, every 15 minutes while you are logged in. To keep them running after you log out, run: sudo loginctl enable-linger $USER"
+    if (status.state === "on") {
+        if (status.linger === false)
+            return "Automatic runner updates are on, but they stop when you log out: this machine did not let you keep your user services running. Run this once to keep them running: sudo loginctl enable-linger $USER";
+        if (status.lingerTurnedOn)
+            return "Automatic runner updates are on: this machine checks for an approved release every 15 minutes, and keeps checking after you log out. To do that, setup turned on lingering for you, which keeps your user services running after logout. To undo it: loginctl disable-linger $USER";
+        return status.linger
+            ? "Automatic runner updates are on: this machine checks for an approved release every 15 minutes, and keeps checking after you log out."
             : "Automatic runner updates are on: this machine checks for an approved release every 15 minutes.";
-    if (status.state === "off")
-        return `Automatic runner updates are off (${status.detail}). Turn them on with: catalyst runner auto-update on`;
+    }
+    if (status.state === "off") {
+        const off = `Automatic runner updates are off (${status.detail}). Turn them on with: catalyst runner auto-update on`;
+        return status.linger
+            ? `${off}. Lingering is still on for you, which keeps your user services running after logout. If nothing else needs it: loginctl disable-linger $USER`
+            : off;
+    }
     if (status.detail === "no_systemd_user_manager")
         return "Automatic runner updates need your systemd user manager, which is not running for you. Run: sudo loginctl enable-linger $USER, then catalyst runner auto-update on";
     return `Automatic runner updates are not available on this machine (${status.detail}). Run catalyst runner update yourself.`;

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@catalyst-cloud/cli",
-  "version": "0.16.20",
+  "version": "0.16.22",
   "description": "Set up Catalyst Cloud, check your tickets and manage your account from the command line.",
   "license": "MIT",
   "type": "module",
@@ -53,16 +53,16 @@
     "prepublishOnly": "node scripts/release-train-check.mjs --publish cli"
   },
   "dependencies": {
-    "@catalyst-cloud/sdk": "0.16.6",
+    "@catalyst-cloud/sdk": "0.16.9",
     "@clack/prompts": "1.8.1",
     "fast-string-width": "3.0.2",
     "fast-wrap-ansi": "0.2.2",
     "smol-toml": "^1.7.1",
     "yaml": "^2.9.0",
-    "@catalyst-cloud/sdk-replica-node": "0.16.6"
+    "@catalyst-cloud/sdk-replica-node": "0.16.9"
   },
   "devDependencies": {
-    "@catalyst-cloud/schema": "0.16.5",
+    "@catalyst-cloud/schema": "0.16.7",
     "@types/node": "^26.3.0",
     "@vitest/coverage-v8": "^4.1.11",
     "typescript": "^7.0.2",

package/skills/catalyst-github/SKILL.md

@@ -4,7 +4,7 @@ description: >-
   Catalyst's GitHub: show a ticket's pull request with its checks, reviews and review threads, say whether it is mergeable under this repository's policy, and explain what a PR accumulates as the ticket moves (the branch, the draft, the rewrite, the force-pushes, the labels, the queue). Use when someone asks "show me the PR", "what are the checks saying", "why hasn't it merged", "what does the queue need", "what does that label mean", or wants the branch and merge conventions Catalyst follows.
 allowed-tools: Bash(catalyst:*) Bash(npx -p @catalyst-cloud/cli catalyst:*)
 ---
-<!-- vendored-from: @catalyst-cloud/catalyst-skills@0.16.20 — written in this repository for customer accounts -->
+<!-- vendored-from: @catalyst-cloud/catalyst-skills@0.16.22 — written in this repository for customer accounts -->
 
 # Catalyst's GitHub
 

package/skills/catalyst-linear/SKILL.md

@@ -4,7 +4,7 @@ description: >-
   Catalyst's view of Linear on the customer's own cloud account. Reads a ticket with its comments, relations, labels, linked pull requests and agent sessions inline, from the cloud API by default, with local replica reads available as an explicit opt-in, always naming the source; searches tickets, PRs, projects and initiatives; writes comments, card moves, labels and new tickets through the account's agent proxy as the app actor, with every route, stage id, label id and marker read from the account's contract. Knows what a ticket accumulates as Catalyst works it (phase-outcome comments, the document per phase, the agent session, the labels, the single blocks relation, the bookkeeping marker, the eyes acknowledgement). Use when a person says "show me the ticket", "what did Catalyst write on it", "comment on it", "move it", "label it" or "file a ticket". Not for raising a decision for a human (what-needs-me) and not for pull requests (catalyst-github).
 allowed-tools: Bash(catalyst:*) Bash(npx -p @catalyst-cloud/cli catalyst:*)
 ---
-<!-- vendored-from: @catalyst-cloud/catalyst-skills@0.16.20 — written in this repository for customer accounts -->
+<!-- vendored-from: @catalyst-cloud/catalyst-skills@0.16.22 — written in this repository for customer accounts -->
 
 # Catalyst Linear
 

package/skills/catalyst-onboard/SKILL.md

@@ -4,7 +4,7 @@ description: >-
   Set up Catalyst Cloud and say whether setup is working. Walks a person from nothing to their first ticket running, one step at a time: the coding account, the project, the integrations and connected accounts, each repository's settings file, then one real ticket moving. Also logs this machine in, reads the readiness verdict with who can fix each failure, and checks the optional local replica. Use when someone says "set me up", "onboard me", "I just signed up", "get me started", "what do I do first", "log me in", "which account is this machine on", "am I set up", "what is missing", "why does nothing happen" or "is the replica running", when a login expired, or when a skill script exits 2 saying this machine is not connected. Does every step a key can do through the catalyst CLI, hands over the exact page for the steps only a browser can do, and never claims a step it did not watch succeed.
 allowed-tools: Bash(catalyst:*) Bash(npx -p @catalyst-cloud/cli catalyst:*)
 ---
-<!-- vendored-from: @catalyst-cloud/catalyst-skills@0.16.20 — written in this repository for customer accounts -->
+<!-- vendored-from: @catalyst-cloud/catalyst-skills@0.16.22 — written in this repository for customer accounts -->
 
 # Onboard me
 

package/skills/catalyst-onboard/scripts/where-am-i.mjs

@@ -32,7 +32,7 @@ const NOTES = [
   "Reads, in this order: `status` (machine), `ready --json` (machine checks and project checks, kept apart),",
   "`replica status --probe --json` and `events status --from-cache --probe --json` (optional local freshness),",
   "`me --json` and personal connection statuses (person), `contract --path …` for the account, the projects and the repositories,",
-  "`contract --path codingAccounts` and `accounts --json` (coding accounts, and which one needs a new credential), and each",
+  "`contract --path codingAccounts` and `accounts --all --json` (coding accounts, and which one needs a new credential), and each",
   "project's hosts_current check with its fixedWhere (host), and each project's environment_declared check with its per-repository notes (repository declarations). The teams read is refreshed, so a mapping just saved reads back mapped.",
   "Reads `capabilities --json` once: when the installed CLI can run a step for this person's role (`team check`, `team map`), the next step is that command; otherwise the page, with who can.",
   "Reads `legacy --json` when the CLI has the verb: leftovers of the old local Catalyst runtime become a machine line and a note; removing them is the person's yes.",
@@ -716,7 +716,8 @@ const credentialProblem = (a) => {
   return null;
 };
 const readAccountRows = () => {
-  const acc = runCli(["accounts", "--json"]);
+  // --all: the CLI leaves removed accounts out by default, and the retire note needs them.
+  const acc = runCli(["accounts", "--all", "--json"]);
   const doc = tryJson(acc.stdout);
   const rows = Array.isArray(doc)
     ? doc

package/skills/run-this-project/SKILL.md

@@ -4,7 +4,7 @@ description: >-
   Own one Catalyst Cloud project end to end until it closes. Use when the person says "run this project for me", "own this until it ships", "keep this moving", or hands you a project id or a set of tickets to drive. Subscribes to the account's event stream for the scope through the catalyst CLI, reacts to each change in the same turn, makes tickets ready and moves them to dispatch, parks what should stop, chases stalls, escalates inward, and keeps one status summary current. Writes to Linear as the app actor; never polls.
 allowed-tools: Bash(catalyst:*) Bash(npx -p @catalyst-cloud/cli catalyst:*)
 ---
-<!-- vendored-from: @catalyst-cloud/catalyst-skills@0.16.20 — written in this repository for customer accounts -->
+<!-- vendored-from: @catalyst-cloud/catalyst-skills@0.16.22 — written in this repository for customer accounts -->
 
 # Run this project
 

package/skills/unstick/SKILL.md

@@ -4,7 +4,7 @@ description: >-
   Get a stuck Catalyst Cloud ticket moving again. Use when the person asks "why is this parked and can you release it?", "unpark this", "get things flowing again", "the outage is over, retry what failed", or hands you a ticket that is not moving. Reads why nothing runs and what holds the ticket through the catalyst CLI, decides whether the recorded cause is fixed, previews the release, releases every governor holding the ticket the right way (or one failure class across a team), and raises an ask only for what a person has to do. Never releases a cause it cannot show changed without saying so.
 allowed-tools: Bash(catalyst:*) Bash(npx -p @catalyst-cloud/cli catalyst:*)
 ---
-<!-- vendored-from: @catalyst-cloud/catalyst-skills@0.16.20 — written in this repository for customer accounts -->
+<!-- vendored-from: @catalyst-cloud/catalyst-skills@0.16.22 — written in this repository for customer accounts -->
 
 # Unstick
 

package/skills/what-needs-me/SKILL.md

@@ -4,7 +4,7 @@ description: >-
   The human's decision inbox on Catalyst Cloud, and the one way an agent raises a decision on their behalf. Use when the person asks "what needs me?", "what am I blocking?", or when active work is gated on a choice only they can make. Lists open asks ranked by how much open work each one holds, files an ask through the cloud's ask route with the account's own template, and records the answer so the held work releases. Never answers as the human, never duplicates an open ask.
 allowed-tools: Bash(catalyst:*) Bash(npx -p @catalyst-cloud/cli catalyst:*)
 ---
-<!-- vendored-from: @catalyst-cloud/catalyst-skills@0.16.20 — written in this repository for customer accounts -->
+<!-- vendored-from: @catalyst-cloud/catalyst-skills@0.16.22 — written in this repository for customer accounts -->
 
 # What needs me
 

package/skills/what-this-repo-needs/SKILL.md

@@ -4,7 +4,7 @@ description: >-
   What environment variable names does this repository need, and where does each one come from? Scans the repository offline (no login, no network) and lists the names in three groups (build/test, deploy-only, bindings), each with where it was found, what uses it, and where a local value would come from. Never reads a value or prints one. Also checks the environment variable table in `.catalyst/catalyst.toml` offline. Use when someone asks "what does catalyst.env.json mean", "what env vars does this repo need", "why does the container need this", or before reviewing or writing the declaration.
 allowed-tools: Bash(catalyst:*) Bash(npx -p @catalyst-cloud/cli catalyst:*)
 ---
-<!-- vendored-from: @catalyst-cloud/catalyst-skills@0.16.20 — written in this repository for customer accounts -->
+<!-- vendored-from: @catalyst-cloud/catalyst-skills@0.16.22 — written in this repository for customer accounts -->
 
 # What this repository needs
 

package/skills/whats-happening/SKILL.md

@@ -4,7 +4,7 @@ description: >-
   Use for "what's happening?", "what machines do we have?", "how much capacity do we have?", "where are we?", "why is that stuck?", "what closed?", "what's next?", "how does this work?", "why did it do that?", "how does it prioritise?" and "what does this setting do, where is it set?" in Catalyst Cloud, or asks for something to be done rather than known. Reads the contract via catalyst CLI. Read-only: route work/decisions, never answer as the human.
 allowed-tools: Bash(catalyst:*) Bash(npx -p @catalyst-cloud/cli catalyst:*)
 ---
-<!-- vendored-from: @catalyst-cloud/catalyst-skills@0.16.20 — written in this repository for customer accounts -->
+<!-- vendored-from: @catalyst-cloud/catalyst-skills@0.16.22 — written in this repository for customer accounts -->
 
 # What's happening
 

package/skills/whats-happening/references/coding-accounts.md

@@ -1,6 +1,6 @@
 # Coding accounts
 
-snapshot.mjs --accounts omits credentials/emails. An owner/admin enrols, pauses, removes or replaces credentials at `<their cloud>/settings/coding-accounts`; no command does these yet. `catalyst accounts` reads them.
+snapshot.mjs --accounts omits credentials/emails. An owner/admin enrols, pauses, removes or replaces credentials at `<their cloud>/settings/coding-accounts`; no command does these yet. `catalyst accounts` reads them. It leaves out removed accounts (revoked, or paid access that ended). They are kept for history, never take work again and take no new credential, so never suggest reviving one. `catalyst accounts --all` lists them.
 
 Slots identify credentials, not emails. Claude/GLM/Qwen use Claude CLI, Codex uses Codex; GLM/Qwen also use OpenCode. Routing names the model.