@catalyst-cloud/catalyst-skills 0.7.0 → 0.8.0

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

@@ -1,245 +0,0 @@
-#!/usr/bin/env node
-// where-am-i.mjs — how far has setup got? FIVE PARTS, EACH READ BY THE INSTRUMENT THAT OWNS IT, and
-// each finding labelled with the part it belongs to. The whole point of this script is that no part
-// answers for another: a project that is not ready is reported as a project finding with a tenant
-// owner's name on it, never as something the person at this keyboard can fix by running anything.
-//
-// Every count and every name below is read off what a verb printed. Nothing here is written down.
-import { cliTarget, CONNECT_LINE, parseFlags, printHelp, runCli, tryJson, tryLoadConfig } from "./lib/cli.mjs";
-
-const SPEC = {
-  next: { help: "print only the single next step" },
-  json: { help: "one JSON document instead of the report" },
-};
-const NOTES = [
-  "Reads, in this order: `status` (machine), `ready --json` (machine checks and project checks, kept apart),",
-  "`me --json` (person), and `contract --path …` for the account, the projects and the repositories.",
-  "Writes nothing and changes nothing. Runs before this machine is connected — that is one of the states it reports.",
-];
-
-const { help, flags, positionals } = parseFlags(process.argv.slice(2), SPEC);
-if (help) {
-  printHelp("node scripts/where-am-i.mjs [--next] [--json]", SPEC, NOTES);
-  process.exit(0);
-}
-if (positionals.length > 0) {
-  process.stderr.write(`unexpected argument: ${positionals[0]} (try --help)\n`);
-  process.exit(1);
-}
-
-const via = cliTarget().via;
-const parts = [];
-// `blocking` is false for a finding that is real and reportable but does not stop the next step —
-// an unmatched Linear identity is the one that matters: it must be said, and it must not become the
-// thing the person is told to go and do before they can map a project.
-const add = (part, instrument, verdict, lines, owner = null, where = null, blocking = true) =>
-  parts.push({ part, instrument, verdict, lines, owner, where, blocking });
-
-// ── machine ───────────────────────────────────────────────────────────────────────────────────────
-const status = runCli(["status"]);
-if (!status.ran) {
-  process.stderr.write(`${status.stderr}\n`);
-  process.stderr.write(`the catalyst-skills CLI could not be started. Install it, then run this again.\n`);
-  process.exit(2);
-}
-const statusLines = status.stdout.split("\n").map((l) => l.trim()).filter(Boolean);
-const field = (name) => {
-  const line = statusLines.find((l) => l.startsWith(`${name}:`));
-  return line ? line.slice(name.length + 1).trim() : null;
-};
-const tenant = field("Tenant");
-const api = field("API");
-const connected = tenant !== null && tryLoadConfig() !== null;
-// The app and the API share an origin; the base URL is whatever this machine was connected to, so
-// no page link in this report is a host anyone typed from memory.
-const cloud = api === null ? null : api.split(" ")[0].replace(/\/+$/, "");
-const link = (path) => (cloud === null ? `<your cloud>${path}` : `${cloud}${path}`);
-
-const machineLines = connected ? statusLines : [statusLines[0] ?? "status printed nothing"];
-let machineVerdict = connected ? "ok" : "unfinished";
-
-// `ready` is ONE verdict over two parts; split it by check id before anything is reported. A check
-// whose id begins with "team:" belongs to a project and cannot be moved from this machine.
-let projectChecks = [];
-let machineFix = null;
-if (connected) {
-  const ready = runCli(["ready", "--json"]);
-  const report = tryJson(ready.stdout);
-  const checks = Array.isArray(report?.checks) ? report.checks : null;
-  if (checks === null) {
-    machineLines.push(`ready: could not be read (${(ready.stderr || ready.stdout).trim().split("\n")[0] ?? "no output"})`);
-    machineVerdict = "unfinished";
-  } else {
-    projectChecks = checks.filter((c) => typeof c.id === "string" && c.id.startsWith("team:"));
-    const machineChecks = checks.filter((c) => !(typeof c.id === "string" && c.id.startsWith("team:")));
-    const failed = machineChecks.filter((c) => !c.ok && !c.note);
-    for (const c of machineChecks) machineLines.push(`${c.note ? "note" : c.ok ? "ok  " : "FAIL"} ${c.line}${!c.ok && !c.note && c.fix ? ` — fix: ${c.fix}` : ""}`);
-    if (failed.length > 0) {
-      machineVerdict = "unfinished";
-      machineFix = failed.find((c) => typeof c.fix === "string")?.fix ?? null;
-    }
-  }
-}
-add(
-  "machine",
-  "catalyst-skills status, and the non-team checks of catalyst-skills ready",
-  machineVerdict,
-  machineLines,
-  "you, on this machine",
-  connected ? null : CONNECT_LINE,
-);
-
-// ── person ────────────────────────────────────────────────────────────────────────────────────────
-if (!connected) {
-  add("person", "catalyst-skills me", "unreadable", ["not readable until this machine is connected"], null, null);
-} else {
-  const me = runCli(["me", "--json"]);
-  const doc = tryJson(me.stdout);
-  const user = doc && typeof doc.user === "object" && doc.user !== null ? doc.user : null;
-  if (doc === null) {
-    add("person", "catalyst-skills me", "unreadable", [`me could not be read (${(me.stderr || me.stdout).trim().split("\n")[0] ?? "no output"})`], null, null);
-  } else if (user === null) {
-    add(
-      "person",
-      "catalyst-skills me",
-      "unfinished",
-      ["this credential names no person — it is a host credential, so nothing an agent writes will carry a name"],
-      "you: connect again with your own login",
-      CONNECT_LINE,
-    );
-  } else {
-    const matched = typeof user.linearUserId === "string" && user.linearUserId !== "";
-    add(
-      "person",
-      "catalyst-skills me",
-      matched ? "ok" : "unfinished",
-      [`${user.label ?? "(unnamed)"} (${user.role ?? "role unknown"})`, matched ? "Linear identity matched" : "Linear identity NOT matched — asks assigned to you cannot be told apart from everyone else's. It blocks nothing below; get it fixed when convenient."],
-      matched ? null : "a tenant owner or admin",
-      matched ? null : link("/settings/account"),
-      false,
-    );
-  }
-}
-
-// ── account ───────────────────────────────────────────────────────────────────────────────────────
-if (!connected) {
-  add("account", "catalyst-skills contract --path account", "unreadable", ["not readable until this machine is connected"], null, null);
-} else {
-  const acct = runCli(["contract", "--path", "account", "--json"]);
-  const doc = tryJson(acct.stdout);
-  if (doc === null) {
-    add("account", "catalyst-skills contract --path account", "unreadable", ["the account block could not be read — try: catalyst-skills contract --refresh"], null, null);
-  } else {
-    const workspace = typeof doc.linearWorkspaceSlug === "string" && doc.linearWorkspaceSlug !== "" ? doc.linearWorkspaceSlug : typeof doc.linearWorkspaceId === "string" && doc.linearWorkspaceId !== "" ? doc.linearWorkspaceId : null;
-    // The declaration is the one part of the account a key can also READ — and it is the one part a
-    // key can WRITE, so it is reported here rather than left to the settings page like the rest.
-    const envLines = [];
-    const env = runCli(["environment", "read", "--json"]);
-    const envDoc = tryJson(env.stdout);
-    if (envDoc === null) {
-      envLines.push(`environment: not readable (${(env.stderr || env.stdout).trim().split("\n")[0] ?? "no output"})`);
-    } else if (envDoc.current === null || envDoc.current === undefined) {
-      envLines.push("environment: nothing declared yet — declare it with `catalyst-skills environment propose --file <path> --approve`");
-    } else {
-      envLines.push(`environment: revision ${envDoc.current.revision} (${envDoc.current.canonicalHash}), ${envDoc.isApproved ? "approved" : "NOT approved — a proposal nobody approved changes nothing"}`);
-      envLines.push(envDoc.delivered ? `environment delivered to phases: revision ${envDoc.delivered.revision}` : "environment delivered to phases: nothing yet");
-      const unresolved = Array.isArray(envDoc.unresolvedReferences) ? envDoc.unresolvedReferences : [];
-      if (unresolved.length > 0) envLines.push(`environment names values this tenant does not carry yet: ${unresolved.join(", ")}`);
-    }
-    add(
-      "account",
-      "catalyst-skills contract --path account, and catalyst-skills environment read",
-      workspace === null ? "unfinished" : "ok",
-      [
-        `${doc.name ?? "(unnamed tenant)"} (${doc.slug ?? "?"})`,
-        workspace === null ? "no Linear workspace resolved on this contract" : `Linear workspace resolved: ${workspace}`,
-        "the GitHub App install is NOT carried here — the connections page is the only place that shows it",
-        ...envLines,
-      ],
-      "a tenant owner or admin",
-      link("/settings/connections"),
-    );
-  }
-}
-
-// ── projects (a project is one Linear team) ───────────────────────────────────────────────────────
-if (!connected) {
-  add("projects", "catalyst-skills contract --path teams", "unreadable", ["not readable until this machine is connected"], null, null);
-} else {
-  const teams = runCli(["contract", "--path", "teams", "--json"]);
-  const doc = tryJson(teams.stdout);
-  const rows = Array.isArray(doc) ? doc : null;
-  if (rows === null) {
-    add("projects", "catalyst-skills contract --path teams", "unreadable", ["the project list could not be read — try: catalyst-skills contract --refresh"], null, null);
-  } else {
-    const lines = [`${rows.length} mapped`];
-    for (const t of rows) {
-      const key = t.key ?? t.id ?? "(unkeyed)";
-      const readiness = t.readiness ?? {};
-      const bad = Array.isArray(readiness.checks) ? readiness.checks.filter((c) => c.state !== "pass") : [];
-      lines.push(`${key}: ${readiness.status ?? "unknown"}${bad.length ? ` — ${bad.map((c) => `${c.id} ${c.state}`).join(", ")}` : ""}`);
-    }
-    for (const c of projectChecks) lines.push(`${c.ok ? "note" : "FAIL"} ${c.line}${c.who ? ` — who: ${c.who}` : ""}`);
-    lines.push("⛔ MAPPED projects only. An empty list means nothing is mapped yet, NOT that there are no projects — the full list is on the page below.");
-    const ready = rows.length > 0 && rows.every((t) => (t.readiness?.status ?? "unchecked") === "ready");
-    add("projects", "catalyst-skills contract --path teams, and the team: checks of ready", ready ? "ok" : "unfinished", lines, "a tenant owner or admin", link("/settings/linear-teams"));
-  }
-}
-
-// ── repositories ──────────────────────────────────────────────────────────────────────────────────
-if (!connected) {
-  add("repositories", "catalyst-skills contract --path merge.repositories", "unreadable", ["not readable until this machine is connected"], null, null);
-} else {
-  const repos = runCli(["contract", "--path", "merge.repositories", "--json"]);
-  const doc = tryJson(repos.stdout);
-  const rows = Array.isArray(doc) ? doc : null;
-  if (rows === null) {
-    add("repositories", "catalyst-skills contract --path merge.repositories", "unreadable", ["the repository list could not be read — try: catalyst-skills contract --refresh"], null, null);
-  } else {
-    const lines = [`${rows.length} registered`, ...rows.map((r) => `${r.owner ?? "?"}/${r.name ?? "?"}`)];
-    lines.push("⛔ REGISTRATION only. This carries no status and no project attachment, so it never proves a repository can be dispatched into.");
-    add("repositories", "catalyst-skills contract --path merge.repositories", rows.length > 0 ? "ok" : "unfinished", lines, "a tenant owner or admin", link("/settings/repositories"));
-  }
-}
-
-// ── the single next step ──────────────────────────────────────────────────────────────────────────
-// The machine's next action is not one sentence: an unconnected machine needs the login, and a
-// connected one needs whatever check failed — and `ready` already printed that check's own fix, so
-// this carries it through rather than inventing a second answer to the same question.
-const machineNext = connected
-  ? `clear the machine check that failed — ${machineFix ?? "see the machine lines above"}`
-  : "connect this machine";
-const NEXT = {
-  machine: machineNext,
-  person: "get this person's seat and Linear identity sorted",
-  account: "connect Linear, and install the GitHub App",
-  projects: "pick ONE project and map its stages (or adopt the Catalyst workflow)",
-  repositories: "register the repository, attaching it to the project you mapped",
-};
-const blocked = parts.filter((p) => p.verdict !== "ok" && p.blocking);
-const stuck = blocked[0] ?? parts.find((p) => p.verdict !== "ok") ?? null;
-const next =
-  stuck === null
-    ? null
-    : { part: stuck.part, action: NEXT[stuck.part], owner: stuck.owner, where: stuck.where, blocking: stuck.blocking };
-const finished = parts.every((p) => p.verdict === "ok");
-
-if (flags.json) {
-  console.log(JSON.stringify({ cli: via, connected, cloud, parts, next, finished }));
-} else if (flags.next) {
-  if (next === null) console.log("nothing left: every part this machine can read is finished. Move one card into the project's dispatch stage.");
-  else console.log(`${next.part}: ${next.action}${next.blocking ? "" : " (does not block the steps below)"}${next.owner ? ` — who: ${next.owner}` : ""}${next.where ? ` — ${next.where.startsWith("http") ? "where" : "do"}: ${next.where}` : ""}`);
-} else {
-  for (const p of parts) {
-    console.log(`${p.part}  [${p.verdict}]`);
-    console.log(`  instrument: ${p.instrument}`);
-    for (const l of p.lines) console.log(`  ${l}`);
-    if (p.verdict !== "ok" && p.owner) console.log(`  who: ${p.owner}`);
-    // A page gets "where"; a command gets "do". Labelling a command "where" is how a person ends up
-    // looking for a settings page that is actually a line to run.
-    if (p.verdict !== "ok" && p.where) console.log(`  ${p.where.startsWith("http") ? "where" : "do"}: ${p.where}`);
-    console.log("");
-  }
-  console.log(next === null ? "next: nothing left — move one card into the project's dispatch stage and watch." : `next: ${next.part} — ${next.action}${next.owner ? ` (${next.owner})` : ""}${next.where ? ` — ${next.where}` : ""}`);
-}
-process.exit(finished ? 0 : 1);

