edsger 0.65.0 → 0.67.0

package/dist/commands/chat-serve/index.d.ts

@@ -0,0 +1,20 @@
+/**
+ * `edsger chat-serve` — long-lived daemon that answers human messages on issue
+ * and product group chat channels.
+ *
+ * This is the standalone replacement for the old `chat-worker` that
+ * `AgentWorkflowProcessor` used to fork. Running it as its own top-level
+ * process (spawned by the desktop app, sibling to `edsger --verbose` and
+ * `edsger session-serve`) decouples chat from the autonomous workflow: chat
+ * works whether or not the workflow is running, and the two never both claim
+ * the same messages.
+ *
+ * Like the agent workflow, it requires `edsger login` first and exits promptly
+ * if no auth is found. The actual chat-serving logic lives in {@link ChatServer}.
+ */
+export interface ChatServeCliOptions {
+    verbose?: boolean;
+    /** Optional path to an edsger config file (forwarded to validateConfiguration). */
+    config?: string;
+}
+export declare function runChatServeCommand(options?: ChatServeCliOptions): Promise<void>;

package/dist/commands/chat-serve/index.js

@@ -0,0 +1,58 @@
+/**
+ * `edsger chat-serve` — long-lived daemon that answers human messages on issue
+ * and product group chat channels.
+ *
+ * This is the standalone replacement for the old `chat-worker` that
+ * `AgentWorkflowProcessor` used to fork. Running it as its own top-level
+ * process (spawned by the desktop app, sibling to `edsger --verbose` and
+ * `edsger session-serve`) decouples chat from the autonomous workflow: chat
+ * works whether or not the workflow is running, and the two never both claim
+ * the same messages.
+ *
+ * Like the agent workflow, it requires `edsger login` first and exits promptly
+ * if no auth is found. The actual chat-serving logic lives in {@link ChatServer}.
+ */
+import { isLoggedIn } from '../../auth/auth-store.js';
+import { logError, logInfo } from '../../utils/logger.js';
+import { validateConfiguration } from '../../utils/validation.js';
+import { ensureWorkspaceDir } from '../../workspace/workspace-manager.js';
+import { ChatServer } from './chat-server.js';
+export async function runChatServeCommand(options = {}) {
+    // Mirror the agent workflow: auth is required, and we exit fast when absent
+    // so the desktop supervisor can surface a "run `edsger login`" hint.
+    if (!isLoggedIn()) {
+        logError('Not authenticated. Please run `edsger login` first.');
+        process.exit(1);
+    }
+    const cliOptions = {
+        verbose: options.verbose,
+        config: options.config,
+    };
+    const config = validateConfiguration(cliOptions);
+    const workspaceRoot = ensureWorkspaceDir();
+    logInfo(`Workspace: ${workspaceRoot}`);
+    const server = new ChatServer({
+        config,
+        workspaceRoot,
+        verbose: options.verbose,
+    });
+    await server.start();
+    let shuttingDown = false;
+    const shutdown = async (signal) => {
+        if (shuttingDown) {
+            return;
+        }
+        shuttingDown = true;
+        logInfo(`Received ${signal} — shutting down chat server.`);
+        await server.stop();
+        process.exit(0);
+    };
+    process.on('SIGTERM', () => void shutdown('SIGTERM'));
+    process.on('SIGINT', () => void shutdown('SIGINT'));
+    process.on('uncaughtException', (error) => {
+        logError(`Uncaught exception: ${error instanceof Error ? error.message : String(error)}`);
+        void server.stop().finally(() => process.exit(1));
+    });
+    // The Realtime socket / poll timer keep the event loop alive; nothing else
+    // to do on the main path. The process lives until a signal arrives.
+}

package/dist/commands/session-serve/index.d.ts

