specrails-desktop 2.48.0 → 2.49.0

package/client/dist/index.html

@@ -204,7 +204,7 @@
         .specrails-splash__mark .pill { opacity: 1; }
       }
     </style>
-    <script type="module" crossorigin src="/assets/index-DORCrgbI.js"></script>
+    <script type="module" crossorigin src="/assets/index-CjAPu3wb.js"></script>
     <link rel="modulepreload" crossorigin href="/assets/rolldown-runtime-CNC7AqOf.js">
     <link rel="modulepreload" crossorigin href="/assets/jsx-runtime-zu2_FqZY.js">
     <link rel="modulepreload" crossorigin href="/assets/react-dom-DiWzBDP9.js">
@@ -212,7 +212,7 @@
     <link rel="modulepreload" crossorigin href="/assets/chunk-KS7C4IRE-DEKu087k.js">
     <link rel="modulepreload" crossorigin href="/assets/activity-DiyjsgQV.js">
     <link rel="modulepreload" crossorigin href="/assets/addspec-BOvgmcgk.js">
-    <link rel="modulepreload" crossorigin href="/assets/agent-Bh9K7iEt.js">
+    <link rel="modulepreload" crossorigin href="/assets/agent-BIO4q6b0.js">
     <link rel="modulepreload" crossorigin href="/assets/agentRuntime-bAAjw1vw.js">
     <link rel="modulepreload" crossorigin href="/assets/agents-CTwbx-fb.js">
     <link rel="modulepreload" crossorigin href="/assets/agentstudio-CN2pokQu.js">
@@ -234,22 +234,22 @@
     <link rel="modulepreload" crossorigin href="/assets/mcp-CUAN6ORK.js">
     <link rel="modulepreload" crossorigin href="/assets/narration-n3hOA7LY.js">
     <link rel="modulepreload" crossorigin href="/assets/nav-Ch-zHBG5.js">
-    <link rel="modulepreload" crossorigin href="/assets/packet-_m5aOy_d.js">
+    <link rel="modulepreload" crossorigin href="/assets/packet-BTRySHoQ.js">
     <link rel="modulepreload" crossorigin href="/assets/settings-HZSu-K4l.js">
     <link rel="modulepreload" crossorigin href="/assets/setup-DpqzaEEA.js">
     <link rel="modulepreload" crossorigin href="/assets/specs-DII0C8gw.js">
     <link rel="modulepreload" crossorigin href="/assets/terminal-BAzpHtpY.js">
     <link rel="modulepreload" crossorigin href="/assets/tickets-W6pBmbrX.js">
     <link rel="modulepreload" crossorigin href="/assets/createLucideIcon-Bjbbp_KS.js">
-    <link rel="modulepreload" crossorigin href="/assets/useSharedWebSocket-BHIfW4QT.js">
-    <link rel="modulepreload" crossorigin href="/assets/Trans-9pHTy2fH.js">
-    <link rel="modulepreload" crossorigin href="/assets/useDesktop-CAisjKWC.js">
+    <link rel="modulepreload" crossorigin href="/assets/useSharedWebSocket-BN3Lmehi.js">
+    <link rel="modulepreload" crossorigin href="/assets/Trans-BLljsfHR.js">
+    <link rel="modulepreload" crossorigin href="/assets/useDesktop-BJ8IRBRt.js">
     <link rel="modulepreload" crossorigin href="/assets/provider-capabilities-Vi1ZGvAK.js">
     <link rel="modulepreload" crossorigin href="/assets/save-B6wGWwBR.js">
-    <link rel="modulepreload" crossorigin href="/assets/spending-hcgxHP4O.js">
+    <link rel="modulepreload" crossorigin href="/assets/spending-DJBbdJyD.js">
     <link rel="modulepreload" crossorigin href="/assets/sparkles-DrY8hb0X.js">
     <link rel="modulepreload" crossorigin href="/assets/x-CBMI9ejn.js">
-    <link rel="modulepreload" crossorigin href="/assets/MinimizedChatsContext-UpnqccPx.js">
+    <link rel="modulepreload" crossorigin href="/assets/MinimizedChatsContext-CX1i2kQ8.js">
     <link rel="modulepreload" crossorigin href="/assets/circle-x-CMYsN4ZH.js">
     <link rel="modulepreload" crossorigin href="/assets/download-CFHyyHcw.js">
     <link rel="modulepreload" crossorigin href="/assets/file-text-CFT-xXKN.js">
@@ -267,18 +267,18 @@
     <link rel="modulepreload" crossorigin href="/assets/utils-BC4DHlz2.js">
     <link rel="modulepreload" crossorigin href="/assets/dialog-xXB2q5HJ.js">
     <link rel="modulepreload" crossorigin href="/assets/lib-CGdyxIWg.js">
-    <link rel="modulepreload" crossorigin href="/assets/getTimezoneOffsetInMilliseconds-BRymg1Kk.js">
-    <link rel="modulepreload" crossorigin href="/assets/formatDistanceToNow-w_2U5pm0.js">
+    <link rel="modulepreload" crossorigin href="/assets/getTimezoneOffsetInMilliseconds-pBVK3rJC.js">
+    <link rel="modulepreload" crossorigin href="/assets/formatDistanceToNow-CbQZkD8M.js">
     <link rel="modulepreload" crossorigin href="/assets/button-Ccc9Dc-D.js">
-    <link rel="modulepreload" crossorigin href="/assets/jira-api-BqHbSdxK.js">
-    <link rel="modulepreload" crossorigin href="/assets/project-repositories-BsCs1PPA.js">
-    <link rel="modulepreload" crossorigin href="/assets/RepositoryScopeSelector-0Gz_fR1E.js">
-    <link rel="modulepreload" crossorigin href="/assets/TicketDetailModalContext-C5GgJlEt.js">
+    <link rel="modulepreload" crossorigin href="/assets/jira-api-f-sYCIuX.js">
+    <link rel="modulepreload" crossorigin href="/assets/project-repositories-DAjJbFhm.js">
+    <link rel="modulepreload" crossorigin href="/assets/RepositoryScopeSelector-DG8KKPrm.js">
+    <link rel="modulepreload" crossorigin href="/assets/TicketDetailModalContext-D2MEhRwJ.js">
     <link rel="modulepreload" crossorigin href="/assets/core-B3mKBIh5.js">
-    <link rel="modulepreload" crossorigin href="/assets/RepositoryDeliveries-C36ipKp_.js">
-    <link rel="modulepreload" crossorigin href="/assets/format-duration-NJVPOPBG.js">
+    <link rel="modulepreload" crossorigin href="/assets/RepositoryDeliveries-DqmlG0Zs.js">
+    <link rel="modulepreload" crossorigin href="/assets/useRuntimeRuns-Ch1KUc7k.js">
     <link rel="modulepreload" crossorigin href="/assets/event-Bt7f3wXe.js">
-    <link rel="stylesheet" crossorigin href="/assets/index-D0ScFZvR.css">
+    <link rel="stylesheet" crossorigin href="/assets/index-UDzndadF.css">
   </head>
   <body>
     <div id="specrails-splash" aria-hidden="false" role="status" aria-label="Loading Specrails">

package/docs/guide/de/integrations/6-agent-chat.md