package/skills/catalyst-setup/SKILL.md

@@ -1,32 +0,0 @@
----
-name: catalyst-setup
-description: >-
-  Am I set up? Machine readiness (Node, the tenant connection, the cached contract, the CLI path, the skills, the SDK, the optional replica) plus tenant readiness from the contract's per-team checks, in one verdict: what passes, what is blocked, what is merely waiting, and who can click what. Use when someone asks "am I set up", "what is missing", "why does nothing happen", "is the replica running", or right after connecting a new machine. Reports; never repairs.
-allowed-tools: Bash(catalyst-skills:*) Bash(npx @catalyst-cloud/catalyst-skills:*)
----
-<!-- vendored-from: @catalyst-cloud/catalyst-skills@0.7.0 — written in this repository for customer tenants -->
-
-# Am I set up?
-
-You answer one question with one verdict and one list. The verdict is READY or NOT READY. The list is who can click what: the fixes only the person at the keyboard can make, the fixes only a tenant owner or admin can make in settings, and the checks that are simply waiting for the first event. The live check ids, severities, states and the people who can answer come from the contract; the scripts print them, you never restate them.
-
-## Run first
-
-- `node scripts/check.mjs --help` — every machine and tenant check, one line each, the fix and who for each failure, the verdict, then the who-can-click-what list. Exit 1 when NOT READY.
-- `node scripts/replica-status.mjs --help` — the optional replica's verdict with no network (add `--probe` for how far behind it is). Exit 0 fresh, 1 stale, 2 not connected, 3 absent.
-
-## Load on demand
-
-| when | read |
-| -- | -- |
-| any check is red, unknown or waiting and the person asks what it proves, how to fix it, or who can | `references/what-each-check-means.md` |
-
-## Rules
-
-- Report, never repair. No tenant-reachable repair verb exists for a key yet; the settings page is where a tenant owner or admin fixes a mapping, a connection or a label, and you say which one.
-- End every answer with the verdict and the who-can-click-what list, in that order.
-- A stale or absent replica is a note, never a failure: every skill reads the API meanwhile and says so. Do not tell the person to start it unless they want local SQL or cheaper repeated reads.
-- Not connected (exit 2) means the connect step, not a retry: `npx @catalyst-cloud/catalyst-skills login`, which logs the person in keyless in their browser; with a personal key from Settings → API keys instead, prefix it with `CATALYST_CLOUD_TOKEN=<your personal key>`. Never guess a tenant; the login (or the key) is the only selector.
-- Waiting is not failing. "No write observed", "no delivery observed" and "no host connected" clear themselves the first time the thing happens; say that instead of raising them.
-- Unknown is not a pass. A check the engine could not run is reported as such, never rounded up.
-- Never run a check in a loop. If the person wants to know when a waiting check clears, that is the project-running skill's watch.