@@ -0,0 +1,32 @@
+/**
+ * `edsger session-serve <channelId>` — long-lived conversational agent for one
+ * chat session.
+ *
+ * Where `session-turn` runs a single turn and exits, `session-serve` prepares
+ * the session context once (repo clone, MCP toolbelt, system prompt) and then
+ * stays alive, running one turn per command it reads from stdin. The SDK
+ * session id is kept in memory and carried into the next turn automatically, so
+ * the conversation (and prompt cache) stays warm without a per-turn cold start.
+ *
+ * Protocol — one JSON object per line on stdin:
+ *   {"type":"turn"}                                  process pending messages
+ *   {"type":"run-finished","runId":"…","command":"…"} report a finished cli_* run
+ *   {"type":"shutdown"}                               drain + exit cleanly
+ *
+ * Turns run strictly one at a time (a session never has two turns in flight).
+ * When stdin closes, the process exits after the current turn drains. Markers
+ * (session id, background cli runs) are written to stdout exactly as the
+ * one-shot command emits them, so the desktop's existing parsing is unchanged.
+ */
+import { type SessionTurnCliOptions } from '../session-turn/index.js';
+/**
+ * Emitted once the session context is built and the process is ready to accept
+ * turn commands on stdin. The desktop may use it to know the daemon is live;
+ * it is harmless to ignore.
+ */
+export declare const SESSION_READY_MARKER = "__EDSGER_SESSION_READY__";
+export type SessionServeCliOptions = Omit<SessionTurnCliOptions, 'runFinished'> & {
+    /** SDK session id to resume on the first turn (e.g. after a crash-restart). */
+    resumeSessionId?: string;
+};
+export declare function runSessionServeCommand(options: SessionServeCliOptions): Promise<void>;

package/dist/commands/session-serve/index.js

@@ -0,0 +1,100 @@
+/**
+ * `edsger session-serve <channelId>` — long-lived conversational agent for one
+ * chat session.
+ *
+ * Where `session-turn` runs a single turn and exits, `session-serve` prepares
+ * the session context once (repo clone, MCP toolbelt, system prompt) and then
+ * stays alive, running one turn per command it reads from stdin. The SDK
+ * session id is kept in memory and carried into the next turn automatically, so
+ * the conversation (and prompt cache) stays warm without a per-turn cold start.
+ *
+ * Protocol — one JSON object per line on stdin:
+ *   {"type":"turn"}                                  process pending messages
+ *   {"type":"run-finished","runId":"…","command":"…"} report a finished cli_* run
+ *   {"type":"shutdown"}                               drain + exit cleanly
+ *
+ * Turns run strictly one at a time (a session never has two turns in flight).
+ * When stdin closes, the process exits after the current turn drains. Markers
+ * (session id, background cli runs) are written to stdout exactly as the
+ * one-shot command emits them, so the desktop's existing parsing is unchanged.
+ */
+import { createInterface } from 'node:readline';
+import { logError, logInfo } from '../../utils/logger.js';
+import { prepareSessionContext, runTurn, } from '../session-turn/index.js';
+/**
+ * Emitted once the session context is built and the process is ready to accept
+ * turn commands on stdin. The desktop may use it to know the daemon is live;
+ * it is harmless to ignore.
+ */
+export const SESSION_READY_MARKER = '__EDSGER_SESSION_READY__';
+export async function runSessionServeCommand(options) {
+    const ctx = await prepareSessionContext(options);
+    process.stdout.write(`\n${SESSION_READY_MARKER}\n`);
+    logInfo(`Session ${ctx.channelId} ready — awaiting turns on stdin.`);
+    // Commands queue up here; we drain them one at a time so a session never has
+    // two turns running concurrently. `shuttingDown` stops accepting new work.
+    const queue = [];
+    let running = false;
+    let shuttingDown = false;
+    let stdinEnded = false;
+    const maybeExit = () => {
+        if ((shuttingDown || stdinEnded) && !running && queue.length === 0) {
+            logInfo(`Session ${ctx.channelId} shutting down.`);
+            process.exit(0);
+        }
+    };
+    const drain = async () => {
+        if (running) {
+            return;
+        }
+        running = true;
+        try {
+            while (queue.length > 0) {
+                const cmd = queue.shift();
+                if (cmd.type === 'shutdown') {
+                    shuttingDown = true;
+                    continue;
+                }
+                try {
+                    if (cmd.type === 'run-finished' && cmd.runId) {
+                        await runTurn(ctx, {
+                            runFinished: { runId: cmd.runId, command: cmd.command },
+                        });
+                    }
+                    else {
+                        await runTurn(ctx);
+                    }
+                }
+                catch (error) {
+                    logError(`Turn failed: ${error instanceof Error ? error.message : String(error)}`);
+                }
+            }
+        }
+        finally {
+            running = false;
+            maybeExit();
+        }
+    };
+    const rl = createInterface({ input: process.stdin });
+    rl.on('line', (line) => {
+        const trimmed = line.trim();
+        if (!trimmed || shuttingDown) {
+            return;
+        }
+        let cmd;
+        try {
+            cmd = JSON.parse(trimmed);
+        }
+        catch {
+            logError(`Ignoring malformed command: ${trimmed}`);
+            return;
+        }
+        queue.push(cmd);
+        void drain();
+    });
+    // stdin closing is the desktop's normal "stop this session" signal.
+    rl.on('close', () => {
+        stdinEnded = true;
+        maybeExit();
+    });
+}

