specrails-desktop 2.26.0 → 2.26.2

package/client/dist/index.html

@@ -47,8 +47,14 @@
         } catch (_) { /* storage unavailable — nothing to migrate */ }
         try {
           var k = 'specrails-desktop:ui-theme'
-          var allowed = ['dracula', 'aurora-light', 'obsidian-dark', 'matrix', 'specrails']
+          var legacyThemeIds = { 'star-wars': 'galaxy', matrix: 'code-rain' }
+          var allowed = ['dracula', 'aurora-light', 'obsidian-dark', 'code-rain', 'specrails', 'galaxy']
           var v = localStorage.getItem(k)
+          var migrated = legacyThemeIds[v]
+          if (migrated) {
+            v = migrated
+            localStorage.setItem(k, migrated)
+          }
           document.documentElement.dataset.theme =
             v && allowed.indexOf(v) !== -1 ? v : 'specrails'
         } catch (_) {
@@ -85,7 +91,7 @@
         --splash-secondary: #f48fc7;
         --splash-muted: #8b8fa3;
       }
-      html[data-theme="matrix"] {
+      html[data-theme="code-rain"] {
         --splash-bg: #08120e;
         --splash-fg: #b8ffd9;
         --splash-primary: #00ff66;
@@ -99,6 +105,13 @@
         --splash-secondary: #9a6fce;
         --splash-muted: #6b6f8c;
       }
+      html[data-theme="galaxy"] {
+        --splash-bg: hsl(220 20% 4%);
+        --splash-fg: hsl(210 30% 94%);
+        --splash-primary: hsl(212 100% 62%);
+        --splash-secondary: hsl(210 12% 65%);
+        --splash-muted: hsl(215 15% 60%);
+      }
       html, body {
         margin: 0;
         background: var(--splash-bg);
@@ -191,14 +204,14 @@
         .specrails-splash__mark .pill { opacity: 1; }
       }
     </style>
-    <script type="module" crossorigin src="/assets/index-DnkfABxY.js"></script>
+    <script type="module" crossorigin src="/assets/index-Dw1N2-ci.js"></script>
     <link rel="modulepreload" crossorigin href="/assets/chunk-BNv3lrIs.js">
     <link rel="modulepreload" crossorigin href="/assets/preload-helper-DSXbuxSR.js">
     <link rel="modulepreload" crossorigin href="/assets/clsx-CNmW0Nip.js">
     <link rel="modulepreload" crossorigin href="/assets/auth-Cvsb7-Ek.js">
     <link rel="modulepreload" crossorigin href="/assets/activity-D8vQJrpW.js">
     <link rel="modulepreload" crossorigin href="/assets/addspec-DxW6oPsk.js">
-    <link rel="modulepreload" crossorigin href="/assets/agent-Bn6ZmjHj.js">
+    <link rel="modulepreload" crossorigin href="/assets/agent-CLCyDaZh.js">
     <link rel="modulepreload" crossorigin href="/assets/agents-Cev2oFfX.js">
     <link rel="modulepreload" crossorigin href="/assets/agentstudio-CZm2rOzt.js">
     <link rel="modulepreload" crossorigin href="/assets/aiedit-DYtnZU9H.js">
@@ -209,7 +222,7 @@
     <link rel="modulepreload" crossorigin href="/assets/code-thSEptMx.js">
     <link rel="modulepreload" crossorigin href="/assets/commands-CckaBWdV.js">
     <link rel="modulepreload" crossorigin href="/assets/common-CYaT2yHp.js">
-    <link rel="modulepreload" crossorigin href="/assets/dashboard-Dwnssayh.js">
+    <link rel="modulepreload" crossorigin href="/assets/dashboard-BurhUI8_.js">
     <link rel="modulepreload" crossorigin href="/assets/explore-BKVV5JSu.js">
     <link rel="modulepreload" crossorigin href="/assets/integrations-CuWnMR5L.js">
     <link rel="modulepreload" crossorigin href="/assets/jira-B3613-gj.js">
@@ -217,12 +230,12 @@
     <link rel="modulepreload" crossorigin href="/assets/loops-Brnx4Fji.js">
     <link rel="modulepreload" crossorigin href="/assets/mcp-CIH0pH1K.js">
     <link rel="modulepreload" crossorigin href="/assets/nav-CzKzuwH8.js">
-    <link rel="modulepreload" crossorigin href="/assets/settings-DXgPh9-k.js">
-    <link rel="modulepreload" crossorigin href="/assets/setup-VNqXyB6Y.js">
+    <link rel="modulepreload" crossorigin href="/assets/settings-D9bDDe2O.js">
+    <link rel="modulepreload" crossorigin href="/assets/setup-RiUHzq7E.js">
     <link rel="modulepreload" crossorigin href="/assets/specs-CmEZY57v.js">
     <link rel="modulepreload" crossorigin href="/assets/terminal-DFPNRLKp.js">
     <link rel="modulepreload" crossorigin href="/assets/tickets-CkfbISuK.js">
-    <link rel="stylesheet" crossorigin href="/assets/index-cvOunQkD.css">
+    <link rel="stylesheet" crossorigin href="/assets/index-C695aPdV.css">
   </head>
   <body>
     <div id="specrails-splash" aria-hidden="false" role="status" aria-label="Loading Specrails">

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "specrails-desktop",
-  "version": "2.26.0",
+  "version": "2.26.2",
   "license": "MIT",
   "repository": {
     "type": "git",

package/server/dist/agent-operator-prompt.js

@@ -118,6 +118,39 @@ tool for exactly that, and never refuse or push this back to the user's terminal
   (\`rm -rf\`, force-push, branch deletion, history rewrite) to "make something
   work" — surface the blocker instead.
 
+## Support & troubleshooting
+
+When the user asks for help installing or using Specrails, asks "how do I...?",
+reports a broken setup, provider CLI/auth issue, MCP/Agent Chat issue, failed
+job, missing agents/skills/slash commands, PR-delivery confusion, costs, or
+plugin trouble, this is SUPPORT — not backlog work. Call
+\`specrails_support(action:'triage', question, projectId?)\` first and answer
+from its diagnostics/playbook. Do NOT create or propose a spec unless the user
+explicitly pivots from troubleshooting to product work.
+
+For job failures that mention missing agents, missing skills, missing
+\`/specrails:*\` commands, \`/opsx:*\` commands, "baseline agents", or a
+command not installed, explain the storage model correctly: upstream agents,
+skills and slash commands live in the app-global specrails-core framework, NOT
+inside the selected project. Give the user the repair path:
+
+- If global core may be stale, offer
+  \`specrails_support(action:'core_update_check')\`, then with confirmation
+  \`specrails_support(action:'core_update_apply')\`.
+- If global core is current and there is no concrete failing job/error, say the
+  core installation looks healthy. Do NOT infer a MyProject problem from
+  \`setup/checkpoints\`.
+- A setup checkpoint summary showing pending checkpoints, 0 agents, or
+  0 \`specrails:*\` commands is NOT a specrails-core health signal and is NOT a
+  reason to run \`specrails_setup(install)\`. Do not say they "live in
+  MyProject", and do not claim MyProject's projection is broken from that alone.
+- If a real job still reports missing core definitions while global core is
+  current, ask for/read \`specrails_jobs(get)\` or \`specrails_jobs(diagnostic)\`
+  and report it as a framework-loading/job diagnostic issue, not a project setup
+  checkpoint issue.
+- Manual fallback for standalone/legacy core installs: from the project root run
+  \`npx specrails-core@latest update\`, then retry the job.
+
 ## Permission ladder & confirmation rules
 
 Your actions are gated by a cumulative level the user steers live with
@@ -147,7 +180,9 @@ above the current level, say so up front.
 
 ## Think in specs (default stance)
 
-When the user describes work to be done, the natural unit is a SPEC:
+When the user describes product/code work to be done, the natural unit is a
+SPEC. This default does NOT apply to support/troubleshooting questions; route
+those through \`specrails_support\` instead.
 
 1. Check the backlog for duplicates first: \`specrails_specs(list)\`.
 2. Capture the work as a spec — pick the right creation path (next section).
@@ -337,6 +372,11 @@ summary later.
   is explicit, covering Jira projects whose Review status has not been mapped to
   Specrails \`on_review\`. You do NOT need to know or pass the branch name. If
   there is no confident open PR match, the normal new-work flow is preserved.
+- A published PR card (\`decision:'pr_ready'\`) is STILL an open PR continuation
+  target, not a blocker. If the user asks for modifications on that PR, assign
+  the same spec(s) to a rail and launch again; do NOT tell them they must publish,
+  discard, or merge first. \`pr_decision_pending\` should only block unresolved
+  deliveries with no continuable PR head yet.
 - Launch proposal shape: tickets (ids + titles), rail number, mode, engine and
   model/profile, plus "runs for minutes and costs money". If the API mode is
   \`freestyle\`, write "Freestyle" to the user. Wait for yes.
@@ -350,9 +390,9 @@ summary later.
   tickets to the returned \`railIndex\`, and launch. Never wedge waiting for a
   slot and never steal a configured rail's tickets to free one.
 - **Launching many rails**: \`specrails_rails(launch_all)\` launches every rail
-  that has tickets and no active run / pending PR decision in ONE call, each
-  with its own stored mode/engine/profile, and returns per-rail outcomes
-  (launched / skipped with reason / failed) — report them per rail. It is
+  that has tickets and no active run / uncontinuable pending PR decision in ONE
+  call, each with its own stored mode/engine/profile, and returns per-rail
+  outcomes (launched / skipped with reason / failed) — report them per rail. It is
   ai-spawn: propose it with the total rail + spec count and cost framing
   first. One yes covers the whole batch when the user asked for the batch
   ("launch everything") — do not re-ask per rail.
@@ -431,4 +471,4 @@ When the user has no projects yet, or asks to add one:
 Setup is QUICK-only (fast, offline). Do NOT offer, mention, or attempt a "full"
 or "enrich" install — that flow is deprecated and not available through you.
 `;
-exports.OPERATOR_SYSTEM_PROMPT = `You are the Specrails operator agent, embedded inside the Specrails Desktop app; drive it on the user's behalf using the specrails_* MCP tools. Your full operator manual is the CLAUDE.md auto-loaded from your working directory — follow it. Non-negotiables: target a project with specrails_select_project or the projectId argument, and ask rather than guess when none is pinned; short async 202 ops (spec generation, ai-edit) may be awaited with specrails_watch (projectId required), but after a rail/job LAUNCH is accepted end your reply immediately — progress streams live in the conversation's run card and the app; watch a launched run only when the user explicitly asks you to wait, with a bounded untilMs; never claim success from a 202 acceptance alone — verify from a terminal event or a domain read (e.g. specrails_jobs get); call the free-form autonomous rail mode Freestyle in prose — freestyle/factory:freestyle/{{cmd:freestyle}} are canonical API/id/token values for that same capability; respect the cumulative permission ladder observe / edit / operate / autonomous — if a tool is refused, name the level the user must Shift+Tab to, never work around it; when refining a spec, ground it in the real codebase FIRST (specrails_code tree/read_file/summary + specrails_specs list) and show the evolving draft as one fenced spec-draft JSON block (title, description, labels, priority, acceptanceCriteria) at the end of each turn that changed it — the app renders it as a live card; persist the refined spec with specrails_specs commit_draft (no conversationId) — never route it through create/generate, which regenerate the content with AI; commit_draft appends a Contract Layer by default via one short background AI pass — pass contractRefine false when the user declines it; report tool outputs faithfully, including failures. Format replies for easy reading: short paragraphs separated by blank lines, bullet lists for enumerations. When asking the user to pick between concrete choices, end the reply with a fenced options code block containing a JSON array of the 2-6 choice labels (rendered as clickable chips); never use that block otherwise.`;
+exports.OPERATOR_SYSTEM_PROMPT = `You are the Specrails operator agent, embedded inside the Specrails Desktop app; drive it on the user's behalf using the specrails_* MCP tools. Your full operator manual is the CLAUDE.md auto-loaded from your working directory — follow it. Non-negotiables: target a project with specrails_select_project or the projectId argument, and ask rather than guess when none is pinned; support/troubleshooting/install/usage/job-failure questions use specrails_support first and never become specs unless the user pivots to product work; missing agents/skills/slash commands concern the app-global specrails-core framework, never project-owned files — never say agents/skills/commands live inside the project; project setup checkpoints are not a core health signal, so pending/0 agents/0 commands must not trigger specrails_setup(install) or a project repair recommendation; offer core_update_check/core_update_apply only for global core updates, and if global core is current ask for the concrete job error/diagnostic; an on_review spec with an open PR, including a published pr_ready card, can be relaunched to continue that PR branch — do not require publish/discard/merge first; short async 202 ops (spec generation, ai-edit) may be awaited with specrails_watch (projectId required), but after a rail/job LAUNCH is accepted end your reply immediately — progress streams live in the conversation's run card and the app; watch a launched run only when the user explicitly asks you to wait, with a bounded untilMs; never claim success from a 202 acceptance alone — verify from a terminal event or a domain read (e.g. specrails_jobs get); call the free-form autonomous rail mode Freestyle in prose — freestyle/factory:freestyle/{{cmd:freestyle}} are canonical API/id/token values for that same capability; respect the cumulative permission ladder observe / edit / operate / autonomous — if a tool is refused, name the level the user must Shift+Tab to, never work around it; when refining a spec, ground it in the real codebase FIRST (specrails_code tree/read_file/summary + specrails_specs list) and show the evolving draft as one fenced spec-draft JSON block (title, description, labels, priority, acceptanceCriteria) at the end of each turn that changed it — the app renders it as a live card; persist the refined spec with specrails_specs commit_draft (no conversationId) — never route it through create/generate, which regenerate the content with AI; commit_draft appends a Contract Layer by default via one short background AI pass — pass contractRefine false when the user declines it; report tool outputs faithfully, including failures. Format replies for easy reading: short paragraphs separated by blank lines, bullet lists for enumerations. When asking the user to pick between concrete choices, end the reply with a fenced options code block containing a JSON array of the 2-6 choice labels (rendered as clickable chips); never use that block otherwise.`;

package/server/dist/desktop-router.js

@@ -64,7 +64,11 @@ function isGeminiBetaDisabled() {
 }
 // Theme allow-list. Mirror of THEME_IDS in `client/src/lib/themes.ts` —
 // kept duplicated to avoid pulling client code into the server bundle.
-const THEME_ID_ALLOWLIST = new Set(['dracula', 'aurora-light', 'obsidian-dark', 'matrix', 'specrails']);
+const THEME_ID_ALLOWLIST = new Set(['dracula', 'aurora-light', 'obsidian-dark', 'code-rain', 'specrails', 'galaxy']);
+const LEGACY_THEME_ID_MAP = {
+    'star-wars': 'galaxy',
+    matrix: 'code-rain',
+};
 // Language allow-list. Mirror of LANGUAGE_IDS in `client/src/lib/i18n.ts` —
 // kept duplicated to avoid pulling client code into the server bundle.
 const LANGUAGE_ID_ALLOWLIST = new Set(['en', 'es', 'fr', 'de', 'pt', 'it', 'zh', 'ja']);
@@ -840,7 +844,10 @@ function createDesktopRouter(registry, broadcast) {
     // Persisted under desktop_settings key `ui_theme`. Default seeded by migration 8.
     router.get('/theme', (_req, res) => {
         const stored = (0, desktop_db_1.getDesktopSetting)(registry.desktopDb, 'ui_theme');
-        const theme = stored && THEME_ID_ALLOWLIST.has(stored) ? stored : 'specrails';
+        const migrated = stored ? LEGACY_THEME_ID_MAP[stored] : undefined;
+        const theme = migrated ?? (stored && THEME_ID_ALLOWLIST.has(stored) ? stored : 'specrails');
+        if (migrated)
+            (0, desktop_db_1.setDesktopSetting)(registry.desktopDb, 'ui_theme', migrated);
         res.json({ theme });
     });
     router.patch('/theme', (req, res) => {

package/server/dist/mcp/guide.js

@@ -53,6 +53,13 @@ Codex, Gemini) to implement specs.
 
 ## Creating specs — three paths, one decision rule
 
+Before creating a spec, classify the user's intent. If they are asking for
+help using Specrails, installation/setup, a failed job, missing agents/skills,
+MCP connection, provider auth, GitHub/PR delivery, costs, or "how do I...?"
+support, DO NOT create a spec. Call \`specrails_support(action:'triage')\`
+and solve it conversationally first. Only move to spec creation when the user
+explicitly asks for product/backlog work.
+
 1. **Quick (AI-generated)** — \`specrails_specs(action:'generate', idea, …)\`, or
    the simpler \`create\` with title/description: routes through the app's Quick
    Add Spec — an AI pass structures the request into a complete spec, so
@@ -105,15 +112,20 @@ heading inside the description); \`labels\`; \`priority\`. Spec content is Engli
   other work, create one and proceed; never wait for a slot.
 - Parallel launches are safe and normal: each launch isolates its work in
   per-ticket git worktrees, so several rails can run at once. \`launch_all\`
-  (ai-spawn) launches EVERY rail that has tickets and no active run / pending
-  PR decision in one call, each with its stored mode/engine/profile, returning
-  per-rail outcomes (launched / skipped with reason / failed).
+  (ai-spawn) launches EVERY rail that has tickets and no active run /
+  uncontinuable pending PR decision in one call, each with its stored
+  mode/engine/profile, returning per-rail outcomes (launched / skipped with
+  reason / failed).
 - Relaunching an \`on_review\` ticket with a matching OPEN GitHub PR continues
   that PR's head branch automatically. Jira-linked \`in_progress\` tickets can
   also continue an open PR when the match is explicit, covering Jira projects
   whose Review status has not been mapped to Specrails \`on_review\`. New
   tickets, or tickets without a confident open-PR match, keep the normal
   branch-from-integration flow.
+- A published PR delivery (\`decision:'pr_ready'\`) is still an open PR
+  continuation target when it has a PR URL/head branch covering the rail's
+  tickets. Do not tell the user to Publish/Discard/Merge first when they ask for
+  more changes on that same PR; assign the spec(s) to a rail and launch again.
 - Projects without Git cannot use isolated worktrees or PR continuation. A
   launch degrades to shared-cwd execution and returns \`isolationUnavailable\`;
   explain that it writes directly to files and no PR card/branch will appear.
@@ -171,7 +183,10 @@ Tools cannot raise their own permissions in either regime. Common tiers:
 list/get/spending/watch = read; commit_draft, from_prompt, update, set_tickets,
 create_rail, plugin install, Jira connect = write; spec create/generate, rail
 launch/launch_all, chat send, job spawn = ai-spawn; spec delete, rail stop, job
-purge, plugin uninstall, Jira disconnect, project unregister = destructive. Note the
+purge, plugin uninstall, Jira disconnect, project unregister = destructive.
+\`specrails_support(triage/core_update_status/core_update_check)\` is read;
+\`specrails_support(core_update_apply)\` is ai-spawn because it runs longer
+global update work. Note the
 embedded spec-refinement happy path (investigate + commit_draft) needs only
 read + write — ai-spawn is required only to launch work or spawn a nested AI.
 
@@ -216,6 +231,20 @@ read + write — ai-spawn is required only to launch work or spawn a nested AI.
   \`install_config\` per provider → ONE \`install\` (provisions all chosen
   providers; quick-only, offline) → poll \`checkpoints\` until
   \`isInstalling === false\`.
+- **Support** (\`specrails_support\`): use FIRST for installation/usage help,
+  provider CLI/auth, MCP/Agent Chat issues, missing agents/skills/commands,
+  failed jobs, PR delivery confusion, costs, and plugin questions. It returns a
+  support playbook plus local diagnostics and never creates specs. When a job
+  says agents, skills, or slash commands are missing, explain that upstream
+  definitions live in the APP-GLOBAL specrails-core framework, not inside the
+  project. For specrails-core installation questions, project setup checkpoints
+  are NOT a health signal: pending checkpoints or 0 agents/commands do not prove
+  a core problem and must not trigger \`specrails_setup(install)\`. If global
+  core is stale, offer \`core_update_check\` + \`core_update_apply\`. If global
+  core is current but a real job still reports missing core definitions, ask for
+  the job error/diagnostic and give the manual fallback for standalone/legacy
+  core installs: from the project root, run \`npx specrails-core@latest update\`,
+  then retry the job.
 - **Loops lifecycle** (\`specrails_loops\`): Draft → \`publish\` (graph-validated)
   → runnable; \`update\` reverts to Draft and returns 409 while running;
   \`preview\` dry-runs token resolution without spawning; constants are shared

package/server/dist/mcp/tools/app-settings.js

@@ -8,8 +8,12 @@ const mcp_tiers_1 = require("../mcp-tiers");
 // permission-tier toggles are intentionally NOT writable here — an external LLM
 // must never be able to escalate its own permissions. Those are user-only,
 // changed in the Settings ▸ MCP panel.
-const WRITABLE_THEMES = ['specrails', 'dracula', 'aurora-light', 'obsidian-dark', 'matrix'];
+const WRITABLE_THEMES = ['specrails', 'dracula', 'aurora-light', 'obsidian-dark', 'code-rain', 'galaxy'];
 const WRITABLE_LANGS = ['en', 'es', 'fr', 'de', 'pt', 'it', 'zh', 'ja'];
+const LEGACY_THEME_ID_MAP = {
+    'star-wars': 'galaxy',
+    matrix: 'code-rain',
+};
 function appTools() {
     return [
         {
@@ -44,8 +48,9 @@ function appTools() {
             handler: (ctx, args) => {
                 const db = ctx.desktopDb;
                 if (args.action === 'get') {
+                    const theme = normalizeStoredTheme(db);
                     return {
-                        theme: (0, desktop_db_1.getDesktopSetting)(db, 'ui_theme') ?? 'specrails',
+                        theme,
                         language: (0, desktop_db_1.getDesktopSetting)(db, 'ui_language') ?? null,
                         dailyBudgetUsd: num((0, desktop_db_1.getDesktopSetting)(db, 'desktop_daily_budget_usd')),
                         costAlertThresholdUsd: num((0, desktop_db_1.getDesktopSetting)(db, 'cost_alert_threshold_usd')),
@@ -102,6 +107,17 @@ function appTools() {
         },
     ];
 }
+function normalizeStoredTheme(db) {
+    const stored = (0, desktop_db_1.getDesktopSetting)(db, 'ui_theme');
+    if (!stored)
+        return 'specrails';
+    const migrated = LEGACY_THEME_ID_MAP[stored];
+    if (migrated) {
+        (0, desktop_db_1.setDesktopSetting)(db, 'ui_theme', migrated);
+        return migrated;
+    }
+    return WRITABLE_THEMES.includes(stored) ? stored : 'specrails';
+}
 function num(v) {
     if (v === undefined)
         return null;

package/server/dist/mcp/tools/catalog.js

@@ -17,6 +17,7 @@ const code_1 = require("./code");
 const setup_1 = require("./setup");
 const analytics_1 = require("./analytics");
 const git_1 = require("./git");
+const support_1 = require("./support");
 /**
  * The full MCP tool catalog. Domain-facade tools each expose an `action` enum
  * and call the app's REST API over loopback (see apiCall). Meta tools receive a
@@ -41,6 +42,7 @@ function buildToolSpecs() {
     specs.push(...(0, setup_1.setupTools)());
     specs.push(...(0, analytics_1.analyticsTools)());
     specs.push(...(0, git_1.gitTools)());
+    specs.push(...(0, support_1.supportTools)());
     // Meta last (needs the full list for search/describe)
     specs.push(...(0, meta_1.metaTools)(() => specs));
     return specs;

package/server/dist/mcp/tools/rails.js

@@ -7,6 +7,26 @@ const types_1 = require("./types");
  *  efforts outside it (codex 'minimal', claude 'xhigh') are never defaulted —
  *  a default must not 400 a launch that would succeed without it. */
 const RAIL_REASONING_EFFORTS = new Set(['low', 'medium', 'high']);
+function isRecord(value) {
+    return typeof value === 'object' && value !== null && !Array.isArray(value);
+}
+function prDeliveryContinuesTickets(raw, ticketIds) {
+    if (!isRecord(raw))
+        return false;
+    const decision = raw.decision;
+    if (decision !== 'pr_draft' && decision !== 'pr_ready')
+        return false;
+    if (typeof raw.prUrl !== 'string' || !raw.prUrl)
+        return false;
+    if (typeof raw.branch !== 'string' || !raw.branch)
+        return false;
+    if (raw.prState !== 'pr-created')
+        return false;
+    if (!Array.isArray(raw.ticketIds))
+        return false;
+    const covered = new Set(raw.ticketIds.filter((id) => typeof id === 'number'));
+    return ticketIds.length > 0 && ticketIds.every((id) => covered.has(id));
+}
 /**
  * Rails domain facade. A "rail" is a numbered launch slot per project: it holds
  * a set of assigned ticket IDs plus a mode/profile/engine/name, and launching it
@@ -27,9 +47,9 @@ function railsTools() {
                 'Actions: list (rails + active jobs/loop runs), create_rail (add a new rail slot; returns its railIndex), set_tickets (assign ticket IDs), set_profile (default agent profile, null=legacy), ' +
                 'set_engine (provider override, null=primary), set_name (display label, null clears), ' +
                 'launch (ai-spawn — spawns claude/codex/gemini CLI job(s) that WRITE CODE, RUN TESTS, COMMIT, and INCUR TOKEN COST; returns 202 with jobId/jobIds/loopRunIds), ' +
-                'launch_all (ai-spawn — launches EVERY rail that has tickets and no active run/pending PR decision, in parallel, using each rail\'s stored mode/engine/profile; returns per-rail outcomes with skip reasons), ' +
+                'launch_all (ai-spawn — launches EVERY rail that has tickets and no active run/uncontinuable pending PR decision, in parallel, using each rail\'s stored mode/engine/profile; returns per-rail outcomes with skip reasons), ' +
                 'stop (destructive — kills all active jobs and loop runs for the rail). ' +
-                'For on_review tickets with an already-open GitHub PR, launch automatically tries to continue that PR head branch; Jira-linked in_progress tickets can do the same when the PR match is explicit; fresh tickets still start from the project integration branch. ' +
+                'For on_review tickets with an already-open GitHub PR (including a published pr_ready delivery), launch automatically tries to continue that PR head branch; Jira-linked in_progress tickets can do the same when the PR match is explicit; fresh tickets still start from the project integration branch. ' +
                 'When launched from the in-app agent chat without an explicit aiEngine, the engine defaults to your conversation\'s provider (pass aiEngine to override; launch_all always uses each rail\'s stored engine). ' +
                 'User-facing naming: call the free-form autonomous mode "Freestyle"; use "freestyle" as the canonical API enum value for that same capability. ' +
                 'NAMING: railIndex is the 0-BASED internal identity; the dashboard shows rails 1-based ("Rail N" = railIndex N-1). When talking to the user, ALWAYS say "Rail <railIndex + 1>" (or the rail\'s custom name) — results include railLabel with the correct user-facing label.',
@@ -236,7 +256,7 @@ function railsTools() {
                         return {
                             ...r,
                             railLabel,
-                            hint: `Launch accepted (202) on ${railLabel} (isolated worktree, PR flow active) — tell the user it runs on "${railLabel}" (UI labels are 1-based). If the assigned spec is on_review with a matching open PR, or is Jira-linked in_progress with an explicit PR match, Specrails continues that PR branch automatically; otherwise it starts a fresh branch from the integration branch. The PR-decision card will appear here and on the rail header when it settles. Use specrails_watch with the returned loopRunIds to await completion only if asked. Rails run for minutes; pass untilMs up to 600000 and re-watch on timeout.`,
+                            hint: `Launch accepted (202) on ${railLabel} (isolated worktree, PR flow active) — tell the user it runs on "${railLabel}" (UI labels are 1-based). If the assigned spec is on_review with a matching open PR, including an already-published pr_ready PR, or is Jira-linked in_progress with an explicit PR match, Specrails continues that PR branch automatically; otherwise it starts a fresh branch from the integration branch. The PR-decision card will appear here and on the rail header when it settles. Use specrails_watch with the returned loopRunIds to await completion only if asked. Rails run for minutes; pass untilMs up to 600000 and re-watch on timeout.`,
                         };
                     }
                     case 'launch_all': {
@@ -244,8 +264,9 @@ function railsTools() {
                         // because each launch isolates its work in per-ticket git worktrees
                         // (allocation is serialized per repo by the launch path itself).
                         // Eligibility mirrors the dashboard's Launch-all control: the rail
-                        // must hold tickets, have no active job/loop run, and no undecided
-                        // PR delivery. Each rail launches with its OWN stored config
+                        // must hold tickets, have no active job/loop run, and no uncontinuable
+                        // PR delivery. A draft/published PR covering the rail's tickets is
+                        // intentionally continuable. Each rail launches with its OWN stored config
                         // (mode/engine/profile) — conversation-provider defaults do NOT
                         // apply here (they would clobber per-rail engines).
                         const snapshot = (await (0, types_1.apiCall)(ctx, 'GET', base));
@@ -267,7 +288,7 @@ function railsTools() {
                                 results.push({ railIndex: idx, outcome: 'skipped', reason: 'already-running', ticketIds });
                                 continue;
                             }
-                            if (key in prDeliveries) {
+                            if (key in prDeliveries && !prDeliveryContinuesTickets(prDeliveries[key], ticketIds)) {
                                 results.push({ railIndex: idx, outcome: 'skipped', reason: 'pr-decision-pending', ticketIds });
                                 continue;
                             }