package/skills/catalyst-setup/agents/openai.yaml

@@ -1,6 +0,0 @@
-interface:
-  display_name: "Am I set up?"
-  short_description: "Machine and tenant readiness in one verdict: what passes, what is blocked, and who can click what"
-  default_prompt: "Use $catalyst-setup to tell me whether this machine and my tenant are ready, and what is missing."
-policy:
-  allow_implicit_invocation: true

package/skills/catalyst-setup/agents/portability.yaml

@@ -1,4 +0,0 @@
-identity: { pack: catalyst-cloud-skills, skill: catalyst-setup }
-effects: []
-invocation: implicit
-exposure: [catalog]

package/skills/catalyst-setup/references/what-each-check-means.md

@@ -1,78 +0,0 @@
-# What each check means
-
-This page restates invariants: the per-team readiness checks the cloud runs, what each proves, its fix and who can click it; the machine checks the CLI adds; and the four replica verdicts. The live values are never restated: each check's severity and whether it needs a human's answer come from the contract's `readinessChecks[]`, each team's current states from `teams[].readiness`, and the people who can answer from `humans[]`. `node scripts/check.mjs` prints all of it; this page is how to read what it printed.
-
-## How a team's readiness is scored
-
-A team's status is one of `ready`, `degraded`, `blocked` or `unchecked`. The engine always reports every check the contract lists; a check it could not run is `unknown`, never `pass`. Any failing check the contract marks as blocking makes the team blocked; any unknown, and any failing check marked degrading, makes it degraded. Unchecked means no readiness pass has run for that team yet, which is a note, not a failure. Readiness is stamped with the account-wide mapping revision it was computed against, so a stale verdict is visible as such.
-
-## The checks
-
-The contract's `readinessChecks[]` is the list of record. A check that appears there and not here is newer than this page; `node scripts/check.mjs` still prints it with its own severity, fix and owner, so read the printed line and say you did.
-
-| check id | proves | when it fails, the fix | who clicks |
-| -- | -- | -- | -- |
-| `oauth_scope` | Catalyst holds the Linear permissions it needs | re-authorise the Linear connection to grant the missing scope | a tenant owner or admin, in settings |
-| `token_live` | the Linear connection is accepted right now | reconnect Linear (expired or revoked), or wait and re-check (Linear unreachable). A distinct reason says Linear was never connected at all | owner or admin |
-| `team_visible` | Catalyst can see this team | most often the team was made private: grant Catalyst access in Linear's team settings, then re-check | owner or admin, in Linear |
-| `mapped_states_exist` | every stage Catalyst mapped still exists in Linear | re-map the team; nothing in the workspace was changed. A pending-write reason means a mapping was just saved and the read has not caught up: wait, do not re-map | owner or admin, in settings |
-| `mapping_total` | every stage Catalyst moves tickets into is mapped | map the missing stages. "Absent" means the team was never mapped; "incomplete" means a few of the load-bearing stages are missing | owner or admin, in settings |
-| `types_compatible` | each load-bearing mapped stage is the right kind (dispatch and intake unstarted or backlog, PR started, done completed, canceled canceled) | change the mapping to a stage of the right kind | owner or admin, in settings |
-| `labels_present` | the labels Catalyst uses exist in the workspace | none needed by a person: Catalyst creates them the first time it uses them | nobody |
-| `writes_land` | Catalyst has written to this team successfully | "no write observed" is waiting, not failing: it clears the first time Catalyst moves a ticket. "Write refused" means Linear rejected the last write: check the connection and the team's permissions | owner or admin when refused; otherwise nobody |
-| `webhook_covers_team` | events for this team are arriving | confirmed once a repository is registered and events flow; "no delivery observed" is waiting | owner or admin, by registering the repository |
-| `hosts_current` | no connected host runs an older mapping revision | a host that is behind re-loads the mapping on its next connect; a host that did not report its revision is flagged rather than assumed current; "no host connected" is waiting | whoever runs that host |
-| `environment_declared` | a committed environment declaration for the team's default repository is in effect (`catalyst.env.json` at the repository root was ingested, is valid, and its latest proposal is approved) | `no_team_repo_default`: register a repository and make it the team's default; `no_environment_declaration`: commit the declaration file to that repository; `declaration_invalid` / `declaration_read_failed`: fix the file (the ingest names the error); `declaration_awaiting_approval`: an owner or admin approves the proposal in Settings → Environment | owner or admin, except committing the file, which is whoever can push to the repository |
-| `tools_resolvable` | every MCP server and CLI the team's approved environment declaration names can be resolved for that team's repository | `tool_reference_unresolved`: the declaration names a vault secret that does not exist — add it at the right scope or correct the declaration; `toolchain_cli_missing`: a declared CLI is not in the runner image, which is not self-service; `tool_declarations_unread` reads as `unknown` and clears itself | owner or admin, in the declaration or Settings → Environment |
-| `reviewer_required` | this team's repository can merge under its own merge policy with the reviewers configured | it fails only under a strict merge policy with no reviewer — configure one at Settings → Repositories → Code reviews, or change the repository's merge policy; work still runs, only the merge waits | owner or admin, in settings |
-| `reviewer_configured` | a code reviewer is configured for this team's repository at all, whatever the current policy requires | a *failing* `reviewer_configured` never blocks or degrades a team — with no reviewer, pull requests merge on green checks and resolved threads alone; configure one at Settings → Repositories → Code reviews. An `unknown` one (`merge_reviewer_unread`: the reviewer registry could not be read) still degrades the team, like any unknown | owner or admin, in settings; nobody is required when it fails |
-
-Some checks degrade a team without ever blocking it, and one is informational only — informational means a *fail* never moves the verdict, not that the check cannot: an unknown still degrades. Which check is which is served on `readinessChecks[].severity`; do not memorise the split.
-
-## Reasons that look like failures and are not
-
-- `no_write_observed`, `no_delivery_observed`, `no_host_connected`: nothing has happened yet. Expected on a fresh tenant; they clear on their own.
-- `stages_pending_write`: a mapping was saved and the read predates it. Re-check shortly; re-mapping would be a second write for no reason.
-- `unknown` on any check: the engine could not look. It is not a pass and not a fail; say so.
-
-## The machine checks the CLI adds
-
-`catalyst-skills ready` prepends checks about this machine before the tenant's:
-
-| id | proves | fix |
-| -- | -- | -- |
-| `node` | Node 22 or newer, which the SDK's built-in SQLite engine needs | install Node 22+ |
-| `config` | this machine is connected: `customer.json` exists and loads | `npx @catalyst-cloud/catalyst-skills login` (keyless: the person approves in their browser); or, with a personal key minted at Settings → API keys, the same command prefixed with `CATALYST_CLOUD_TOKEN=<your personal key>` |
-| `contract` | the tenant contract is cached and its major version is one this bundle accepts | `catalyst-skills contract --refresh`; a version outside the range means update the bundle. A 403 naming an older cloud means the cloud has not yet deployed personal-key access |
-| `bundle` | the installed CLI is at least the version this tenant requires | `npm install -g @catalyst-cloud/catalyst-skills@latest && catalyst-skills login`; a note, never a failure |
-| `cliPath` | the CLI path recorded at login still exists, so skill scripts can spawn it | re-run login |
-| `skills` | every skill of this bundle is present where the CLI installed them | `catalyst-skills install` |
-| `cliRelease` | the installed CLI is not behind the newest published release | the same upgrade command as `bundle`; a note, never a failure |
-| `skillsRelease` | the installed skill files are not behind the newest published bundle | `npx skills update -y`; a note, never a failure. A line saying the check could not run means the registry was unreachable, not that anything is wrong |
-| `sdk` | the SDK loads, so the replica and the watch are available | run under Node 22.15 or newer; every read still works through the API meanwhile |
-| `replica` | the optional replica is fresh | a note, never a failure; see below |
-
-## The replica's four verdicts
-
-`node scripts/replica-status.mjs` needs no network and exits with the verdict:
-
-| exit | verdict | what a skill does with it |
-| -- | -- | -- |
-| 0 | fresh: a live writer, a heartbeat younger than the staleness threshold, a non-empty cursor | reads the replica and says so |
-| 1 | stale: the file exists but the writer is gone, the heartbeat is old, or there is no cursor | reads the API and says so; `catalyst-skills replica start --detach` brings it back |
-| 2 | not connected to a tenant | the connect step first |
-| 3 | absent: no replica file at all | reads the API; the replica is optional and one command away |
-
-`--probe` adds the one network call: it compares the local cursor with the cloud's head and prints how far behind the replica is, the only honest "how stale" number. A skill must never refuse to work because the replica is down, and must never silently read a stale one; both halves are one exit code away.
-
-## The writer stops itself after repeated snapshot failures
-
-`replica start` backs off with jitter after a failed or incomplete snapshot pull, and gives up after five consecutive snapshot failures rather than retrying forever — a writer that keeps failing never hammers the tenant. A snapshot that completes resets the count to zero. Both `catalyst-skills replica status` and `catalyst-skills ready` name the stopped state, the count, the last error, and the command that restarts it. The four exit codes above are unchanged: a stopped writer with a database already on disk still reads stale, since there truly is no live writer.
-
-## Who can click what
-
-The last block `check.mjs` prints groups every failure by the person it needs. Machine fixes name "you", the person at the keyboard. Tenant fixes name the owner or admin roles the contract lists (as Linear user ids, since that is how the cloud knows them), because the settings page that repairs a mapping, a connection or a label is theirs. A check the contract marks as not needing an answer names nobody: it is informational or self-clearing. This skill reports; it never repairs, because no key-reachable repair verb exists yet.
-
-## Setting up one team at a time
-
-A team starts receiving work only once its stages are saved, and that is done one team at a time: a tenant owner or admin opens Settings → Linear teams, picks the team and presses Map my stages (or Adopt the Catalyst workflow). No other team's stages or tickets change; only the labels Adopt creates are shared across the workspace. Before saving, the screen lists which of that team's tickets would start and which stay where they are. Once saved, the tickets in the team's dispatch stage start; tickets in other stages that Catalyst never worked on stay where they are. To pilot safely, pick a low-stakes team, move anything in its dispatch stage that should not start back to Backlog, and leave the other teams unmapped. `gitAutomation` in the contract plays no part: nothing reads it.