package/dist/commands/session-turn/index.d.ts

@@ -12,6 +12,7 @@ export declare const SESSION_ID_MARKER = "__EDSGER_SESSION_ID__=";
  * to ask. The JSON payload is `{ run_id, pid, log_path, command }`.
  */
 export declare const CLI_RUN_MARKER = "__EDSGER_CLI_RUN__=";
+import { loadExternalMcpServers } from 'edsger-tools';
 export interface SessionTurnCliOptions {
     channelId: string;
     productId: string;
@@ -30,4 +31,43 @@ export interface SessionTurnCliOptions {
     };
     verbose?: boolean;
 }
+/**
+ * Everything a session needs to run turns, built once and reused. The daemon
+ * keeps a single instance alive across turns so repo clones, the MCP toolbelt,
+ * the system prompt, and the SDK session id all persist.
+ */
+export interface SessionContext {
+    channelId: string;
+    productId: string;
+    repositoryIds: string[];
+    verbose: boolean;
+    sessionDir?: string;
+    systemPrompt: string;
+    sessionServer: any;
+    external: ReturnType<typeof loadExternalMcpServers>;
+    /** Latest SDK session id; carried into the next turn's `resume`. Mutable. */
+    sdkSessionId: string;
+}
+/**
+ * Build the one-time session context: clone repos, assemble the MCP toolbelt
+ * and external servers, and build the system prompt. Cheap to call once per
+ * session process; expensive to call per turn (which is why the daemon doesn't).
+ */
+export declare function prepareSessionContext(options: SessionTurnCliOptions): Promise<SessionContext>;
+/**
+ * Run a single agent turn against an already-prepared {@link SessionContext}.
+ * Mutates `ctx.sdkSessionId` so the next turn resumes the same SDK conversation
+ * (and prompt cache). Safe to call repeatedly for the life of the process.
+ */
+export declare function runTurn(ctx: SessionContext, opts?: {
+    runFinished?: {
+        runId: string;
+        command?: string;
+    };
+}): Promise<void>;
+/**
+ * One-shot `session-turn`: prepare the context and run a single turn. Retained
+ * for callers that want the previous per-turn-process behaviour (and as the
+ * building block the daemon reuses).
+ */
 export declare function runSessionTurnCommand(options: SessionTurnCliOptions): Promise<void>;

package/dist/commands/session-turn/index.js

@@ -23,6 +23,12 @@ export const CLI_RUN_MARKER = '__EDSGER_CLI_RUN__=';
  * to the channel and marks the messages processed. The agent decides what to
  * do (answer, generate stories/test cases, launch cli_* analyses, open PRs);
  * there is no fixed pipeline.
+ *
+ * The per-turn work is split into {@link prepareSessionContext} (one-time
+ * workspace clone + toolbelt + prompt build) and {@link runTurn} (one agent
+ * turn against that context). The one-shot `session-turn` command does both
+ * once; the long-lived `session-serve` daemon prepares the context once and
+ * calls {@link runTurn} repeatedly, keeping the SDK session warm across turns.
  */
 import { query } from '@anthropic-ai/claude-agent-sdk';
 import { buildSessionAgentOptions, buildSessionSystemPrompt, buildSessionUserPrompt, createSessionMcpServer, listActiveCliRuns, loadExternalMcpServers, SESSION_MAX_TURNS, } from 'edsger-tools';
@@ -53,54 +59,21 @@ async function prepareSessionWorkspace(opts) {
         repoScopeNote: workspace ? describeSessionRepos(workspace.repos) : '',
     };
 }
