@qodeca/xezar 0.10.1

package/dist/server/forge/github.js

@@ -0,0 +1,2544 @@
+import { execFile } from 'node:child_process';
+import { promisify } from 'node:util';
+import { z } from 'zod';
+import { REFERENCE_STATUS_MAX } from '../../contract/index.js';
+import { autosaveCommit } from '../../git-worktree.js';
+/**
+ * The GitHub forge driver — all `gh`-CLI logic in one place, moved here from
+ * `src/server/github.ts` (tab listing) and `src/server/pr.ts` (draft PRs)
+ * behind the `ForgeDriver` seam. Those modules remain as thin delegates.
+ * `/api/github`'s response shape is this driver's serialization and is
+ * protected by BACKWARD_COMPATIBILITY.md — additive changes only.
+ */
+const exec = promisify(execFile);
+export const GH_PR_DIFF_FILE_CAP = 300;
+export const GH_PR_PATCH_CAP = 512 * 1024;
+export const GH_PR_DIFF_JSON_CAP = 4 * 1024 * 1024;
+const ghPrFileSchema = z.object({
+    filename: z.string().min(1),
+    previous_filename: z.string().optional(),
+    status: z.enum(['added', 'modified', 'removed', 'renamed', 'copied', 'changed']),
+    additions: z.number().int().nonnegative(),
+    deletions: z.number().int().nonnegative(),
+    patch: z.string().optional(),
+});
+const ghPrHeadSchema = z.object({ headRefOid: z.string().regex(/^[0-9a-f]{40}$/i) });
+export class GithubPrNotFoundError extends Error {
+}
+const prDiffCache = new Map();
+/** Fetch no more than the three GitHub pages represented by the public 300-file response cap. */
+export async function fetchPrFilePages(runPage) {
+    const rows = [];
+    for (let page = 1; page <= GH_PR_DIFF_FILE_CAP / 100; page++) {
+        const next = z.array(z.unknown()).parse(JSON.parse(await runPage(page)));
+        rows.push(...next);
+        if (next.length < 100)
+            break;
+    }
+    return rows;
+}
+export async function fetchGithubPrDiff(repoRoot, number, refresh = false) {
+    if (process.env.XEZ_DRY_RUN === '1')
+        return mockGithubPrDiff(number);
+    try {
+        const head = ghPrHeadSchema.parse(JSON.parse(await gh(repoRoot, ['pr', 'view', String(number), '--json', 'headRefOid']))).headRefOid;
+        const key = `${repoRoot}\0${number}\0${head}`;
+        const hit = prDiffCache.get(key);
+        if (!refresh && hit && Date.now() - hit.at < CACHE_MS)
+            return hit.data;
+        const rows = z.array(ghPrFileSchema).parse(await fetchPrFilePages((page) => gh(repoRoot, ['api', `repos/{owner}/{repo}/pulls/${number}/files?per_page=100&page=${page}`], 30_000)));
+        const limited = rows.slice(0, GH_PR_DIFF_FILE_CAP);
+        // A full third page may have a successor. Without fetching a 301st file, conservatively call
+        // the response partial rather than claiming completeness we cannot prove.
+        let responseTruncated = rows.length >= GH_PR_DIFF_FILE_CAP;
+        const reasons = responseTruncated ? [`Only the first ${GH_PR_DIFF_FILE_CAP} files are shown.`] : [];
+        const files = limited.map((row) => {
+            let patch = row.patch;
+            let truncated = false;
+            let patchUnavailableReason;
+            if (patch !== undefined && Buffer.byteLength(patch, 'utf8') > GH_PR_PATCH_CAP) {
+                patch = undefined;
+                truncated = true;
+                patchUnavailableReason = 'too-large';
+                responseTruncated = true;
+            }
+            else if (patch === undefined) {
+                patchUnavailableReason = row.additions === 0 && row.deletions === 0 ? 'binary' : 'not-provided';
+            }
+            return {
+                path: row.filename,
+                ...(row.previous_filename ? { previousPath: row.previous_filename } : {}),
+                status: row.status,
+                additions: row.additions,
+                deletions: row.deletions,
+                ...(patch !== undefined ? { patch } : {}),
+                ...(patchUnavailableReason ? { patchUnavailableReason } : {}),
+                ...(truncated ? { truncated: true } : {}),
+            };
+        });
+        let kept = files;
+        while (kept.length > 0 &&
+            Buffer.byteLength(JSON.stringify({ available: true, number, headSha: head, files: kept }), 'utf8') >
+                GH_PR_DIFF_JSON_CAP) {
+            kept = kept.slice(0, -1);
+            responseTruncated = true;
+        }
+        if (kept.length < files.length)
+            reasons.push('The response size limit omitted some files.');
+        if (files.some((file) => file.truncated))
+            reasons.push('One or more patches exceeded the per-file limit.');
+        const data = {
+            available: true,
+            number,
+            headSha: head,
+            files: kept,
+            additions: rows.reduce((sum, row) => sum + row.additions, 0),
+            deletions: rows.reduce((sum, row) => sum + row.deletions, 0),
+            truncated: responseTruncated,
+            ...(reasons.length ? { reason: reasons.join(' ') } : {}),
+        };
+        prDiffCache.set(key, { at: Date.now(), data });
+        while (prDiffCache.size > 50)
+            prDiffCache.delete(prDiffCache.keys().next().value);
+        return data;
+    }
+    catch (err) {
+        const message = err instanceof Error ? err.message : String(err);
+        if (/HTTP 404|Could not resolve to a PullRequest|no pull requests found/i.test(message)) {
+            throw new GithubPrNotFoundError(`Pull request #${number} was not found`);
+        }
+        return {
+            available: false,
+            reason: /ENOENT/.test(message)
+                ? 'gh CLI not found — install it and run `gh auth login`'
+                : firstLine(message),
+        };
+    }
+}
+function mockGithubPrDiff(number) {
+    return {
+        available: true,
+        number,
+        headSha: '0123456789abcdef0123456789abcdef01234567',
+        additions: 15,
+        deletions: 4,
+        truncated: true,
+        reason: 'One or more patches were not provided by GitHub.',
+        files: [
+            { path: 'src/session.ts', status: 'modified', additions: 8, deletions: 3, patch: '@@ -1,3 +1,4 @@\n-old\n+new\n context' },
+            { path: 'src/new-name.ts', previousPath: 'src/old-name.ts', status: 'renamed', additions: 7, deletions: 1, patch: '@@ -1 +1 @@\n-old name\n+new name' },
+            { path: 'assets/logo.png', status: 'modified', additions: 0, deletions: 0, patchUnavailableReason: 'binary' },
+            { path: 'generated/output.txt', status: 'modified', additions: 0, deletions: 0, patchUnavailableReason: 'too-large', truncated: true },
+        ],
+    };
+}
+// `gh … --json` output — validated at the boundary, extras stripped.
+const ghAuthor = z.object({ login: z.string() }).nullish();
+// `color` is the 6-hex GitHub label color (no `#`), '' when gh omits it.
+const ghLabel = z.object({ name: z.string(), color: z.string().default('') });
+const ghIssueSchema = z.object({
+    number: z.number(),
+    title: z.string(),
+    author: ghAuthor,
+    createdAt: z.string(),
+    labels: z.array(ghLabel).default([]),
+    body: z.string().nullish(),
+    url: z.string(),
+});
+// One check run's `gh --json statusCheckRollup` entry — every field optional/nullish because
+// gh's shape varies by check provider (exported so #400's unit tests can build fixtures).
+export const ghCheckRunSchema = z.object({
+    state: z.string().nullish(),
+    status: z.string().nullish(),
+    conclusion: z.string().nullish(),
+});
+const ghStatusCheckRollup = z.array(ghCheckRunSchema).nullish();
+// The list tier no longer requests `statusCheckRollup` (#664) — it is hydrated lazily per
+// on-screen PR row (`fetchGithubChecks`). `checks` is set to `null` on list rows; the schema
+// keeps no rollup field because the list call never asks for it.
+const ghPrSchema = ghIssueSchema.extend({
+    isDraft: z.boolean().default(false),
+    additions: z.number().default(0),
+    deletions: z.number().default(0),
+});
+const ghPrViewSchema = z.object({
+    number: z.number(),
+    url: z.string(),
+    state: z.string().default('OPEN'),
+    isDraft: z.boolean().default(false),
+    statusCheckRollup: ghStatusCheckRollup,
+});
+const mergeCheckSchema = z.object({
+    name: z.string().default('Check'),
+    state: z.string().nullish(),
+    status: z.string().nullish(),
+    conclusion: z.string().nullish(),
+    detailsUrl: z.string().nullish(),
+});
+const mergePrSchema = z.object({
+    number: z.number(),
+    title: z.string(),
+    url: z.string(),
+    state: z.string(),
+    isDraft: z.boolean().default(false),
+    headRefName: z.string(),
+    baseRefName: z.string(),
+    headRefOid: z.string().regex(/^[0-9a-f]{40}$/),
+    mergeable: z.string().nullish(),
+    mergeStateStatus: z.string().nullish(),
+    reviewDecision: z.string().nullish(),
+    statusCheckRollup: z.array(mergeCheckSchema).nullish(),
+});
+const repoMergePolicySchema = z.object({
+    allow_merge_commit: z.boolean().default(false),
+    allow_squash_merge: z.boolean().default(false),
+    allow_rebase_merge: z.boolean().default(false),
+    merge_commit_title: z.string().nullish(),
+    squash_merge_commit_title: z.string().nullish(),
+});
+const ghMergeResultSchema = z.object({
+    merged: z.boolean(),
+    message: z.string().nullish(),
+    sha: z.string().nullish(),
+});
+/** Exported for unit tests (#400) — collapses a zod-validated `statusCheckRollup` array down to
+ *  the single enum the GitHub tab (list rows + detail badge) renders. */
+export function rollupToChecks(rollup) {
+    if (!rollup || rollup.length === 0)
+        return null;
+    const states = rollup.map((r) => (r.conclusion || r.state || r.status || '').toUpperCase());
+    if (states.some((s) => ['FAILURE', 'ERROR', 'TIMED_OUT', 'ACTION_REQUIRED'].includes(s)))
+        return 'failing';
+    if (states.some((s) => ['PENDING', 'IN_PROGRESS', 'QUEUED', 'EXPECTED', ''].includes(s)))
+        return 'pending';
+    return 'passing';
+}
+async function gh(repoRoot, args, timeout = 15_000) {
+    const { stdout } = await exec('gh', args, {
+        cwd: repoRoot,
+        timeout,
+        maxBuffer: 50 * 1024 * 1024,
+    });
+    return stdout;
+}
+/** GraphQL's max page size; pagination is capped at 10 pages/kind (1000 rows — the GUI's full
+ *  background shot). Rows past the window keep `comments: 0`, which the UI reads as "no badge". */
+export const GH_COUNTS_MAX_PAGES = 10;
+const countsQuery = (root) => `
+query ($owner: String!, $name: String!, $endCursor: String) {
+  repository(owner: $owner, name: $name) {
+    ${root}(first: 100, after: $endCursor, states: OPEN,
+           orderBy: {field: CREATED_AT, direction: DESC}) {
+      nodes { number comments { totalCount } }
+      pageInfo { hasNextPage endCursor }
+    }
+  }
+}`;
+const ghCountsPageSchema = z.object({
+    nodes: z.array(z.object({ number: z.number(), comments: z.object({ totalCount: z.number() }) })),
+    pageInfo: z.object({ hasNextPage: z.boolean(), endCursor: z.string().nullish() }),
+});
+/** Validate + flatten one gh GraphQL counts response into a `number → count` map plus the page
+ *  cursor. Exported for unit tests (the zod boundary + shape). Throws on a malformed envelope. */
+export function parseCountsPage(out, root) {
+    const parsed = JSON.parse(out);
+    const page = ghCountsPageSchema.parse(parsed?.data?.repository?.[root]);
+    const counts = {};
+    for (const node of page.nodes)
+        counts[node.number] = node.comments.totalCount;
+    return { counts, hasNextPage: page.pageInfo.hasNextPage, endCursor: page.pageInfo.endCursor ?? null };
+}
+async function paginateCounts(runGraphql, owner, name, root, maxPages) {
+    const counts = {};
+    let cursor = null;
+    for (let page = 0; page < maxPages; page++) {
+        const variables = { owner, name };
+        if (cursor)
+            variables.endCursor = cursor;
+        const res = parseCountsPage(await runGraphql(countsQuery(root), variables), root);
+        Object.assign(counts, res.counts);
+        if (!res.hasNextPage || !res.endCursor)
+            break;
+        cursor = res.endCursor;
+    }
+    return counts;
+}
+/** Comment counts for open issues and PRs as `number → count` maps. Two independent paginated
+ *  queries (issues and PRs need separate cursors) run in parallel; any failure degrades the whole
+ *  thing to empty maps so the tab is never held up by counts. Exported for unit tests. */
+export async function fetchCommentCounts(runGraphql, owner, name, maxPages = GH_COUNTS_MAX_PAGES) {
+    try {
+        const [issues, prs] = await Promise.all([
+            paginateCounts(runGraphql, owner, name, 'issues', maxPages),
+            paginateCounts(runGraphql, owner, name, 'pullRequests', maxPages),
+        ]);
+        return { issues, prs };
+    }
+    catch {
+        return { issues: {}, prs: {} };
+    }
+}
+/** `owner/name` → `{ owner, name }`, or null when the handle isn't a clean two-part slug. */
+export function parseOwnerName(nameWithOwner) {
+    const [owner, name, ...rest] = nameWithOwner.trim().split('/');
+    return owner && name && rest.length === 0 ? { owner, name } : null;
+}
+/* Reads degrade to `available: false` with a hint — never an error (plan rule
+   7): no `gh`, no remote, offline all land on the same quiet path. A short
+   cache keeps tab switches from hammering the GitHub API; a cached fetch with
+   a bigger limit than asked serves fine (it's a superset). Keyed by `repoRoot`
+   (multi-project workspace, step 2.6): one project's — possibly private —
+   issues/PRs must never be served under another project's scope. Bounded like
+   `commentsCache` so an unbounded workspace can't grow it without limit. */
+const listCache = new Map();
+const LIST_CACHE_MAX = 50;
+const CACHE_MS = 60_000;
+export const GH_MAX_LIMIT = 1000;
+export async function fetchGithub(repoRoot, refresh = false, limit = 30) {
+    if (process.env.XEZ_DRY_RUN === '1')
+        return mockGithub();
+    const capped = Math.min(Math.max(limit, 1), GH_MAX_LIMIT);
+    const hit = listCache.get(repoRoot);
+    if (!refresh && hit && Date.now() - hit.at < CACHE_MS && hit.limit >= capped) {
+        return hit.data;
+    }
+    try {
+        // No `comments` field — `gh … --json comments` ships full comment bodies.
+        // No `statusCheckRollup` either (#664): the CI rollup for every open PR was the
+        // dominant cost — it forced the 60 s budget below — and is now hydrated lazily per
+        // on-screen PR row via `fetchGithubChecks`. A big list still gets a little more wall
+        // clock than the default 30, but nothing like the old rollup walk.
+        const timeout = capped > 100 ? 30_000 : 15_000;
+        const fields = 'number,title,author,createdAt,labels,body,url';
+        // The repo handle first (cheap) so the counts GraphQL query — which needs owner/name —
+        // can run parallel to the two expensive list calls below.
+        const repoOut = await gh(repoRoot, ['repo', 'view', '--json', 'nameWithOwner', '--jq', '.nameWithOwner'], timeout);
+        const ownerName = parseOwnerName(repoOut);
+        const runGraphql = (query, variables) => {
+            const args = ['api', 'graphql', '-f', `query=${query}`];
+            for (const [key, value] of Object.entries(variables))
+                args.push('-f', `${key}=${value}`);
+            return gh(repoRoot, args, timeout);
+        };
+        // Bound the counts pagination to the rows actually being fetched: a page is 100, so
+        // `ceil(capped / 100)` pages (still capped at GH_COUNTS_MAX_PAGES) cover exactly the visible
+        // window and no more — the default 30-item load pays ONE counts round-trip, not ten. Rows
+        // beyond the window keep `comments: 0`, which the UI reads as "no badge" (same as before).
+        const countsMaxPages = Math.min(GH_COUNTS_MAX_PAGES, Math.max(1, Math.ceil(capped / 100)));
+        const [issuesOut, prsOut, counts] = await Promise.all([
+            gh(repoRoot, ['issue', 'list', '--limit', String(capped), '--json', fields], timeout),
+            gh(repoRoot, ['pr', 'list', '--limit', String(capped), '--json', `${fields},isDraft,additions,deletions`], timeout),
+            // Real comment counts (#499). Degrades to empty maps on its own — a failure here leaves
+            // every count at 0, never fails the tab. Skipped entirely if the handle isn't parseable.
+            ownerName
+                ? fetchCommentCounts(runGraphql, ownerName.owner, ownerName.name, countsMaxPages)
+                : Promise.resolve({ issues: {}, prs: {} }),
+        ]);
+        // One repo-wide label→color map, filled as we flatten each item's labels.
+        const labelColors = {};
+        const recordColor = (l) => {
+            if (l.color && !labelColors[l.name])
+                labelColors[l.name] = l.color;
+        };
+        const issues = z.array(ghIssueSchema).parse(JSON.parse(issuesOut)).map((i) => {
+            i.labels.forEach(recordColor);
+            return {
+                kind: 'issue',
+                number: i.number,
+                title: i.title,
+                author: i.author?.login ?? '?',
+                createdAt: i.createdAt,
+                labels: i.labels.map((l) => l.name),
+                body: (i.body ?? '').slice(0, 8_000),
+                url: i.url,
+                comments: counts.issues[i.number] ?? 0,
+            };
+        });
+        const prs = z.array(ghPrSchema).parse(JSON.parse(prsOut)).map((p) => {
+            p.labels.forEach(recordColor);
+            return {
+                kind: 'pr',
+                number: p.number,
+                title: p.title,
+                author: p.author?.login ?? '?',
+                createdAt: p.createdAt,
+                labels: [...p.labels.map((l) => l.name), ...(p.isDraft ? ['draft'] : [])],
+                body: (p.body ?? '').slice(0, 8_000),
+                url: p.url,
+                comments: counts.prs[p.number] ?? 0,
+                isDraft: p.isDraft,
+                additions: p.additions,
+                deletions: p.deletions,
+                // Hydrated lazily by `fetchGithubChecks` for on-screen rows (#664) — the list no
+                // longer pays for the CI rollup of every open PR.
+                checks: null,
+            };
+        });
+        const data = {
+            available: true,
+            repo: repoOut.trim() || undefined,
+            syncedAt: new Date().toISOString(),
+            issues,
+            prs,
+            labelColors,
+        };
+        listCache.delete(repoRoot); // re-insert so this key becomes the newest
+        listCache.set(repoRoot, { at: Date.now(), limit: capped, data });
+        while (listCache.size > LIST_CACHE_MAX) {
+            const oldest = listCache.keys().next().value;
+            if (oldest === undefined)
+                break;
+            listCache.delete(oldest);
+        }
+        return data;
+    }
+    catch (err) {
+        const message = err instanceof Error ? err.message : String(err);
+        const reason = /ENOENT/.test(message)
+            ? 'gh CLI not found — install it and run `gh auth login`'
+            : firstLine(message);
+        return { available: false, reason, issues: [], prs: [] };
+    }
+}
+function firstLine(s) {
+    return s.split('\n').find((l) => l.trim().length > 0)?.trim() ?? 'gh failed';
+}
+// ---- search across states (#730) -------------------------------------------
+// `fetchGithub` above lists the OPEN set only (`gh issue/pr list` defaults to `--state open`),
+// and the tab's search is an in-memory filter over exactly that payload — so a closed or merged
+// item is not "past the window", it was never fetched at all and no amount of scrolling reaches
+// it. This tier asks GitHub instead of re-filtering what we already hold. It is deliberately a
+// SECOND, on-demand path rather than widening the list to `--state all`: the list is the tab's
+// hot path, and making every load pay for hundreds of closed rows to serve an occasional lookup
+// would trade a search bug for a performance one.
+/** Hits per search. `gh search`'s own default is 30; 50 matches the page size the incremental-
+ *  loading spec settled on and keeps one search to a single `gh` round-trip. */
+export const GH_SEARCH_MAX = 50;
+/** The `--json` field set each search path requests. Neither path asks for `additions`/`deletions`
+ *  or `statusCheckRollup` — the same reason the list tier stopped (#664), those are the expensive
+ *  per-PR lookups.
+ *
+ *  `isDraft` is added for PRs only, and that is a hard requirement rather than a nicety: `gh search
+ *  issues` does not define the field at all and rejects the whole call with `Unknown JSON field:
+ *  "isDraft"`, which would turn every text query on the Issues tab into the "could not be searched"
+ *  degrade. `gh {issue,pr} view` is the opposite — it tolerates the field for both kinds — so only
+ *  the search path needs to discriminate. */
+const SEARCH_FIELDS = 'number,title,author,createdAt,labels,body,url';
+/** `gh search {prs,issues} --json` field list for `kind`. See `SEARCH_FIELDS` on why `isDraft`
+ *  cannot be sent to the issues search. */
+function searchJsonFields(kind) {
+    return kind === 'pr'
+        ? `${SEARCH_FIELDS},isDraft,commentsCount`
+        : `${SEARCH_FIELDS},commentsCount`;
+}
+/** `gh search issues|prs` returns `commentsCount` where the list tier gets its counts from a
+ *  separate GraphQL walk. Same value, different spelling — normalized into `ForgeItem.comments`. */
+const ghSearchHitSchema = ghIssueSchema.extend({
+    isDraft: z.boolean().default(false),
+    commentsCount: z.number().default(0),
+});
+/** `gh {issue,pr} view <n> --json …` — the exact-number path. Shares `ghIssueSchema`'s core;
+ *  `isDraft`/`additions`/`deletions` are PR-only and default harmlessly for issues. */
+const ghViewHitSchema = ghIssueSchema.extend({
+    isDraft: z.boolean().default(false),
+    additions: z.number().default(0),
+    deletions: z.number().default(0),
+});
+/** Flatten one validated hit into the `ForgeItem` the tab's rows already render. `checks: null`
+ *  is what the list tier ships too since #664 — the glyph hydrates lazily via `/api/github/checks`
+ *  — so a searched row and a listed row are indistinguishable to the UI. */
+function toSearchItem(kind, hit, labelColors) {
+    for (const label of hit.labels) {
+        if (label.color && !labelColors[label.name])
+            labelColors[label.name] = label.color;
+    }
+    const item = {
+        kind,
+        number: hit.number,
+        title: hit.title,
+        author: hit.author?.login ?? '?',
+        createdAt: hit.createdAt,
+        labels: hit.labels.map((l) => l.name),
+        body: (hit.body ?? '').slice(0, 8_000),
+        url: hit.url,
+        comments: 'commentsCount' in hit ? hit.commentsCount : 0,
+    };
+    if (kind === 'pr') {
+        item.isDraft = hit.isDraft;
+        // Draft is a label on list rows as well as a flag — keep the parity so filtering by the
+        // `draft` chip behaves the same on a searched row.
+        if (hit.isDraft)
+            item.labels = [...item.labels, 'draft'];
+        if ('additions' in hit)
+            item.additions = hit.additions;
+        if ('deletions' in hit)
+            item.deletions = hit.deletions;
+        item.checks = null;
+    }
+    return item;
+}
+/**
+ * Find issues/PRs in ANY state (#730).
+ *
+ * Two query shapes, because they want different GitHub calls:
+ *  - **A bare number** (`4507`, `#4507`) is a lookup, not a search: `gh {pr,issue} view <n>` is
+ *    one cheap, state-agnostic call that finds a PR merged two years ago as readily as one opened
+ *    today. GitHub's search index cannot be relied on to surface an exact number at all.
+ *  - **Anything else** is a text search: `gh search {prs,issues} <query> --repo owner/name`, with
+ *    `--state` deliberately OMITTED — the flag only accepts `open|closed`, and leaving it off is
+ *    what searches every state.
+ *
+ * A numeric query that resolves to nothing (wrong repo, deleted, or simply a number the user meant
+ * as text) falls through to the text path rather than reporting "not found" — `4507` should still
+ * find a PR whose title contains it.
+ *
+ * Never throws: every failure lands on `{available: false, reason}`, the same quiet degrade the
+ * rest of the tab uses. Exported for unit tests.
+ */
+export async function searchGithubItems(repoRoot, kind, query, limit = GH_SEARCH_MAX) {
+    const trimmed = query.trim();
+    if (trimmed === '')
+        return { available: true, items: [] };
+    const capped = Math.min(Math.max(limit, 1), GH_SEARCH_MAX);
+    if (process.env.XEZ_DRY_RUN === '1') {
+        const mock = mockGithub();
+        const pool = kind === 'issue' ? mock.issues : mock.prs;
+        const needle = trimmed.replace(/^#/, '').toLowerCase();
+        // The fixture obeys `limit` and flags `truncated` on the live path's own rule (#838). The
+        // catalog is a handful of rows, so the cap never bites in the demo itself — but offline mode
+        // is the only place anyone developing without `gh` exercises cap-and-truncate at all, and a
+        // dry-run that returned the whole pool unflagged would hide a regression in it.
+        const items = pool
+            .filter((i) => String(i.number).includes(needle) || i.title.toLowerCase().includes(needle))
+            .slice(0, capped);
+        return { available: true, items, truncated: items.length >= capped };
+    }
+    const labelColors = {};
+    const numeric = trimmed.replace(/^#/, '');
+    try {
+        if (/^\d+$/.test(numeric)) {
+            // `Number()` before interpolation: the regex already guarantees digits, but the number is
+            // user input reaching an argv, so it is normalized rather than passed through verbatim.
+            const number = Number(numeric);
+            try {
+                const out = await gh(repoRoot, [
+                    kind === 'pr' ? 'pr' : 'issue',
+                    'view',
+                    String(number),
+                    '--json',
+                    kind === 'pr' ? `${SEARCH_FIELDS},isDraft,additions,deletions` : SEARCH_FIELDS,
+                ]);
+                const hit = ghViewHitSchema.parse(JSON.parse(out));
+                return { available: true, items: [toSearchItem(kind, hit, labelColors)], labelColors };
+            }
+            catch {
+                // Not a number in this repo (or not this kind) — fall through to the text search below.
+            }
+        }
+        // The memoized handle first (usually a hit). Its `null` is deliberately ambiguous — it swallows
+        // "gh is missing" and "no remote" alike — so on a miss, ask once more directly and let the real
+        // failure reach the catch below, where it becomes the same honest hint the list tier gives.
+        // Only a genuinely unparseable slug reaches the "no remote" reason.
+        const handle = (await resolveRepoHandle(repoRoot)) ??
+            parseOwnerName(await gh(repoRoot, ['repo', 'view', '--json', 'nameWithOwner', '--jq', '.nameWithOwner']));
+        if (!handle) {
+            return { available: false, reason: 'no GitHub remote to search', items: [] };
+        }
+        const out = await gh(repoRoot, [
+            'search',
+            kind === 'pr' ? 'prs' : 'issues',
+            '--repo',
+            `${handle.owner}/${handle.name}`,
+            '--limit',
+            String(capped),
+            '--json',
+            searchJsonFields(kind),
+            // End-of-flags, then the query: `gh` parses a leading `-`/`--` as a flag otherwise, so a
+            // flag-shaped query would degrade the tab to "GitHub could not be searched: unknown flag",
+            // and the exact text `--web` would match `gh search`'s own `-w, --web` and open a browser
+            // on the cockpit's host. Behind `--` it is search text, which is all the box ever means.
+            '--',
+            trimmed,
+        ]);
+        const hits = z.array(ghSearchHitSchema).parse(JSON.parse(out));
+        return {
+            available: true,
+            items: hits.map((hit) => toSearchItem(kind, hit, labelColors)),
+            truncated: hits.length >= capped,
+            labelColors,
+        };
+    }
+    catch (err) {
+        const message = err instanceof Error ? err.message : String(err);
+        const reason = /ENOENT/.test(message)
+            ? 'gh CLI not found — install it and run `gh auth login`'
+            : firstLine(message);
+        return { available: false, reason, items: [] };
+    }
+}
+/** XEZ_DRY_RUN=1 — a small fixed catalog so the GitHub tab is demoable offline. */
+function mockGithub() {
+    const mk = (over) => ({
+        author: 'mock',
+        createdAt: new Date(Date.now() - over.number * 3_600_000).toISOString(),
+        labels: [],
+        url: `https://github.com/mock/repo/${over.kind === 'pr' ? 'pull' : 'issues'}/${over.number}`,
+        comments: 0,
+        ...over,
+    });
+    return {
+        available: true,
+        repo: 'mock/repo',
+        syncedAt: new Date().toISOString(),
+        issues: [
+            mk({ kind: 'issue', number: 142, title: 'Login form drops session on refresh', labels: ['bug', 'auth'], comments: 3, body: 'Repro: log in, hit reload — you land back on /login. The session cookie is set correctly, but the client store rehydrates before the cookie check resolves, so the auth guard redirects.' }),
+            mk({ kind: 'issue', number: 139, title: 'Add --json flag to xez CLI output', labels: ['enhancement', 'cli'], comments: 1, body: 'For scripting it would help if `xez list` and `xez status` could emit machine-readable JSON instead of the table view.' }),
+            mk({ kind: 'issue', number: 135, title: 'Flaky e2e: worktree cleanup race on cancel', labels: ['bug', 'flaky-test'], comments: 6, body: 'Cancelling a run while the agent holds a file lock leaves a dangling worktree. The next run on the same branch then fails with "worktree already exists".' }),
+        ],
+        prs: [
+            mk({ kind: 'pr', number: 128, title: 'Fix flaky auth test in CI', labels: ['tests'], checks: 'passing', additions: 6, deletions: 3, body: 'Loosens the timing assertion in refresh.test.ts to a realistic budget.' }),
+            mk({ kind: 'pr', number: 124, title: 'Rate limit /api/runs', labels: ['server', 'draft'], isDraft: true, checks: 'failing', additions: 118, deletions: 7, comments: 4, body: 'Draft: token-bucket middleware on the runs router. Still needs the config surface and README docs before review.' }),
+        ],
+        labelColors: {
+            bug: 'd73a4a',
+            auth: '5319e7',
+            enhancement: 'a2eeef',
+            cli: '0e8a16',
+            'flaky-test': 'fbca04',
+            tests: 'c5def5',
+            server: '1d76db',
+            draft: '6a737d',
+        },
+    };
+}
+// ---- comment threads (#499 Phase 2) ----------------------------------------
+// A lazy per-thread fetch behind `GET /api/github/comments/:kind/:number`: the
+// conversation comments (issues endpoint — GitHub serves PR conversation
+// comments there too), plus submitted reviews for PRs, normalized into one
+// chronological `ForgeComment[]`. Its own bounded 60 s cache keeps an open
+// detail view from re-fetching on every focus. Degrades to `available: false`
+// exactly like the list fetch — never a 5xx.
+const ghCommentUser = z.object({ login: z.string(), avatar_url: z.string().nullish() }).nullish();
+const ghIssueCommentSchema = z.object({
+    id: z.number(),
+    user: ghCommentUser,
+    created_at: z.string(),
+    body: z.string().nullish(),
+    html_url: z.string(),
+});
+const ghReviewSchema = z.object({
+    id: z.number(),
+    user: ghCommentUser,
+    body: z.string().nullish(),
+    state: z.string(),
+    submitted_at: z.string().nullish(),
+    html_url: z.string(),
+});
+// ---- timeline events (#525) -------------------------------------------------
+// The thread's non-comment history — commits, label changes, assignments, merges, force-pushes,
+// cross-references. Sourced from `/issues/{n}/timeline`, which returns comments AND events in one
+// chronological stream, so the `commented` rows keep flowing through `normalizeComments` unchanged
+// and `comments[]` stays exactly what BACKWARD_COMPATIBILITY.md §2 promises.
+/** The event kinds rendered in v1 — an allowlist, so a new GitHub event type is dropped rather
+ *  than rendered and can never crash or clutter the thread. Real timelines carry plenty that
+ *  github.com itself doesn't surface (`subscribed`, `mentioned`, `review_requested`).
+ *
+ *  `reviewed` is deliberately absent: timeline `reviewed` rows DO carry a body and would work,
+ *  but `/pulls/{n}/reviews` is already normalized, chipped and empty-body-filtered, so sourcing
+ *  both would render every review twice. */
+export const TIMELINE_EVENT_KINDS = new Set([
+    'committed',
+    'labeled',
+    'unlabeled',
+    'assigned',
+    'unassigned',
+    'merged',
+    'closed',
+    'reopened',
+    'head_ref_force_pushed',
+    'cross-referenced',
+    'renamed',
+]);
+/** Events get their OWN cap, independent of `THREAD_ENTRY_CAP`. A combined cap would mean a
+ *  thread with 150 comments and 100 events returns ~120 comments — silently removing contents
+ *  from a §2-protected response. */
+export const TIMELINE_EVENT_CAP = 200;
+/** `gh api --paginate` has no page limit, so the timeline fetch hand-rolls a bounded loop. */
+export const TIMELINE_MAX_PAGES = 10;
+/** ONE budget shared by every page. `gh()`'s timeout is per invocation, so ten pages at the 15 s
+ *  default would put the ceiling at 150 s — an order of magnitude worse than the single
+ *  `--paginate` spawn this replaces. The loop tracks a deadline and passes what's left. */
+export const TIMELINE_BUDGET_MS = 15_000;
+/** Never spawn a page that cannot finish. A bare `remaining <= 0` guard catches only the exact
+ *  boundary; the realistic case is 300 ms left, which spawns `gh` with a 300 ms timeout, throws,
+ *  and is indistinguishable from a real endpoint failure. */
+export const TIMELINE_MIN_PAGE_MS = 2_000;
+/** `committed` messages are trimmed to their first line, then this. */
+const COMMIT_MESSAGE_CAP = 120;
+/** One timeline row. `event` stays a loose `z.string()` so unknown kinds parse and are dropped by
+ *  the allowlist rather than throwing the whole page. Extras are stripped by default — notably
+ *  `author.email`, which is read for nothing and must not reach the wire type. */
+export const ghTimelineEventSchema = z.object({
+    event: z.string(),
+    id: z.number().nullish(),
+    node_id: z.string().nullish(),
+    created_at: z.string().nullish(),
+    actor: z.object({ login: z.string(), avatar_url: z.string().nullish() }).nullish(),
+    url: z.string().nullish(),
+    html_url: z.string().nullish(),
+    // `committed`
+    sha: z.string().nullish(),
+    message: z.string().nullish(),
+    author: z.object({ name: z.string().nullish(), date: z.string().nullish() }).nullish(),
+    // `labeled` / `unlabeled`
+    label: z.object({ name: z.string(), color: z.string().nullish() }).nullish(),
+    // `assigned` / `unassigned`
+    assignee: z.object({ login: z.string() }).nullish(),
+    // `renamed`
+    rename: z.object({ from: z.string().nullish(), to: z.string().nullish() }).nullish(),
+    // `cross-referenced`
+    source: z
+        .object({
+        issue: z
+            .object({
+            number: z.number().nullish(),
+            title: z.string().nullish(),
+            html_url: z.string().nullish(),
+            pull_request: z.unknown().nullish(),
+        })
+            .nullish(),
+    })
+        .nullish(),
+});
+const REVIEW_STATE = {
+    APPROVED: 'approved',
+    CHANGES_REQUESTED: 'changes_requested',
+    COMMENTED: 'commented',
+    DISMISSED: 'dismissed',
+};
+/** First 200 thread entries, then `truncated`; each body sliced to 8 000 chars (same cap as
+ *  item bodies). */
+export const THREAD_ENTRY_CAP = 200;
+const COMMENT_BODY_CAP = 8_000;
+/** `gh api …/issues/{n}/comments` JSON → `ForgeComment[]`. Exported for unit tests. */
+export function normalizeComments(raw) {
+    return z.array(ghIssueCommentSchema).parse(raw).map((c) => ({
+        id: c.id,
+        author: c.user?.login ?? '?',
+        avatarUrl: c.user?.avatar_url ?? undefined,
+        createdAt: c.created_at,
+        body: (c.body ?? '').slice(0, COMMENT_BODY_CAP),
+        kind: 'comment',
+        url: c.html_url,
+    }));
+}
+/** `gh api …/pulls/{n}/reviews` JSON → `ForgeComment[]`. Reviews with an empty body AND state
+ *  COMMENTED/PENDING carry no signal in a flat thread and are dropped; the rest map to
+ *  `kind: 'review'` (Q4). Exported for unit tests. */
+export function normalizeReviews(raw) {
+    return z
+        .array(ghReviewSchema)
+        .parse(raw)
+        .filter((r) => {
+        const state = r.state.toUpperCase();
+        const emptyBody = (r.body ?? '').trim().length === 0;
+        return !(emptyBody && (state === 'COMMENTED' || state === 'PENDING'));
+    })
+        .map((r) => ({
+        id: r.id,
+        author: r.user?.login ?? '?',
+        avatarUrl: r.user?.avatar_url ?? undefined,
+        createdAt: r.submitted_at ?? '',
+        body: (r.body ?? '').slice(0, COMMENT_BODY_CAP),
+        kind: 'review',
+        reviewState: REVIEW_STATE[r.state.toUpperCase()],
+        url: r.html_url,
+    }));
+}
+/**
+ * `gh api …/issues/{n}/timeline` JSON → `ForgeTimelineEvent[]`, plus whether the cap fired.
+ *
+ * Returns `truncated` rather than just the array because the caller has no other way to learn it:
+ * `events.length === TIMELINE_EVENT_CAP` is ambiguous on a thread with exactly that many.
+ *
+ * Three details here are load-bearing and were verified against a real timeline, not assumed:
+ *
+ * 1. **`committed` rows return `created_at: null`** — the real timestamp is at `author.date`.
+ *    Mapping `created_at` naively yields `createdAt: null` on every commit, which string-sorts to
+ *    the top and silently reorders the entire thread.
+ * 2. **`committed` carries a git author, not a GitHub actor** — a name, no login, no avatar.
+ * 3. **The cap keeps the NEWEST events — `slice(-cap)`**, the opposite of the neighbouring
+ *    `mergeThread`, which head-slices. The timeline arrives oldest-first, so `slice(0, cap)` would
+ *    retain 200 stale day-one `labeled` rows and discard the merge and the recent commits — the
+ *    exact rows #525 asks for.
+ *
+ * Exported for unit tests.
+ */
+export function normalizeEvents(raw, cap = TIMELINE_EVENT_CAP) {
+    const rows = z.array(ghTimelineEventSchema).parse(raw);
+    const mapped = [];
+    rows.forEach((row, index) => {
+        const kind = row.event;
+        if (!TIMELINE_EVENT_KINDS.has(kind))
+            return; // unknown//noise → dropped, never rendered
+        // Per-kind timestamp resolution — see (1) above.
+        const rawAt = kind === 'committed' ? row.author?.date : row.created_at;
+        if (!rawAt)
+            return; // no resolvable timestamp → drop, rather than merge at an arbitrary spot
+        // `author.date` arrives with a numeric offset (`+02:00`); normalize so the string compare the
+        // thread sorts by stays correct across zones.
+        const parsedAt = new Date(rawAt);
+        if (Number.isNaN(parsedAt.getTime()))
+            return;
+        const createdAt = parsedAt.toISOString();
+        // Per-kind actor resolution — see (2) above.
+        const actor = (kind === 'committed' ? row.author?.name : row.actor?.login) ?? '?';
+        // Identity: `sha` sits ahead of `node_id` deliberately. `committed` rows carry both, and a
+        // node_id-first order would key commits by an opaque `C_kwDO…` blob instead of the SHA, which
+        // is the natural, debuggable identifier and is already the rollup key. The bare-index fallback
+        // reaches only `cross-referenced`, the one kind with no identity at all — as a general scheme
+        // it would be wrong, since the id becomes the React key and an index over the post-sort array
+        // shifts for every row below an insertion, remounting them on each 60 s refetch.
+        const identity = row.id ?? row.sha ?? row.node_id ?? index;
+        const event = {
+            id: `evt-${identity}`,
+            kind,
+            actor,
+            createdAt,
+        };
+        // A git author has no avatar, so `committed` deliberately carries none.
+        if (kind !== 'committed' && row.actor?.avatar_url)
+            event.avatarUrl = row.actor.avatar_url;
+        switch (kind) {
+            case 'committed': {
+                // Enforce the full-40-hex invariant the rollup query depends on rather than assuming it:
+                // `oid` rejects anything else, and a malformed value embedded in the batched query would
+                // cost the whole chunk its glyphs instead of just this commit.
+                if (row.sha && /^[0-9a-f]{40}$/i.test(row.sha))
+                    event.sha = row.sha;
+                if (row.message)
+                    event.message = (row.message.split('\n')[0] ?? '').slice(0, COMMIT_MESSAGE_CAP);
+                if (row.html_url)
+                    event.url = row.html_url;
+                break;
+            }
+            case 'labeled':
+            case 'unlabeled': {
+                if (row.label) {
+                    event.label = { name: row.label.name };
+                    if (row.label.color)
+                        event.label.color = row.label.color;
+                }
+                break;
+            }
+            case 'assigned':
+            case 'unassigned': {
+                if (row.assignee?.login)
+                    event.subject = row.assignee.login;
+                break;
+            }
+            case 'renamed': {
+                if (row.rename?.to)
+                    event.subject = row.rename.to;
+                break;
+            }
+            case 'cross-referenced': {
+                const issue = row.source?.issue;
+                if (issue?.number != null)
+                    event.refNumber = issue.number;
+                if (issue?.title)
+                    event.refTitle = issue.title;
+                if (issue)
+                    event.refIsPr = Boolean(issue.pull_request);
+                if (issue?.html_url)
+                    event.url = issue.html_url;
+                break;
+            }
+            default:
+                break;
+        }
+        mapped.push(event);
+    });
+    const truncated = mapped.length > cap;
+    // slice(-cap), NOT slice(0, cap) — see (3) above.
+    return { events: truncated ? mapped.slice(-cap) : mapped, truncated };
+}
+/** Merge comment/review lists chronologically (oldest first) and apply the entry cap. Exported
+ *  for unit tests. */
+export function mergeThread(parts, cap = THREAD_ENTRY_CAP) {
+    const all = parts.flat().sort((a, b) => a.createdAt.localeCompare(b.createdAt));
+    const truncated = all.length > cap;
+    return { comments: truncated ? all.slice(0, cap) : all, truncated };
+}
+// Per-thread cache: keyed `repoRoot␀kind#number` (the root scopes the key — two projects each
+// having a PR #42 must not collide; step 2.6), same 60 s TTL as the list cache but BOUNDED — a
+// long browsing session can't grow it without limit (Map preserves insertion order → oldest
+// first).
+const commentsCache = new Map();
+const COMMENTS_CACHE_MAX = 50;
+function cacheComments(key, data) {
+    commentsCache.delete(key); // re-insert so this key becomes the newest
+    commentsCache.set(key, { at: Date.now(), data });
+    while (commentsCache.size > COMMENTS_CACHE_MAX) {
+        const oldest = commentsCache.keys().next().value;
+        if (oldest === undefined)
+            break;
+        commentsCache.delete(oldest);
+    }
+}
+/** Test-only: drop the per-thread cache so cases don't leak state into each other. */
+export function __clearCommentsCacheForTests() {
+    commentsCache.clear();
+}
+const TIMELINE_PER_PAGE = 100;
+// The repo handle for the per-commit checks query (#525 Phase 2). Memoized per repoRoot — stable
+// in practice, and keyed per root rather than globally for multi-project forward-compatibility.
+// `null` is a cached PERMANENT negative (the slug isn't a clean two-part name, so retrying cannot
+// help). A *thrown* gh failure is transient and deliberately NOT cached: caching it would disable
+// glyphs until process restart on one network blip.
+const repoHandleCache = new Map();
+/** Test-only: drop the memoized repo handles. */
+export function __clearRepoHandleCacheForTests() {
+    repoHandleCache.clear();
+}
+/** The `owner/name` for `repoRoot`, memoized. Returns null when the handle isn't a clean two-part
+ *  slug or `gh` failed — the caller then skips checks entirely and commits render unglyphed. */
+export async function resolveRepoHandle(repoRoot) {
+    const memo = repoHandleCache.get(repoRoot);
+    if (memo !== undefined)
+        return memo;
+    let handle;
+    try {
+        handle = parseOwnerName(await gh(repoRoot, ['repo', 'view', '--json', 'nameWithOwner', '--jq', '.nameWithOwner']));
+    }
+    catch {
+        // Transient — do NOT memoize, so the next thread retries.
+        return null;
+    }
+    repoHandleCache.set(repoRoot, handle); // includes the permanent negative
+    return handle;
+}
+/**
+ * Walk `/issues/{n}/timeline` under ONE shared time budget.
+ *
+ * `gh api --paginate` is not used here: it pages *"until there are no more pages of results"* and
+ * exposes no page-limit flag, so the only way to bound the walk is to hand-roll it. The cap that
+ * `paginateCounts` gets comes from being a JS cursor loop, not from a `gh` flag.
+ *
+ * The budget is a **total**, not a per-page allowance. `gh()` takes its timeout per invocation, so
+ * ten sequential spawns at the 15 s default would put the ceiling at 150 s — an order of magnitude
+ * worse than the single `--paginate` spawn this replaces. The loop tracks a deadline and passes
+ * each page whatever remains.
+ *
+ * Exported for unit tests; `run` is injected so the loop is testable without shelling out.
+ */
+export async function fetchTimelinePages(run, opts = {}) {
+    const maxPages = opts.maxPages ?? TIMELINE_MAX_PAGES;
+    const budgetMs = opts.budgetMs ?? TIMELINE_BUDGET_MS;
+    const minPageMs = opts.minPageMs ?? TIMELINE_MIN_PAGE_MS;
+    const now = opts.now ?? Date.now;
+    const deadline = now() + budgetMs;
+    const rows = [];
+    let stoppedShort = false;
+    let page = 1;
+    for (; page <= maxPages; page++) {
+        const remaining = deadline - now();
+        // Never spawn a page that cannot finish. A bare `remaining <= 0` guard catches only the exact
+        // boundary; the realistic case is 300 ms left, which spawns gh with a 300 ms timeout, throws,
+        // and looks indistinguishable from a real endpoint failure.
+        if (remaining < minPageMs) {
+            stoppedShort = true;
+            break;
+        }
+        let parsed;
+        try {
+            parsed = z.array(z.unknown()).parse(JSON.parse(await run(page, remaining)));
+        }
+        catch (err) {
+            // Page 1 rethrows so the caller's inner catch can decide whether substitution helps —
+            // nothing was fetched, so there is nothing to lose. A failure on any later page keeps the
+            // pages already in hand: discarding nine good pages to re-fetch comments-only is strictly
+            // worse than what the loop already holds.
+            if (page === 1)
+                throw err;
+            stoppedShort = true;
+            break;
+        }
+        rows.push(...parsed);
+        if (parsed.length < TIMELINE_PER_PAGE)
+            break; // short page — the real end of the timeline
+    }
+    if (page > maxPages)
+        stoppedShort = true; // fell out on the page cap
+    return { rows, stoppedShort };
+}
+/** SHAs per rollup query. Aliases resolve independently, so a chunk that fails costs only its own
+ *  glyphs — but an unbounded alias list would eventually blow the query size limit. */
+export const COMMIT_CHECKS_CHUNK = 50;
+/** One aliased `object(oid:)` per SHA. `oid` requires a FULL 40-char SHA in both literal and
+ *  variable form (`Could not coerce value "babda63" to GitObjectID`), which constrains fixtures
+ *  rather than production data — the timeline always supplies full SHAs. */
+function commitChecksQuery(shas) {
+    const aliases = shas
+        .map((sha, i) => `    c${i}: object(oid: "${sha}") { ... on Commit { statusCheckRollup { state } } }`)
+        .join('\n');
+    return `query ($owner: String!, $name: String!) {\n  repository(owner: $owner, name: $name) {\n${aliases}\n  }\n}`;
+}
+const ghCommitChecksSchema = z.record(z.string(), z.object({ statusCheckRollup: z.object({ state: z.string().nullish() }).nullish() }).nullish());
+/**
+ * Rolled-up CI state per commit SHA, as a `sha → checks` map.
+ *
+ * Batched and aliased so a 40-commit PR costs one subprocess, not forty. Verified against the live
+ * API: each alias resolves independently and an unknown SHA comes back `null` rather than erroring
+ * the batch, so partial results degrade cleanly.
+ *
+ * Degrades to an empty map on any failure — exactly as `fetchCommentCounts` does for counts. The
+ * caller then leaves `checks` **absent**, which the UI renders as no glyph. Exported for tests;
+ * `runGraphql` is injected so this is testable without shelling out.
+ */
+export async function fetchCommitChecks(runGraphql, owner, name, shas, chunkSize = COMMIT_CHECKS_CHUNK) {
+    const out = {};
+    if (shas.length === 0)
+        return out;
+    for (let i = 0; i < shas.length; i += chunkSize) {
+        const chunk = shas.slice(i, i + chunkSize);
+        try {
+            const raw = JSON.parse(await runGraphql(commitChecksQuery(chunk), { owner, name }));
+            const repository = ghCommitChecksSchema.parse(raw?.data?.repository ?? {});
+            chunk.forEach((sha, index) => {
+                const node = repository[`c${index}`];
+                if (!node)
+                    return; // unknown SHA → alias resolved null; leave `checks` absent
+                // Adapt the single rollup state into the array shape `rollupToChecks` expects, so the
+                // existing FAILURE/PENDING/SUCCESS vocabulary is reused rather than duplicated.
+                out[sha] = node.statusCheckRollup
+                    ? rollupToChecks([{ state: node.statusCheckRollup.state, status: null, conclusion: null }])
+                    : null; // no CI configured — distinct from absent
+            });
+        }
+        catch {
+            // A failed chunk costs only its own glyphs; the rest still resolve.
+        }
+    }
+    return out;
+}
+/** PR numbers per checks query. Aliases resolve independently (a failed chunk costs only its own
+ *  glyphs); bounded so an unbounded number list can't blow the query size limit. Also the route's
+ *  hard cap on how many PRs one request may ask about. */
+export const GH_CHECKS_MAX = 100;
+/** One aliased `pullRequest(number:)` per PR; the rolled-up CI state lives on the head commit. */
+function prChecksQuery(numbers) {
+    const aliases = numbers
+        .map((n, i) => `    p${i}: pullRequest(number: ${n}) { commits(last: 1) { nodes { commit { statusCheckRollup { state } } } } }`)
+        .join('\n');
+    return `query ($owner: String!, $name: String!) {\n  repository(owner: $owner, name: $name) {\n${aliases}\n  }\n}`;
+}
+const ghPrChecksSchema = z.record(z.string(), z
+    .object({
+    commits: z.object({
+        nodes: z.array(z.object({
+            commit: z.object({
+                statusCheckRollup: z.object({ state: z.string().nullish() }).nullish(),
+            }),
+        })),
+    }),
+})
+    .nullish());
+/**
+ * Rolled-up CI state per PR number, as a `number → glyph` map.
+ *
+ * Batched and aliased so a 100-PR window costs one subprocess, not a hundred. Each alias resolves
+ * independently and an unknown number comes back `null` (alias resolved null → left absent), so
+ * partial results degrade cleanly. Degrades to an empty map on any failure — exactly as
+ * `fetchCommitChecks` does. Exported for tests; `runGraphql` is injected so this is testable
+ * without shelling out.
+ */
+export async function fetchPrChecks(runGraphql, owner, name, numbers, chunkSize = GH_CHECKS_MAX) {
+    const out = {};
+    if (numbers.length === 0)
+        return out;
+    for (let i = 0; i < numbers.length; i += chunkSize) {
+        const chunk = numbers.slice(i, i + chunkSize);
+        try {
+            const raw = JSON.parse(await runGraphql(prChecksQuery(chunk), { owner, name }));
+            const repository = ghPrChecksSchema.parse(raw?.data?.repository ?? {});
+            chunk.forEach((number, index) => {
+                const node = repository[`p${index}`];
+                if (!node)
+                    return; // unknown PR → alias resolved null; leave the glyph absent
+                const rollup = node.commits.nodes[0]?.commit.statusCheckRollup;
+                // Adapt the single rollup state into the array shape `rollupToChecks` expects, reusing the
+                // FAILURE/PENDING/SUCCESS vocabulary rather than duplicating it.
+                out[number] = rollup
+                    ? rollupToChecks([{ state: rollup.state, status: null, conclusion: null }]) ?? null
+                    : null; // no CI configured — distinct from absent
+            });
+        }
+        catch {
+            // A failed chunk costs only its own glyphs; the rest still resolve.
+        }
+    }
+    return out;
+}
+// Per-PR checks cache: keyed `repoRoot␀number`, same 60 s TTL as the list cache but BOUNDED. Lets
+// a repeated visible-window hydration within a minute serve cached glyphs instead of re-querying.
+const checksCache = new Map();
+const CHECKS_CACHE_MAX = 500;
+/** Test hook — the per-PR checks cache would otherwise leak state across cases in one process. */
+export function __clearChecksCacheForTests() {
+    checksCache.clear();
+}
+/**
+ * Lazy checks glyphs for the given PR numbers (route-facing). Resolves the repo handle once,
+ * serves fresh cache entries, queries only the misses, and degrades to `{ available: false,
+ * reason }` when `gh` or the handle is unavailable — never a throw, never a 5xx (plan rule 7).
+ * Numbers are de-duplicated, validated, and capped at `GH_CHECKS_MAX`.
+ */
+export async function fetchGithubChecks(repoRoot, numbers) {
+    if (process.env.XEZ_DRY_RUN === '1')
+        return mockGithubChecks(numbers);
+    const wanted = [...new Set(numbers)].filter((n) => Number.isInteger(n) && n > 0).slice(0, GH_CHECKS_MAX);
+    const checks = {};
+    const misses = [];
+    const now = Date.now();
+    for (const n of wanted) {
+        const hit = checksCache.get(`${repoRoot}\0${n}`);
+        if (hit && now - hit.at < CACHE_MS)
+            checks[n] = hit.glyph;
+        else
+            misses.push(n);
+    }
+    if (misses.length === 0)
+        return { available: true, checks };
+    try {
+        const repoOut = await gh(repoRoot, ['repo', 'view', '--json', 'nameWithOwner', '--jq', '.nameWithOwner']);
+        const ownerName = parseOwnerName(repoOut);
+        if (!ownerName)
+            return { available: false, reason: 'repository handle unavailable' };
+        const runGraphql = (query, variables) => {
+            const args = ['api', 'graphql', '-f', `query=${query}`];
+            for (const [key, value] of Object.entries(variables))
+                args.push('-f', `${key}=${value}`);
+            return gh(repoRoot, args);
+        };
+        const fetched = await fetchPrChecks(runGraphql, ownerName.owner, ownerName.name, misses);
+        for (const n of misses) {
+            // Absent (unknown/closed PR) caches as `null` so a nonexistent number isn't re-queried.
+            const glyph = n in fetched ? fetched[n] : null;
+            checks[n] = glyph;
+            checksCache.set(`${repoRoot}\0${n}`, { at: now, glyph });
+        }
+        while (checksCache.size > CHECKS_CACHE_MAX) {
+            const oldest = checksCache.keys().next().value;
+            if (oldest === undefined)
+                break;
+            checksCache.delete(oldest);
+        }
+        return { available: true, checks };
+    }
+    catch (err) {
+        const message = err instanceof Error ? err.message : String(err);
+        return {
+            available: false,
+            reason: /ENOENT/.test(message)
+                ? 'gh CLI not found — install it and run `gh auth login`'
+                : firstLine(message),
+        };
+    }
+}
+/** XEZ_DRY_RUN=1 — glyphs straight from the mock catalog so the offline demo shows checks. */
+function mockGithubChecks(numbers) {
+    const byNumber = new Map(mockGithub().prs.map((p) => [p.number, (p.checks ?? null)]));
+    const checks = {};
+    for (const n of numbers)
+        checks[n] = byNumber.get(n) ?? null;
+    return { available: true, checks };
+}
+/** Numbers per kind in one ref-status query — the same bound, and for the same reasons, as
+ *  `GH_CHECKS_MAX`: aliases resolve independently, and the query size stays finite. Taken from the
+ *  contract rather than restated, because the cockpit caps its batches by the same number and a
+ *  client that guessed high would have every chip in a batch 400 instead of losing its tail. */
+export const GH_REF_STATUS_MAX = REFERENCE_STATUS_MAX;
+/** A requested reviewer, as either connection spells them. `login` covers `User` and `Bot`, `slug`
+ *  covers `Team`; `reviewerKey` folds them into one comparable string. */
+const reviewerRefSchema = z
+    .object({
+    __typename: z.string().nullish(),
+    login: z.string().nullish(),
+    slug: z.string().nullish(),
+})
+    .nullish();
+/** One reviewer as a comparable key, or `null` when GitHub named nobody we can match on — which
+ *  must never compare equal to another unnamed reviewer, hence `null` rather than a shared "". */
+function reviewerKey(ref) {
+    const name = ref?.login ?? ref?.slug;
+    return name ? `${ref?.__typename ?? '?'}:${name}` : null;
+}
+const ghRefStatusPrSchema = z
+    .object({
+    state: z.string(),
+    isDraft: z.boolean().nullish(),
+    reviewDecision: z.string().nullish(),
+    /** `MERGEABLE` | `CONFLICTING` | `UNKNOWN` — GitHub computes it in the background, so
+     *  `UNKNOWN` is normal on a PR that was just pushed and must never read as "clean". */
+    mergeable: z.string().nullish(),
+    commits: z
+        .object({
+        nodes: z.array(z.object({
+            commit: z.object({
+                committedDate: z.string().nullish(),
+                /** `totalCount` says whether the head is a merge; the first parent is the branch's
+                 *  previous tip, which is the newest commit that is actual WORK when it is. */
+                parents: z
+                    .object({
+                    totalCount: z.number(),
+                    nodes: z.array(z.object({ committedDate: z.string().nullish() }).nullish()).nullish(),
+                })
+                    .nullish(),
+                statusCheckRollup: z.object({ state: z.string().nullish() }).nullish(),
+            }),
+        })),
+    })
+        .nullish(),
+    reviews: z.object({ nodes: z.array(z.object({ submittedAt: z.string().nullish() })) }).nullish(),
+    /** Who is on the hook RIGHT NOW. The reviewers are carried, not just the count, because a
+     *  request's date has to be matched to a request that still stands — see `reviewRequestedAt`. */
+    reviewRequests: z
+        .object({
+        totalCount: z.number(),
+        nodes: z.array(z.object({ requestedReviewer: reviewerRefSchema }).nullish()).nullish(),
+    })
+        .nullish(),
+    timelineItems: z
+        .object({
+        nodes: z
+            .array(z.object({ createdAt: z.string().nullish(), requestedReviewer: reviewerRefSchema }).nullish())
+            .nullish(),
+    })
+        .nullish(),
+})
+    .nullish();
+/**
+ * When was the newest STILL-STANDING review request made?
+ *
+ * The two connections answer different halves and neither answers both: `reviewRequests` says who
+ * is on the hook right now but carries no date, while a `ReviewRequestedEvent` carries the date and
+ * survives the request being withdrawn. Reading the newest event on its own therefore dates a
+ * request that may no longer exist — and a request added after a review and then removed would make
+ * a live rejection read as answered, which is the exact bug the precedence above exists to fix.
+ * Matching the two by reviewer is what keeps the date attached to a request that is really there.
+ *
+ * `null` when nothing matches, which the precedence reads as an undated request and treats
+ * conservatively: the review stands rather than being dismissed on a guess.
+ */
+function standingReviewRequestedAt(requests, timeline) {
+    const standing = new Set();
+    for (const node of requests?.nodes ?? []) {
+        const key = reviewerKey(node?.requestedReviewer);
+        if (key)
+            standing.add(key);
+    }
+    if (standing.size === 0)
+        return null;
+    let newest = null;
+    for (const node of timeline?.nodes ?? []) {
+        if (!node?.createdAt)
+            continue;
+        const key = reviewerKey(node.requestedReviewer);
+        if (!key || !standing.has(key))
+            continue;
+        if (!newest || isAfter(node.createdAt, newest))
+            newest = node.createdAt;
+    }
+    return newest;
+}
+const ghRefStatusIssueSchema = z.object({ state: z.string(), stateReason: z.string().nullish() }).nullish();
+// The aliases hold two DIFFERENT shapes, so the record stays unvalidated here and each alias is
+// parsed by its own schema below. A union at this level would be wrong, not merely loose: zod
+// strips unknown keys, so a PR node matched by the issue arm would come back with `isDraft` and
+// `commits` silently removed.
+const ghRefStatusSchema = z.record(z.string(), z.unknown());
+/**
+ * One alias per NUMBER, asking `issueOrPullRequest` rather than `pullRequest`/`issue`.
+ *
+ * Issues and pull requests share one numbering space in a repository, so a number is exactly one
+ * of the two and asking which is a question the forge can answer — where asking `issue(number:)`
+ * about a pull request is a question with no answer, and GitHub says so with a NOT_FOUND *error*
+ * rather than a null. That mattered far more than it looks: `gh api graphql` exits non-zero the
+ * moment a response carries an `errors` array, so one mis-guessed kind used to fail the whole
+ * batch and report every reference in it as "not found" (see `refStatusGraphql`).
+ *
+ * It also fixes the reference whose kind the cockpit guessed wrong — `taskReferences` infers it
+ * from which field carried the number, and a bare `#774` can land in either — because the answer
+ * carries `__typename` and is filed under what the number REALLY is.
+ *
+ * `committedDate`, the head commit's `parents.totalCount` (`first: 0` — the COUNT is the whole
+ * question, so no parent is fetched) and the last CHANGES_REQUESTED review's `submittedAt` cost
+ * nothing extra, riding the same node, and are what let the precedence tell a review the author has
+ * already responded to from one still about the code on screen. The last `ReviewRequestedEvent` is
+ * asked for the same reason: `reviewRequests` says only THAT someone is on the hook, never since
+ * when, and the difference between a request made before the review and one made after it is the
+ * difference between a reviewer who has not looked yet and an author who has answered.
+ *
+ * `mergeable` rides it too, and is the reason the batch can answer "this one conflicts" without
+ * the per-PR probe `prMergeState` runs for the merge box. It is NOT folded into the status: see
+ * `conflicts` in the contract for why the two stay separate axes.
+ */
+function refStatusQuery(numbers) {
+    const aliases = numbers
+        .map((n, i) => `    r${i}: issueOrPullRequest(number: ${n}) { __typename ... on PullRequest { state isDraft reviewDecision mergeable commits(last: 1) { nodes { commit { committedDate parents(first: 1) { totalCount nodes { committedDate } } statusCheckRollup { state } } } } reviews(last: 1, states: CHANGES_REQUESTED) { nodes { submittedAt } } reviewRequests(first: 20) { totalCount nodes { requestedReviewer { __typename ... on User { login } ... on Bot { login } ... on Team { slug } } } } timelineItems(last: 20, itemTypes: [REVIEW_REQUESTED_EVENT]) { nodes { ... on ReviewRequestedEvent { createdAt requestedReviewer { __typename ... on User { login } ... on Bot { login } ... on Team { slug } } } } } } ... on Issue { state stateReason } }`)
+        .join('\n');
+    return `query ($owner: String!, $name: String!) {\n  repository(owner: $owner, name: $name) {\n${aliases}\n  }\n}`;
+}
+/**
+ * The one place a PR's signals collapse into a single word.
+ *
+ * The question the chip answers is "what is this waiting on RIGHT NOW", so the ranking is by
+ * freshness of the signal, not by how heavy a blocker it is:
+ *
+ * Read the ranking as **whose move is it**, which is the question a table is scanned for:
+ *
+ *  1. `merged` / `closed` — nobody's. Terminal, whatever checks or reviews say.
+ *  2. `draft` — the author's, and they have said so themselves.
+ *  3. `checks-pending` — the machine's. CI running means a commit was JUST pushed, the newest
+ *     thing that has happened to this PR, so it outranks a requested change unconditionally.
+ *  4. `changes-requested` — the AUTHOR's, and only while that is still true: the review must be
+ *     about the code that is there now, with no re-review already asked for.
+ *  5. `checks-failing` — the author's again. A reviewer cannot approve a red PR anyway.
+ *  6. `review-required` — the REVIEWER's: they have been asked, or the author has answered and
+ *     the merge is now blocked on someone coming back to look.
+ *  7. `ready` — open, not a draft, nothing failing, nothing running, nobody waited on.
+ *
+ * The subtle one is (4) → (6), and it is not a preference but a data finding. `reviewDecision`
+ * stays `CHANGES_REQUESTED` after the author has responded — GitHub does not clear it until a
+ * reviewer submits again — so on its own it points at the author forever. Two signals say the ball
+ * has moved back:
+ *
+ *  - **a review request made AFTER the review**, which is the author clicking re-request.
+ *    Authoritative, and observed live alongside a stale `CHANGES_REQUESTED` and an EMPTY
+ *    `latestReviews` — the case that has no other tell.
+ *  - **a non-merge commit newer than the review**, the fallback for an author who pushed without
+ *    clicking anything. Merges are excluded because GitHub's "Update branch" button writes one,
+ *    dated now, that answers nothing — the reflexive click on a stale PR must not clear a
+ *    rejection.
+ *
+ * The "after" in the first one is load-bearing, and its absence was a reported bug. A request that
+ * PREDATES the review is a reviewer who has not looked yet, and on a PR where several people were
+ * asked and one of them rejected it the others stay listed forever — so a bare
+ * `reviewRequests.totalCount > 0` reads a live "changes requested" as answered and hides it behind
+ * "waiting for review" (observed live: three reviewers asked at 10:28, changes requested
+ * the next day, one reviewer still pending).
+ *
+ * Either way the words change from "you owe edits" to "they owe a look", and so does the colour:
+ * danger is the author's move, info is the reviewer's.
+ *
+ * Both timestamps are optional and their ABSENCE is conservative: with no dates to compare and no
+ * re-request, a review counts as current, and the chip keeps pointing at the author.
+ *
+ * `reviewDecision` is null on a repo with no review policy, which is exactly why `ready` is not
+ * spelled "approved": on such a repo a green PR IS ready, and no approval will ever arrive — but a
+ * requested reviewer still moves it to `review-required`, because someone was explicitly asked.
+ */
+export function derivePrReferenceStatus(pr) {
+    const state = pr.state.toUpperCase();
+    if (state === 'MERGED')
+        return 'merged';
+    if (state === 'CLOSED')
+        return 'closed';
+    if (pr.isDraft)
+        return 'draft';
+    if (pr.checks === 'pending')
+        return 'checks-pending';
+    const decision = (pr.reviewDecision ?? '').toUpperCase();
+    const changesRequested = decision === 'CHANGES_REQUESTED';
+    // Has the author already answered the review — by asking for another look, or by pushing?
+    // A standing request counts as the ask only if it POSTDATES the review; one made before it is a
+    // reviewer who has not got to the PR yet, and on a PR where someone else rejected it that
+    // request would otherwise mask the rejection indefinitely. With no review date at all it still
+    // counts — that is the empty-`reviews` case above, where it is the only signal there is.
+    const reRequested = pr.reviewRequested === true && (!pr.changesRequestedAt || isAfter(pr.reviewRequestedAt, pr.changesRequestedAt));
+    // A push counts as the answer, judged by the newest commit that is actual WORK. GitHub's "Update
+    // branch" button (and this cockpit's own "Resolve conflicts") writes `Merge branch 'main' into
+    // <branch>` dated NOW, newer than any review while addressing none of it: the click people make
+    // reflexively on a stale PR must not wipe a rejection off the chip. Two parents is what tells
+    // that commit apart from work.
+    //
+    // Which is why a merge is not simply DISQUALIFYING: it is transparent. Reading only the head
+    // would let a merge landing on top of a genuine fix erase that fix's answer and flip the chip
+    // back to red, blaming an author who already responded — the same misattribution this whole
+    // function exists to prevent, just pointed the other way. The merge's FIRST parent is the
+    // branch's previous tip, so it carries the date of the work the merge sat on top of.
+    const workCommittedAt = (pr.headParentCount ?? 1) < 2 ? pr.headCommittedAt : pr.headFirstParentCommittedAt;
+    const pushed = isAfter(workCommittedAt, pr.changesRequestedAt);
+    const answered = reRequested || pushed;
+    if (changesRequested && !answered)
+        return 'changes-requested';
+    if (pr.checks === 'failing')
+        return 'checks-failing';
+    // `APPROVED` is the forge saying the review requirement IS MET, and it outranks a pending
+    // request: a reviewer left on the list after someone else approved is a courtesy ask, not an
+    // unmet gate. (A repo needing two approvals reports `REVIEW_REQUIRED` until it has both, so
+    // `APPROVED` never arrives early.) Without this, an approved, green, mergeable pull request
+    // reads "waiting for review" for as long as anyone stays listed — which is indefinitely.
+    if (decision === 'APPROVED')
+        return 'ready';
+    if (changesRequested || decision === 'REVIEW_REQUIRED' || pr.reviewRequested === true) {
+        return 'review-required';
+    }
+    return 'ready';
+}
+export function mergeabilityOf(state, mergeable) {
+    if (state.toUpperCase() !== 'OPEN')
+        return undefined;
+    switch (mergeable?.toUpperCase()) {
+        case 'MERGEABLE':
+            return 'mergeable';
+        case 'CONFLICTING':
+            return 'conflicting';
+        default:
+            // Includes a field GitHub omitted entirely: not being told is not being told.
+            return 'unknown';
+    }
+}
+/** Did `later` happen AFTER `earlier` — a commit, or a re-request, landing past the review?
+ *  Unparseable or missing dates answer `false`, which is the conservative direction for both
+ *  callers: they only ever use a `true` to demote a review, so no answer must keep the review
+ *  current rather than silently dismiss one. */
+function isAfter(later, earlier) {
+    const a = later ? Date.parse(later) : NaN;
+    const b = earlier ? Date.parse(earlier) : NaN;
+    return Number.isFinite(a) && Number.isFinite(b) && a > b;
+}
+/**
+ * An issue's two signals as one word. `NOT_PLANNED` is kept apart from `completed` because they
+ * are opposite outcomes — "we did it" vs "we won't" — and a task whose issue was declined must
+ * not read as a task that landed.
+ */
+export function deriveIssueReferenceStatus(issue) {
+    if (issue.state.toUpperCase() !== 'CLOSED')
+        return 'open';
+    return (issue.stateReason ?? '').toUpperCase() === 'NOT_PLANNED' ? 'not-planned' : 'completed';
+}
+/**
+ * Status per NUMBER, resolved to whatever that number actually is.
+ *
+ * Batched and aliased like `fetchPrChecks`: one subprocess per chunk, each alias resolving
+ * independently, and a number the forge does not have simply staying absent from `resolved` (its
+ * chip then renders neutral, as it did before this seam existed). A failed chunk costs only its
+ * own numbers, and says so rather than letting them look absent. Exported for tests; `runGraphql`
+ * is injected so this is testable without shelling out.
+ */
+export async function fetchRefStatuses(runGraphql, owner, name, numbers, chunkSize = GH_REF_STATUS_MAX) {
+    const out = { resolved: {}, failed: [] };
+    if (numbers.length === 0)
+        return out;
+    for (let i = 0; i < numbers.length; i += chunkSize) {
+        const chunk = numbers.slice(i, i + chunkSize);
+        try {
+            const raw = JSON.parse(await runGraphql(refStatusQuery(chunk), { owner, name }));
+            const repository = ghRefStatusSchema.parse(raw?.data?.repository ?? {});
+            chunk.forEach((number, index) => {
+                const node = repository[`r${index}`];
+                // Absent alias → the number is not in this repository at all. Left out of the map, which
+                // is what the route reports as "not found" and the chip paints as neutral.
+                if (!node)
+                    return;
+                if (node.__typename === 'PullRequest') {
+                    const pr = ghRefStatusPrSchema.parse(node);
+                    if (!pr)
+                        return;
+                    const head = pr.commits?.nodes[0]?.commit;
+                    const rollup = head?.statusCheckRollup;
+                    const mergeability = mergeabilityOf(pr.state, pr.mergeable);
+                    out.resolved[number] = {
+                        kind: 'pr',
+                        status: derivePrReferenceStatus({
+                            state: pr.state,
+                            isDraft: pr.isDraft,
+                            reviewDecision: pr.reviewDecision,
+                            // Adapt the single rollup state into the array shape `rollupToChecks` expects,
+                            // reusing the FAILURE/PENDING/SUCCESS vocabulary rather than duplicating it.
+                            checks: rollup ? rollupToChecks([{ state: rollup.state, status: null, conclusion: null }]) ?? null : null,
+                            headCommittedAt: head?.committedDate,
+                            // Two parents = "Update branch", which is dated now and answers nothing on its own —
+                            // so the first parent's date, the work it sat on top of, is carried with it.
+                            headParentCount: head?.parents?.totalCount,
+                            headFirstParentCommittedAt: head?.parents?.nodes?.[0]?.committedDate,
+                            // `reviews(last: 1, states: CHANGES_REQUESTED)` — the timestamp only. WHETHER changes
+                            // are requested stays `reviewDecision`'s answer, which is the one that accounts for
+                            // dismissed and superseded reviews.
+                            changesRequestedAt: pr.reviews?.nodes[0]?.submittedAt,
+                            reviewRequested: (pr.reviewRequests?.totalCount ?? 0) > 0,
+                            // WHEN that standing request was made. `reviewRequests` carries no date of its own,
+                            // and without one an old request looks exactly like a re-request.
+                            reviewRequestedAt: standingReviewRequestedAt(pr.reviewRequests, pr.timelineItems),
+                        }),
+                        // The tri-state, not a boolean: `unknown` has to survive as far as the cache, which
+                        // is what decides to ask again in seconds rather than in a minute.
+                        ...(mergeability ? { mergeable: mergeability } : {}),
+                    };
+                }
+                else if (node.__typename === 'Issue') {
+                    const issue = ghRefStatusIssueSchema.parse(node);
+                    if (!issue)
+                        return;
+                    out.resolved[number] = { kind: 'issue', status: deriveIssueReferenceStatus(issue) };
+                }
+            });
+        }
+        catch (err) {
+            // A failed chunk costs only its own numbers; the rest still resolve. They are recorded as
+            // FAILED rather than left absent, so nothing downstream mistakes them for "no such number".
+            out.failed.push(...chunk);
+            out.reason ??= firstLine(err instanceof Error ? err.message : String(err));
+        }
+    }
+    return out;
+}
+// Per-reference cache: keyed `repoRoot␀number` — by NUMBER, not by kind, because the kind is now
+// something the forge answers rather than something the caller asserts. Same 60 s TTL and bounded
+// shape as the checks cache; `null` is a cached "this repository has no such number", so a
+// transcript-scraped number from another repo is not re-queried on every table repaint.
+//
+// `unknownSince` is when this reference FIRST came back with its mergeability still being
+// computed, carried across refreshes so the fast recheck below is bounded to that first window
+// rather than restarting on every answer that is still `unknown`.
+const refStatusCache = new Map();
+const REF_STATUS_CACHE_MAX = 500;
+/** Test-only: drop the per-reference cache so cases don't leak state into each other. */
+export function __clearRefStatusCacheForTests() {
+    refStatusCache.clear();
+}
+/** Test-only: warm the cache the way the lazy route would have, so a reader can be tested
+ *  without a forge behind it. */
+export function __seedRefStatusCacheForTests(repoRoot, entries) {
+    for (const [number, resolved] of entries) {
+        refStatusCache.set(refStatusKey(repoRoot, number), { at: Date.now(), resolved });
+    }
+}
+/**
+ * Forget what we knew about one reference, so the next read asks GitHub again.
+ *
+ * Called where xezar itself CHANGES a pull request — it merges one, it opens one — because those
+ * are the only forge changes this process can know about without asking. Everything else has to
+ * be polled (GitHub cannot push to a cockpit with no public endpoint), but waiting out a TTL to
+ * notice our own merge is a self-inflicted staleness: for up to a minute every chip would keep
+ * showing the pre-merge status of a pull request the user watched this server merge.
+ *
+ * Deleting rather than overwriting with a guessed `merged`: the forge is the authority on what a
+ * reference is, and a mutation that reports success is still not the same as having read the
+ * result. The next reader pays one query and gets the truth — after which the answer is `merged`,
+ * `recheckAfterMs` goes null, and the cockpit stops polling that batch entirely. Invalidating here
+ * therefore REDUCES long-run traffic rather than adding to it.
+ */
+export function forgetRefStatus(repoRoot, number) {
+    refStatusCache.delete(refStatusKey(repoRoot, number));
+}
+/**
+ * Everything the cache ALREADY knows about these numbers. Never spawns `gh`, never awaits.
+ *
+ * This is what lets a status ride along with the rows that carry the references, instead of the
+ * cockpit fetching it separately a moment later: the run index reads whatever is warm and ships
+ * it, and a cold entry is simply absent — the lazy `/github/ref-status` route stays the thing that
+ * actually goes and asks.
+ *
+ * Because it cannot cost anything, the caller may pass a SUPERSET of the numbers it will really
+ * display. That matters: deciding which of a run's references a chip shows is the cockpit's rule
+ * (#407, #526), deliberately not duplicated server-side, and a cache read does not need to know —
+ * it can look up every number a run mentions and let the client pick.
+ */
+export function readCachedRefStatuses(repoRoot, numbers) {
+    const out = { prs: {}, issues: {} };
+    const now = Date.now();
+    for (const number of new Set(numbers)) {
+        const hit = refStatusCache.get(refStatusKey(repoRoot, number));
+        if (!hit || !hit.resolved || now - hit.at >= refStatusTtl(hit.resolved, hit.unknownSince, now))
+            continue;
+        out[hit.resolved.kind === 'pr' ? 'prs' : 'issues'][number] = hit.resolved.status;
+    }
+    return out;
+}
+/** The `#N` in a forge URL — `…/pull/774` → 774. Null when the tail is not a number, so a URL
+ *  shape we do not recognise invalidates nothing rather than inventing a key. */
+export function refNumberFromUrl(url) {
+    const last = /\/(\d+)\/?$/.exec(url.trim());
+    const parsed = last ? Number(last[1]) : Number.NaN;
+    return Number.isInteger(parsed) && parsed > 0 ? parsed : null;
+}
+/** A closed issue or an abandoned PR can be REOPENED, so this is long rather than forever — but
+ *  it is the rare event, and re-asking a hundred settled references every minute to catch it is
+ *  the wrong trade. */
+const REF_STATUS_CLOSED_TTL = 10 * 60_000;
+/** A merged pull request is merged forever: GitHub has no un-merge. Capped at a day only so a
+ *  long-lived server eventually re-reads rather than trusting a value from another era. */
+const REF_STATUS_MERGED_TTL = 24 * 60 * 60_000;
+/**
+ * How long a cached answer stays fresh — by how changeable that answer IS.
+ *
+ * One TTL for everything gets both ends wrong: it re-asks about a merged PR (which cannot change)
+ * every minute, and it is the only thing standing between a running CI job and a stale chip. What
+ * a reader wants rechecked is precisely what is still moving.
+ *
+ * A number the repository does not have keeps the short TTL: it is usually a wrong number, but it
+ * is also what a reference to a not-yet-created PR looks like, and re-asking is cheap.
+ */
+function refStatusTtl(entry, unknownSince, now = Date.now()) {
+    if (!entry)
+        return CACHE_MS;
+    // Mergeability GitHub has not finished computing is not an answer to cache for a minute. It is
+    // the normal reply for the first seconds after a push, and holding it that long is what let a
+    // conflicting pull request read "Ready to merge" until the page was reloaded. Ask again in
+    // seconds instead — and only while it is still plausibly being computed, so a repository that
+    // answers `UNKNOWN` indefinitely settles back to the ordinary cadence rather than spawning `gh`
+    // every few seconds forever.
+    if (entry.mergeable === 'unknown' &&
+        unknownSince !== undefined &&
+        now - unknownSince < MERGEABILITY_UNKNOWN_WINDOW_MS) {
+        return MERGEABILITY_UNKNOWN_TTL_MS;
+    }
+    switch (entry.status) {
+        case 'merged':
+            return REF_STATUS_MERGED_TTL;
+        case 'closed':
+        case 'completed':
+        case 'not-planned':
+            return REF_STATUS_CLOSED_TTL;
+        default:
+            return CACHE_MS;
+    }
+}
+/** How long a status can be trusted to stay put — `null` when it can never change again. The
+ *  cadence half of `refStatusTtl`, and deliberately the same function: a value the cache would
+ *  still be serving is a value there is no point asking for, and a value it would NOT serve —
+ *  mergeability still being computed — is one the cockpit should come back for just as soon. */
+function refStatusRecheckAfter(entry, unknownSince, now = Date.now()) {
+    if (entry?.status === 'merged')
+        return null; // GitHub has no un-merge
+    return refStatusTtl(entry, unknownSince, now);
+}
+/** How long the WHOLE answer holds — the soonest any single reference in it could differ. `null`
+ *  only when every one of them is immutable, which is what tells the cockpit to stop scheduling.
+ *  Taking the per-reference values rather than the entries, because one of them may be on the fast
+ *  mergeability cadence and the batch has to travel at the speed of its most impatient member. */
+function batchRecheckAfter(rechecks) {
+    let soonest = null;
+    for (const after of rechecks) {
+        if (after === null)
+            continue;
+        soonest = soonest === null ? after : Math.min(soonest, after);
+    }
+    return soonest;
+}
+/**
+ * How long a still-computing mergeability holds, and for how long that fast cadence applies.
+ *
+ * Five seconds because that is the shape of the thing being waited for: GitHub kicks off the
+ * merge-base computation when asked and usually has it by the next request. Bounded to a minute
+ * because a value that is STILL unknown after that is not a computation in flight any more — it is
+ * a repository that will not answer, and re-asking it every five seconds forever costs a `gh`
+ * subprocess a second for nothing.
+ */
+const MERGEABILITY_UNKNOWN_TTL_MS = 5_000;
+const MERGEABILITY_UNKNOWN_WINDOW_MS = 60_000;
+/** A forge that could not be reached is worth retrying, and worth not hammering: a workspace with
+ *  no `gh` installed would otherwise spawn a subprocess a minute, forever, to be told the same
+ *  thing. Five minutes is the same order as the cockpit's own reconnect cadence. */
+const REF_STATUS_RETRY_MS = 5 * 60_000;
+/**
+ * GraphQL through `gh`, tolerating a PARTIALLY failed response.
+ *
+ * `gh api graphql` exits non-zero whenever the reply carries an `errors` array — even when `data`
+ * is fully populated for every alias that DID resolve. With one alias per reference that is not an
+ * edge case, it is the normal case: a single number that no longer exists (or never did, having
+ * been scraped from a transcript that named another repository) makes GitHub answer
+ * `{data: {...everything else...}, errors: [NOT_FOUND]}` and `gh` exit 1.
+ *
+ * `execFile` rejects on a non-zero exit, so that used to throw away a whole batch's worth of
+ * perfectly good statuses and report every reference in it as "not found" — including, in the bug
+ * that produced this function, an open pull request in the project's own repository.
+ *
+ * So: a non-zero exit whose stdout still carries a usable `data.repository` is a partial success
+ * and is used as-is. Anything else — no stdout, unparseable stdout, or a null `repository`, which
+ * means the repo handle itself did not resolve — rethrows, so a real failure still degrades to
+ * `{available: false}` instead of masquerading as "none of these exist".
+ */
+function refStatusGraphql(repoRoot) {
+    return async (query, variables) => {
+        const args = ['api', 'graphql', '-f', `query=${query}`];
+        for (const [key, value] of Object.entries(variables))
+            args.push('-f', `${key}=${value}`);
+        try {
+            return await gh(repoRoot, args);
+        }
+        catch (err) {
+            const stdout = err.stdout;
+            if (typeof stdout === 'string' && hasResolvedRepository(stdout))
+                return stdout;
+            throw err;
+        }
+    };
+}
+/**
+ * The repo handle, memoized in the same map `resolveRepoHandle` uses — but rethrowing instead of
+ * answering `null`.
+ *
+ * The memo is the point: without it every recheck tick spawned a second subprocess to re-learn an
+ * `owner/name` that changes approximately never, doubling the cost of the one query that actually
+ * carries information. The difference from `resolveRepoHandle` is the failure: this route turns a
+ * `gh` error into the payload's `reason` — "gh CLI not found — install it and run `gh auth login`"
+ * is what the chip's tooltip now shows a user — and a `null` would erase which failure it was.
+ */
+async function resolveRepoHandleStrict(repoRoot) {
+    const memo = repoHandleCache.get(repoRoot);
+    if (memo !== undefined)
+        return memo;
+    // A throw here is transient and deliberately NOT memoized, exactly as in `resolveRepoHandle`.
+    const handle = parseOwnerName(await gh(repoRoot, ['repo', 'view', '--json', 'nameWithOwner', '--jq', '.nameWithOwner']));
+    repoHandleCache.set(repoRoot, handle); // includes the permanent negative
+    return handle;
+}
+/** Is this a reply we can still read aliases out of? `repository: null` says the handle did not
+ *  resolve, which is a real failure and must not be read as "the numbers are all missing". */
+function hasResolvedRepository(stdout) {
+    try {
+        const parsed = JSON.parse(stdout);
+        const repository = parsed?.data?.repository;
+        return typeof repository === 'object' && repository !== null;
+    }
+    catch {
+        return false;
+    }
+}
+/**
+ * Route-facing reference status. Resolves the repo handle once, serves fresh cache entries,
+ * queries only the misses, and degrades to `{ available: false, reason }` when `gh` or the handle
+ * is unavailable — never a throw, never a 5xx.
+ *
+ * The two request lists are merged into ONE set of numbers: issues and pull requests share a
+ * repository's numbering space, so a number is one thing and asking about it twice would be asking
+ * the same question twice. What comes back is filed by what each number turned out to BE, which is
+ * why a chip whose kind the cockpit guessed wrong still gets the right status.
+ */
+export async function fetchGithubRefStatus(repoRoot, input) {
+    const asPrs = sanitizeRefNumbers(input.prs);
+    const asIssues = sanitizeRefNumbers(input.issues);
+    if (process.env.XEZ_DRY_RUN === '1')
+        return mockGithubRefStatus(asPrs, asIssues);
+    const wanted = [...new Set([...asPrs, ...asIssues])];
+    const resolved = { prs: {}, issues: {} };
+    // How soon each reference in the answer could differ — what the batch's cadence is the minimum
+    // of. Per reference rather than per batch because mergeability still being computed is worth
+    // coming back for in seconds while everything else holds for a minute.
+    const rechecks = [];
+    // The second axis, and a list rather than a map because it is nearly always empty: only the
+    // pull requests the forge actively called CONFLICTING are named (see `mergeabilityOf`).
+    const conflicts = [];
+    const file = (number, entry, unknownSince) => {
+        rechecks.push(refStatusRecheckAfter(entry, unknownSince));
+        if (!entry)
+            return;
+        resolved[entry.kind === 'pr' ? 'prs' : 'issues'][number] = entry.status;
+        if (entry.mergeable === 'conflicting')
+            conflicts.push(number);
+    };
+    const misses = [];
+    const now = Date.now();
+    for (const n of wanted) {
+        const hit = refStatusCache.get(refStatusKey(repoRoot, n));
+        if (!hit || now - hit.at >= refStatusTtl(hit.resolved, hit.unknownSince, now))
+            misses.push(n);
+        else
+            file(n, hit.resolved, hit.unknownSince);
+    }
+    if (misses.length === 0) {
+        return {
+            available: true,
+            prs: resolved.prs,
+            issues: resolved.issues,
+            conflicts,
+            recheckAfterMs: batchRecheckAfter(rechecks),
+        };
+    }
+    try {
+        const ownerName = await resolveRepoHandleStrict(repoRoot);
+        if (!ownerName) {
+            return { available: false, reason: 'repository handle unavailable', recheckAfterMs: REF_STATUS_RETRY_MS };
+        }
+        const batch = await fetchRefStatuses(refStatusGraphql(repoRoot), ownerName.owner, ownerName.name, misses);
+        const failed = new Set(batch.failed);
+        // Stamped when the answer ARRIVED, not when the request was assembled: `now` above predates
+        // the round trip, and dating an entry by it would age a slow query's results by its own
+        // duration — shortening the TTL of exactly the answers that cost the most to get.
+        const storedAt = Date.now();
+        for (const n of misses) {
+            // A number we could not ask about is NOT cached: caching it would pin "this repository has
+            // no such number" for a minute on the strength of a network blip.
+            if (failed.has(n))
+                continue;
+            const entry = batch.resolved[n] ?? null;
+            // Kept from the previous answer, not restarted: the fast cadence is bounded from when this
+            // reference FIRST came back still-computing, so a forge that never resolves it cannot hold
+            // the batch on a five-second poll indefinitely.
+            const unknownSince = entry?.mergeable === 'unknown'
+                ? (refStatusCache.get(refStatusKey(repoRoot, n))?.unknownSince ?? storedAt)
+                : undefined;
+            file(n, entry, unknownSince);
+            refStatusCache.set(refStatusKey(repoRoot, n), {
+                at: storedAt,
+                resolved: entry,
+                ...(unknownSince === undefined ? {} : { unknownSince }),
+            });
+        }
+        while (refStatusCache.size > REF_STATUS_CACHE_MAX) {
+            const oldest = refStatusCache.keys().next().value;
+            if (oldest === undefined)
+                break;
+            refStatusCache.delete(oldest);
+        }
+        // Anything unasked makes the whole answer `unavailable`, deliberately. The alternative is a
+        // payload where a number we could not reach is indistinguishable from one that does not exist,
+        // and the cockpit would paint "not found on this repository" over a perfectly good PR — the
+        // exact defect this route was reported for. The successes are cached either way, so the next
+        // request costs only the numbers that failed and usually answers in full.
+        if (failed.size > 0) {
+            return {
+                available: false,
+                reason: batch.reason ?? 'GitHub could not be reached',
+                recheckAfterMs: REF_STATUS_RETRY_MS,
+            };
+        }
+        return {
+            available: true,
+            prs: resolved.prs,
+            issues: resolved.issues,
+            conflicts,
+            recheckAfterMs: batchRecheckAfter(rechecks),
+        };
+    }
+    catch (err) {
+        const message = err instanceof Error ? err.message : String(err);
+        return {
+            available: false,
+            reason: /ENOENT/.test(message)
+                ? 'gh CLI not found — install it and run `gh auth login`'
+                : firstLine(message),
+            recheckAfterMs: REF_STATUS_RETRY_MS,
+        };
+    }
+}
+/** NUL separator, as everywhere else here: two projects each having a #42 must not collide. */
+function refStatusKey(repoRoot, number) {
+    return `${repoRoot}\0#${number}`;
+}
+function sanitizeRefNumbers(numbers) {
+    return [...new Set(numbers ?? [])].filter((n) => Number.isInteger(n) && n > 0).slice(0, GH_REF_STATUS_MAX);
+}
+/** XEZ_DRY_RUN=1 — statuses derived from the mock catalog so the offline demo paints real chips. */
+function mockGithubRefStatus(prs, issues) {
+    const catalog = mockGithub();
+    const byPr = new Map(catalog.prs.map((p) => [p.number, p]));
+    const byIssue = new Set(catalog.issues.map((i) => i.number));
+    const out = { available: true, prs: {}, issues: {}, recheckAfterMs: CACHE_MS };
+    for (const n of prs) {
+        const pr = byPr.get(n);
+        if (pr) {
+            out.prs[n] = derivePrReferenceStatus({
+                state: 'OPEN',
+                isDraft: pr.isDraft,
+                reviewDecision: null,
+                checks: (pr.checks ?? null),
+            });
+        }
+    }
+    for (const n of issues)
+        if (byIssue.has(n))
+            out.issues[n] = 'open';
+    return out;
+}
+/**
+ * The conversation thread for one issue/PR, lazily. `{owner}`/`{repo}` in the gh api paths are
+ * filled from the worktree's remote by gh itself, so no extra handle lookup. Everything degrades:
+ * gh missing/offline → `{ available: false, reason }`, a 404 → a "not found" hint — never a throw.
+ *
+ * Since #525 the thread is sourced from `/issues/{n}/timeline`, which returns comments AND events
+ * in one stream: `commented` rows go through the unchanged `normalizeComments`, the rest through
+ * `normalizeEvents`. `comments[]` therefore keeps its exact pre-#525 shape, contents and cap
+ * (BACKWARD_COMPATIBILITY.md §2) — see the top-up below for the one case that needed defending.
+ */
+export async function fetchGithubComments(repoRoot, kind, number, refresh = false) {
+    if (process.env.XEZ_DRY_RUN === '1')
+        return mockGithubComments(kind);
+    // NUL separator: cannot appear in a filesystem path, so roots can never alias.
+    const key = `${repoRoot}\0${kind}#${number}`;
+    const hit = commentsCache.get(key);
+    if (!refresh && hit && Date.now() - hit.at < CACHE_MS)
+        return hit.data;
+    // PR conversation comments live on the issues endpoint too — always use it for the body thread.
+    const legacyComments = () => gh(repoRoot, ['api', `repos/{owner}/{repo}/issues/${number}/comments`, '--paginate']);
+    try {
+        let commentRows = [];
+        let events;
+        let eventsTruncated = false;
+        let stoppedShort = false;
+        try {
+            const pages = await fetchTimelinePages((page, timeoutMs) => gh(repoRoot, [
+                'api',
+                '-H',
+                'Accept: application/vnd.github+json',
+                `repos/{owner}/{repo}/issues/${number}/timeline?per_page=${TIMELINE_PER_PAGE}&page=${page}`,
+            ], timeoutMs));
+            stoppedShort = pages.stoppedShort;
+            commentRows = pages.rows.filter((r) => r?.event === 'commented');
+            const normalized = normalizeEvents(pages.rows);
+            events = normalized.events;
+            eventsTruncated = normalized.truncated;
+            // Comments top-up. The two ENTRY caps are independent, but the FETCH budget is not: today's
+            // call is an unbounded --paginate over a comments-only endpoint, so every comment is fetched
+            // and mergeThread picks the oldest 200 from the complete set. Under the timeline those same
+            // 200 slots are filled from at most 1000 rows in which events compete with comments — so on
+            // a 1500-row thread with 250 interleaved comments, comments[] would return ~167 where today
+            // it returns 200. Same §2 defect class as a combined entry cap, arriving via the source set.
+            //
+            // The trigger deliberately over-fires: it cannot distinguish "comments were cut off" from
+            // "this thread just has few comments", because the second is only knowable by fetching them.
+            // So on an event-heavy thread with 30 comments it re-fetches 30 complete comments. Accepted
+            // — it fires only past ~1000 timeline rows, behind the 60 s LRU, and the alternative is a §2
+            // regression. In the other direction the threshold is provably sound: with ≥200 commented
+            // rows already in the oldest-first prefix, mergeThread's oldest-200 cut lies inside it.
+            if (stoppedShort && commentRows.length < THREAD_ENTRY_CAP) {
+                // Its OWN nested catch. The inner handler's remedy is the fallback — which is this very
+                // call — and the outer handler returns { available: false, comments: [] }, emptying a
+                // thread that was about to render. So a thrown top-up is swallowed: keep the commented
+                // rows the timeline already returned and carry on. That is at worst the short list the
+                // safeguard existed to avoid, never worse than not having attempted it.
+                try {
+                    commentRows = z.array(z.unknown()).parse(JSON.parse(await legacyComments()));
+                }
+                catch {
+                    // keep the timeline's own commented rows
+                }
+            }
+        }
+        catch (timelineErr) {
+            // Scoped INSIDE the existing outer catch on purpose: the outer handler's /404|not found/i
+            // branch would otherwise turn a timeline 404 into an empty thread. ENOENT is the one failure
+            // the fallback cannot rescue — nothing will work, and a second spawn fails identically.
+            const message = timelineErr instanceof Error ? timelineErr.message : String(timelineErr);
+            if (/ENOENT/.test(message))
+                throw timelineErr;
+            // Every other endpoint-level failure substitutes the legacy comments call. It is a
+            // substitution, not a retry — a different endpoint, which typically still answers. (A 403
+            // attaches to the token rather than the endpoint, so it cannot succeed either; not
+            // special-cased, since rate-limit replies are immediate and it costs one fast spawn.)
+            commentRows = z.array(z.unknown()).parse(JSON.parse(await legacyComments()));
+            events = undefined;
+        }
+        // Per-commit CI (#525 Phase 2). One extra subprocess per opened thread that contains commits,
+        // behind the same 60 s LRU — a per-thread-open cost, not per-render. Every failure path here
+        // leaves `checks` ABSENT rather than null, so commits simply render unglyphed: the fetch
+        // degrades to "no data" and the render decides what absence looks like.
+        const commitShas = (events ?? []).flatMap((e) => (e.kind === 'committed' && e.sha ? [e.sha] : []));
+        if (commitShas.length > 0) {
+            const handle = await resolveRepoHandle(repoRoot);
+            if (handle) {
+                const runGraphql = (query, variables) => {
+                    const args = ['api', 'graphql', '-f', `query=${query}`];
+                    for (const [k, v] of Object.entries(variables))
+                        args.push('-f', `${k}=${v}`);
+                    return gh(repoRoot, args);
+                };
+                const checks = await fetchCommitChecks(runGraphql, handle.owner, handle.name, commitShas);
+                for (const event of events ?? []) {
+                    if (event.kind !== 'committed' || !event.sha)
+                        continue;
+                    if (event.sha in checks)
+                        event.checks = checks[event.sha];
+                }
+            }
+        }
+        const parts = [normalizeComments(commentRows)];
+        if (kind === 'pr') {
+            const reviewsOut = await gh(repoRoot, ['api', `repos/{owner}/{repo}/pulls/${number}/reviews`, '--paginate']);
+            parts.push(normalizeReviews(JSON.parse(reviewsOut)));
+        }
+        const { comments, truncated } = mergeThread(parts);
+        const data = {
+            available: true,
+            comments,
+            // OR-folded exactly as before, so the pre-existing >200-comments trigger is preserved
+            // rather than replaced.
+            truncated: truncated || eventsTruncated || stoppedShort || undefined,
+        };
+        if (events)
+            data.events = events;
+        cacheComments(key, data);
+        return data;
+    }
+    catch (err) {
+        const message = err instanceof Error ? err.message : String(err);
+        const reason = /ENOENT/.test(message)
+            ? 'gh CLI not found — install it and run `gh auth login`'
+            : /404|not found/i.test(message)
+                ? 'not found on GitHub — it may be closed or deleted'
+                : firstLine(message);
+        return { available: false, reason, comments: [] };
+    }
+}
+/** XEZ_DRY_RUN=1 — a small fixed thread (one image-bearing comment, plus a review for PRs) so
+ *  the whole feature is demoable and e2e-testable offline. */
+function mockGithubComments(kind) {
+    const base = Date.now() - 3_600_000;
+    const at = (offset) => new Date(base + offset).toISOString();
+    const comments = [
+        {
+            id: 1,
+            author: 'ada',
+            avatarUrl: 'https://avatars.githubusercontent.com/u/1?v=4',
+            createdAt: at(0),
+            body: 'Thanks for the report — I can reproduce. Which browser were you on?\n\n```\nchrome 126, macOS\n```',
+            kind: 'comment',
+            url: 'https://github.com/mock/repo/issues/1#issuecomment-1',
+        },
+        {
+            id: 2,
+            author: 'lin',
+            createdAt: at(600_000),
+            // An inline image, so the dry-run demo exercises the comment renderer's image path.
+            // It points at this app's OWN asset rather than a stranger's profile photo: this mock is
+            // what a public demo and every README screenshot show, and a real person's likeness has
+            // no business being either.
+            body: 'Here is the screen I attached:\n\n![attachment](/xezar.svg)',
+            kind: 'comment',
+            url: 'https://github.com/mock/repo/issues/1#issuecomment-2',
+        },
+    ];
+    if (kind === 'pr') {
+        comments.push({
+            id: 3,
+            author: 'grace',
+            avatarUrl: 'https://avatars.githubusercontent.com/u/3?v=4',
+            createdAt: at(1_200_000),
+            body: 'Looks good overall — please add a regression test before this lands.',
+            kind: 'review',
+            reviewState: 'changes_requested',
+            url: 'https://github.com/mock/repo/pull/1#pullrequestreview-3',
+        });
+    }
+    // Timeline events (#525) so the whole feature is demoable and e2e-testable offline. Deliberately
+    // covers the cases that are easy to get wrong rather than one of each: a multi-commit run by ONE
+    // author (exercises the client-side grouping) with MIXED check states (passing/failing/pending
+    // plus one `null` = no CI configured), a label change, a cross-reference, and — for PRs — a
+    // merge. SHAs are full 40-char because the rollup query's `oid` rejects abbreviated ones, and a
+    // fixture that cheated there would not survive being pasted into a real query.
+    const sha = (seed) => seed.repeat(40).slice(0, 40);
+    const events = [
+        {
+            id: 'evt-100',
+            kind: 'labeled',
+            actor: 'ada',
+            avatarUrl: 'https://avatars.githubusercontent.com/u/1?v=4',
+            createdAt: at(300_000),
+            label: { name: 'bug', color: 'd73a4a' },
+        },
+        {
+            id: `evt-${sha('a')}`,
+            kind: 'committed',
+            actor: 'Lin Zhao',
+            createdAt: at(900_000),
+            sha: sha('a'),
+            message: 'fix(session): keep the refresh token on reload',
+            checks: 'passing',
+        },
+        {
+            id: `evt-${sha('b')}`,
+            kind: 'committed',
+            actor: 'Lin Zhao',
+            createdAt: at(960_000),
+            sha: sha('b'),
+            message: 'test(session): cover the reload path',
+            checks: 'failing',
+        },
+        {
+            id: `evt-${sha('c')}`,
+            kind: 'committed',
+            actor: 'Lin Zhao',
+            createdAt: at(1_020_000),
+            sha: sha('c'),
+            message: 'chore: appease the linter',
+            checks: 'pending',
+        },
+        {
+            id: `evt-${sha('d')}`,
+            kind: 'committed',
+            actor: 'Lin Zhao',
+            createdAt: at(1_080_000),
+            sha: sha('d'),
+            message: 'docs: note the new behavior',
+            checks: null, // no CI configured — renders no glyph, distinct from absent
+        },
+        {
+            id: 'evt-101',
+            kind: 'cross-referenced',
+            actor: 'grace',
+            avatarUrl: 'https://avatars.githubusercontent.com/u/3?v=4',
+            createdAt: at(1_500_000),
+            refNumber: 42,
+            refTitle: 'Session handling rewrite',
+            refIsPr: true,
+            url: 'https://github.com/mock/repo/pull/42',
+        },
+    ];
+    if (kind === 'pr') {
+        events.push({
+            id: 'evt-102',
+            kind: 'merged',
+            actor: 'grace',
+            avatarUrl: 'https://avatars.githubusercontent.com/u/3?v=4',
+            createdAt: at(1_800_000),
+        });
+    }
+    return { available: true, comments, events };
+}
+// ---- draft-PR creation (review gate, spec 009) ------------------------------
+// Final autosave-commit → `git push -u origin xez/<id8>` → `gh pr create
+// --draft`, all executed in the task worktree (gh picks the repo up from the
+// worktree's remote). Every failure maps to a one-line human error — the GUI
+// shows it as a toast plus the manual `git merge <branch>` fallback. Never throws.
+const PR_URL_RE = /https:\/\/github\.com\/[^/\s]+\/[^/\s]+\/pull\/\d+/;
+const PUSH_TIMEOUT_MS = 60_000;
+const PROGRESS_LINES_MAX = 10;
+export async function createDraftPr(input) {
+    const { run } = input;
+    const worktree = run.worktreePath;
+    const branch = run.branch;
+    if (!worktree || !branch) {
+        return { ok: false, error: 'this task has no worktree/branch to publish' };
+    }
+    // Final autosave: the branch must hold everything before it leaves the box.
+    // This is the LAST flush — unlike the turn-end and run-finalize ones there is
+    // no later autosave to pick the work up, so a refusal (conflicted tree) or a
+    // failed commit has to stop the publish instead of silently opening a PR from
+    // a branch that is missing the run's final state.
+    const saved = await autosaveCommit(worktree, 'pre-PR');
+    if (saved === 'refused') {
+        return {
+            ok: false,
+            error: 'worktree has unresolved merge conflicts — resolve them, then publish again',
+        };
+    }
+    if (saved === 'failed') {
+        return { ok: false, error: 'could not commit the final changes — check git status in the worktree' };
+    }
+    // DRY-RUN (XEZ_DRY_RUN=1): no push, no gh — simulate success with a fake PR
+    // URL so the whole review → PR flow is testable without GitHub.
+    if (process.env.XEZ_DRY_RUN === '1') {
+        return { ok: true, url: 'https://github.com/open-mercato/demo/pull/777', dryRun: true };
+    }
+    const remote = await execTool(['remote', 'get-url', 'origin'], worktree, 'git');
+    if (!remote.ok || !remote.stdout.trim()) {
+        return { ok: false, error: 'no git remote — add one (git remote add origin <url>) or merge the branch locally' };
+    }
+    const push = await execTool(['push', '-u', 'origin', branch], worktree, 'git', PUSH_TIMEOUT_MS);
+    if (!push.ok) {
+        return { ok: false, error: `git push failed — ${tail(push.stderr) || 'unknown error'}` };
+    }
+    const body = buildPrBody(input.handoffText, run.task);
+    // Target the branch the worktree forked from (config `baseBranch`) — without
+    // --base, gh aims at the repo default (main) even when work started on
+    // develop. `origin/x` normalizes to `x`; a raw sha (detached-HEAD fork
+    // point) can't be a PR base, so gh falls back to the default branch.
+    const prBase = run.baseBranch?.replace(/^origin\//, '');
+    const baseArgs = prBase && !/^[0-9a-f]{7,40}$/i.test(prBase) ? ['--base', prBase] : [];
+    const pr = await execTool(['pr', 'create', '--draft', '--head', branch, ...baseArgs, '--title', run.title, '--body', body], worktree, 'gh', PUSH_TIMEOUT_MS);
+    if (!pr.ok) {
+        if (pr.notFound) {
+            return { ok: false, error: 'gh not found — install the GitHub CLI and run `gh auth login`, or merge the branch locally' };
+        }
+        const hint = /auth|log ?in|credential/i.test(pr.stderr) ? ' (try `gh auth login`)' : '';
+        return { ok: false, error: `gh pr create failed — ${tail(pr.stderr) || 'unknown error'}${hint}` };
+    }
+    // gh prints the PR URL on stdout; some versions echo it to stderr instead.
+    const match = PR_URL_RE.exec(`${pr.stdout}\n${pr.stderr}`);
+    if (!match) {
+        return { ok: false, error: 'gh pr create returned no PR URL — check `gh pr list` manually' };
+    }
+    return { ok: true, url: match[0], dryRun: false };
+}
+/**
+ * PR body from the handoff journal: the "## Goal" section (task text as
+ * fallback) + the first ~10 lines of "## Progress log" (newest first) +
+ * the xezar footer.
+ */
+export function buildPrBody(handoffText, task) {
+    const goal = section(handoffText, '## Goal') || task.trim();
+    const progress = section(handoffText, '## Progress log')
+        .split('\n')
+        .filter((l) => l.trim())
+        .slice(0, PROGRESS_LINES_MAX)
+        .join('\n');
+    const parts = ['## Goal', '', goal];
+    if (progress)
+        parts.push('', '## Progress log', '', progress);
+    parts.push('', '---', '', '🤖 made with xezar');
+    return parts.join('\n');
+}
+/** Text of one `## Header` section, up to the next `## ` header. */
+function section(text, header) {
+    const start = text.indexOf(`${header}\n`);
+    if (start < 0)
+        return '';
+    const rest = text.slice(start + header.length + 1);
+    const next = rest.indexOf('\n## ');
+    return (next >= 0 ? rest.slice(0, next) : rest).trim();
+}
+/** Last 3 stderr lines, pipe-joined — enough context, toast-sized. */
+function tail(stderr) {
+    return stderr.trim().split('\n').slice(-3).join(' | ').slice(0, 300);
+}
+function execTool(args, cwd, bin, timeoutMs = 30_000) {
+    return new Promise((resolve) => {
+        execFile(bin, args, { cwd, timeout: timeoutMs, maxBuffer: 4 * 1024 * 1024, encoding: 'utf8' }, (err, stdout, stderr) => resolve({
+            ok: !err,
+            stdout: stdout ?? '',
+            stderr: stderr ?? '',
+            notFound: err?.code === 'ENOENT',
+        }));
+    });
+}
+// ---- the driver -------------------------------------------------------------
+/** Cached availability probe so `GET /api/health` never pays a full listing. */
+let detectCache = null;
+async function detectGithub(repoRoot) {
+    if (process.env.XEZ_DRY_RUN === '1')
+        return { available: true };
+    if (detectCache && detectCache.repoRoot === repoRoot && Date.now() - detectCache.at < CACHE_MS) {
+        return detectCache.result;
+    }
+    let result;
+    try {
+        await gh(repoRoot, ['repo', 'view', '--json', 'nameWithOwner'], 5_000);
+        result = { available: true };
+    }
+    catch (err) {
+        const message = err instanceof Error ? err.message : String(err);
+        result = {
+            available: false,
+            reason: /ENOENT/.test(message)
+                ? 'gh CLI not found — install it and run `gh auth login`'
+                : firstLine(message),
+        };
+    }
+    detectCache = { at: Date.now(), repoRoot, result };
+    return result;
+}
+/**
+ * Non-blocking availability for `GET /api/health` (#major-health-latency): serves the last-known
+ * probe immediately (stale-while-revalidate) and only returns `null` on a cold start, before the
+ * first probe has ever warmed the cache. It NEVER shells out to `gh` on the request that reads it,
+ * so health stays under the bookmarklet's 800 ms port budget (a `gh repo view` round-trip is
+ * ~500–650 ms on its own). `null` is contract-safe — the whole `forge` field is additive, so
+ * "unknown until warm" is a valid answer.
+ *
+ * Serving the stale value while revalidating is what keeps the GitHub nav item from flickering:
+ * without it, every time the 60 s cache expired this returned `null` for one 5 s health poll,
+ * dropping `forge.available` and blinking the sidebar item out until the background probe warmed.
+ */
+export function detectGithubCached(repoRoot) {
+    if (process.env.XEZ_DRY_RUN === '1')
+        return { available: true };
+    const cached = detectCache && detectCache.repoRoot === repoRoot ? detectCache.result : null;
+    const fresh = detectCache && detectCache.repoRoot === repoRoot && Date.now() - detectCache.at < CACHE_MS;
+    if (!fresh) {
+        void detectGithub(repoRoot).catch(() => { }); // revalidate off the request path
+    }
+    return cached; // last-known value while revalidating; null only until the first probe warms
+}
+const mergeStateCache = new Map();
+const mergeInflight = new Set();
+const MERGE_CACHE_MS = 15_000;
+function mergeCheckState(check) {
+    const value = (check.conclusion || check.state || check.status || '').toUpperCase();
+    if (['SUCCESS', 'NEUTRAL', 'SKIPPED'].includes(value))
+        return 'passing';
+    if (['FAILURE', 'ERROR', 'TIMED_OUT', 'ACTION_REQUIRED', 'CANCELLED'].includes(value))
+        return 'failing';
+    if (['PENDING', 'IN_PROGRESS', 'QUEUED', 'EXPECTED', 'WAITING', 'REQUESTED'].includes(value))
+        return 'pending';
+    return 'unknown';
+}
+export function normalizeMergeState(raw, policyRaw, requirements = {
+    readable: false,
+    requiredChecks: [],
+}) {
+    const pr = mergePrSchema.parse(raw);
+    const policy = repoMergePolicySchema.parse(policyRaw);
+    const state = pr.state.toUpperCase() === 'MERGED' ? 'merged' : pr.state.toUpperCase() === 'CLOSED' ? 'closed' : 'open';
+    const mergeable = pr.mergeable?.toUpperCase() === 'MERGEABLE'
+        ? 'mergeable'
+        : pr.mergeable?.toUpperCase() === 'CONFLICTING'
+            ? 'conflicting'
+            : 'unknown';
+    const reviewDecision = pr.reviewDecision?.toUpperCase() === 'APPROVED'
+        ? 'approved'
+        : pr.reviewDecision?.toUpperCase() === 'CHANGES_REQUESTED'
+            ? 'changes-requested'
+            : pr.reviewDecision?.toUpperCase() === 'REVIEW_REQUIRED'
+                ? 'review-required'
+                : 'unknown';
+    const checks = (pr.statusCheckRollup ?? []).map((check) => ({
+        name: check.name,
+        state: mergeCheckState(check),
+        required: requirements.readable ? requirements.requiredChecks.includes(check.name) : null,
+        ...(check.detailsUrl?.startsWith('https://') || check.detailsUrl?.startsWith('http://')
+            ? { url: check.detailsUrl }
+            : {}),
+    }));
+    const methods = [];
+    if (policy.allow_squash_merge)
+        methods.push('squash');
+    if (policy.allow_merge_commit)
+        methods.push('merge');
+    if (policy.allow_rebase_merge)
+        methods.push('rebase');
+    const defaultMethod = policy.squash_merge_commit_title && methods.includes('squash')
+        ? 'squash'
+        : policy.merge_commit_title && methods.includes('merge')
+            ? 'merge'
+            : methods[0] ?? null;
+    const blockers = [];
+    let eligibility = 'ready';
+    if (state !== 'open') {
+        eligibility = 'terminal';
+        blockers.push({ code: 'terminal', message: state === 'merged' ? 'This pull request is merged.' : 'This pull request is closed.' });
+    }
+    else if (pr.isDraft) {
+        eligibility = 'blocked';
+        blockers.push({ code: 'draft', message: 'Mark the pull request ready for review before merging.' });
+    }
+    else if (mergeable === 'conflicting') {
+        eligibility = 'blocked';
+        blockers.push({ code: 'conflicts', message: 'Conflicts must be resolved before merging.' });
+    }
+    else if (checks.some((check) => check.state === 'failing')) {
+        eligibility = 'blocked';
+        blockers.push({ code: 'checks-failing', message: 'One or more checks are failing.' });
+    }
+    else if (reviewDecision === 'changes-requested' || reviewDecision === 'review-required') {
+        eligibility = 'blocked';
+        blockers.push({ code: 'reviews', message: reviewDecision === 'changes-requested' ? 'Changes were requested.' : 'A required review is missing.' });
+    }
+    else if (reviewDecision === 'unknown' || !requirements.readable) {
+        eligibility = 'unknown';
+        blockers.push({
+            code: 'rules-unknown',
+            message: 'GitHub could not confirm review and branch-protection requirements.',
+        });
+    }
+    else if (checks.some((check) => check.state === 'pending') || pr.mergeStateStatus?.toUpperCase() === 'UNSTABLE') {
+        eligibility = 'pending';
+        blockers.push({ code: 'pending', message: 'Checks or GitHub mergeability are still pending.' });
+    }
+    else if (mergeable !== 'mergeable' ||
+        !['CLEAN', 'HAS_HOOKS'].includes(pr.mergeStateStatus?.toUpperCase() ?? '') ||
+        methods.length === 0) {
+        eligibility = 'unknown';
+        blockers.push({ code: 'unknown', message: 'GitHub could not confirm every merge requirement.' });
+    }
+    const canMerge = eligibility === 'ready';
+    const canOverride = !canMerge &&
+        state === 'open' &&
+        !pr.isDraft &&
+        mergeable !== 'conflicting' &&
+        methods.length > 0;
+    return {
+        number: pr.number,
+        title: pr.title,
+        url: pr.url,
+        state,
+        isDraft: pr.isDraft,
+        headRef: pr.headRefName,
+        baseRef: pr.baseRefName,
+        headSha: pr.headRefOid,
+        mergeable,
+        reviewDecision,
+        checks,
+        methods,
+        defaultMethod,
+        eligibility,
+        blockers,
+        canMerge,
+        canOverride,
+    };
+}
+async function fetchPrMergeState(repoRoot, repoRef, number, refresh = false) {
+    if (process.env.XEZ_DRY_RUN === '1') {
+        return {
+            available: true,
+            mergeState: normalizeMergeState({
+                number,
+                title: 'Dry-run pull request',
+                url: `https://github.com/mock/repo/pull/${number}`,
+                state: 'OPEN',
+                isDraft: false,
+                headRefName: 'feat/dry-run',
+                baseRefName: 'main',
+                headRefOid: '0123456789abcdef0123456789abcdef01234567',
+                mergeable: 'MERGEABLE',
+                mergeStateStatus: 'CLEAN',
+                reviewDecision: 'APPROVED',
+                statusCheckRollup: [{ name: 'test', conclusion: 'SUCCESS', detailsUrl: 'https://github.com/mock/repo/actions' }],
+            }, { allow_merge_commit: true, allow_squash_merge: true, allow_rebase_merge: true }, { readable: true, requiredChecks: ['test'] }),
+        };
+    }
+    if (!repoRef)
+        return { available: false, reason: 'GitHub remote could not be resolved' };
+    const key = `${repoRoot}:${number}`;
+    const hit = mergeStateCache.get(key);
+    if (!refresh && hit && Date.now() - hit.at < MERGE_CACHE_MS)
+        return hit.value;
+    try {
+        const prOut = await gh(repoRoot, [
+            'pr', 'view', String(number), '--json',
+            'number,title,url,state,isDraft,headRefName,baseRefName,headRefOid,mergeable,mergeStateStatus,reviewDecision,statusCheckRollup',
+        ]);
+        const parsedPr = mergePrSchema.parse(JSON.parse(prOut));
+        const [policyOut, requiredChecks] = await Promise.all([
+            gh(repoRoot, ['api', `repos/${repoRef.owner}/${repoRef.repo}`]),
+            gh(repoRoot, [
+                'api',
+                `repos/${repoRef.owner}/${repoRef.repo}/branches/${encodeURIComponent(parsedPr.baseRefName)}/protection/required_status_checks`,
+                '--jq',
+                '[.contexts[]?, .checks[]?.context] | unique',
+            ])
+                .then((output) => ({ readable: true, requiredChecks: z.array(z.string()).parse(JSON.parse(output)) }))
+                .catch(() => ({ readable: false, requiredChecks: [] })),
+        ]);
+        const value = {
+            available: true,
+            mergeState: normalizeMergeState(parsedPr, JSON.parse(policyOut), requiredChecks),
+        };
+        mergeStateCache.set(key, { at: Date.now(), value });
+        return value;
+    }
+    catch (error) {
+        return { available: false, reason: firstLine(error instanceof Error ? error.message : String(error)) };
+    }
+}
+export function evictGithubProjectCaches(repoRoot) {
+    listCache.delete(repoRoot);
+    mergeStateCache.forEach((_value, key) => {
+        if (key.startsWith(`${repoRoot}:`))
+            mergeStateCache.delete(key);
+    });
+    commentsCache.forEach((_value, key) => {
+        if (key.startsWith(`${repoRoot}:`))
+            commentsCache.delete(key);
+    });
+}
+async function mergePullRequest(repoRoot, repoRef, number, input) {
+    const key = `${repoRoot}:${number}`;
+    if (mergeInflight.has(key))
+        return { merged: false, status: 409, error: 'A merge is already in progress.', code: 'concurrent' };
+    mergeInflight.add(key);
+    try {
+        const fresh = await fetchPrMergeState(repoRoot, repoRef, number, true);
+        if (!fresh.available)
+            return { merged: false, status: 502, error: fresh.reason };
+        const current = fresh.mergeState;
+        if (current.headSha !== input.expectedHeadSha) {
+            return { merged: false, status: 409, error: 'The pull request head changed. Review the new commits before merging.', code: 'stale-head', current };
+        }
+        if (!current.methods.includes(input.method)) {
+            return { merged: false, status: 409, error: 'That merge method is no longer enabled.', code: 'disabled-method', current };
+        }
+        if (!mergePreflightAllowed(current, input.overrideRules)) {
+            return { merged: false, status: 409, error: current.blockers[0]?.message ?? 'The pull request is not eligible to merge.', code: current.eligibility, current };
+        }
+        if (process.env.XEZ_DRY_RUN === '1') {
+            evictGithubProjectCaches(repoRoot);
+            return { merged: true, number, url: current.url, method: input.method, mergeCommitSha: 'abcdef0123456789abcdef0123456789abcdef01' };
+        }
+        if (!repoRef)
+            return { merged: false, status: 404, error: 'GitHub repository not found.' };
+        const out = await gh(repoRoot, [
+            'api', '--method', 'PUT', `repos/${repoRef.owner}/${repoRef.repo}/pulls/${number}/merge`,
+            '-f', `merge_method=${input.method}`, '-f', `sha=${input.expectedHeadSha}`,
+        ]);
+        const result = ghMergeResultSchema.parse(JSON.parse(out));
+        if (!result.merged)
+            return { merged: false, status: 409, error: result.message ?? 'GitHub refused the merge.', code: 'github-blocked', current };
+        evictGithubProjectCaches(repoRoot);
+        return { merged: true, number, url: current.url, method: input.method, ...(result.sha ? { mergeCommitSha: result.sha } : {}) };
+    }
+    catch (error) {
+        const message = firstLine(error instanceof Error ? error.message : String(error));
+        const status = /403|permission|forbidden/i.test(message) ? 403 : /404|not found/i.test(message) ? 404 : 502;
+        return { merged: false, status, error: status === 403 ? 'GitHub permission denied.' : status === 404 ? 'Pull request or repository not found.' : 'GitHub could not complete the merge.' };
+    }
+    finally {
+        mergeInflight.delete(key);
+    }
+}
+export function mergePreflightAllowed(current, overrideRules = false) {
+    return current.canMerge || (overrideRules && current.canOverride);
+}
+const GH_PR_STATES = {
+    MERGED: 'merged',
+    CLOSED: 'closed',
+};
+export function createGithubDriver(repoRoot, repoRef) {
+    return {
+        kind: 'github',
+        detect: () => detectGithub(repoRoot),
+        detectCached: () => detectGithubCached(repoRoot),
+        listIssues: async (opts) => (await fetchGithub(repoRoot, opts?.refresh, opts?.limit)).issues,
+        listPRs: async (opts) => (await fetchGithub(repoRoot, opts?.refresh, opts?.limit)).prs,
+        // The open-only list tier's escape hatch (#730) — this is the only path that can reach a
+        // closed or merged item.
+        searchItems: (kind, query, opts) => searchGithubItems(repoRoot, kind, query, opts?.limit),
+        prDiff: (number, opts) => fetchGithubPrDiff(repoRoot, number, opts?.refresh),
+        createPR: (input) => createDraftPr(input),
+        // Null covers everything from "no PR yet" to "gh missing" — the callers
+        // (Create PR → View PR flip) treat all of it as "nothing to link".
+        prStatus: async (branch) => {
+            if (process.env.XEZ_DRY_RUN === '1')
+                return null;
+            try {
+                const out = await gh(repoRoot, ['pr', 'view', branch, '--json', 'number,url,state,isDraft,statusCheckRollup']);
+                const pr = ghPrViewSchema.parse(JSON.parse(out));
+                return {
+                    number: pr.number,
+                    url: pr.url,
+                    state: GH_PR_STATES[pr.state.toUpperCase()] ?? 'open',
+                    isDraft: pr.isDraft,
+                    checks: rollupToChecks(pr.statusCheckRollup) ?? null,
+                };
+            }
+            catch {
+                return null;
+            }
+        },
+        prMergeState: (number, opts) => fetchPrMergeState(repoRoot, repoRef, number, opts?.refresh),
+        mergePR: (number, input) => mergePullRequest(repoRoot, repoRef, number, input),
+        viewUrl: (kind, ref) => {
+            if (!repoRef)
+                return null;
+            const base = `https://github.com/${repoRef.owner}/${repoRef.repo}`;
+            // Branch names may contain '/' — encode per segment, keep the slashes.
+            const path = String(ref).split('/').map(encodeURIComponent).join('/');
+            switch (kind) {
+                case 'repo':
+                    return base;
+                case 'issue':
+                    return `${base}/issues/${path}`;
+                case 'pr':
+                    return `${base}/pull/${path}`;
+                case 'branch':
+                    return `${base}/tree/${path}`;
+                case 'commit':
+                    return `${base}/commit/${path}`;
+            }
+        },
+    };
+}
+//# sourceMappingURL=github.js.map