package/skills/catalyst-setup/scripts/check.mjs

@@ -1,75 +0,0 @@
-#!/usr/bin/env node
-// check.mjs — "am I set up?" in one verdict: the machine checks the CLI runs (Node, the connection,
-// the cached contract, the CLI path, the skills, the SDK, the optional replica) plus every team's
-// readiness vector from the tenant contract, then the list of who can click what. Wraps
-// `catalyst-skills ready --json`; reports, never repairs. Exit 0 READY, 1 NOT READY, 2 not connected.
-import { parseJson, runCli } from "./lib/cli.mjs";
-
-const HELP = `Usage: node scripts/check.mjs [--json]
-
-Prints one line per check (ok / note / FAIL), the fix and who can apply it for every failure, the
-verdict, and a "who can click what" list grouped by the person or role each fix needs.
-A note never flips the verdict (the replica is optional; an informational readiness check is a note).
-
---json prints the CLI's report document {ready, checks[]} unchanged.
-Exit 0 READY, 1 NOT READY, 2 this machine is not connected to a tenant yet.`;
-
-const args = process.argv.slice(2);
-if (args.includes("--help") || args.includes("-h")) {
-  console.log(HELP);
-  process.exit(0);
-}
-const unknown = args.filter((a) => a !== "--json");
-if (unknown.length > 0) {
-  console.error(`unknown argument: ${unknown.join(" ")}`);
-  console.log(HELP);
-  process.exit(1);
-}
-
-const res = runCli(["ready", "--json"]);
-if (res.code === 2) {
-  console.error(res.stderr.trim() || "catalyst-skills ready refused");
-  process.exit(2);
-}
-const report = parseJson(res.stdout);
-if (!report || !Array.isArray(report.checks)) {
-  console.error(res.stderr.trim() || res.stdout.trim() || "catalyst-skills ready printed no report");
-  process.exit(res.code === 0 ? 1 : res.code);
-}
-if (args.includes("--json")) {
-  console.log(JSON.stringify(report));
-  process.exit(report.ready ? 0 : 1);
-}
-
-const failures = [];
-for (const c of report.checks) {
-  const tag = c.note ? "note" : c.ok ? "ok  " : "FAIL";
-  console.log(`${tag}  ${c.line}`);
-  if (!c.ok && !c.note) {
-    if (c.fix) console.log(`      fix: ${c.fix}`);
-    if (c.who) console.log(`      who: ${c.who}`);
-    failures.push(c);
-  }
-}
-console.log(report.ready ? "READY" : "NOT READY");
-
-if (failures.length > 0) {
-  console.log("");
-  console.log("Who can click what:");
-  const byWho = new Map();
-  for (const c of failures) {
-    const who = c.who ?? "unknown (the check named nobody)";
-    if (!byWho.has(who)) byWho.set(who, []);
-    byWho.get(who).push(c);
-  }
-  for (const [who, list] of byWho) {
-    console.log(`  ${who}:`);
-    for (const c of list) console.log(`    - ${c.id}: ${c.fix ?? c.line}`);
-  }
-}
-const notes = report.checks.filter((c) => c.note && !c.ok);
-if (notes.length > 0) {
-  console.log("");
-  console.log(`Notes that do not block: ${notes.map((c) => c.id).join(", ")} — see references/what-each-check-means.md`);
-}
-process.exit(report.ready ? 0 : 1);

