specrails-desktop 2.42.1 → 2.43.0

package/docs/ci-cd.md

@@ -42,7 +42,7 @@ The macOS job retains `artifacts/chromium-signing/` as the `chromium-signing-mac
 ## Credentials and external requirements
 
 - `RELEASE_PAT` must be authorized for release-please's pull requests and releases. It also permits tag pushes to trigger publication workflows; events created with the repository's ordinary `GITHUB_TOKEN` generally do not trigger another workflow.
-- `NPM_TOKEN` must authenticate an account with publishing permission for `specrails-desktop`. The workflow checks authentication and gives an explicit error before publishing. Provenance requires `id-token: write`; it does **not** grant npm publishing permission. Trusted publishing requires separate registry configuration and is not silently enabled here. An npm `E404` during publication is not sufficient evidence to identify a particular token or permission failure. [npm publishing and provenance](https://docs.github.com/en/actions/tutorials/publish-packages/publish-nodejs-packages).
+- Publication uses one of two credentials. When the `NPM_TOKEN` secret is set, it must authenticate an account with publishing permission for `specrails-desktop` (npm now requires such tokens to be granular with *bypass 2FA*, and they expire within 90 days); the workflow checks authentication and gives an explicit error before publishing. When the secret is empty, the job publishes through npm **trusted publishing**: it installs npm 11, removes the empty token line that `setup-node` writes, and lets npm exchange the job's OIDC identity (`id-token: write`) for a short-lived publish grant. That path only works once the package's *Trusted publisher* on npmjs.com names this repository (`fjpulidop/specrails-desktop`) and workflow file (`npm-publish.yml`, no environment); registry configuration is never changed from here. Provenance does **not** grant publishing permission in either mode. An npm `E404` during publication is npm's answer to an unauthorized publish and does not identify which token or permission failed; an `E403` mentioning two-factor authentication means the stored token lacks *bypass 2FA*. [npm publishing and provenance](https://docs.github.com/en/actions/tutorials/publish-packages/publish-nodejs-packages).
 - Existing Apple signing/notarization and Tauri updater signing secrets remain required. Installer build steps retain their platform-specific checks.
 - Hostinger credentials must support **explicit FTPS**, a valid TLS certificate, uploads and `RNFR`/`RNTO` in the release directory. There is no plaintext FTP fallback. A failed transfer or rename fails the workflow before old files are removed. [FTP action protocol and security options](https://github.com/SamKirkland/FTP-Deploy-Action/blob/v4.3.6/action.yml).
 

package/docs/codex.md

@@ -46,9 +46,9 @@ binary isn't on `PATH`; it shows install commands if you click "More info".
    The first provider you select becomes the project default.
 4. Submit. The app writes `.specrails/install-config.yaml` (with
    `provider: codex` and `tier: quick` as YAML keys) and spawns
-   `npx --yes --prefer-online specrails-core@^4.12.0 init --yes --from-config <file>`
+   `npx --yes --prefer-online specrails-core@^5.1.0 init --yes --from-config <file>`
    — the provider and tier live in the YAML, not as CLI flags. (The app
-   pins `specrails-core@^4.12.0`; that floor is the version that ships the
+   pins `specrails-core@^5.1.0`; that floor is the version that ships the
    current provider targets, including Kimi and the Codex skill set.) The install
    produces:
    - `.codex/config.toml` — model, reasoning effort, sandbox mode, and

package/docs/customizing.md

@@ -148,7 +148,7 @@ Most settings live in the UI. A few app-level switches are env-only because they
 
 | Variable | Effect |
 |----------|--------|
-| `SPECRAILS_CORE_BIN` | Override the `specrails-core` binary (default: `npx --yes --prefer-online specrails-core@^4.12.0` — the 4.12.0 floor is the release that ships the Kimi provider target) |
+| `SPECRAILS_CORE_BIN` | Override the `specrails-core` binary (default: `npx --yes --prefer-online specrails-core@^5.1.0` — the 5.1.0 floor is the release that quotes the command path in its Windows shell runner, so OpenSpec init works from an install directory with spaces; it is also the version bundled with the app) |
 | `SPECRAILS_TECH_URL` | Override the specrails-tech proxy base URL |
 | `SPECRAILS_AGENTS_SECTION=false` | Hide the Agents section from every project |
 | `SPECRAILS_PLUGINS_SECTION=false` | Hide the Integrations section from every project |

package/docs/gemini.md

@@ -24,11 +24,11 @@ Specrails supports **four AI providers**: Anthropic's
 |---|---|---|
 | `gemini` CLI ≥ 0.11.0 | Earlier versions lack `--output-format stream-json` + headless `--resume`, which the app relies on | `npm i -g @google/gemini-cli` · check with `gemini --version` |
 | A Gemini API key | The app spawns Gemini headlessly, so it needs non-interactive auth | Set `GEMINI_API_KEY` to a paid Gemini Developer API key from [Google AI Studio](https://aistudio.google.com/apikey) |
-| `specrails-core` ≥ 4.8.0 in the project | 4.8.0 ships the Gemini provider target (`.gemini/` commands + agents) that the rails pipeline needs | The current Add-Project install flow uses `specrails-core@^4.12.0` automatically |
+| `specrails-core` ≥ 4.8.0 in the project | 4.8.0 ships the Gemini provider target (`.gemini/` commands + agents) that the rails pipeline needs | The current Add-Project install flow uses `specrails-core@^5.1.0` automatically |
 | `git`, `node`, `npm`, `npx` | Same as Claude — needed for `specrails-core init` | Use your usual installer |
 
 > **Two different minimums.** The `gemini` **binary** floor is **0.11.0**.
-> The current Desktop `specrails-core` **package** floor is **4.12.0** (a
+> The current Desktop `specrails-core` **package** floor is **5.1.0** (a
 > single shared version for all providers, including Kimi). They are separate
 > things — the binary on your
 > machine vs. the artifacts installed into the project.
@@ -52,7 +52,7 @@ the Gemini provider checkbox with a "not found" hint when the binary isn't on
    project](#running-multiple-providers-in-one-project)). The first provider
    you select becomes the project default.
 4. Submit. The app writes `.specrails/install-config.yaml` and spawns
-   `npx --yes --prefer-online specrails-core@^4.12.0 init --yes --from-config <file>`.
+   `npx --yes --prefer-online specrails-core@^5.1.0 init --yes --from-config <file>`.
    The install produces the `.gemini/` artifacts (commands + `sr-*` agents),
    plus a `GEMINI.md` instructions file.
 

package/docs/getting-started.md

@@ -61,7 +61,7 @@ specrails-desktop list   # verify
 The setup wizard runs automatically. Three steps:
 
 1. **Configure** — choose which agents to install (the baseline trio `sr-architect`, `sr-developer`, `sr-reviewer` is always selected; optional agents like Test Writer or Security Reviewer are opt-in). Pick a model preset (Balanced / Budget / Max) and optionally override the model per agent.
-2. **Install** — the app runs the installer (`npx --yes --prefer-online specrails-core@^4.12.0 init --yes --from-config <config>`) non-interactively and streams the output live. The version is pinned to the core release the app ships with — it never silently jumps to a new major.
+2. **Install** — the app runs the installer (`npx --yes --prefer-online specrails-core@^5.1.0 init --yes --from-config <config>`) non-interactively and streams the output live. The version is pinned to the core release the app ships with — it never silently jumps to a new major.
 3. **Done** — a summary tells you how many agents and commands landed. Click **Continue to project**.
 
 That's the whole onboarding. No tier picker, no second wizard. You can manage agents and their per-agent models later from the **Agents** page (Profiles tab).

package/docs/platforms/windows-parity.md

@@ -26,7 +26,7 @@ This audit covers the `codex/multi-repo-projects` branch, including mission stee
 
 ## Automated gates
 
-`.github/workflows/windows-parity.yml` runs a `windows-parity` job on `windows-latest` (x64) for every push and pull request, and adds `windows-11-arm` on pushes to `main`. It installs dependencies, checks TypeScript, runs release/PTY helper regression tests, native filesystem/process tests (retried once, they drive real processes), the application build, native host build/tests, and four real native fixtures: WebView2 capture/selection, authentication popups, mission window handoff, and browser multiwindow transfer/parking. It is deliberately a separate workflow from `ci.yml`: `release.yml` waits for CI only, so a slow or flaky Windows run never delays the release PR, while Desktop Release still builds and installs on Windows before publication. The jsdom client suite is not repeated on Windows; it runs on Linux in CI. The bundled-core matrix in `ci.yml` exercises Windows junction/copy relocation for providers.
+`.github/workflows/windows-parity.yml` runs a `windows-parity` job on `windows-latest` (x64) for every pull request and push to `main`, adding `windows-11-arm` on the `main` pushes. It installs dependencies, checks TypeScript, runs release/PTY helper regression tests, native filesystem/process tests (retried once, they drive real processes), the application build, native host build/tests, and four real native fixtures: WebView2 capture/selection, authentication popups, mission window handoff, and browser multiwindow transfer/parking. It is deliberately a separate workflow from `ci.yml`: `release.yml` waits for CI only, so a slow or flaky Windows run never delays the release PR, while Desktop Release still builds and installs on Windows before publication. The jsdom client suite is not repeated on Windows; it runs on Linux in CI. The bundled-core matrix in `ci.yml` exercises Windows junction/copy relocation for providers.
 
 `.github/workflows/desktop-release.yml` builds the real installers and runs `scripts/smoke-windows-installers.ps1` before publishing artifacts. For each NSIS and MSI package, the script installs into a temporary path containing spaces and drives `scripts/smoke-installed-windows.mjs` with the installed Node runtime. The driver uses an isolated user profile and tests:
 

package/package.json

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

package/server/dist/code-explorer-router.js

@@ -139,7 +139,7 @@ async function gitIgnoredSet(projectPath, relPaths, maxDurationMs = Number.POSIT
             let stdout = '';
             let settled = false;
             let overflow = false;
-            const child = (0, child_process_1.spawn)('git', ['check-ignore', '--stdin', '-z'], { cwd: projectPath, stdio: ['pipe', 'pipe', 'ignore'], env: file_provenance_1.GIT_EXEC_ENV });
+            const child = (0, child_process_1.spawn)('git', ['check-ignore', '--stdin', '-z'], { cwd: projectPath, stdio: ['pipe', 'pipe', 'ignore'], env: (0, file_provenance_1.gitExecEnv)() });
             const finish = (complete) => { if (!settled) {
                 settled = true;
                 resolve({ stdout, complete: complete && !overflow });

package/server/dist/core-package.js

@@ -1,7 +1,10 @@
 "use strict";
 Object.defineProperty(exports, "__esModule", { value: true });
 exports.CORE_PACKAGE_SPEC = void 0;
-/** Online fallback selects the supported Core 5 lifecycle. Bundled Core 4 remains
- * readable for installed apps; the runtime resolver selects the newest usable
- * compatible package and never downgrades a newer activated framework. */
-exports.CORE_PACKAGE_SPEC = 'specrails-core@^5.0.0';
+/** Online fallback selects the supported Core 5 lifecycle; 5.1.0 is the floor
+ * because it quotes the command path in its Windows shell runner (OpenSpec init
+ * from an install directory with spaces). The desktop bundles the same version.
+ * Bundled Core 4 remains readable for installed apps; the runtime resolver
+ * selects the newest usable compatible package and never downgrades a newer
+ * activated framework. */
+exports.CORE_PACKAGE_SPEC = 'specrails-core@^5.1.0';

package/server/dist/file-provenance.js

@@ -3,7 +3,8 @@ var __importDefault = (this && this.__importDefault) || function (mod) {
     return (mod && mod.__esModule) ? mod : { "default": mod };
 };
 Object.defineProperty(exports, "__esModule", { value: true });
-exports.STORY_EXCERPT_MAX_BYTES = exports.GIT_EXEC_ENV = void 0;
+exports.STORY_EXCERPT_MAX_BYTES = void 0;
+exports.gitExecEnv = gitExecEnv;
 exports.resolveHeadSha = resolveHeadSha;
 exports.listUntracked = listUntracked;
 exports.snapshotWorkingTree = snapshotWorkingTree;
@@ -34,9 +35,13 @@ const GIT_MAX_BUFFER = 16 * 1024 * 1024;
 // the on-demand diff patches beyond this cap are skipped (the UI shows "diff
 // unavailable" for them). Mirrors the existing large-job warn threshold (50).
 const MAX_PATCH_FILES = 50;
-// Exported: project-git.ts (the Agent-Mode git bar) runs the same cwd-scoped
-// git calls and needs the identical hostile-repo hardening.
-exports.GIT_EXEC_ENV = (() => {
+// Exported: project-git.ts (the Agent-Mode git bar), the code explorer and the
+// git diagnostics run the same cwd-scoped git calls and need the identical
+// hostile-repo hardening. Computed PER CALL, never at module load: the startup
+// path resolver prepends the bundled git directory to process.env.PATH after
+// this module was imported, and a snapshot taken earlier could not find git in
+// a packaged app without a system git — every guard then failed closed.
+function gitExecEnv() {
     // Inherit the parent env but STRIP git-location vars. If the app process (or a
     // parent) ever exports GIT_DIR / GIT_WORK_TREE / GIT_INDEX_FILE, every cwd-scoped
     // git call below would silently operate on that repo instead of the project —
@@ -61,7 +66,7 @@ exports.GIT_EXEC_ENV = (() => {
     env.GIT_CONFIG_NOSYSTEM = '1';
     env.GIT_CONFIG_PARAMETERS = "'core.fsmonitor=false' 'core.hooksPath=/dev/null' 'protocol.ext.allow=user'";
     return env;
-})();
+}
 /** Resolve the current HEAD commit SHA. Best-effort: '' on any git failure
  *  (no repo, unborn HEAD, no git, timeout). */
 function resolveHeadSha(cwd) {
@@ -72,7 +77,7 @@ function resolveHeadSha(cwd) {
             stdio: ['ignore', 'pipe', 'pipe'],
             timeout: GIT_TIMEOUT_MS,
             maxBuffer: GIT_MAX_BUFFER,
-            env: exports.GIT_EXEC_ENV,
+            env: gitExecEnv(),
         });
         return out.trim();
     }
@@ -90,7 +95,7 @@ function listUntracked(cwd) {
             stdio: ['ignore', 'pipe', 'pipe'],
             timeout: GIT_TIMEOUT_MS,
             maxBuffer: GIT_MAX_BUFFER,
-            env: exports.GIT_EXEC_ENV,
+            env: gitExecEnv(),
         });
         return out.split('\0').filter((p) => p.length > 0);
     }
@@ -107,7 +112,7 @@ function snapshotWorkingTree(cwd) {
             stdio: ['ignore', 'pipe', 'pipe'],
             timeout: GIT_TIMEOUT_MS,
             maxBuffer: GIT_MAX_BUFFER,
-            env: exports.GIT_EXEC_ENV,
+            env: gitExecEnv(),
         });
         ref = out.trim();
     }
@@ -141,7 +146,7 @@ function diffAgainstSnapshot(cwd, snapshotRef, untrackedBefore, baseSha) {
             stdio: ['ignore', 'pipe', 'pipe'],
             timeout: GIT_TIMEOUT_MS,
             maxBuffer: GIT_MAX_BUFFER,
-            env: exports.GIT_EXEC_ENV,
+            env: gitExecEnv(),
         });
     }
     catch {
@@ -309,7 +314,7 @@ function collectDiffPatches(cwd, snapshotRef, diff, baseSha) {
                 stdio: ['ignore', 'pipe', 'pipe'],
                 maxBuffer: MAX_PATCH_BYTES + 64 * 1024,
                 timeout: GIT_TIMEOUT_MS,
-                env: exports.GIT_EXEC_ENV,
+                env: gitExecEnv(),
             });
         }
         catch (err) {

package/server/dist/git-diagnostics.js

@@ -17,7 +17,7 @@ const win_spawn_1 = require("./util/win-spawn");
  * SAFETY: the command list is a FIXED ALLOWLIST — the caller only picks an
  * action name, never arguments, so no flag/ref/path can be smuggled in. Every
  * command is read-only (no push/commit/checkout/pr-create). git runs with the
- * hardened `GIT_EXEC_ENV` (hostile-repo config stripped, prompts disabled); gh
+ * hardened `gitExecEnv()` (hostile-repo config stripped, prompts disabled); gh
  * runs with the normal env so it finds the user's `~/.config/gh` auth and the
  * bundled `gh` on PATH.
  */
@@ -43,7 +43,7 @@ const OUTPUT_CAP = 8_000;
 const defaultExec = (cmd, args, cwd) => new Promise((resolve) => {
     // git: hardened, cwd-pinned env. gh: user env (needs ~/.config/gh auth) with
     // the Windows shell-critical vars guaranteed present.
-    const env = cmd === 'gh' ? (0, win_spawn_1.windowsSpawnEnv)() : file_provenance_1.GIT_EXEC_ENV;
+    const env = cmd === 'gh' ? (0, win_spawn_1.windowsSpawnEnv)() : (0, file_provenance_1.gitExecEnv)();
     (0, child_process_1.execFile)(cmd, args, { cwd, env, timeout: 15_000, maxBuffer: 8 * 1024 * 1024, windowsHide: true }, (err, stdout, stderr) => {
         const code = err && typeof err.code === 'number'
             ? err.code

package/server/dist/pr-publisher.js

@@ -35,7 +35,7 @@ function createBoundedExec(timeoutMs = exports.PR_COMMAND_TIMEOUT_MS) {
                 // `windowsSpawnEnv()` backfills SystemRoot / ComSpec / USERPROFILE, which a
                 // GUI-launched / pkg-stripped Windows sidecar can lack — without them the
                 // `git`/`gh` child (and the `sh -c` the `!gh …` credential helper runs) can
-                // fail to start. NOT `GIT_EXEC_ENV`: that hardened env disables credentials
+                // fail to start. NOT `gitExecEnv()`: that hardened env disables credentials
                 // (GIT_ASKPASS=echo / GIT_TERMINAL_PROMPT=0), which the push must keep. No-op
                 // on POSIX (returns process.env), so mac/Linux behaviour is byte-identical.
                 const env = (0, win_spawn_1.windowsSpawnEnv)();

package/server/dist/project-git.js

@@ -21,7 +21,7 @@ const GIT_MAX_BUFFER = 4 * 1024 * 1024;
 const COMMIT_SHA_RE = /^[0-9a-f]{40,64}$/i;
 function git(repoDir, args) {
     return new Promise((resolve, reject) => {
-        (0, child_process_1.execFile)('git', args, { cwd: repoDir, env: file_provenance_1.GIT_EXEC_ENV, timeout: GIT_TIMEOUT_MS, maxBuffer: GIT_MAX_BUFFER, windowsHide: true }, (err, stdout, stderr) => {
+        (0, child_process_1.execFile)('git', args, { cwd: repoDir, env: (0, file_provenance_1.gitExecEnv)(), timeout: GIT_TIMEOUT_MS, maxBuffer: GIT_MAX_BUFFER, windowsHide: true }, (err, stdout, stderr) => {
             if (err) {
                 const detail = String(stderr || err.message).trim();
                 reject(new Error(detail));

package/server/dist/setup-manager.js

@@ -772,7 +772,13 @@ class SetupManager {
             providers: list,
             continueOnError: true,
             onProviderStart: (p) => emit(p, 'running'),
-            onProviderResult: (r) => emit(r.provider, r.ok ? 'done' : 'failed', r.error),
+            onProviderResult: (r) => {
+                // The WS event carries the reason to the app; the server log must too,
+                // or a packaged-app failure (installer smoke, support bundle) is blind.
+                if (!r.ok)
+                    console.warn(`[SetupManager] silent assemble: ${r.provider} failed for ${projectId}: ${r.error ?? 'unknown error'}`);
+                emit(r.provider, r.ok ? 'done' : 'failed', r.error);
+            },
         })
             .then((results) => {
             const failed = results.filter((r) => !r.ok).map((r) => r.provider);

package/server/dist/terminal-manager.js

@@ -4,6 +4,7 @@ var __importDefault = (this && this.__importDefault) || function (mod) {
 };
 Object.defineProperty(exports, "__esModule", { value: true });
 exports.TerminalManager = exports.TERMINAL_EARLY_EXIT_MS = exports.TerminalSpawnError = exports.TerminalNameInvalidError = exports.TerminalNotFoundError = exports.TerminalLimitExceededError = exports.RingBuffer = exports.TERMINAL_DEFAULT_ROWS = exports.TERMINAL_DEFAULT_COLS = exports.TERMINAL_NAME_MAX = exports.TERMINAL_MAX_PER_PROJECT = exports.TERMINAL_KILL_GRACE_MS = exports.TERMINAL_SCROLLBACK_BYTES = void 0;
+exports.killTerminalTree = killTerminalTree;
 exports.resolveShell = resolveShell;
 exports.resolveShellFor = resolveShellFor;
 exports.shellArgs = shellArgs;
@@ -20,6 +21,21 @@ const terminal_marks_store_1 = require("./terminal-marks-store");
 const terminal_shell_integration_1 = require("./terminal-shell-integration");
 exports.TERMINAL_SCROLLBACK_BYTES = 262_144;
 exports.TERMINAL_KILL_GRACE_MS = 2_000;
+/**
+ * Windows: node-pty ends a ConPTY session by enumerating the pseudo console's
+ * processes through a helper it starts with `process.execPath`. In the
+ * packaged sidecar that path is the sidecar binary itself, so the helper never
+ * runs, only the shell is terminated and whatever the shell started (a dev
+ * server, a watcher) survives the closed terminal. Kill the shell's process
+ * tree ourselves (`taskkill /T /F` through tree-kill). No-op elsewhere: the
+ * POSIX pty closes its process group.
+ */
+function killTerminalTree(pid, platform = process.platform, kill = win_spawn_1.treeKillSafe) {
+    if (platform !== 'win32' || !pid || !Number.isInteger(pid) || pid <= 0)
+        return false;
+    kill(pid, 'SIGKILL');
+    return true;
+}
 exports.TERMINAL_MAX_PER_PROJECT = 10;
 exports.TERMINAL_NAME_MAX = 64;
 exports.TERMINAL_DEFAULT_COLS = 80;
@@ -455,6 +471,7 @@ class TerminalManager {
     async shutdown() {
         const all = Array.from(this.sessions.values());
         for (const s of all) {
+            killTerminalTree(s.pty.pid);
             try {
                 s.pty.kill('SIGTERM');
             }
@@ -462,6 +479,7 @@ class TerminalManager {
         }
         await new Promise((r) => setTimeout(r, exports.TERMINAL_KILL_GRACE_MS));
         for (const s of Array.from(this.sessions.values())) {
+            killTerminalTree(s.pty.pid);
             try {
                 s.pty.kill('SIGKILL');
             }
@@ -540,12 +558,14 @@ class TerminalManager {
             return;
         this.detachFromRegistry(s);
         if (!s.exited) {
+            killTerminalTree(s.pty.pid);
             try {
                 s.pty.kill('SIGTERM');
             }
             catch { /* ignore */ }
             s.killTimer = setTimeout(() => {
                 if (!s.exited) {
+                    killTerminalTree(s.pty.pid);
                     try {
                         s.pty.kill('SIGKILL');
                     }