@catalyst-cloud/cli 0.16.38 → 0.16.39

package/CHANGELOG.md

@@ -1,5 +1,11 @@
 # Changelog
 
+## 0.16.39
+
+`catalyst query pulls` now sends `--state`, `--repo` and `--draft` to Catalyst, so `--state open --all` reads only the workspace's open pull requests instead of paging through every pull request it has ever had. `--state` takes `open`, `closed` or `merged`, and `--draft` takes `draft` or `ready`. Any other value is refused before a request is made. `open` and `closed` leave out merged pull requests, and the repository and state match in any letter case. Against an older Catalyst that ignores these filters, the CLI applies them to the rows it gets back, so the result is the same. A filtered read of the local replica now checks every pull request it holds, so an older pull request linked to a ticket is still found.
+
+The `catalyst-linear` skill reads the project's label definitions before it chooses a ticket's work type and component.
+
 ## 0.16.38
 
 On a Mac with thoughts custody, a runner update agent that 0.16.35 or 0.16.36 moved kept failing every update with `custody_restore_failed:runtime_custody_mismatch`, even after the CLI updated itself to 0.16.37. The scheduled update installs the new CLI beside the old one, not globally, so the 0.16.37 repair never ran. Now `catalyst runner update` checks which node it runs under. When that differs from the node the custody was set up with, it runs the same command again under the custody's node and exits with that run's result. The agent file is left as it is, and no run in progress is interrupted. `--check` and `--fleet`, a Mac without thoughts custody, and Linux are unchanged.

package/dist/args.js