package/skills/catalyst-setup/scripts/lib/cli.mjs

@@ -1,103 +0,0 @@
-#!/usr/bin/env node
-// lib/cli.mjs — the one way a skill script reaches the Catalyst Cloud SDK and API: by spawning the
-// catalyst-skills CLI this bundle installed. It reads customer.json to find that CLI and nothing
-// else; it never holds the key itself. This file is a library — run a sibling script with
-// --help for usage. Identical in every skill of this bundle on purpose (skills install one directory
-// at a time, so nothing shared outside the skill would ever be installed).
-import { spawnSync } from "node:child_process";
-import { existsSync, readFileSync } from "node:fs";
-import { join } from "node:path";
-import { fileURLToPath } from "node:url";
-import { CONNECT_COMMAND, hasCredential } from "./credential.mjs";
-
-export const PACKAGE = "@catalyst-cloud/catalyst-skills";
-export const CONNECT_HINT = `this machine is not connected to a tenant yet — run: ${CONNECT_COMMAND}`;
-
-/** ~/.config/catalyst-cloud/customer.json, honouring CATALYST_SKILLS_HOME before HOME. */
-export function configPath() {
-  const home = process.env.CATALYST_SKILLS_HOME ?? process.env.HOME ?? process.env.USERPROFILE ?? "";
-  return join(home, ".config", "catalyst-cloud", "customer.json");
-}
-
-/** The customer config, or exit 2 with one line naming the connect command. Never throws. */
-export function requireCustomerConfig() {
-  const path = configPath();
-  if (!existsSync(path)) {
-    console.error(CONNECT_HINT);
-    process.exit(2);
-  }
-  let cfg;
-  try {
-    cfg = JSON.parse(readFileSync(path, "utf8"));
-  } catch (err) {
-    console.error(`${path} could not be read (${err instanceof Error ? err.message : String(err)}) — ${CONNECT_HINT}`);
-    process.exit(2);
-  }
-  if (!hasCredential(cfg) || typeof cfg.baseUrl !== "string") {
-    console.error(`${path} is missing required fields — ${CONNECT_HINT}`);
-    process.exit(2);
-  }
-  return cfg;
-}
-
-/**
- * Run one catalyst-skills verb and return {code, stdout, stderr}. Spawns the CLI whose path the
- * connect step recorded in customer.json; falls back to `npx @catalyst-cloud/catalyst-skills` when
- * no path is recorded or it no longer exists. Exits 2 when the machine is not connected.
- */
-export function runCli(args, opts = {}) {
-  const cfg = requireCustomerConfig();
-  const recorded = typeof cfg.cliPath === "string" && existsSync(cfg.cliPath);
-  const command = recorded ? process.execPath : process.platform === "win32" ? "npx.cmd" : "npx";
-  const argv = recorded ? [cfg.cliPath, ...args] : [PACKAGE, ...args];
-  const res = spawnSync(command, argv, {
-    encoding: "utf8",
-    input: opts.stdin,
-    env: process.env,
-    maxBuffer: 64 * 1024 * 1024,
-    shell: !recorded && process.platform === "win32",
-  });
-  if (res.error) {
-    console.error(`could not run ${recorded ? cfg.cliPath : `npx ${PACKAGE}`}: ${res.error.message}`);
-    process.exit(2);
-  }
-  return { code: res.status ?? 1, stdout: res.stdout ?? "", stderr: res.stderr ?? "" };
-}
-
-/**
- * Run a verb that must succeed. On exit 2 (the CLI's "not configured / refused" class) the script
- * exits 2; on any other non-zero exit it exits 1. The CLI's own stderr is forwarded either way so the
- * reason is never lost.
- */
-export function runCliOrExit(args, opts = {}) {
-  const res = runCli(args, opts);
-  if (res.code === 0) return res;
-  const why = res.stderr.trim() || res.stdout.trim() || `catalyst-skills ${args.join(" ")} exited ${res.code}`;
-  console.error(why);
-  process.exit(res.code === 2 ? 2 : 1);
-}
-
-/** Parse the CLI's --json stdout; null when it is not JSON (the caller decides what that means). */
-export function parseJson(stdout) {
-  try {
-    return JSON.parse(stdout);
-  } catch {
-    return null;
-  }
-}
-
-/** Forward the `source: replica|api (...)` line a query verb prints, so the answer names its source. */
-export function forwardSourceLine(res) {
-  for (const line of res.stderr.split("\n")) {
-    if (line.startsWith("source:")) console.error(line);
-  }
-}
-
-/** True for a ticket identifier such as ABC-123; false for a GitHub node id or anything else. */
-export function looksLikeTicket(s) {
-  return /^[A-Za-z][A-Za-z0-9]*-\d+$/.test(s);
-}
-
-if (process.argv[1] && fileURLToPath(import.meta.url) === process.argv[1]) {
-  console.log("lib/cli.mjs is a library used by the scripts beside it; run any of those with --help for usage.");
-}