@@ -70,6 +70,14 @@ Antworten strömen flüssig herein und landen bereits formatiert (Überschriften
 - **Missionen wechseln.** Der Missions-Selektor neben dem Projekt-Selektor listet deine Unterhaltungen von neu nach alt — ein pulsierender Punkt markiert die, an denen der Agent noch arbeitet, und ein kleines Badge zählt die Nachrichten in der Warteschlange. Die Suche erscheint, sobald die Liste mehr als acht Einträge hat, und das Papierkorb-Symbol jeder Zeile löscht eine Mission nach einer kurzen Inline-Bestätigung — auch eine laufende (es warnt zuerst und stoppt dann den Agenten).
 - **Eine Mission von überall finden.** Drücke **⌘K** (oder den **Suchen**-Button in der Seitenleiste im Agent-Modus) und tippe irgendein Fragment, an das du dich erinnerst — ein Wort aus dem Titel *oder* aus dem, was darin gesagt wurde. Missionen treffen sofort per Titel aus dem Speicher, einen Herzschlag später kommen die Inhaltstreffer mit hervorgehobener Passage dazu, plus angepinntes Projekt und letzte Aktivität. Im Agent-Modus sind Missionen die erste Gruppe; auf dem Board stehen sie direkt nach den Projekten. Enter öffnet die Mission.
 
+## Launch-Karten und Run-Karten
+
+- **Der Agent schlägt vor, du drückst Play.** Bitte ihn, Specs auf ein Rail zu legen („bereite #12 und #14 auf einem Rail vor“), und statt es zu beschreiben, gibt er dir eine **Launch-Karte**: das Rail (oder ein neues), die Specs, Engine, Modell, Aufwand, Profil, Loop, optional Ziel-PR und Basis-Branch — alles mit seiner Empfehlung vorausgefüllt und alles editierbar. Ändere, was du willst, und drücke **Play**. Sagst du „starte es jetzt“, startet er direkt.
+- **Eine Karte begleitet den Run.** Nach Play friert der Vorschlag als „Gestartet → Rail N“ ein und eine **Run-Karte** übernimmt: Status, verstrichene Zeit, was die Pipeline gerade tut, Log-Button und Stopp. Ist die Arbeit bereit zur Prüfung, wird dieselbe Karte zur bekannten PR-Karte (PR erstellen, lokal integrieren, verwerfen).
+- **Fehler melden sich.** Schlägt ein Run fehl oder bleibt er hängen, zeigt die Karte den Grund im Klartext und bietet die echten Optionen — Fortsetzen, Wiederherstellen, Freigeben, Neu starten, Verwerfen — und der Agent postet ein kurzes Briefing, was passiert ist und was er empfiehlt. Er setzt nie von allein fort oder startet neu; du entscheidest über die Karte.
+- **Ohne Git keine PR-Phase.** Ein Projekt ohne Git-Repository (oder ohne Commits) bekommt trotzdem eine Run-Karte — Fortschritt, Log, Fehler und Wiederherstellung —, aber es gibt keinen Branch und keinen PR-Schritt; die Karte sagt das.
+- **`@rail-N`.** Tippe `@` und wähle ein Rail, um es in deiner Nachricht zu referenzieren, mit seinen Specs und ob es frei, belegt oder in Entscheidung ist.
+
 ## Ein paar Dinge, die du wissen solltest
 
 - **Ausführen und Autonom kosten Geld**, weil sie KI laufen lassen. Der Agent hebt kostenverursachende Aktionen hervor, bevor er sie ausführt; belasse die Stufe bei Beobachten oder Bearbeiten, wenn du nur schauen und aufräumen willst.

package/docs/guide/en/integrations/6-agent-chat.md

@@ -75,6 +75,14 @@ Replies stream in smoothly and land formatted (headings, tables, lists), each wi
 - **Switch missions.** The mission selector next to the project picker lists your conversations newest-first — a pulsing dot marks the ones where the agent is still working, and a small badge counts queued messages. Search appears when the list grows past eight, and the trash icon on each row deletes a mission after a quick inline confirm — even a running one (it warns first, then stops the agent).
 - **Find a mission from anywhere.** Press **⌘K** (or the sidebar **Search** button in Agent Mode) and type any fragment you remember — a word from the title *or* from what was said inside. Missions match instantly by title from memory, and a heartbeat later the matches by content arrive with the matching passage highlighted, plus the pinned project and when it was last active. In Agent Mode missions are the first group; on the board they sit right after Projects. Enter opens the mission.
 
+## Rail launch cards and run cards
+
+- **Propose, then you press Play.** Ask the agent to put specs on a rail ("prepare #12 and #14 for a rail") and, instead of describing it, it hands you a **launch card**: the rail (or a brand-new one), the specs, engine, model, effort, profile, loop, optional target PR and base branch — all pre-filled with its recommendation and all editable. Change what you like and press **Play**. Say "launch it now" and it launches directly instead.
+- **One card follows the run.** After Play the proposal freezes into a "Launched → Rail N" stub and a **run card** takes over: status, elapsed time, what the pipeline is doing, a log button and Stop. When the work is ready to review, the same card becomes the familiar PR card (create the PR, integrate locally, discard).
+- **Failures speak up.** If a run fails or stalls, the card shows the reason in plain text and offers the real options — Resume, Recover, Approve, Relaunch, Discard — and the agent posts a short briefing explaining what happened and what it recommends. It never resumes or relaunches on its own; you decide from the card.
+- **No git, no PR phase.** A project without a git repository (or without commits) still gets a run card — progress, log, failure and recovery — but there is no branch and no PR step; the card says so.
+- **`@rail-N`.** Type `@` and pick a rail to reference it in your message, with its specs and whether it is free, busy or awaiting a decision.
+
 ## A few things to know
 
 - **Operate and Autonomous cost money** because they run AI. The agent surfaces cost-incurring actions before doing them; keep the level at Observe or Edit if you just want to look and tidy.

package/docs/guide/es/integrations/6-agent-chat.md

@@ -70,6 +70,14 @@ Las respuestas llegan fluidas y ya formateadas (encabezados, tablas, listas), ca
 - **Cambia de misión.** El selector de misiones junto al selector de proyecto lista tus conversaciones de más reciente a más antigua — un punto pulsante marca aquellas donde el agente sigue trabajando, y una pequeña insignia cuenta los mensajes en cola. La búsqueda aparece cuando la lista supera las ocho, y el icono de papelera de cada fila elimina una misión tras una confirmación rápida en línea — incluso una en marcha (avisa primero y luego detiene al agente).
 - **Encuentra una misión desde cualquier sitio.** Pulsa **⌘K** (o el botón **Buscar** del sidebar en modo Agente) y escribe cualquier fragmento que recuerdes: una palabra del título *o* de lo que se dijo dentro. Las misiones coinciden al instante por título desde memoria y, un latido después, llegan las coincidencias por contenido con el pasaje resaltado, más el proyecto anclado y cuándo tuvo actividad por última vez. En modo Agente las misiones son el primer grupo; en el tablero van justo después de Proyectos. Enter abre la misión.
 
+## Cards de lanzamiento y cards de ejecución
+
+- **El agente propone, tú pulsas Play.** Pídele que ponga specs en un rail ("prepara #12 y #14 en un rail") y, en vez de describirlo, te entrega una **card de lanzamiento**: el rail (o uno nuevo), las specs, motor, modelo, esfuerzo, perfil, loop, PR destino y rama base opcionales — todo prerrellenado con su recomendación y todo editable. Cambia lo que quieras y pulsa **Play**. Si dices "lánzalo ya", lo lanza directamente.
+- **Una sola card sigue la ejecución.** Tras Play la propuesta queda congelada como "Lanzado → Rail N" y una **card de ejecución** toma el relevo: estado, tiempo transcurrido, qué está haciendo el pipeline, botón de log y Detener. Cuando el trabajo está listo para revisar, esa misma card se convierte en la card de PR de siempre (crear PR, integrar en local, descartar).
+- **Los fallos hablan.** Si una ejecución falla o se atasca, la card muestra el motivo en texto claro y ofrece las opciones reales — Reanudar, Recuperar, Aprobar, Relanzar, Descartar — y el agente publica un breve informe explicando qué pasó y qué recomienda. Nunca reanuda ni relanza por su cuenta; decides tú desde la card.
+- **Sin git no hay fase de PR.** Un proyecto sin repositorio git (o sin commits) también tiene card de ejecución — progreso, log, fallo y recuperación — pero no hay rama ni paso de PR; la card lo indica.
+- **`@rail-N`.** Escribe `@` y elige un rail para referenciarlo en tu mensaje, con sus specs y si está libre, ocupado o pendiente de decisión.
+
 ## Algunas cosas que conviene saber
 
 - **Opera y Autónomo cuestan dinero** porque ejecutan IA. El agente saca a la luz las acciones que generan coste antes de hacerlas; mantén el nivel en Observa o Edita si solo quieres mirar y ordenar.

package/docs/guide/fr/integrations/6-agent-chat.md

@@ -70,6 +70,14 @@ Les réponses arrivent en flux fluide et s'affichent déjà mises en forme (titr
 - **Changez de mission.** Le sélecteur de missions, à côté du sélecteur de projet, liste vos conversations de la plus récente à la plus ancienne — un point clignotant signale celles où l'agent travaille encore, et un petit badge compte les messages en file. La recherche apparaît dès que la liste dépasse huit entrées, et l'icône corbeille de chaque ligne supprime une mission après une confirmation rapide en ligne — même une mission en cours (elle prévient d'abord, puis arrête l'agent).
 - **Retrouvez une mission de n'importe où.** Appuyez sur **⌘K** (ou le bouton **Rechercher** de la barre latérale en mode Agent) et tapez n'importe quel fragment dont vous vous souvenez — un mot du titre *ou* de ce qui a été dit dedans. Les missions correspondent instantanément par titre depuis la mémoire, puis un instant plus tard arrivent les correspondances par contenu avec le passage surligné, le projet épinglé et la date de dernière activité. En mode Agent, les missions forment le premier groupe ; sur le tableau, elles suivent les Projets. Entrée ouvre la mission.
 
+## Cartes de lancement et cartes d'exécution
+
+- **L'agent propose, vous appuyez sur Play.** Demandez-lui de placer des specs sur un rail (« prépare #12 et #14 sur un rail ») et, au lieu de le décrire, il vous remet une **carte de lancement** : le rail (ou un nouveau), les specs, moteur, modèle, effort, profil, loop, PR cible et branche de base optionnelles — tout prérempli avec sa recommandation et tout modifiable. Changez ce que vous voulez et appuyez sur **Play**. Dites « lance-le maintenant » et il lance directement.
+- **Une seule carte suit l'exécution.** Après Play, la proposition se fige en « Lancé → Rail N » et une **carte d'exécution** prend le relais : état, temps écoulé, ce que fait le pipeline, bouton de log et Arrêter. Quand le travail est prêt à relire, la même carte devient la carte PR habituelle (créer la PR, intégrer en local, abandonner).
+- **Les échecs parlent.** Si une exécution échoue ou se bloque, la carte affiche la raison en clair et propose les vraies options — Reprendre, Récupérer, Approuver, Relancer, Abandonner — et l'agent publie un court compte rendu expliquant ce qui s'est passé et ce qu'il recommande. Il ne reprend ni ne relance jamais seul ; vous décidez depuis la carte.
+- **Sans git, pas de phase PR.** Un projet sans dépôt git (ou sans commits) a quand même une carte d'exécution — progression, log, échec et récupération — mais il n'y a ni branche ni étape PR ; la carte le dit.
+- **`@rail-N`.** Tapez `@` et choisissez un rail pour le référencer dans votre message, avec ses specs et son état : libre, occupé ou en attente de décision.
+
 ## Quelques points à savoir
 
 - **Opérer et Autonome coûtent de l'argent** car ils exécutent de l'IA. L'agent met en avant les actions génératrices de coût avant de les réaliser ; gardez le niveau sur Observer ou Modifier si vous voulez juste regarder et ranger.

package/docs/guide/it/integrations/6-agent-chat.md

@@ -70,6 +70,14 @@ Le risposte arrivano fluide e già formattate (titoli, tabelle, elenchi), ciascu
 - **Cambia missione.** Il selettore di missioni accanto al selettore di progetto elenca le conversazioni dalla più recente alla più vecchia — un punto pulsante segnala quelle in cui l'agente sta ancora lavorando, e un piccolo badge conta i messaggi in coda. La ricerca compare quando la lista supera le otto voci, e l'icona del cestino su ogni riga elimina una missione dopo una rapida conferma in linea — anche una in corso (prima avvisa, poi ferma l'agente).
 - **Trova una missione da ovunque.** Premi **⌘K** (o il pulsante **Cerca** della barra laterale in modalità Agente) e digita un frammento qualsiasi che ricordi — una parola del titolo *o* di ciò che è stato detto dentro. Le missioni corrispondono all'istante per titolo dalla memoria e, un battito dopo, arrivano le corrispondenze per contenuto con il passaggio evidenziato, più il progetto fissato e l'ultima attività. In modalità Agente le missioni sono il primo gruppo; sulla board stanno subito dopo i Progetti. Invio apre la missione.
 
+## Card di lancio e card di esecuzione
+
+- **L'agente propone, tu premi Play.** Chiedigli di mettere delle spec su un rail ("prepara #12 e #14 su un rail") e, invece di descriverlo, ti consegna una **card di lancio**: il rail (o uno nuovo), le spec, engine, modello, sforzo, profilo, loop, PR di destinazione e branch base opzionali — tutto precompilato con la sua raccomandazione e tutto modificabile. Cambia ciò che vuoi e premi **Play**. Se dici "lancialo adesso", lancia direttamente.
+- **Una sola card segue l'esecuzione.** Dopo Play la proposta si congela come "Lanciato → Rail N" e una **card di esecuzione** prende il testimone: stato, tempo trascorso, cosa sta facendo la pipeline, pulsante log e Stop. Quando il lavoro è pronto per la revisione, la stessa card diventa la solita card PR (crea PR, integra in locale, scarta).
+- **I fallimenti parlano.** Se un'esecuzione fallisce o si blocca, la card mostra il motivo in chiaro e offre le opzioni reali — Riprendi, Recupera, Approva, Rilancia, Scarta — e l'agente pubblica un breve resoconto di cosa è successo e cosa consiglia. Non riprende né rilancia mai da solo; decidi tu dalla card.
+- **Senza git niente fase PR.** Un progetto senza repository git (o senza commit) ha comunque una card di esecuzione — progresso, log, fallimento e recupero — ma non c'è branch né passaggio PR; la card lo dice.
+- **`@rail-N`.** Digita `@` e scegli un rail per citarlo nel messaggio, con le sue spec e se è libero, occupato o in attesa di decisione.
+
 ## Alcune cose da sapere
 
 - **Opera e Autonomo costano denaro** perché eseguono IA. L'agente mette in evidenza le azioni che generano costi prima di eseguirle; tieni il livello su Osserva o Modifica se vuoi solo guardare e mettere in ordine.

package/docs/guide/ja/integrations/6-agent-chat.md

@@ -69,6 +69,14 @@ pure-output action は spawn 前に拒否されます。詳細は
 - **ミッションの切り替え。** プロジェクトセレクターの隣にあるミッションセレクターは、会話を新しい順に一覧表示します — 点滅するドットはエージェントがまだ作業中の会話を示し、小さなバッジはキュー内のメッセージ数を表します。リストが 8 件を超えると検索欄が現れます。各行のゴミ箱アイコンは、行内のクイック確認のあとにミッションを削除します — 実行中のものでも可能です（先に警告し、その後エージェントを停止します）。
 - **どこからでもミッションを探す。** **⌘K**（またはエージェントモードのサイドバーの **検索** ボタン）を押して、覚えている断片を入力してください——タイトルの単語でも、*中で話された内容* でも構いません。ミッションはまずメモリからタイトルで即座に一致し、一拍おいて内容による一致がハイライト付きで届き、固定されたプロジェクトと最終アクティビティも表示されます。エージェントモードではミッションが最初のグループ、ボードではプロジェクトの直後に並びます。Enter でミッションを開きます。
 
+## 起動カードと実行カード
+
+- **エージェントが提案し、あなたが Play を押す。** spec を rail に載せるよう頼むと（「#12 と #14 を rail に準備して」）、文章で説明する代わりに**起動カード**を渡してきます。rail（または新規 rail）、spec、エンジン、モデル、推論の深さ、プロファイル、loop、任意の対象 PR とベースブランチが、推奨値で事前入力され、すべて編集できます。好きに変えて **Play** を押してください。「今すぐ起動して」と言えば直接起動します。
+- **1 枚のカードが実行を追いかける。** Play の後、提案は「起動済み → Rail N」として固定され、**実行カード**が引き継ぎます。状態、経過時間、パイプラインが今していること、ログボタン、停止。作業がレビュー可能になると、同じカードがおなじみの PR カード（PR 作成、ローカル統合、破棄）になります。
+- **失敗は黙らない。** 実行が失敗または停止すると、カードが理由を平文で示し、本当に取れる選択肢——再開、復旧、承認、再起動、破棄——を提示し、エージェントは何が起きたか・何を勧めるかを短く報告します。勝手に再開や再起動はしません。決めるのはカード上のあなたです。
+- **git がなければ PR フェーズもない。** git リポジトリ（またはコミット）のないプロジェクトにも実行カードはあります——進捗、ログ、失敗と復旧——ただしブランチも PR ステップもありません。カードにそう書かれます。
+- **`@rail-N`。** `@` を入力して rail を選ぶと、その spec と状態（空き・使用中・決定待ち）付きでメッセージから参照できます。
+
 ## 知っておくとよいこと
 
 - **操作と自律は料金が発生します**。AI を実行するからです。エージェントは料金の発生する操作を実行する前に前面に示します。眺めて整理したいだけなら、レベルは観察か編集にしておいてください。

package/docs/guide/pt/integrations/6-agent-chat.md

@@ -69,6 +69,14 @@ As respostas chegam de forma fluida e já formatadas (títulos, tabelas, listas)
 - **Troque de missão.** O seletor de missões ao lado do seletor de projeto lista suas conversas da mais recente para a mais antiga — um ponto pulsante marca aquelas em que o agente ainda está trabalhando, e um pequeno selo conta as mensagens na fila. A busca aparece quando a lista passa de oito, e o ícone de lixeira de cada linha exclui uma missão após uma confirmação rápida em linha — mesmo uma em andamento (ele avisa primeiro e depois para o agente).
 - **Encontre uma missão de qualquer lugar.** Pressione **⌘K** (ou o botão **Pesquisar** da barra lateral no modo Agente) e digite qualquer fragmento de que se lembre — uma palavra do título *ou* do que foi dito lá dentro. As missões coincidem na hora por título a partir da memória e, um instante depois, chegam as coincidências por conteúdo com o trecho destacado, mais o projeto fixado e quando teve atividade pela última vez. No modo Agente as missões são o primeiro grupo; no quadro ficam logo depois de Projetos. Enter abre a missão.
 
+## Cards de lançamento e cards de execução
+
+- **O agente propõe, você aperta Play.** Peça para colocar specs em um rail ("prepara #12 e #14 em um rail") e, em vez de descrever, ele entrega um **card de lançamento**: o rail (ou um novo), as specs, engine, modelo, esforço, perfil, loop, PR de destino e branch base opcionais — tudo pré-preenchido com a recomendação dele e tudo editável. Mude o que quiser e aperte **Play**. Diga "lança agora" e ele lança direto.
+- **Um único card acompanha a execução.** Depois do Play a proposta congela como "Lançado → Rail N" e um **card de execução** assume: status, tempo decorrido, o que o pipeline está fazendo, botão de log e Parar. Quando o trabalho está pronto para revisar, o mesmo card vira o card de PR de sempre (criar PR, integrar localmente, descartar).
+- **Falhas falam.** Se uma execução falha ou trava, o card mostra o motivo em texto claro e oferece as opções reais — Retomar, Recuperar, Aprovar, Relançar, Descartar — e o agente publica um breve relato explicando o que aconteceu e o que recomenda. Ele nunca retoma nem relança sozinho; você decide pelo card.
+- **Sem git, sem fase de PR.** Um projeto sem repositório git (ou sem commits) também recebe um card de execução — progresso, log, falha e recuperação — mas não há branch nem etapa de PR; o card avisa.
+- **`@rail-N`.** Digite `@` e escolha um rail para referenciá-lo na mensagem, com suas specs e se está livre, ocupado ou aguardando decisão.
+
 ## Algumas coisas para saber
 
 - **Opera e Autônomo custam dinheiro** porque executam IA. O agente destaca as ações que geram custo antes de fazê-las; mantenha o nível em Observa ou Edita se você só quer olhar e organizar.

package/docs/guide/zh/integrations/6-agent-chat.md

@@ -68,6 +68,14 @@ spawn 前拒绝；详见 [Kimi matrix](../../../kimi.md)。
 - **切换任务。** 项目选择器旁的任务选择器按从新到旧列出你的对话——跳动的圆点标记代理仍在工作的对话，小徽章显示排队消息的数量。列表超过八条时会出现搜索框；每行的垃圾桶图标在快速的行内确认后删除任务——即使是正在运行的任务（会先警告，然后停止代理）。
 - **随时随地找到任务。** 按 **⌘K**（或代理模式下侧边栏的 **搜索** 按钮），输入你记得的任何片段——标题中的一个词，*或者* 对话里说过的内容。任务会立刻按标题从内存中匹配，紧接着按内容匹配的结果也会到达，并高亮匹配段落，同时显示固定的项目和最近活动时间。在代理模式下任务是第一组；在看板中紧跟在项目之后。按 Enter 打开任务。
 
+## 启动卡片与运行卡片
+
+- **代理提议，你按 Play。** 让它把 spec 放到某条 rail 上（"把 #12 和 #14 准备到一条 rail"），它不会用文字描述，而是给你一张**启动卡片**：rail（或新建一条）、spec、引擎、模型、推理强度、profile、loop，以及可选的目标 PR 和基础分支——全部按它的建议预填，全部可改。改好后按 **Play**。若你说"现在就启动"，它会直接启动。
+- **一张卡片跟随整个运行。** 按下 Play 后，提议冻结为"已启动 → Rail N"，一张**运行卡片**接管：状态、已用时间、流水线正在做什么、日志按钮和停止。工作可供审阅时，这张卡片会变成熟悉的 PR 卡片（创建 PR、本地集成、丢弃）。
+- **失败会说话。** 运行失败或卡住时，卡片以明文显示原因并提供真实选项——恢复、修复、批准、重新启动、丢弃——代理还会发布一段简短说明，解释发生了什么并给出建议。它绝不会自行恢复或重启；由你在卡片上决定。
+- **没有 git 就没有 PR 阶段。** 没有 git 仓库（或没有提交）的项目同样有运行卡片——进度、日志、失败与恢复——但没有分支也没有 PR 步骤；卡片会明确说明。
+- **`@rail-N`。** 输入 `@` 并选择一条 rail 即可在消息中引用它，附带其 spec 以及空闲、忙碌或待决定的状态。
+
 ## 一些需要知道的事
 
 - **操作和自主会产生费用**，因为它们运行 AI。智能体会在执行会产生费用的操作前把它们摆到明面上；如果你只想查看和整理，就把级别保持在观察或编辑。

package/docs/internals/mission-rail-cards.md

@@ -0,0 +1,130 @@
+# Mission rail cards — as-built record
+
+> OpenSpec change `mission-rail-cards` (2026-09-18), branch `feat/mission-rail-cards`. Companion to the CLAUDE.md section of the same name. Everything below is what the code on disk does; "deferred" means it does not.
+
+## The problem
+
+Mission mode (Agent Mode) replaces the routed dashboard, so `RailsBoard`, `SpecsBoard`, `RailRow` (with `RailPrDecisionStrip` and `AgentRuntimeRuns`) are never mounted there. The only object a mission had for an implementation run was the PR-decision card. On 2026-09-18 three gaps were verified:
+
+1. **No git ⇒ no object.** The shared-cwd launch path in `server/rails-router.ts` (`isolationUnavailable = 'no-git' | 'no-commits'`) never received `originConversationId`; no `rail_pr_deliveries` row, no card, only a `202 { isolationUnavailable }` the agent rarely mentioned.
+2. **Failure was mute.** `discarded` swallowed `statusDetail` (gated on `deliveryBlocked`); `implementation_failed` offered Discard only; no WS event wrote into the conversation or started a turn; `/agent-runtime/runs` (resume / approve / recover) was absent from MCP.
+3. **Assignment was prose.** Rails were not a palette entity; assigning specs meant dictating rail / engine / profile / loop in sentences, so users went to Board mode.
+
+## The card lifecycle
+
+```
+  agent turn                  user                      run                      settle
+┌──────────────┐   Play    ┌──────────────┐        ┌──────────────┐        ┌──────────────────────┐
+│ rail-launch  │ ────────▶ │ launched     │ ─────▶ │ running      │ ─────▶ │ settled              │
+│ (editable)   │  POST     │ stub in msg  │  card  │ status pill  │        │ ok → completed /     │
+│ Dismiss ─┐   │  /launch  │ + run card   │        │ elapsed      │        │      delivery phase  │
+└──────────┼───┘           └──────────────┘        │ log · Stop   │        │ fail → failure block │
+           ▼                                       └──────────────┘        │   Resume/Recover/    │
+     dismissed stub                                       │                │   Approve/Relaunch/  │
+                                                          │ failure        │   Discard/Dismiss    │
+                                                          ▼                └──────────────────────┘
+                                          notifyMissionRunFailure
+                                          card update + run-failure row
+                                          + ONE automatic briefing turn
+```
+
+- **Proposal** — an assistant message with one or more fenced `rail-launch` blocks. Each block is one `AgentRailLaunchCard`; undecided proposals are pinned in the dock above the composer.
+- **Launched** — Play succeeded (202). The proposal freezes into a "Launched → Rail N" stub (persisted on the message row), and the run card takes over.
+- **Running / settled / delivery** — the SAME envelope (`PrDecisionCardEnvelope`) carries `phase`, `runtime` and `hasDelivery`. With git, the delivery phase is the pre-existing PR-decision card. Without git, the card is run-only and ends at `completed` / `implementation_failed` / `discarded`.
+
+## Protocol contract
+
+```rail-launch
+{
+  "version": 1,
+  "railIndex": 1,
+  "newRail": null,
+  "ticketIds": [12, 14],
+  "mode": "implement",
+  "loopId": "factory:implement",
+  "aiEngine": "claude",
+  "model": "opus",
+  "reasoningEffort": "high",
+  "profileName": "fast",
+  "targetPrNumber": null,
+  "baseBranch": null,
+  "railName": "Auth",
+  "rationale": "Both specs touch the auth flow; one rail keeps the diff coherent."
+}
+```
+
+Parser pair `server/rail-launch-parser.ts` ⇄ `client/src/lib/rail-launch-draft.ts` (byte-identical except the mirror note; `server/rail-launch-parser.test.ts` enforces parity). `extractRailLaunchProposals(content, streaming)` returns `{ body, proposals, rejected, pending, truncated, repaired }`:
+
+- tolerant JSON repair (`json-tolerant`) before rejecting; `repaired` flags it;
+- unknown keys dropped; `ticketIds` accepts `12`, `"12"`, `"#12"` (also under `specs` / `tickets`); `mode` accepts `batch` for `batch-implement`, `newRail: true` for an unnamed rail; `railIndex` is ignored when `newRail` is set;
+- rejection reasons: `invalid_json | not_object | unsupported_version | no_tickets | invalid_mode`, each with a ≤160-char excerpt — never silent;
+- while streaming an open fence is cut from the body (`pending`); once settled an unreadable open fence is cut and reported `truncated`;
+- every valid block is kept in order: a batch proposal is N blocks, N cards.
+
+`agent-fence-promotion.ts` (server and client copies) re-tags a generic ```` ```json ```` fence whose body is a launch shape (ticket list plus a rail/launch key), checked after the spec-draft shape so a draft never becomes a launch.
+
+## Server chokepoints and surfaces
+
+| Piece | Where | Notes |
+|---|---|---|
+| Operator prompt | `server/agent-operator-prompt.ts` `RAIL_LAUNCH_CARD_SECTION`, `RAIL_LAUNCH_CARD_SYSTEM_CLAUSE`, `buildOperatorSystemPrompt()` | Propose = block; launch directly only on an explicit "now"; failure briefing reply ≤ 6 lines + one action, no mutation. Gated on `isMissionRailCardsEnabled()`. |
+| Message intent | desktop-db migration 29 (`agent_messages.intent`, column-guarded); `agent-store.ts` `setAgentMessageIntent`; `PATCH /api/agent/conversations/:id/messages/:mid/intent` | JSON ARRAY of decisions keyed by `proposalIndex`; append-only; 409 `already_decided`; 403 when the feature is off. Rows expose `intents[]`. |
+| Envelope | `server/types.ts` `PrDecisionCardEnvelope` (+ `MissionRunPhase`, `MissionRunRuntime`, `MissionRunFailure`) | `hasDelivery`, `phase`, `railName`, `runtime` — all optional; `decision` vocabulary unchanged. |
+| Run-only cards | `server/mission-run-notify.ts` `runCardId` / `isRunCardId` / `buildRunCardEnvelope` / `postRunCard` / `settleRunCard` / `failureForLoopOutcome` / `runtimeFromSummary` | Synthetic `prDeliveryId = 'run:<runId>'`, `hasDelivery:false`. Wired in the shared-cwd branch of `rails-router.ts` (origin stored on `railLoopRuns` meta; 202 returns `runIds`). |
+| Run-only dismiss | `POST /rails/pr-decision { prDeliveryId:'run:…', action:'dismiss', expectedDecision, conversationId }` → `AgentChatManager.dismissRunCard` | Other actions ⇒ 400 `run_card_dismiss_only`; unknown card ⇒ 404 `run_card_not_found`. |
+| Failure trigger | `notifyMissionRunFailure` (`mission-run-notify.ts`) | Envelope update with `runtime.failure` → `AgentChatManager.postRunFailureRow` (one `system` row per run, WS `agent_run_failure`) → `AgentChatManager.startSystemTurn` (queueId `mission-failure:<runId>`, gated `isMissionFailureTurnEnabled()`). Callers: shared-cwd run promise, isolated settle (`implementation_failed`), `closeFailedGeneration` (`launch_failed`). Cancel updates the card, no turn. No origin ⇒ no-op. |
+| Briefing | `server/agent-failure-briefing.ts` `buildFailureBriefing`, `failureBriefingRef`, `FAILURE_CODE_LABELS`, `FAILURE_BRIEFING_MAX_TAIL` | Fixed text: rail, specs, failure code + detail, bounded verify tail, recovery options, "do not relaunch by yourself". Persisted as a `user` row whose `context_refs[0].kind === 'system-briefing'`. |
+| Settle snapshots | `rail-isolated-launch.ts` settle, `rail-pr-store.ts` `toPrDecisionCardEnvelope`, `agent-runtime-controls-router.ts` `runtimeRunSummary()` | `phase` + `runtime` on `implementation_failed` and launch-failed `discarded`; `statusDetail` as text. |
+| Rails availability | `GET /:projectId/rails` | `availability: 'free' \| 'busy' \| 'pending_decision' \| 'on_review'` per rail. |
+| MCP | `server/mcp/tools/jobs.ts` `runtime_runs`, `runtime_evidence` (read) · `runtime_resume`, `runtime_recover` (ai-spawn) · `runtime_approve`, `runtime_settle`, `runtime_dismiss` (write) · `runtime_cancel` (destructive); `mcp/guide.ts` recovery section | Over the existing `/agent-runtime/runs` routes; approve/recover are `resume` bodies. |
+| Palette | `server/agent-chat-router.ts` `CONTEXT_KINDS` += `rail`; `server/agent-context-resolver.ts` `formatRail` | `@rail-N` reference serialization. |
+
+WS messages: `agent_pr_decision` (existing, now carries the new fields), `agent_run_failure` (new, app-global, `AgentRunFailureMessage`).
+
+## Client components
+
+- `client/src/components/agent-chat/AgentMessage.tsx` — extraction step after spec-draft (flag `FEATURE_MISSION_RAIL_CARDS`); renders `AgentRailLaunchCard` per proposal, `AgentRailLaunchPending`, `AgentRailLaunchUnreadable`.
+- `AgentRailLaunchCard.tsx` — live reconciliation (`/rails` availability, `/tickets`, `/profiles`, `useProviderDetection`, model/effort catalogs, loops), New rail, Play flow (`POST /rails` → `PUT /tickets` → `POST /launch` with `originConversationId` + `originSurface:'agent-chat'` → `notifyGitChanged` → intent PATCH), inline 400/409, launched/dismissed stubs, `FOCUS_PR_CARD_EVENT`.
+- `client/src/lib/rail-launch-intents.ts` — session overlay (`recordLocalIntent`, `intentFor`); `useRailLaunchProposals.ts` — undecided proposals for the dock; `AgentPrPinnedDock.tsx` — proposals pinned above PR cards.
+- `AgentPrDecisionCard.tsx` — run phase header (`deriveMissionRunStatus`, live `useRuntimeRuns` first), run-only rendering for `hasDelivery === false`, `RunFailureBlock`, Resume / Approve / Recover / Relaunch, focus-bus scroll + flash.
+- `agent-pr-pinning.ts` `isPrEnvelopePinned`; `agent-run-failure.ts` (`parseRunFailureRow`, `systemBriefingRunId`, `FOCUS_PR_CARD_EVENT`, `MISSION_OPEN_RUN_EVENT`, `requestMissionOpenRun`); `AgentRunFailureMarker.tsx`.
+- `client/src/context/AgentChatContext.tsx` — appends the `run-failure` row live on `agent_run_failure`; `AgentWorkspaceContext.tsx` / `AgentModeJobsPane.tsx` — `specrails:mission-open-run` opens the Jobs pane + `JobDetailModal`; `hooks/useOsNotifications.ts` — stays in Mission mode.
+- Palette: `client/src/lib/agent-context-palette.ts` (`rail` kind, `railsFromResponse`, `railChip`), `AgentComposer.tsx`, `AgentComposerEditor.tsx`, `AgentContextPalette.tsx`.
+
+## Honesty rules
+
+- Play is a user action: it never rides the agent tier ladder, and the server re-validates every launch (409s render inline; the card never pretends success).
+- The card shows only real state: live runtime data wins over the settle snapshot; a run-only card says plainly that no PR phase exists; failure detail is text, never hover-only; nothing is estimated.
+- The automatic failure turn is bounded: one per run (durable queueId), queued behind a live turn, accounted like any turn, forbidden from mutating in that turn, switchable off independently.
+- A decision is final per proposal index; reload renders the frozen stub, never a second Play.
+
+## Flags and rollback
+
+| Flag | Default | Off means |
+|---|---|---|
+| `SPECRAILS_MISSION_RAIL_CARDS` | on | legacy prompt verbs, intent route 403, no run-only cards, no failure trigger |
+| `VITE_FEATURE_MISSION_RAIL_CARDS` | on | `rail-launch` fences ignored, PR card renders exactly as before |
+| `SPECRAILS_MISSION_FAILURE_TURN` | on | card + `run-failure` row still update, no automatic turn |
+
+Migration 29 and the envelope fields are additive; persisted intents are inert when the feature is off.
+
+## Deferred
+
+- `job.stuck` → failure trigger: the stuck detector has no origin link (needs the rails meta map).
+- QueueManager `/spawn` jobs: no origin, no card (unchanged).
+- Per-step envelope updates while running: only launch → running and settle are emitted; the client reads live runtime meanwhile.
+- One grouped card for `launch_all`: v1 emits N blocks.
+- Translated `rationale` — the agent writes it in the conversation language.
+
+## Test map
+
+| Area | Tests |
+|---|---|
+| Parser + promotion + mirror parity | `server/rail-launch-parser.test.ts` |
+| Intent store/route, `dismissRunCard` | `server/agent-message-intent.test.ts` |
+| Run-only cards, availability, run-card dismiss route | `server/rails-router.test.ts`, `server/mcp/tools/rails-origin.test.ts` |
+| Failure trigger / briefing / system turn | `server/mission-run-notify.test.ts`, `server/agent-failure-briefing.test.ts`, `server/agent-chat-mission-turn.test.ts`, `server/rail-isolated-launch.test.ts` |
+| MCP runtime actions | `server/mcp/tools/jobs-runtime.test.ts` |
+| Launch card, proposals hook, stubs | `client/src/components/agent-chat/__tests__/agent-rail-launch-card.test.tsx` |
+| Run card phases / failure block / pinning / marker | `mission-run-card.test.tsx`, `mission-run-pinning.test.ts`, `agent-run-failure.test.ts`, `agent-run-failure-marker.test.tsx` |
+| Palette rails, Mission-mode notifications | `client/src/lib/__tests__/agent-context-palette-rails.test.ts`, `client/src/hooks/__tests__/useOsNotifications.mission-mode.test.ts` |

package/docs/internals/review-packet.md

@@ -109,9 +109,11 @@ holds no optimistic state; a raced answer surfaces the neutral
 
   The "What you asked" / "What was done" slots are spec markdown and render
   through `PacketMarkdown` (react-markdown + GFM, raw HTML skipped, images
-  dropped, inline code as quiet chips). `solution` is the tight digest; when
-  the composer clamps it, `solutionOverflow` carries the full text and the
-  page shows it behind a "Read the full solution" disclosure. The server
+  dropped, inline code as quiet chips, `unfoldInlineNumberedList` for specs
+  written as one "1. … 2. …" paragraph). "What was done" leads with the
+  durable outcome pill and the measured churn; the spec's proposed solution
+  (`solutionOverflow ?? solution`) sits below in a collapsed "Planned approach
+  (from the spec)" disclosure, labelled as the request, never as a report. The server
   digests each headed section as `**Label**` + a blank line + the content, so
   a numbered journey survives as a list in the packet AND in the PR body.
 - "Discuss this delivery" deliberately routes into the existing agent chat
@@ -218,3 +220,14 @@ their pre-change behaviour, with no toggle at all.
   toggle and render exactly as before.
 
 Any flag off leaves the existing decision strip byte-identical.
+
+
+## 2026-09-19 — "What was done" tells facts, not the plan
+
+Observed: the section rendered the spec's *Proposed Solution* digest as raw markdown (`**Proposed Solution** — …`, backticks) under the heading "What was done" — i.e. the PLAN presented as a REPORT. Fix (client only, `ReviewPacketPage.tsx`): each ticket row now leads with the durable per-unit outcome pill (`outcome.*`, derived from `implementationOutcome`/`deliveryOutcome`/`changed`, never from prose), the measured churn line now also states test files touched (`churn.testFiles`/`noTestFiles`), and the spec digest moved into a collapsed `<details>` labelled **Planned approach (from the spec)** with an explicit caveat that it is not a report of what the AI did. Both narratives (`problem`, `solution`) render through `ReactMarkdown` (`PacketMarkdown`) so headings, bold and inline code never leak raw. i18n `packet:planned.*`, `outcome.*`, `churn.testFiles*` ×8. Server composition unchanged.
+
+## 2026-09-19 — Programmatic-runtime evidence (host-run verification + reviewer verdict)
+
+Observed: a delivery built by the programmatic agent runtime (core-host) rendered **"The AI did not report any verification"** and **"No reviewer score"** although the host had run `npm test` (exit 0, output persisted) and the reviewer returned a structured verdict (score 92). The harvest only knew the legacy loop channels — the `VERIFICATION:` prose sentinel and `openspec/changes/**/confidence-score.json` — neither of which that runtime produces. Fix (`server/delivery-evidence.ts` `readRuntimeEvidence`, wired from `rail-isolated-launch.ts` via the new `EvidenceHarvestUnit.runtimeDir` = `<workspace>/.specrails/pipeline/<runId>`): read `state.json` `verification.commands[]` (+ each `verification/evidence/<id>.json` for exit code, duration, bounded output and `origin`), `acceptance.checks[]` / `acceptance.findings[]`, and the reviewer step output in `agent-workflow/<runId>/checkpoint.json` (`approved`, `score`, `aspects`, `issues`, `summary`). Every field is bounded; a malformed file degrades to nothing.
+
+Tier placement (`review-packet.ts` `buildProof`): commands whose `origin` includes `host` are **app-verified** (`proof.hostCommandPassed|Failed` with exit code + seconds + output tail) — the runtime executed them and recorded the exit code, which is a measurement, not a claim; non-host acceptance checks, the reviewer summary and findings are **ai-reported** (`proof.acceptanceCheckPassed|Failed`, `proof.reviewerSummary`, `proof.reviewerFinding`); the structured verdict fills `confidence` (score/aspects/issues→flags) ONLY when no file-based score exists, so the **reviewer-score** tier and the human-review band work unchanged. `proof.noVerificationReported` is emitted only when no channel reported anything. Older deliveries heal lazily: `GET …/packet` runs `healRuntimeEvidence` over units lacking `runtime` and persists the result (`updatePrDeliverySettleEvidence`), so a packet stops claiming silence once the pipeline dir exists. Still never a numeric test-count claim: the "70 passed" line rides inside the labelled raw output, not as a number the app asserts.

package/docs/mcp.md

@@ -40,7 +40,7 @@ reading one description. The tools are:
 | `specrails_context` | Compact live briefing: project/providers, backlog, rails/runs/deliveries, Git/worktrees, blueprint; source and availability per section |
 | `specrails_specs` | The spec/ticket backlog: list, get, create, update, delete, drafts, AI generate, AI-edit, Contract Refine, SMASH, per-ticket spend |
 | `specrails_rails` | Configure/launch dynamic rails (`create_rail`, up to 12), inspect PR candidates/review packets; `launch_all` reports outcomes and isolation availability per rail |
-| `specrails_jobs` | Inspect paginated job events, phase breakdowns, queues and background processes; stop jobs |
+| `specrails_jobs` | Inspect paginated job events, phase breakdowns, queues and background processes; stop jobs; read and drive programmatic runtime runs (`runtime_*`) |
 | `specrails_chat` | Explore / sidebar chat conversations and turns |
 | `specrails_agents` | Provider-scoped agent profiles and catalog; explicit profiles are validated for the selected provider |
 | `specrails_plugins` | The per-project plugin marketplace (install / verify / uninstall) |
@@ -107,6 +107,29 @@ Project Builder generation, Loop Decider, Code Explorer AI transforms, and
 Agent Studio automation are rejected before spawn. Destructive gates run
 before any mutation.
 
+## Runtime runs and rail availability (mission-rail-cards)
+
+`specrails_jobs` exposes the programmatic runtime of a job (the same state the
+app's Resume / Approve / Recover controls use), so an agent can explain a
+failure and act only on the user's confirmation:
+
+| Action | Tier | What it does |
+|---|---|---|
+| `runtime_runs` | read | Runtime state of `jobId` (or every run when omitted): status, current step, `canResume`, `recoverableSteps`, `pendingApproval` |
+| `runtime_evidence` | read | Durable runtime evidence of `jobId` |
+| `runtime_resume` | ai-spawn | Continue a resumable run (optional `approve` / `recover` / instruction body) |
+| `runtime_recover` | ai-spawn | Shorthand for `runtime_resume` with `recover: [stepIds]` |
+| `runtime_approve` | write | Shorthand for `runtime_resume` with `approve: [stepId]` |
+| `runtime_settle` | write | Prepare delivery for a succeeded-but-unsettled run |
+| `runtime_dismiss` | write | Dismiss a runtime continuation card |
+| `runtime_cancel` | destructive | Cancel an active runtime continuation |
+
+`specrails_rails(list)` rails carry `availability` — `free`, `busy` (active job
+or loop run), `pending_decision` (an undecided PR delivery) or `on_review` (a
+spec parked on review). Inside the app's own agent chat, a launch proposal is a
+fenced `rail-launch` block the user plays from an editable card; the tool's
+`launch` action is reserved for an explicit "launch now".
+
 ## The four permission tiers
 
 Every tool declares one tier. The server refuses any tool whose tier is not

package/package.json

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

package/server/dist/agent-chat-manager.js

@@ -20,6 +20,7 @@ const live_session_types_1 = require("./providers/live-session-types");
 const cli_prompt_1 = require("./util/cli-prompt");
 const result_event_1 = require("./result-event");
 const desktop_db_1 = require("./desktop-db");
+const feature_flags_1 = require("./feature-flags");
 const agent_cwd_manager_1 = require("./agent-cwd-manager");
 const agent_operator_prompt_1 = require("./agent-operator-prompt");
 const agent_mcp_config_1 = require("./agent-mcp-config");
@@ -436,8 +437,8 @@ class AgentChatManager {
             : '';
         const prompt = `${contextPrefix}\n\n${projectSnapshot}\n\n${inputReceiptNote}${userWithAttachments}`;
         const systemPrompt = hasAttachments
-            ? `${agent_operator_prompt_1.OPERATOR_SYSTEM_PROMPT}\n\n${attachment_manager_1.USER_ATTACHMENT_SYSTEM_NOTE}`
-            : agent_operator_prompt_1.OPERATOR_SYSTEM_PROMPT;
+            ? `${(0, agent_operator_prompt_1.buildOperatorSystemPrompt)()}\n\n${attachment_manager_1.USER_ATTACHMENT_SYSTEM_NOTE}`
+            : (0, agent_operator_prompt_1.buildOperatorSystemPrompt)();
         const effectivePrompt = (useResume) => {
             const freshPrompt = !useResume && historyBlock ? `${contextPrefix}\n\n${historyBlock}\n\n${prompt}` : prompt;
             return adapter.capabilities.systemPromptArg ? freshPrompt : `${systemPrompt}\n\n---\n\n${freshPrompt}`;
@@ -1226,6 +1227,100 @@ class AgentChatManager {
             console.error(`[agent-chat] updatePrDecisionCard failed (${conversationId}):`, err);
         }
     }
+    /**
+     * mission-rail-cards: persist the compact failure marker row for a run into
+     * its origin conversation (once per run — a repeat signal only updates the
+     * card) and broadcast `agent_run_failure`. Returns the row id, or null when
+     * skipped (duplicate / conversation gone / disposed). NEVER throws.
+     */
+    postRunFailureRow(conversationId, row) {
+        if (this._disposed)
+            return null;
+        try {
+            if (!(0, agent_store_1.getAgentConversation)(this._db, conversationId))
+                return null;
+            const existing = (0, agent_store_1.findAgentSystemMessages)(this._db, conversationId, (content) => {
+                try {
+                    const parsed = JSON.parse(content);
+                    return parsed.kind === 'run-failure' && parsed.runId === row.runId;
+                }
+                catch {
+                    return false;
+                }
+            });
+            if (existing.length > 0)
+                return null;
+            const message = (0, agent_store_1.addAgentMessage)(this._db, { conversationId, role: 'system', content: JSON.stringify(row) });
+            this._broadcast({ type: 'agent_run_failure', conversationId, messageId: message.id, ...row, timestamp: new Date().toISOString() });
+            return message.id;
+        }
+        catch (err) {
+            console.error(`[agent-chat] postRunFailureRow failed (${conversationId}):`, err);
+            return null;
+        }
+    }
+    /**
+     * mission-rail-cards: start ONE automatic, app-authored turn (the run-failure
+     * briefing). Reuses `sendMessage` end to end — queued behind a live turn,
+     * accounted like any turn, subject to the conversation's provider/model/tier.
+     * Durable dedup: the queue id is derived from the run id, so a second signal
+     * for the same run is an idempotent no-op (`created:false`) even across a
+     * restart. Flag-gated; NEVER throws.
+     */
+    async startSystemTurn(conversationId, text, opts) {
+        if (this._disposed || !(0, feature_flags_1.isMissionFailureTurnEnabled)())
+            return 'skipped';
+        const key = `${conversationId}:${opts.runId}`;
+        if (this._systemTurnRuns.has(key))
+            return 'skipped';
+        if (!(0, agent_store_1.getAgentConversation)(this._db, conversationId))
+            return 'skipped';
+        this._systemTurnRuns.add(key);
+        try {
+            await this.sendMessage(conversationId, text, {
+                queueId: `mission-failure:${opts.runId}`,
+                ...(opts.ref ? { contextRefs: [opts.ref] } : {}),
+            });
+            return 'started';
+        }
+        catch (err) {
+            console.error(`[agent-chat] startSystemTurn failed (${conversationId}):`, err);
+            return 'skipped';
+        }
+    }
+    _systemTurnRuns = new Set();
+    /**
+     * Dismiss a RUN-ONLY card (mission-rail-cards: a shared-cwd launch keyed on a
+     * synthetic `run:<runId>` id — there is no delivery row for the decision
+     * endpoint to transition). Marks the persisted envelope `discarded` (phase
+     * settled, operation dismiss) and re-broadcasts so every open panel unpins
+     * it. Returns false when no such card exists in that conversation.
+     */
+    dismissRunCard(conversationId, prDeliveryId) {
+        if (this._disposed)
+            return false;
+        const existing = this._findPrDecisionCards(conversationId, prDeliveryId);
+        if (existing.length === 0)
+            return false;
+        let envelope;
+        try {
+            envelope = JSON.parse(existing[existing.length - 1].content);
+        }
+        catch {
+            return false;
+        }
+        if (envelope.hasDelivery !== false)
+            return false;
+        this.updatePrDecisionCard(conversationId, {
+            ...envelope,
+            decision: 'discarded',
+            phase: 'settled',
+            operation: 'dismiss',
+            statusCode: envelope.statusCode ?? 'dismissed',
+            updatedAt: new Date().toISOString(),
+        });
+        return true;
+    }
     _findPrDecisionCards(conversationId, prDeliveryId) {
         return (0, agent_store_1.findAgentSystemMessages)(this._db, conversationId, (content) => {
             try {