@@ -137,7 +137,12 @@ export const FLAG_TABLES = {
     query: {
         team: { value: true, help: "team key filter" },
         project: { value: true, help: "project id filter" },
-        state: { value: true, help: "state name filter" },
+        state: {
+            value: true,
+            help: "issues: state name filter; pulls: open, closed or merged",
+        },
+        repo: { value: true, help: "pulls: only this repository (owner/name)" },
+        draft: { value: true, help: "pulls: draft or ready" },
         limit: {
             value: true,
             help: "max rows (default 50); one page only unless --all",
@@ -618,7 +623,7 @@ export const VERB_USAGE = {
     notice: "notice",
     me: "me [--json]",
     contract: "contract [--refresh] [--path <a.b.c>] [--json]",
-    query: "query <issues|issue <id>|pulls|pull <id>|projects|cycles|search <terms>|changes --since <cursor|head>> [--team K] [--project P] [--state S] [--limit N] [--all] [--source replica|api] [--json]",
+    query: "query <issues|issue <id>|pulls|pull <id>|projects|cycles|search <terms>|changes --since <cursor|head>> [--team K] [--project P] [--state S] [--repo O/N] [--draft draft|ready] [--ticket T] [--limit N] [--all] [--source replica|api] [--json]",
     replica: 'replica <start [--detach]|stop|status [--probe] [--json]|sql "<select>"|schema [table]> [--db <path>]',
     runtime: "runtime <status [--json]|install|path|uninstall>",
     events: "events <tail|wait-for|query|status [--probe] [--json]> [--type NAME] [--ticket CTC-N] [--repo O/N] [--ref O/N:BRANCH] [--pr O/N#N] [--session T/PHASE#N] [--to me] [--after SEQUENCE] [--limit N] [--timeout SECONDS] [--directory PATH]",

package/dist/query.js

@@ -68,7 +68,7 @@ export async function cmdQuery(args, ctx, deps = {}) {
             status.verdict === "not-configured") {
             throw new UsageError(`--source replica but the replica is ${status?.verdict ?? "unavailable"}`);
         }
-        result = await fromReplica(ctx, cfg, sub, rest, filters, deps);
+        result = await fromReplica(ctx, cfg, sub, rest, filters, deps, args);
     }
     else {
         result = await fromApi(ctx, cfg, sub, rest, filters, args);
@@ -80,7 +80,7 @@ export async function cmdQuery(args, ctx, deps = {}) {
     printResult(ctx, args, sub, result);
     return 0;
 }
-async function fromReplica(ctx, cfg, sub, rest, f, deps) {
+async function fromReplica(ctx, cfg, sub, rest, f, deps, args) {
     const sdk = await loadSdk();
     const dbPath = replicaDbPath(cfg, ctx.home, ctx.env);
     const engine = await engineFor(sdk, dbPath, ctx, {
@@ -100,8 +100,24 @@ async function fromReplica(ctx, cfg, sub, rest, f, deps) {
             }
             case "issue":
                 return replica.issue(needArg(rest, "issue <identifier>"));
-            case "pulls":
-                return replica.pulls({ limit: f.limit });
+            case "pulls": {
+                const scope = pullScope(args);
+                if (!(scope.state || scope.repo || scope.draft || scope.ticket))
+                    return replica.pulls({ limit: f.limit });
+                // CTC-7158 — the replica is local, so a narrowed read scans every row rather than only the
+                // newest window: an older pull request linked to the ticket is still found.
+                const kept = [];
+                for (let offset = 0;; offset += REPLICA_PULL_PAGE) {
+                    const page = replica.pulls({
+                        limit: REPLICA_PULL_PAGE,
+                        offset,
+                    });
+                    kept.push(...page.filter((row) => pullMatches(row, scope)));
+                    if (page.length < REPLICA_PULL_PAGE || kept.length >= f.limit)
+                        break;
+                }
+                return kept.slice(0, f.limit);
+            }
             case "projects":
                 return applyFilters(replica.projects({
                     limit: Math.max(f.limit, 200),
@@ -147,16 +163,23 @@ async function fromApi(ctx, cfg, sub, rest, f, args) {
             return res.status === 404 ? null : res.body;
         }
         case "pulls": {
-            const ticket = flagString(args, "ticket");
+            const scope = pullScope(args);
+            if (scope.ticket) {
+                const rows = await ticketPulls(ctx, api, scope);
+                return f.all ? rows : rows.slice(0, f.limit);
+            }
+            // CTC-7158 — the facets go to the cloud, so `--state open --all` reads the open pull requests
+            // instead of paging every one the workspace has ever had.
+            const query = { state: scope.state, repo: scope.repo, draft: scope.draft };
             if (f.all) {
-                const { rows } = await fetchAllPages(api, "/api/v1/pulls", { ticket });
-                return rows;
+                const { rows } = await fetchAllPages(api, "/api/v1/pulls", query);
+                return keepPullScope(ctx, rows, scope);
             }
             const page = await fetchPage(api, "/api/v1/pulls", {
+                ...query,
                 limit: f.limit,
-                ticket,
             });
-            const rows = page.rows.slice(0, f.limit);
+            const rows = keepPullScope(ctx, page.rows, scope).slice(0, f.limit);
             const notice = truncationNotice(page);
             if (notice)
                 ctx.stderr(notice);
@@ -264,6 +287,78 @@ function requireIssueScope(scope, f) {
         throw new CliError(`the cloud did not apply ${flag} (${scope === null ? "it sent no x-mirror-scope header" : `it applied: ${scope.join(", ") || "nothing"}`}), so the page is not that scope; nothing printed. Read it with --source replica, or drop ${flag}`, "filter-not-applied", 1);
     }
 }
+const REPLICA_PULL_PAGE = 500;
+const PULL_STATES = ["open", "closed", "merged"];
+const PULL_DRAFTS = ["draft", "ready"];
+/** CTC-7158 — the cloud reads an unknown `?state=` or `?draft=` as no narrowing, so a typo would
+ *  page every pull request. Refuse it here instead. */
+function pullScope(args) {
+    const state = trimmedFlag(args, "state")?.toLowerCase();
+    if (state !== undefined && !PULL_STATES.includes(state))
+        throw new UsageError(`--state for pulls is one of ${PULL_STATES.join(", ")} (got "${state}")`);
+    const draft = trimmedFlag(args, "draft")?.toLowerCase();
+    if (draft !== undefined && !PULL_DRAFTS.includes(draft))
+        throw new UsageError(`--draft is one of ${PULL_DRAFTS.join(", ")} (got "${draft}")`);
+    return {
+        state: state,
+        repo: trimmedFlag(args, "repo"),
+        draft: draft,
+        ticket: trimmedFlag(args, "ticket"),
+    };
+}
+const truthy = (v) => v === true || v === 1 || v === "1" || v === "true";
+/** The cloud's facet rules (the read model's pull scope): `open` and `closed` leave out merged pull
+ *  requests, `merged` is the merged flag alone, `ready` is not a draft, and state and repo match
+ *  without case. */
+function pullMatches(row, s) {
+    const merged = truthy(row.merged);
+    const state = String(row.state ?? "").toLowerCase();
+    if (s.state === "open" && (state !== "open" || merged))
+        return false;
+    if (s.state === "merged" && !merged)
+        return false;
+    if (s.state === "closed" && (state !== "closed" || merged))
+        return false;
+    if (s.draft === "draft" && !truthy(row.draft))
+        return false;
+    if (s.draft === "ready" && truthy(row.draft))
+        return false;
+    if (s.repo && !sameName(row.repo_id, s.repo))
+        return false;
+    if (s.ticket && "linear_issue_identifier" in row && !sameName(row.linear_issue_identifier, s.ticket))
+        return false;
+    return true;
+}
+/** A cloud that predates a facet returns rows outside it. Drop them and say so, so the answer is
+ *  still the asked scope. */
+function keepPullScope(ctx, rows, s) {
+    const kept = rows.filter((row) => pullMatches(row, s));
+    if (kept.length < rows.length)
+        ctx.stderr(`the cloud returned ${rows.length - kept.length} pull requests outside the asked scope; dropped them here`);
+    return kept;
+}
+/** CTC-7158 — `/pulls` has no ticket facet, and an unknown param narrows nothing, so `?ticket=`
+ *  returned the newest page for any ticket. The ticket's own read names its linked pull requests;
+ *  read each of those instead. */
+async function ticketPulls(ctx, api, s) {
+    const ticket = s.ticket;
+    const res = await api.getJson(`/api/v1/issues/${encodeURIComponent(ticket)}`, { accept: [404] });
+    if (res.status === 404)
+        throw new CliError(`--ticket ${ticket}: no such ticket`, "not-found", 1);
+    const rows = [];
+    for (const link of res.body.linked_pulls ?? []) {
+        if (!link.node_id)
+            continue;
+        const pr = await api.getJson(`/api/v1/pulls/${encodeURIComponent(link.node_id)}`, { accept: [404] });
+        if (pr.status === 404) {
+            ctx.stderr(`--ticket ${ticket}: linked pull request ${link.node_id} is not in the mirror`);
+            continue;
+        }
+        if (pullMatches(pr.body, { ...s, ticket: undefined }))
+            rows.push(pr.body);
+    }
+    return rows;
+}
 function trimmedFlag(args, name) {
     const value = flagString(args, name)?.trim();
     return value === "" ? undefined : value;

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@catalyst-cloud/cli",
-  "version": "0.16.38",
+  "version": "0.16.39",
   "description": "Set up Catalyst Cloud, check your tickets and manage your account from the command line.",
   "license": "MIT",
   "type": "module",

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.38 — written in this repository for customer accounts -->
+<!-- vendored-from: @catalyst-cloud/catalyst-skills@0.16.39 — written in this repository for customer accounts -->
 
 # Catalyst's GitHub
 

package/skills/catalyst-github/references/reading-from-the-cloud.md

@@ -5,6 +5,7 @@ Cloud reads are the default on every machine. They need no local writer and no l
 | question | command |
 | -- | -- |
 | Which pull requests name this ticket? | `catalyst query pulls --ticket <KEY-123>` |
+| Which pull requests are open, in one repository or across them all? | `catalyst query pulls --state open --all` (add `--repo <owner/name>` or `--draft ready`). The cloud filters, so this reads only open ones. Never page every pull request with `--all` and filter it yourself. |
 | What state is the PR in: draft, merged, conflict, auto-merge? | `node scripts/read-pr.mjs <KEY-123>` |
 | Which checks are red or still running at the head? | `node scripts/read-pr.mjs <KEY-123>` |
 | Is it mergeable under this repository's policy? | `node scripts/is-it-mergeable.mjs <KEY-123>`, which also reads `catalyst contract --path merge` |

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.38 — written in this repository for customer accounts -->
+<!-- vendored-from: @catalyst-cloud/catalyst-skills@0.16.39 — written in this repository for customer accounts -->
 
 # Catalyst Linear
 
@@ -30,6 +30,7 @@ Exit codes: 0 done, 1 not found or a usage error, 2 this machine is not connecte
 | "what did Catalyst write on this ticket?", a comment shape, a label, the marker, the 👀 | `references/what-a-ticket-accumulates.md` |
 | before any read you will report on; "is this current?"; citing; searching | `references/reading-a-ticket.md` |
 | before any comment, move, label or new ticket; identity, budget, slots, ids | `references/writing-to-linear.md` |
+| proposing work-type or component labels for creation, triage or backfill | `references/ticket-classification.md`; then the project's `.agents/references/ticket-labels.json` if present |
 | which command answers a ticket question from the cloud: stage, last phase, PR, what changed | `references/reading-from-the-cloud.md` |
 | local SQL, only when `catalyst replica status --json` reports `configured: true` | `references/local-replica.md` |
 

package/skills/catalyst-linear/references/ticket-classification.md

@@ -0,0 +1,11 @@
+# Ticket classification
+
+Use this reference when proposing work-type or component labels while creating, triaging, or backfilling tickets. It describes the process; a project's `.agents/references/ticket-labels.json`, when present, owns its vocabulary and boundaries. Read that file from the project checkout before classifying. Do not copy one project's catalog to another team.
+
+1. Read the ticket's description, acceptance criteria, and current labels. A title or repository route alone is not enough to settle a component. Treat linked implementation paths as supporting evidence for a retrospective review, not as proof of the original request.
+2. Decide whether the record requests delivery or asks for a decision, approval, information, or action. Choose one type from the project's catalog when the evidence supports it. A project may define `ask` as a type for the latter records. Keep that type separate from the workflow marker that routes asks, and from the implementation ticket an ask may block. A bug requires evidence of an existing promised behavior that fails; a new capability is a feature; a new guard is test work, while a broken existing CI contract is a bug. Documentation explains behavior; maintenance publishes or configures it; refactoring preserves it.
+3. Select zero or more components whose behavior the requested work materially changes. Allow more than one for independent affected areas. Abstain on an unclear boundary; a path, a generic word, or a test mention alone does not establish ownership. Keep project and initiative relationships, ask/control state, and repository routing separate from these labels.
+4. Record the evidence, uncertainty, and any alternative before a backfill. Apply recommendations only within the authorized scope and under a reviewed classification policy. Preserve the ticket's existing work type unless a reviewed correction calls for replacement. Add supported components without removing unrelated labels. Create a label only when that scope and policy authorize it.
+5. Before a write, use `writing-to-linear.md` to resolve the live label name, scope, ID or ambiguity through current account access. The project file is policy, not an ID cache. Read back the ticket after a reviewed write.
+
+For cleanup of case-only duplicates, inventory active and archived labels and issues. Check synchronization with linked systems, test a disposable canary, and read back both systems after a delay. A write that appears to remove a duplicate may be reversed by synchronization. Stop broad cleanup until the canary has a stable result.

package/skills/catalyst-linear/references/writing-to-linear.md

@@ -30,6 +30,8 @@ Every write spends one unit of the per-host daily budget (`thresholds.hostDailyW
 
 `--label`, `--add` and `--remove` take a label's name or its UUID. A UUID is sent as a label id; every other value is sent as a name, and the proxy resolves it in the ticket's team. When the contract lists one of Catalyst's own labels (the ask marker, the hold label, the release label) as absent from the workspace, the CLI refuses rather than inventing it.
 
+For work-type and component choices, load [ticket classification](ticket-classification.md) and the project's `.agents/references/ticket-labels.json` when present. Those files define recommendations, not live IDs. Verify the current team's label scope and the ticket's existing memberships before changing any classification label. A case-only duplicate needs a synchronization check, a disposable canary and delayed readback in both systems before wider cleanup. Include archived labels and issues in the inventory.
+
 Two labels are a human's, not yours: the release label (which frees a ticket the shape detector held) is applied by a human; the hold labels on a pull request are `catalyst-github`'s subject.
 
 ## A new ticket takes the team key

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.38 — written in this repository for customer accounts -->
+<!-- vendored-from: @catalyst-cloud/catalyst-skills@0.16.39 — written in this repository for customer accounts -->
 
 # Onboard me
 

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.38 — written in this repository for customer accounts -->
+<!-- vendored-from: @catalyst-cloud/catalyst-skills@0.16.39 — 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.38 — written in this repository for customer accounts -->
+<!-- vendored-from: @catalyst-cloud/catalyst-skills@0.16.39 — 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.38 — written in this repository for customer accounts -->
+<!-- vendored-from: @catalyst-cloud/catalyst-skills@0.16.39 — 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.38 — written in this repository for customer accounts -->
+<!-- vendored-from: @catalyst-cloud/catalyst-skills@0.16.39 — 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.38 — written in this repository for customer accounts -->
+<!-- vendored-from: @catalyst-cloud/catalyst-skills@0.16.39 — written in this repository for customer accounts -->
 
 # What's happening