package/skills/catalyst-setup/scripts/lib/credential.mjs

@@ -1,29 +0,0 @@
-#!/usr/bin/env node
-// lib/credential.mjs — is this machine connected? The ONE place a skill script decides it, vendored
-// byte-identical into every skill's scripts/lib/ from skill-lib/credential.mjs at the package root
-// (`npm run skill-lib:sync`; a test fails on any drift). Skills install one directory at a time, so
-// each carries its own copy. This file is a library — run a sibling script with --help for usage.
-//
-// customer.json carries exactly one credential: a personal key (`key`), or the keyless login's
-// session (`auth`, the recommended rail). A script never reads either for its value: it spawns the
-// catalyst-skills CLI, which authenticates with whichever is present and refreshes a login's token
-// itself. A new credential kind lands here, once.
-
-/** The command that connects this machine, as every not-connected line names it. */
-export const CONNECT_COMMAND =
-  "npx @catalyst-cloud/catalyst-skills login (or, with a personal key: CATALYST_CLOUD_TOKEN=<your personal key> npx @catalyst-cloud/catalyst-skills login)";
-
-/** True when `cfg` (parsed customer.json) holds a usable credential of either kind. Never throws. */
-export function hasCredential(cfg) {
-  if (cfg === null || typeof cfg !== "object") return false;
-  const key = cfg["key"];
-  if (typeof key === "string" && key !== "") return true;
-  const login = cfg["auth"];
-  return (
-    login !== null &&
-    typeof login === "object" &&
-    login["kind"] === "oauth" &&
-    typeof login["refreshToken"] === "string" &&
-    login["refreshToken"] !== ""
-  );
-}