-export async function runSessionTurnCommand(options) {
-    const { channelId, productId, repositoryIds = [], resumeSessionId, runFinished, verbose = false, } = options;
-    // Emit the SDK session id so the desktop can persist it for the next turn.
-    const emitSessionId = (id) => {
-        if (id) {
-            process.stdout.write(`\n${SESSION_ID_MARKER}${id}\n`);
-        }
-    };
-    // Emit a marker for every background cli_* run still in flight, so the
-    // desktop watcher can poll each to completion and re-engage the agent.
-    const emitActiveCliRuns = () => {
-        for (const run of listActiveCliRuns()) {
-            const payload = JSON.stringify({
-                run_id: run.run_id,
-                pid: run.pid,
-                log_path: run.log_path,
-                command: run.command,
-            });
-            process.stdout.write(`\n${CLI_RUN_MARKER}${payload}\n`);
-        }
-    };
-    // 1. Decide what drives this turn. A normal turn replays the channel's
-    //    pending human messages; a watcher-triggered follow-up replays a
-    //    synthetic prompt about the background run that just finished.
-    let messages = [];
-    if (runFinished) {
-        logInfo(`Reporting completion of background run ${runFinished.runId} for session ${channelId}`);
-    }
-    else {
-        const pendingResult = (await callMcpEndpoint('chat/messages/pending', {
-            channel_id: channelId,
-        }));
-        messages = pendingResult.messages ?? [];
-        if (messages.length === 0) {
-            logInfo('No pending messages for this session — nothing to do.');
-            return;
-        }
-        logInfo(`Processing ${messages.length} message(s) for session ${channelId}`);
-    }
-    // 2. Clone the product's in-scope repositories into a local session
-    //    directory so the agent's Read/Grep/Glob can inspect the real code.
+/**
+ * Build the one-time session context: clone repos, assemble the MCP toolbelt
+ * and external servers, and build the system prompt. Cheap to call once per
+ * session process; expensive to call per turn (which is why the daemon doesn't).
+ */
+export async function prepareSessionContext(options) {
+    const { channelId, productId, repositoryIds = [], resumeSessionId, verbose = false, } = options;
+    // Clone the product's in-scope repositories into a local session directory
+    // so the agent's Read/Grep/Glob can inspect the real code.
     const { sessionDir, repoScopeNote } = await prepareSessionWorkspace({
         channelId,
         productId,
         repositoryIds,
         verbose,
     });
-    // 3. Build the session toolbelt + prompts.
     const deps = getToolDeps({
         verbose,
         context: { productId, channelId, repositoryIds },
@@ -118,38 +91,95 @@ export async function runSessionTurnCommand(options) {
         repoScopeNote,
         externalMcpNames: external.names,
     });
+    return {
+        channelId,
+        productId,
+        repositoryIds,
+        verbose,
+        sessionDir,
+        systemPrompt,
+        sessionServer,
+        external,
+        sdkSessionId: resumeSessionId ?? '',
+    };
+}
+/** Emit the SDK session id so the desktop can persist it for the next turn. */
+function emitSessionId(id) {
+    if (id) {
+        process.stdout.write(`\n${SESSION_ID_MARKER}${id}\n`);
+    }
+}
+/**
+ * Emit a marker for every background cli_* run still in flight, so the desktop
+ * watcher can poll each to completion and re-engage the agent.
+ */
+function emitActiveCliRuns() {
+    for (const run of listActiveCliRuns()) {
+        const payload = JSON.stringify({
+            run_id: run.run_id,
+            pid: run.pid,
+            log_path: run.log_path,
+            command: run.command,
+        });
+        process.stdout.write(`\n${CLI_RUN_MARKER}${payload}\n`);
+    }
+}
+/**
+ * Run a single agent turn against an already-prepared {@link SessionContext}.
+ * Mutates `ctx.sdkSessionId` so the next turn resumes the same SDK conversation
+ * (and prompt cache). Safe to call repeatedly for the life of the process.
+ */
+export async function runTurn(ctx, opts = {}) {
+    const { runFinished } = opts;
+    // 1. Decide what drives this turn. A normal turn replays the channel's
+    //    pending human messages; a watcher-triggered follow-up replays a
+    //    synthetic prompt about the background run that just finished.
+    let messages = [];
+    if (runFinished) {
+        logInfo(`Reporting completion of background run ${runFinished.runId} for session ${ctx.channelId}`);
+    }
+    else {
+        const pendingResult = (await callMcpEndpoint('chat/messages/pending', {
+            channel_id: ctx.channelId,
+        }));
+        messages = pendingResult.messages ?? [];
+        if (messages.length === 0) {
+            logInfo('No pending messages for this session — nothing to do.');
+            return;
+        }
+        logInfo(`Processing ${messages.length} message(s) for session ${ctx.channelId}`);
+    }
     const userPrompt = runFinished
         ? buildRunFinishedPrompt(runFinished)
         : buildSessionUserPrompt(messages);
-    // 4. Run one SDK turn. Resume the prior SDK session when we have its id so
+    // 2. Run one SDK turn. Resume the prior SDK session when we have its id so
     //    the conversation (and prompt cache) carries across turns. Point the
     //    agent's cwd at the session directory so its read-only file tools resolve
     //    against the cloned repos. Prompt + tool/MCP wiring come from the shared
     //    session core (edsger-tools) so CLI and worker can't drift apart.
     let finalResponse = '';
-    let sdkSessionId = resumeSessionId ?? '';
     try {
         for await (const message of query({
             prompt: userPrompt,
             options: {
-                ...buildSessionAgentOptions(systemPrompt, {
-                    sessionServer,
-                    externalServers: external.servers,
-                    externalNames: external.names,
-                    sessionDir,
+                ...buildSessionAgentOptions(ctx.systemPrompt, {
+                    sessionServer: ctx.sessionServer,
+                    externalServers: ctx.external.servers,
+                    externalNames: ctx.external.names,
+                    sessionDir: ctx.sessionDir,
                     maxTurns: SESSION_MAX_TURNS,
                 }),
                 model: DEFAULT_MODEL,
-                ...(resumeSessionId ? { resume: resumeSessionId } : {}),
+                ...(ctx.sdkSessionId ? { resume: ctx.sdkSessionId } : {}),
             },
         })) {
             const msg = message;
             // The system/init and result messages carry the (possibly new) session
             // id — keep the latest so we persist what the next turn should resume.
             if (msg.session_id) {
-                sdkSessionId = msg.session_id;
+                ctx.sdkSessionId = msg.session_id;
             }
-            if (verbose && msg.type === 'assistant') {
+            if (ctx.verbose && msg.type === 'assistant') {
                 logInfo('· agent step');
             }
             if (msg.type === 'result') {
@@ -162,22 +192,22 @@ export async function runSessionTurnCommand(options) {
         const reason = error instanceof Error ? error.message : String(error);
         logError(`Session turn failed: ${reason}`);
         await callMcpEndpoint('chat/messages/send_ai', {
-            channel_id: channelId,
+            channel_id: ctx.channelId,
             content: `I hit an error processing that: ${reason}`,
             message_type: 'text',
             metadata: {},
         }).catch(() => undefined);
-        emitSessionId(sdkSessionId);
+        emitSessionId(ctx.sdkSessionId);
         emitActiveCliRuns();
         await markProcessed(messages);
         return;
     }
-    // 5. Post the final reply (the agent may also have posted via
+    // 3. Post the final reply (the agent may also have posted via
     //    send_chat_message during the turn; this carries the closing summary).
     const reply = finalResponse.trim();
     if (reply) {
         await callMcpEndpoint('chat/messages/send_ai', {
-            channel_id: channelId,
+            channel_id: ctx.channelId,
             content: reply,
             message_type: 'text',
             metadata: {},
@@ -185,16 +215,25 @@ export async function runSessionTurnCommand(options) {
             logError(`Failed to post reply: ${e instanceof Error ? e.message : String(e)}`);
         });
     }
-    // 6. Mark the triggering messages processed so they aren't re-run. (No-op for
+    // 4. Mark the triggering messages processed so they aren't re-run. (No-op for
     //    a watcher follow-up, which has no triggering human messages.)
     await markProcessed(messages);
-    // 7. Emit the SDK session id so the desktop persists it for the next turn,
+    // 5. Emit the SDK session id so the desktop persists it for the next turn,
     //    plus a marker for any background run launched this turn so the watcher
     //    keeps following it to completion.
-    emitSessionId(sdkSessionId);
+    emitSessionId(ctx.sdkSessionId);
     emitActiveCliRuns();
     logSuccess('Session turn complete.');
 }
+/**
+ * One-shot `session-turn`: prepare the context and run a single turn. Retained
+ * for callers that want the previous per-turn-process behaviour (and as the
+ * building block the daemon reuses).
+ */
+export async function runSessionTurnCommand(options) {
+    const ctx = await prepareSessionContext(options);
+    await runTurn(ctx, { runFinished: options.runFinished });
+}
 /**
  * The synthetic user prompt for a watcher-triggered follow-up turn. Steers the
  * agent to inspect what the finished run produced and report it — explicitly

package/dist/index.js

@@ -10,6 +10,7 @@ import { runAgentWorkflow } from './commands/agent-workflow/index.js';
 import { runAnalyzeLogs } from './commands/analyze-logs/index.js';
 import { runAppStoreGeneration } from './commands/app-store/index.js';
 import { runBuild } from './commands/build/index.js';
+import { runChatServeCommand } from './commands/chat-serve/index.js';
 import { runChecklists } from './commands/checklists/index.js';
 import { runCodeReview } from './commands/code-review/index.js';
 import { runConfigGet, runConfigList, runConfigSet, runConfigUnset, } from './commands/config/index.js';
@@ -32,6 +33,7 @@ import { runRefactor } from './commands/refactor/refactor.js';
 import { runReleaseSyncCommand } from './commands/release-sync/index.js';
 import { runRunSheetCommand } from './commands/run-sheet/index.js';
 import { runScreenFlow } from './commands/screen-flow/index.js';
+import { runSessionServeCommand } from './commands/session-serve/index.js';
 import { runSessionTurnCommand } from './commands/session-turn/index.js';
 import { runSmokeTestCommand } from './commands/smoke-test/index.js';
 import { runSyncAws } from './commands/sync-aws/index.js';
@@ -466,6 +468,50 @@ program
     }
 });
 // ============================================================
+// Subcommand: edsger session-serve <channelId>
+// ============================================================
+program
+    .command('session-serve <channelId>')
+    .description('Run a long-lived conversational agent for a chat session, taking one turn per command read from stdin')
+    .requiredOption('--product <productId>', 'Product the session is bound to')
+    .option('--repos <ids>', 'Comma-separated repository IDs the agent may touch', '')
+    .option('--resume <sessionId>', 'SDK session id to resume on the first turn (e.g. after a crash-restart)')
+    .option('-v, --verbose', 'Verbose output')
+    .action(async (channelId, opts) => {
+    try {
+        await runSessionServeCommand({
+            channelId,
+            productId: opts.product,
+            repositoryIds: (opts.repos ?? '')
+                .split(',')
+                .map((s) => s.trim())
+                .filter(Boolean),
+            resumeSessionId: opts.resume,
+            verbose: opts.verbose,
+        });
+    }
+    catch (error) {
+        logError(error instanceof Error ? error.message : String(error));
+        process.exit(1);
+    }
+});
+// ============================================================
+// Subcommand: edsger chat-serve
+// ============================================================
+program
+    .command('chat-serve')
+    .description('Run a long-lived daemon that answers human messages on issue and product group chat channels')
+    .option('-v, --verbose', 'Verbose output')
+    .action(async (opts) => {
+    try {
+        await runChatServeCommand({ verbose: opts.verbose });
+    }
+    catch (error) {
+        logError(error instanceof Error ? error.message : String(error));
+        process.exit(1);
+    }
+});
+// ============================================================
 // Subcommand: edsger user-stories-analysis <issueId>
 // ============================================================
 program

package/dist/phases/sync-org-repos/index.d.ts

@@ -1,13 +1,16 @@
 /**
  * Phase: sync-org-repos
  *
- * Fetches all repositories from a GitHub organization using the local `gh` CLI,
- * then upserts a row into the team-scoped `repositories` table for each repo.
- * Products are NOT created here — a product is a higher-level grouping that a
- * user links one or more repositories to afterwards.
+ * Fetches all repositories from a GitHub organization via the Edsger GitHub
+ * App (server-side, through the MCP `github/org_repos` endpoint), then upserts
+ * a row into the team-scoped `repositories` table for each repo. Products are
+ * NOT created here — a product is a higher-level grouping that a user links one
+ * or more repositories to afterwards.
  *
- * Uses `gh api --paginate` for truly unlimited pagination (no hardcoded cap).
- * Forks and archived repos are filtered out client-side.
+ * Repos are listed with a short-lived GitHub App installation token minted on
+ * the server, so this no longer depends on the user's machine having the `gh`
+ * CLI installed, authenticated, and on PATH. Forks and archived repos are
+ * filtered out server-side.
  */
 export interface SyncOrgReposResult {
     status: 'success' | 'error';