package/skills/catalyst-setup/scripts/replica-status.mjs

@@ -1,46 +0,0 @@
-#!/usr/bin/env node
-// replica-status.mjs — is the optional local replica alive, and how far behind is it? Wraps
-// `catalyst-skills replica status`, which needs no network (a pidfile, a writer-lock heartbeat and
-// the cursor row); `--probe` adds the one network call that compares the cursor with the cloud's
-// head. The CLI's exit code passes straight through: 0 fresh, 1 present but stale, 2 not connected,
-// 3 absent. A skill reads that code to choose its source; it never refuses to work over it.
-import { runCli } from "./lib/cli.mjs";
-
-const HELP = `Usage: node scripts/replica-status.mjs [--probe] [--json]
-
-  --probe   also fetch the cloud's head cursor and print how far behind the replica is
-  --json    print the CLI's status document {verdict, exitCode, cursor, heartbeatAgeMs, ...}
-
-Exit codes, passed through from catalyst-skills replica status:
-  0  fresh: a live writer, a young heartbeat, a cursor — skills read the replica
-  1  stale: the file exists but the writer is gone or behind — skills read the API and say so
-  2  not connected to a tenant — run: npx @catalyst-cloud/catalyst-skills login (or, with a personal key: CATALYST_CLOUD_TOKEN=<your personal key> npx @catalyst-cloud/catalyst-skills login)
-  3  absent: no replica file — optional; start one with: catalyst-skills replica start --detach`;
-
-const args = process.argv.slice(2);
-if (args.includes("--help") || args.includes("-h")) {
-  console.log(HELP);
-  process.exit(0);
-}
-const unknown = args.filter((a) => a !== "--probe" && a !== "--json");
-if (unknown.length > 0) {
-  console.error(`unknown argument: ${unknown.join(" ")}`);
-  console.log(HELP);
-  process.exit(1);
-}
-
-const cliArgs = ["replica", "status"];
-if (args.includes("--probe")) cliArgs.push("--probe");
-if (args.includes("--json")) cliArgs.push("--json");
-const res = runCli(cliArgs);
-if (res.stdout.trim()) console.log(res.stdout.trimEnd());
-if (res.code !== 0 && res.stderr.trim()) console.error(res.stderr.trimEnd());
-
-const meaning = {
-  0: "fresh — skills read the replica",
-  1: "stale — skills read the API and name that source",
-  2: "not connected to a tenant",
-  3: "absent — the replica is optional; nothing is wrong",
-};
-if (!args.includes("--json")) console.log(`verdict ${res.code}: ${meaning[res.code] ?? "unexpected exit code"}`);
-process.exit(res.code);