npm - specrails-desktop - Versions diffs - 2.64.1 → 2.65.0 - Mend

specrails-desktop 2.64.1 → 2.65.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.

Files changed (1117) hide show

package/client/dist/index.html CHANGED Viewed

@@ -116,9 +116,9 @@
         margin: 0;
         background: var(--splash-bg);
         color: var(--splash-fg);
-        font-family: -apple-system, BlinkMacSystemFont, "SF Pro Text", "Helvetica Neue", sans-serif;
       }
       #specrails-splash {
+        font-family: -apple-system, BlinkMacSystemFont, "SF Pro Text", "Helvetica Neue", sans-serif;
         position: fixed;
         inset: 0;
         display: flex;
@@ -204,87 +204,102 @@
         .specrails-splash__mark .pill { opacity: 1; }
       }
     </style>
-    <script type="module" crossorigin src="/assets/index-Ce4yZtKf.js"></script>
+    <script type="module" crossorigin src="/assets/index-DHzB0T26.js"></script>
     <link rel="modulepreload" crossorigin href="/assets/rolldown-runtime-CNC7AqOf.js">
     <link rel="modulepreload" crossorigin href="/assets/jsx-runtime-BbYvbtY8.js">
     <link rel="modulepreload" crossorigin href="/assets/react-dom-DDD8FYaU.js">
     <link rel="modulepreload" crossorigin href="/assets/preload-helper-Czpn1I53.js">
-    <link rel="modulepreload" crossorigin href="/assets/chunk-OB3PAWPO-B1EMk45A.js">
-    <link rel="modulepreload" crossorigin href="/assets/tauri-shell-DE6LfGPw.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-Dip4h2YE.js">
-    <link rel="modulepreload" crossorigin href="/assets/agentRuntime-BxYS5V7u.js">
-    <link rel="modulepreload" crossorigin href="/assets/agents-Doe1sHY5.js">
-    <link rel="modulepreload" crossorigin href="/assets/agentstudio-BzugqB_N.js">
-    <link rel="modulepreload" crossorigin href="/assets/aiedit-iIjz2_Qk.js">
-    <link rel="modulepreload" crossorigin href="/assets/analytics-BWynXPEm.js">
+    <link rel="modulepreload" crossorigin href="/assets/chunk-OB3PAWPO-BBaq6pUk.js">
+    <link rel="modulepreload" crossorigin href="/assets/tauri-shell-43ixPGfa.js">
+    <link rel="modulepreload" crossorigin href="/assets/activity-Cevl82ke.js">
+    <link rel="modulepreload" crossorigin href="/assets/addspec-DOFo9pD5.js">
+    <link rel="modulepreload" crossorigin href="/assets/agent-DcsoTnuE.js">
+    <link rel="modulepreload" crossorigin href="/assets/agentRuntime-BijLh8I9.js">
+    <link rel="modulepreload" crossorigin href="/assets/agents-EN1Zl4YZ.js">
+    <link rel="modulepreload" crossorigin href="/assets/agentstudio-DIE_HjsX.js">
+    <link rel="modulepreload" crossorigin href="/assets/aiedit-BrqMZvbc.js">
+    <link rel="modulepreload" crossorigin href="/assets/analytics-BRi4KQD6.js">
     <link rel="modulepreload" crossorigin href="/assets/attachments-B53PG733.js">
     <link rel="modulepreload" crossorigin href="/assets/browser-CG0PE1j_.js">
-    <link rel="modulepreload" crossorigin href="/assets/builder-CpS9liE9.js">
+    <link rel="modulepreload" crossorigin href="/assets/builder-BMVvSr4v.js">
     <link rel="modulepreload" crossorigin href="/assets/chat-BGD7MXAy.js">
-    <link rel="modulepreload" crossorigin href="/assets/code-DaZ-ZwCT.js">
-    <link rel="modulepreload" crossorigin href="/assets/commands-BAWSYHjQ.js">
-    <link rel="modulepreload" crossorigin href="/assets/common-Bdi0qN4S.js">
-    <link rel="modulepreload" crossorigin href="/assets/dashboard-XGdQ5mjw.js">
-    <link rel="modulepreload" crossorigin href="/assets/explore-DgBACn39.js">
-    <link rel="modulepreload" crossorigin href="/assets/integrations-Dwl9KQp0.js">
-    <link rel="modulepreload" crossorigin href="/assets/jira-FXr7u2lh.js">
-    <link rel="modulepreload" crossorigin href="/assets/jobs-De3EqaO0.js">
-    <link rel="modulepreload" crossorigin href="/assets/loops-WyWDkhok.js">
-    <link rel="modulepreload" crossorigin href="/assets/mcp-CUAN6ORK.js">
-    <link rel="modulepreload" crossorigin href="/assets/narration-DbHnz0qV.js">
-    <link rel="modulepreload" crossorigin href="/assets/nav--u7iPYlS.js">
-    <link rel="modulepreload" crossorigin href="/assets/packet-B0H15elv.js">
-    <link rel="modulepreload" crossorigin href="/assets/settings-Pyw8uYtL.js">
-    <link rel="modulepreload" crossorigin href="/assets/setup-CKGUxKr-.js">
-    <link rel="modulepreload" crossorigin href="/assets/specs-DfIdoU5L.js">
+    <link rel="modulepreload" crossorigin href="/assets/code-CK6pm8wY.js">
+    <link rel="modulepreload" crossorigin href="/assets/commands-DNox0Edk.js">
+    <link rel="modulepreload" crossorigin href="/assets/common-5H4TkaoI.js">
+    <link rel="modulepreload" crossorigin href="/assets/dashboard-6zGLGcEz.js">
+    <link rel="modulepreload" crossorigin href="/assets/explore--NOz9LCN.js">
+    <link rel="modulepreload" crossorigin href="/assets/inbox-CFNPDhso.js">
+    <link rel="modulepreload" crossorigin href="/assets/integrations-BmX_XyJq.js">
+    <link rel="modulepreload" crossorigin href="/assets/jira-CkwjeJz6.js">
+    <link rel="modulepreload" crossorigin href="/assets/jobs-DT5s4fZ6.js">
+    <link rel="modulepreload" crossorigin href="/assets/loops-BogV595N.js">
+    <link rel="modulepreload" crossorigin href="/assets/mcp-DbGSFC3f.js">
+    <link rel="modulepreload" crossorigin href="/assets/narration-MYlfktga.js">
+    <link rel="modulepreload" crossorigin href="/assets/nav-DZJbFbah.js">
+    <link rel="modulepreload" crossorigin href="/assets/onboarding-BdZQnNm3.js">
+    <link rel="modulepreload" crossorigin href="/assets/packet-aasskOE7.js">
+    <link rel="modulepreload" crossorigin href="/assets/recovery-pITlc--v.js">
+    <link rel="modulepreload" crossorigin href="/assets/settings-DnWFoY-F.js">
+    <link rel="modulepreload" crossorigin href="/assets/setup-DxTBkX3P.js">
+    <link rel="modulepreload" crossorigin href="/assets/specs-7tAb4IKr.js">
     <link rel="modulepreload" crossorigin href="/assets/subscriptionUsage-CdlE5Mg1.js">
-    <link rel="modulepreload" crossorigin href="/assets/terminal-BAzpHtpY.js">
-    <link rel="modulepreload" crossorigin href="/assets/tickets-D41ZMQpf.js">
+    <link rel="modulepreload" crossorigin href="/assets/terminal-AbUAmCxE.js">
+    <link rel="modulepreload" crossorigin href="/assets/tickets-Bfo2GGmH.js">
+    <link rel="modulepreload" crossorigin href="/assets/undo-ds8nMFbX.js">
     <link rel="modulepreload" crossorigin href="/assets/createLucideIcon-DtODIU64.js">
-    <link rel="modulepreload" crossorigin href="/assets/useSharedWebSocket-Bj4LMp7b.js">
-    <link rel="modulepreload" crossorigin href="/assets/Trans-BbFxRFtR.js">
-    <link rel="modulepreload" crossorigin href="/assets/useDesktop-BjLT0_EE.js">
-    <link rel="modulepreload" crossorigin href="/assets/provider-capabilities-lePfeT_Y.js">
+    <link rel="modulepreload" crossorigin href="/assets/origin-03nTuaOb.js">
+    <link rel="modulepreload" crossorigin href="/assets/api-DOGbyfTO.js">
+    <link rel="modulepreload" crossorigin href="/assets/Trans-C6J0cLyh.js">
+    <link rel="modulepreload" crossorigin href="/assets/core-BozBzB6Y.js">
+    <link rel="modulepreload" crossorigin href="/assets/notify-error-BsWANx1T.js">
+    <link rel="modulepreload" crossorigin href="/assets/provider-capabilities-DtwcTme4.js">
     <link rel="modulepreload" crossorigin href="/assets/save-LmPSfsvZ.js">
-    <link rel="modulepreload" crossorigin href="/assets/spending-CQnrWiR3.js">
-    <link rel="modulepreload" crossorigin href="/assets/chevron-up-6EFqEHBj.js">
+    <link rel="modulepreload" crossorigin href="/assets/es2015-DfnECntk.js">
+    <link rel="modulepreload" crossorigin href="/assets/dist-Di-oOFkX.js">
+    <link rel="modulepreload" crossorigin href="/assets/utils-ELimjS2Y.js">
+    <link rel="modulepreload" crossorigin href="/assets/HelpHint-Crf9_uoR.js">
+    <link rel="modulepreload" crossorigin href="/assets/spending-CVH8VREb.js">
+    <link rel="modulepreload" crossorigin href="/assets/chevron-up-BAMuP0XD.js">
     <link rel="modulepreload" crossorigin href="/assets/sparkles-CCfUdFGY.js">
     <link rel="modulepreload" crossorigin href="/assets/x-Bu7X_eR2.js">
-    <link rel="modulepreload" crossorigin href="/assets/MinimizedChatsContext-DHfigjHS.js">
+    <link rel="modulepreload" crossorigin href="/assets/dialog-C23lB2iP.js">
+    <link rel="modulepreload" crossorigin href="/assets/useDesktop-BuOp2-MR.js">
+    <link rel="modulepreload" crossorigin href="/assets/MinimizedChatsContext-742ypO8n.js">
     <link rel="modulepreload" crossorigin href="/assets/ban-wqfdzoXt.js">
-    <link rel="modulepreload" crossorigin href="/assets/file-text-C0blZHLh.js">
+    <link rel="modulepreload" crossorigin href="/assets/chevron-right-CwMAj0w_.js">
     <link rel="modulepreload" crossorigin href="/assets/circle-x-D2ttKotB.js">
     <link rel="modulepreload" crossorigin href="/assets/download-C9wP_42h.js">
+    <link rel="modulepreload" crossorigin href="/assets/dropdown-menu-Bfp2CK6H.js">
     <link rel="modulepreload" crossorigin href="/assets/external-link-CZ6Q-v1-.js">
-    <link rel="modulepreload" crossorigin href="/assets/git-branch-yf6LE1Bw.js">
-    <link rel="modulepreload" crossorigin href="/assets/layers-BCLTgHXO.js">
-    <link rel="modulepreload" crossorigin href="/assets/loader-circle-BqV9xYGf.js">
+    <link rel="modulepreload" crossorigin href="/assets/file-text-CNXzL3wj.js">
+    <link rel="modulepreload" crossorigin href="/assets/square-Co6h5vZg.js">
+    <link rel="modulepreload" crossorigin href="/assets/button-CHPkroew.js">
+    <link rel="modulepreload" crossorigin href="/assets/confirm-dialog-ChZdHL3Q.js">
     <link rel="modulepreload" crossorigin href="/assets/pencil-CxrRbDwb.js">
-    <link rel="modulepreload" crossorigin href="/assets/square-D0JTbRSR.js">
     <link rel="modulepreload" crossorigin href="/assets/plus-fHDdjBk1.js">
-    <link rel="modulepreload" crossorigin href="/assets/rotate-ccw-DalJAQQX.js">
+    <link rel="modulepreload" crossorigin href="/assets/refresh-cw-DfyTkbsf.js">
     <link rel="modulepreload" crossorigin href="/assets/search-BDVp3fkH.js">
-    <link rel="modulepreload" crossorigin href="/assets/trash-D8zYUmTg.js">
     <link rel="modulepreload" crossorigin href="/assets/triangle-alert-Cxpn8bqr.js">
-    <link rel="modulepreload" crossorigin href="/assets/jira-api-Cabj-H0J.js">
+    <link rel="modulepreload" crossorigin href="/assets/wrench-Br2n1Lxd.js">
     <link rel="modulepreload" crossorigin href="/assets/zap-bugHyWzQ.js">
-    <link rel="modulepreload" crossorigin href="/assets/clsx-CjueKrWZ.js">
-    <link rel="modulepreload" crossorigin href="/assets/utils-BC4DHlz2.js">
-    <link rel="modulepreload" crossorigin href="/assets/dialog-DtdR05v1.js">
+    <link rel="modulepreload" crossorigin href="/assets/a11y-prefs-BqoP5goK.js">
     <link rel="modulepreload" crossorigin href="/assets/lib-DWJfei6y.js">
-    <link rel="modulepreload" crossorigin href="/assets/getTimezoneOffsetInMilliseconds-vJ7qUoqN.js">
-    <link rel="modulepreload" crossorigin href="/assets/formatDistanceToNow-NjPHBLfB.js">
-    <link rel="modulepreload" crossorigin href="/assets/button-4FS1ZDTp.js">
-    <link rel="modulepreload" crossorigin href="/assets/project-repositories-Cnnuj9Ia.js">
-    <link rel="modulepreload" crossorigin href="/assets/RepositoryScopeSelector-2eSqR9WK.js">
-    <link rel="modulepreload" crossorigin href="/assets/TicketDetailModalContext-Dkwo2cDs.js">
-    <link rel="modulepreload" crossorigin href="/assets/core-B3mKBIh5.js">
-    <link rel="modulepreload" crossorigin href="/assets/RepositoryDeliveries-B4ybHOyB.js">
-    <link rel="modulepreload" crossorigin href="/assets/useRuntimeRuns-C97qEqMg.js">
-    <link rel="modulepreload" crossorigin href="/assets/event-Bt7f3wXe.js">
-    <link rel="stylesheet" crossorigin href="/assets/index-BgbCbIua.css">
+    <link rel="modulepreload" crossorigin href="/assets/getTimezoneOffsetInMilliseconds-O61feXch.js">
+    <link rel="modulepreload" crossorigin href="/assets/formatDistanceToNow-DLMIOS0N.js">
+    <link rel="modulepreload" crossorigin href="/assets/select-xA3pSmqE.js">
+    <link rel="modulepreload" crossorigin href="/assets/empty-state-D5w9OWj-.js">
+    <link rel="modulepreload" crossorigin href="/assets/launch-forecast-BTa-p3RP.js">
+    <link rel="modulepreload" crossorigin href="/assets/format-BODoFIw6.js">
+    <link rel="modulepreload" crossorigin href="/assets/RailTrack-BfLmBzBh.js">
+    <link rel="modulepreload" crossorigin href="/assets/jira-api-DHme7Upx.js">
+    <link rel="modulepreload" crossorigin href="/assets/project-repositories-DJPeAVBK.js">
+    <link rel="modulepreload" crossorigin href="/assets/RepositoryScopeSelector-DcxbKI9w.js">
+    <link rel="modulepreload" crossorigin href="/assets/TicketDetailModalContext-B-Gtm6Ob.js">
+    <link rel="modulepreload" crossorigin href="/assets/compass-B7guwBlY.js">
+    <link rel="modulepreload" crossorigin href="/assets/copy-DOPlLymH.js">
+    <link rel="modulepreload" crossorigin href="/assets/useRuntimeRuns-BRS6ncnO.js">
+    <link rel="modulepreload" crossorigin href="/assets/event-BEnMLqAi.js">
+    <link rel="stylesheet" crossorigin href="/assets/index-4UWY7Xyz.css">
   </head>
   <body>
     <div id="specrails-splash" aria-hidden="false" role="status" aria-label="Loading Specrails">

package/docs/ci-cd.md CHANGED Viewed

@@ -36,6 +36,34 @@ npm publication is serialized across versions and checks the current `latest` ve
 Release admission uses the current run/attempt of the named CI workflow and the exact SHA, repository, branch and event. The metadata workflow consumes no artifacts from an untrusted pull request. [Workflow-run trust and event behavior](https://docs.github.com/en/actions/reference/workflows-and-actions/events-that-trigger-workflows), [workflow runs API](https://docs.github.com/en/rest/actions/workflow-runs).
+## Update channels
+Desktop offers two update channels, chosen in **App settings ▸ Updates ▸ Update channel** and stored as the app setting `updateChannel` (`GET/PUT /api/settings`):
+| Channel | Desktop updater manifest | Core (npm dist-tag) |
+|---|---|---|
+| `latest` (default) | `releases/latest/download/latest.json`, the newest release, written by `Desktop Release` | `latest` |
+| `stable` | `releases/download/stable/latest.json`, the promoted release | `stable`; while Core publishes no `stable` dist-tag the check falls back to `latest` and reports `channelFallback: true` |
+**Mechanism.** `stable` is a single moving GitHub **pre-release** tagged `stable`. Its assets are verbatim copies of the promoted version's `latest.json` and `manifest.json`, plus `stable.json` (`{ version, tag, sha, promotedAt }`). The copied `latest.json` still points at that version's signed installers, so promotion rebuilds and re-signs nothing, and the updater's signature check is unchanged. Because the pointer is a pre-release created with `--latest=false`, it never becomes the repository's "latest" release, so the `latest` channel, `release-policy.mjs latest` and specrails.dev downloads are unaffected. The `stable` tag is only an anchor for that release; it is not a version tag and does not match the `v*` trigger of `Desktop Release`.
+The updater endpoint compiled into `tauri.conf.json` stays the `latest` manifest. The app checks through the native command `check_app_update(channel)` (`src-tauri/src/app_updates.rs`), which rebuilds the updater with the selected channel's endpoint and hands the stock plugin `Update` back to the UI, so download, signature verification and install use the plugin unchanged. A `stable` check before the first promotion fails with `stable-channel-unavailable`; the app says so instead of silently switching the user to `latest`.
+**Promoting a release to stable.** Run the `Promote Stable` workflow (`.github/workflows/promote-stable.yml`, `workflow_dispatch` only) with `version=X.Y.Z`:
+```sh
+gh workflow run promote-stable.yml -f version=2.64.2 -f allow_rollback=false
+```
+`node scripts/release-policy.mjs stable-promotion` admits the promotion only when:
+- `vX.Y.Z` is a published GitHub release (not a draft or prerelease) carrying `latest.json`;
+- it was published at least **7 days** ago (`STABLE_SOAK_DAYS`);
+- the exact commit of the tag has a successful `CI` push run on `main` in this repository;
+- it does not move stable to an older version, unless `allow_rollback=true` is set for an incident rollback.
+Only then does the job copy the assets onto the `stable` pre-release (creating it on first use). Nothing is promoted automatically; promoting is a deliberate maintainer action, typically monthly. Core's `stable` dist-tag is promoted in specrails-core on the same cadence; Desktop needs no change when it appears.
 ## Native validation without publication
 Manually running `Desktop Release` defaults to `validation_only=true`. Select a trusted branch in this repository: admission requires successful push CI for that exact branch and SHA, and refuses evidence from another branch, a pull request or a fork. Selecting an existing matching release tag instead requires its main push CI. Validation builds retain their artifacts in GitHub Actions; macOS signing/notarization remains mandatory and the existing Windows installer signing policy is unchanged. The entire GitHub Release publication job is skipped. A passing validation build does not publish a release or move an update channel.
@@ -50,7 +78,7 @@ The macOS job retains `artifacts/chromium-signing/` as the `chromium-signing-mac
 ### Download channel
-GitHub Releases is the only Desktop download channel. Each release carries the canonical installers, the Tauri updater assets and `manifest.json` (version, sha256 and size per platform, with GitHub asset URLs). The Tauri updater reads `releases/latest/download/latest.json`; specrails.dev reads the latest release through the GitHub API. Nothing is uploaded to Hostinger, so a release has no second publication step to recover.
+GitHub Releases is the only Desktop download channel. Each release carries the canonical installers, the Tauri updater assets and `manifest.json` (version, sha256 and size per platform, with GitHub asset URLs). The Tauri updater reads `releases/latest/download/latest.json` on the `latest` channel and the `stable` pointer on the `stable` channel (see [Update channels](#update-channels)); specrails.dev reads the latest release through the GitHub API. Nothing is uploaded to Hostinger, so a release has no second publication step to recover.
 - `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.
 - 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).

package/docs/cli.md CHANGED Viewed

@@ -4,7 +4,7 @@ The `specrails-desktop` CLI does three things:
 1. **Manages the app server** — start, stop, status.
 2. **Manages projects** — list, add, remove.
-3. **Routes commands into the running server** — implement specs, run health checks, pass raw prompts to your AI CLI.
+3. **Routes commands into the running server** — implement specs, retry a failed run, pass raw prompts to your AI CLI.
 Everything here is grouped by what you're trying to do, not by alphabetical order of flags.
@@ -43,7 +43,7 @@ specrails-desktop --status              # one-shot status, compact text output
 specrails-desktop --jobs                # see the note below
 ```
-`--status` prints a compact status line that includes the app version. The bare `status` subcommand prints whether the app is running (with its PID and URL) plus the registered project count and names — but no version. Both are plain text, handy to read or grep, not JSON.
+`--status` prints a compact status line that includes the app version and, from servers that report it, the HTTP API version (`api: v1`, from `apiVersion` in `/api/health`). Scripts can also read the `X-Specrails-Api-Version` response header or `GET /api/meta`; see the [versioning policy](internals/api-reference.md#versioning-and-deprecation-policy). The bare `status` subcommand prints whether the app is running (with its PID and URL) plus the registered project count and names — but no version. Both are plain text, handy to read or grep, not JSON.
 > **Note on `--jobs`:** there is no app-level `/api/jobs` route, so the server returns 404 and `--jobs` prints `jobs history requires manager with SQLite persistence (#57)` and exits non-zero against a running server. Job history lives **per project** — view it on the project's **Jobs** page (right sidebar) in the dashboard instead.
@@ -62,7 +62,7 @@ specrails-desktop add .                 # register the current directory
 specrails-desktop add /path/to/project  # or an explicit path
 ```
-Registers the project with the app. The path can be **absolute or relative** (it's resolved against your current directory) and must exist. If the project doesn't have specrails-core installed, the next dashboard visit triggers the setup wizard.
+Registers the project with the app. The path can be **absolute or relative** (it's resolved against your current directory) and must exist. The app then assembles the project's Specrails workspace in the background (outside your repository), exactly as when you add it from the dashboard; there is no setup wizard.
 ### Remove
@@ -70,7 +70,7 @@ Registers the project with the app. The path can be **absolute or relative** (it
 specrails-desktop remove <project-id>
 ```
-Unregisters the project (use the **ID** from `specrails-desktop list`). Does **not** delete the project directory or its specrails-core installation. To re-register, just `add` it again — job history under `~/.specrails/projects/<slug>/jobs.sqlite` is preserved.
+Unregisters the project (use the **ID** from `specrails-desktop list`). Does **not** delete the project directory. To re-register, just `add` it again — job history under `~/.specrails/projects/<slug>/jobs.sqlite` is preserved.
 ## Run things in the active project
@@ -103,37 +103,16 @@ specrails-desktop implement "#40" "#41" "#43"
 `implement` accepts several specs and runs them in one aggregate job. The old
 `batch-implement` verb was removed; typing it still works and runs `implement`.
-### Health check
-```bash
-specrails-desktop health-check
-```
-Runs `/specrails:health-check`: a comprehensive codebase health pass (tests, linting, coverage, complexity, dependency audit), comparing against previous runs to surface regressions.
-### Compatibility check
-```bash
-specrails-desktop compat-check
-```
-Runs `/specrails:compat-check`: snapshots the current API surface and detects breaking changes against a prior baseline, generating a migration guide when breaking changes are found.
 ### Known verbs
-These are all shorthand for `/specrails:<verb>` — the app auto-prefixes:
+These are shorthand for `/specrails:<verb>` — the app auto-prefixes them. They are the only commands Core 6 ships:
 | Verb | What it does |
 |------|--------------|
-| `implement` | Queue a rail job for one or more specs (one aggregate run) |
-| `why` | Explain why a chunk of code looks the way it does |
-| `propose-spec` | Explore an idea and produce a structured spec proposal |
-| `get-backlog-specs` | View the prioritised spec backlog |
-| `auto-propose-backlog-specs` | Auto-propose new spec ideas from the backlog |
-| `refactor-recommender` | Scan the codebase and recommend high-leverage refactors |
-| `health-check` | Run the codebase health check |
-| `compat-check` | Detect breaking API changes against a baseline |
-| `enrich` | Run the agent enrichment workflow |
+| `implement` | Queue a job for one or more specs (one aggregate run) |
+| `retry` | Resume a failed `implement` run from its last successful phase |
+The removed `batch-implement` verb still maps to `implement`. Commands retired from Core (for example `why`, `health-check`, `compat-check`, `refactor-recommender`, `propose-spec`, `get-backlog-specs`, `auto-propose-backlog-specs`, `enrich`) are no longer verbs: typing one is passed through as a raw prompt.
 ### Pass a raw prompt
@@ -191,7 +170,7 @@ If you invoke a command that routes work (`implement`, a raw prompt, …) while
 [specrails-desktop] manager not running — invoking claude directly
 ```
-This fallback has two important limitations:
+This fallback has one important limitation:
 - **Nothing is recorded.** There's no queue, no job in the Dashboard, and nothing written to Analytics.

package/docs/codex.md CHANGED Viewed

@@ -77,7 +77,7 @@ still takes precedence.
 | **Reasoning efforts** | `low`–`xhigh` | model-dependent | none | `low`/`high`/`max`, K3 only |
 | **Agent profiles** | ✅ | legacy | legacy | ✅ provider-scoped |
 | **Implement** | ✅ | ✅ | ✅ | ✅ |
-| **Freestyle** | ✅ | ❌ | ❌ | ✅ |
+| **Freestyle** | ✅ (+ interactive chat) | ✅ non-interactive | ✅ non-interactive | ✅ non-interactive |
 | **Pure-output transforms** | capability-dependent | capability-dependent | capability-dependent | ❌ fail closed |
 | **Session resume** | `--resume` | `exec resume` | `--resume` | bound `--session=<id>` after resume hint |
 | **Native cost report** | exact | estimated | estimated | unavailable |

package/docs/creating-specs.md CHANGED Viewed

@@ -4,7 +4,7 @@ A **spec** in specrails-desktop is a description of work you want done — what
 ## Creating a spec
-Open the Dashboard and click **Add** (the Plus button on the SpecsBoard toolbar). The **Add Spec** dialog opens with three modes:
+Open the Dashboard and click **New spec** (the Plus button on the SpecsBoard toolbar). The **Add Spec** dialog opens with three modes:
 - **Quick** — you describe what you want; the AI writes the full spec.
 - **Explore** — you converse with the AI and shape the spec turn by turn.
@@ -181,27 +181,30 @@ Every spec card shows a status indicator that stays consistent across view modes
 ## Filtering and sorting
-The SpecsBoard toolbar always shows these four controls plus the Add button:
+The SpecsBoard toolbar has two rows that line up with the Rails toolbar across the splitter.
-- **Status filter** — a single-select dropdown with three values: **All**, **ToDo**, **Done**. Defaults to **All**, which shows everything (including drafts and done specs).
-- **Label dropdown** — multi-select across every label used in the project.
-- **Sort** — **Default**, **Ticket #**, or **Priority**, each with an ascending/descending toggle.
-- **View toggle** — switch between List view and Post-it view (see below).
+**Row 1** (left to right):
-Two more filters appear **only once your board has the data for them**, so don't be surprised if you see five or six controls. Both are surfaced only on **Jira-linked** projects:
+- **Search** — narrows the board by title, `#number` (or a bare number), label or Jira key, as you type. Press `/` anywhere on the board to jump to it; `Esc` clears it, a second `Esc` leaves the field. Search is not saved: it resets when you switch projects.
+- **Filters** — one button for every filter beyond status. A badge shows how many values are active. It opens a panel with a section per dimension, each with its own **Clear**:
+  - **Labels** — multi-select across every label in the project (a "Find a label" box appears once there are more than eight).
+  - **Epic**, **Sprint** and **Jira status** — shown only on **Jira-linked** projects that carry that data. Jira status lists the board's real workflow statuses (e.g. "Code Review") grouped under the state they map to.
+- **Sort and view** — **Default**, **Ticket #**, **Priority** (plus **Jira key** on Jira-linked projects), the ascending/descending toggle, and the List / Post-it switch. On a narrow column they fold into one menu.
+- **New spec** — the primary action (also `⌘↵`).
-- **Epic filter** — appears once at least one spec carries a Jira epic, letting you narrow the board to one epic's children.
-- **Sprint filter** — appears when specs carry Jira sprint data.
+**Row 2** is the **status selector**: **Active** (default: draft, todo, in progress, on review), **All**, then one segment per status, each with a live count. On a narrow column the less-used statuses fold into **More**; the status you picked always stays visible.
-On a **Jira-linked** project the Sort dropdown also gains a fourth mode, **Jira key**, so you can order the board by Jira ticket number.
+**Row 3** appears only while a search or filter narrows the board: one removable chip per active value, "x of y" specs, and **Clear all**, which clears search and filters but keeps your status pick.
-Priority itself is set per spec from the right-click menu (below), not from a toolbar filter — there is no priority filter and no search box on the board.
+Filters and the status pick are remembered per project; status and Jira status are also mirrored to the URL.
+Priority itself is set per spec from the right-click menu (below), not from a toolbar filter — there is no priority filter.
 ## Right-click context menu
 Right-click any spec card (in any view mode):
-- **Delete ticket** — with confirmation.
+- **Delete ticket** — applies at once and offers **Undo** (also **⌘Z** / **Ctrl+Z**) for about eight seconds. The spec moves to **Settings → Recently deleted** for 30 days, where it can be restored or deleted permanently.
 - **Change status → Todo / Done**
 - **Set priority → Critical / High / Medium / Low**

package/docs/customizing.md CHANGED Viewed

@@ -4,7 +4,7 @@ Every setting you can change, grouped by where you'll find it.
 ## Themes
-Open **Desktop Settings** (gear icon at the bottom of the Arc sidebar) → **Appearance**.
+Open **App settings** (gear icon at the bottom of the left sidebar) → **Appearance**.
 Five built-in themes:
@@ -33,16 +33,19 @@ The active theme persists to `desktop_settings.ui_theme` on the server and mirro
 Both sidebars cycle through the same three states with their pin icon:
-- **Pinned-open** — always wide.
-- **Pinned-collapsed** — always a narrow strip of icons.
-- **Unpinned** *(default)* — collapsed strip that expands on hover.
+- **Pinned-open** — always wide; the content makes room for it. The **left** sidebar starts here.
+- **Pinned-collapsed** — always a narrow strip of icons. On the left strip each project shows a two-letter tile (for example **SD** for *specrails-desktop*), with a badge when one of its missions needs you.
+- **Unpinned** — a narrow strip that opens when you rest the pointer on it (or move keyboard focus into it) and closes shortly after you leave. It opens *over* the content, so nothing underneath jumps. The **right** sidebar starts here.
-Keyboard shortcuts:
+In a window 1100px wide or narrower, a pinned-open sidebar behaves as unpinned so the content keeps its room; widen the window and it docks again. Drag a sidebar's inner edge to resize it (or focus the edge and use the arrow keys; **Home** resets).
+Keyboard shortcuts (the VS Code / Cursor convention):
 | Shortcut | Action |
 |----------|--------|
-| `Cmd+B` / `Ctrl+B` | Cycle the **right** project sidebar (Chat) |
-| `⌥⌘B` / `Ctrl+Alt+B` | Cycle the **left** Arc sidebar |
+| `Cmd+B` / `Ctrl+B` | Cycle the **left** sidebar (projects and missions) |
+| `⌥⌘B` / `Ctrl+Alt+B` | Cycle the **right** sidebar (project sections, or **On workspace** in Mission mode) |
+| `⌘[` `⌘]` / `Ctrl+[` `Ctrl+]` or `Alt+←` `Alt+→` | **Back / Forward** through the places you have visited (also the title-bar **← →** buttons and the mouse back/forward buttons; ignored while typing) |
 State is per-machine (local UI preference, not synced).
@@ -67,7 +70,7 @@ A custom instruction appended to every **Implement** rail job, after the ticket
 ### Freestyle pre-prompt
-The instruction sent to the selected provider for **Freestyle** rails. Freestyle skips the OpenSpec pipeline — it hands that provider this pre-prompt plus the spec text and lets it implement autonomously. Claude currently advertise Freestyle support. The spec text is appended automatically after the pre-prompt. Leave it blank to use the built-in default.
+The instruction sent to the selected provider for **Freestyle** rails. Freestyle skips the OpenSpec pipeline — it hands that provider this pre-prompt plus the spec text and lets it implement autonomously. Claude, Codex, Gemini, Kimi and local engines support Freestyle; only Claude adds the interactive in-job chat. The spec text is appended automatically after the pre-prompt. Leave it blank to use the built-in default.
 ### Telemetry
@@ -75,13 +78,13 @@ Opt-in OpenTelemetry capture for rail runs.
 | Setting | Behaviour |
 |---------|-----------|
-| **Enable pipeline telemetry** | Default OFF. When ON, every rail spawn gets OTLP env vars injected. Each rail's traces/metrics/logs are captured to a `.ndjson.gz` blob. |
+| **Enable pipeline telemetry** | Default ON (a project without a saved choice records telemetry). When ON, every queued pipeline job spawn gets OTLP env vars injected (see Scope below). Each rail's traces/metrics/logs are captured to a `.ndjson.gz` blob. |
 When telemetry is on, the **Diagnostic ZIP** button appears on every job's detail page. The ZIP contains `job-metadata.json`, `telemetry.ndjson`, `logs.txt`, `summary.md`, and per-job snapshots of the agent profile and active plugins.
 Retention: raw blobs > 7 days old are compacted at startup (file deleted, aggregates kept).
-Scope: rails only. The sidebar chat, Explore, AI Edit, and the setup wizard are not instrumented (telemetry env injection happens only in the queue manager).
+Scope: jobs that run through the project's job queue (CLI pipeline runs: rails when Loops are disabled, and `implement` commands from the CLI). Telemetry env injection happens only in the queue manager, so loop runs (the default rail path), the sidebar chat, Explore, AI Edit and missions are not instrumented.
 ### Terminal panel
@@ -104,7 +107,7 @@ See [terminal.md](terminal.md) for the full reference of keyboard shortcuts and
 ## App-wide settings
-Open **Desktop Settings** from the Arc sidebar. These apply across every project.
+Open **App settings** from the bottom of the left sidebar. These apply across every project.
 | Section | What it does |
 |---------|--------------|
@@ -136,7 +139,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@^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_CORE_BIN` | Override the `specrails-core` binary (default: the Core bundled with the desktop app; without a bundle, `npx --yes --prefer-online specrails-core@^6.0.0`, the `CORE_PACKAGE_SPEC` range in `server/core-package.ts`) |
 | `SPECRAILS_TECH_URL` | Override the specrails-tech proxy base URL |
 | `SPECRAILS_LOGIN_SHELL_TIMEOUT_MS` | Budget in milliseconds for reading configured project environment names from your login shell (default `10000`, max `120000`). Raise it when the Environment card shows **Shell timed out**. See the [project environment guide](guide/en/settings/5-project-environment.md) |
 | `SPECRAILS_AGENTS_SECTION=false` | Hide the Agents section from every project |
@@ -161,7 +164,7 @@ These feature flags are **default ON**. Set the flag to `false` to hide the feat
 | `VITE_FEATURE_TERMINAL_PANEL=false` | Hide the bottom terminal panel |
 | `VITE_FEATURE_AGENTS_SECTION=false` | Hide the Agents section |
 | `VITE_FEATURE_CODE_EXPLORER=false` | Hide the Code section |
-| `VITE_FEATURE_JIRA=false` | Hide the Jira integration UI (settings section + spec badges) |
+| `VITE_FEATURE_JIRA=false` | Hide the Jira integration UI (Plugins entry + spec badges) |
 | `VITE_FEATURE_INTERACTIVE_JOBS=false` | Hide the in-job chat UI (the composer on Job Detail / the job modal, plus its Finalize / Wrap-up actions) |
 | `VITE_FEATURE_EXPLORE_REVIEW=false` | Disable the Review step in the Explore shell |
 | `VITE_FEATURE_EXPLORE_PREMIUM_UX=false` | Disable the "Conectando…/Pensando…/Consultando código…" pills above the Explore streaming bubble |

package/docs/getting-started.md CHANGED Viewed

@@ -1,6 +1,6 @@
 # Getting started
-This guide walks you from "I just heard about specrails-desktop" to "I just shipped my first AI-driven change" in about ten minutes. No prior knowledge of specrails-core required — the app installs it for you.
+This guide walks you from "I just heard about specrails-desktop" to "I just shipped my first AI-driven change" in about ten minutes. No prior knowledge of specrails-core required — the app sets it up for you.
 ## What you'll need
@@ -8,7 +8,7 @@ This guide walks you from "I just heard about specrails-desktop" to "I just ship
 If you install with **npm** (Option 2 below) you'll also need **Node.js 20+** and **`git`** on your PATH. The **desktop app** bundles its own Node and Git runtimes, so you don't need those installed separately.
-That's it. specrails-desktop will install specrails-core in your project on first run if it isn't there yet.
+That's it. specrails-desktop sets up specrails-core for each project automatically, outside your repository.
 ## Install
@@ -38,7 +38,7 @@ By default the app binds to `http://127.0.0.1:4200`. Open it in your browser.
 There are two ways. Pick whichever feels natural.
-**From the dashboard:**
+**From the dashboard:** click **+ Add project** in the sidebar. Choose **Existing project** and pick the repository folder (the display name defaults to the folder name), or choose **New project** to describe an idea and let the Project Builder bootstrap a repository with a Milestone-1 backlog (see [Project builder](internals/project-builder.md)).
 **From the CLI:**
@@ -47,15 +47,16 @@ specrails-desktop add /path/to/your/project
 specrails-desktop list   # verify
 ```
-### If the project doesn't have specrails-core yet
+### What happens after you add it
-The setup wizard runs automatically. Three steps:
+There is no setup wizard. The project registers immediately and Specrails assembles its workspace in the background:
-1. **Configure** — pick a model preset (Balanced / Budget / Max) and optionally override the model per agent. There are no role files to choose or install: the three pipeline roles (`sr-architect`, `sr-developer`, `sr-reviewer`) are defined by the Core engine's runtime, and their definitions, provider and model live in **Settings → Agent runtime**.
-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 commands landed; its **Agents** tile counts only the project's custom roles (`custom-*`), because the baseline roles are not installed as files. Click **Continue to project**.
+- **AI CLIs are auto-detected.** The app uses every supported CLI it finds on your machine (Claude, Codex). If none is detected, the Add Project dialog shows a warning, but registration is never blocked; the project picks up a provider as soon as one is detected.
+- **The workspace lives outside your repository.** For each detected provider the app runs specrails-core `init` (from the bundled Core in the desktop app, or `npx specrails-core@^6.0.0` when no bundle is present) into `~/.specrails/projects/<slug>/workspace`. Your repository stays pristine: the framework files are not scaffolded into it.
+- **Progress shows on the project's sidebar entry.** A small indicator ("Setting up workspace…") appears while assembly runs. If a provider fails, the entry shows "Workspace setup failed — click to retry"; the retry only re-runs the providers that failed.
+- **Roles and models are configured in the app, not installed as files.** The pipeline roles (`sr-architect`, `sr-developer`, `sr-reviewer`) are defined by the Core engine's runtime; their provider and model live in **Settings → Agent runtime**. Per-agent overrides live in agent profiles on the **Agents** page.
-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).
+The Core version is pinned to the major the app ships with (Core 6); it never silently jumps to a new major. Newer Core releases within that major are offered through the voluntary update channel (see [Core runtime updates](internals/core-runtime-updates.md)).
 ## Your first spec
@@ -119,9 +120,9 @@ lsof -i :4200    # macOS / Linux
 On macOS, this usually means the app was launched from Finder/Dock and didn't pick up Homebrew/Volta paths. The app resolves PATH at startup automatically, but if it still fails, see [platforms/macos.md](platforms/macos.md).
-**The setup wizard fails on `npx specrails-core init`**
+**The sidebar shows "Workspace setup failed"**
-Most likely Node is missing from the shell environment that launched the app, or whichever AI CLI your project uses isn't authenticated:
+Click the entry to retry. If it keeps failing, the usual causes are a missing Node runtime in the environment that launched the app (npm installs only; the desktop app bundles Node) or an AI CLI that isn't authenticated:
 - **Claude** — sign in to the `claude` CLI or set `ANTHROPIC_API_KEY`.
 - **Codex** — sign in to the `codex` CLI.

package/docs/guide/de/agents/1-meet-the-agents.md CHANGED Viewed

@@ -1,4 +1,4 @@
-# Die Agents im Überblick
+# Die Agents im Überblick {#agents}
 Wenn du eine **Implement**-Rail startest, übergibt Specrails deine Spec nicht einfach einer einzigen KI und hofft auf das Beste. Stattdessen arbeitet ein kleines Team spezialisierter *Agents*, jeder mit einer einzigen Aufgabe und in einer bewusst gewählten Reihenfolge. Diese Seite stellt dir vor, wer zu diesem Team gehört und was jeder Einzelne tut.

package/docs/guide/de/getting-started/2-installing-and-first-run.md CHANGED Viewed

@@ -39,3 +39,5 @@ Du siehst:
 Das ist das gesamte Onboarding – kein Konto anzulegen, keine Registrierung. specrails läuft komplett auf deinem Rechner.
 Klicke auf **Dein erstes Projekt hinzufügen** und weiter geht's mit [Dein erstes Projekt hinzufügen](adding-your-first-project).
+Oder starte mit dem [Beispielprojekt](try-the-sample-project): einem kleinen Spiel und drei fertigen Specs, mit den Kosten vorab.

package/docs/guide/de/getting-started/3-try-the-sample-project.md ADDED Viewed

@@ -0,0 +1,35 @@
+# Das Beispielprojekt ausprobieren
+Du willst sehen, wie aus einer Spec eine geprüfte Änderung wird, bevor du specrails auf deinen eigenen Code richtest? Das **Beispielprojekt** ist ein kleines Tic-Tac-Toe-Webspiel mit drei fertigen Specs. Es dauert ein paar Minuten und endet bei einem echten **Review-Paket**.
+## Starten
+Klicke auf dem Startbildschirm auf **Am Beispielprojekt ausprobieren** (neben **Erstes Projekt hinzufügen**). Der Dialog sagt dir, bevor etwas passiert:
+- **Was angelegt wird**: ein kleines Webspiel in einem eigenen Git-Repository, mit drei Specs, die schon auf deinem Board liegen.
+- **Wo**: standardmäßig `~/Specrails Samples/tic-tac-toe` in deinem Home-Ordner. Du kannst den Ordner ändern; ein vorhandener Ordner wird nie überschrieben.
+- **Was ein Lauf kosten würde**: eine Schätzung wie „≈ 0,30–1 $ · etwa 3–5 Min.“. Dollar werden nur gezeigt, wenn dein Anbieter nutzungsabhängig abrechnet. Bei einem Abo steht dort, dass keine Zusatzkosten entstehen, und bei einer lokalen Engine fallen keine API-Kosten an.
+Das Anlegen des Beispiels kostet nichts und führt nichts aus. Klicke auf **Beispielprojekt anlegen**, und du landest auf dem Board.
+## Die drei Schritte
+Eine kleine Anleitungskarte zeigt Schritt für Schritt auf das echte Board. Du kannst sie jederzeit schließen; sie schrumpft zu einer Pille **Beispielprojekt**, über die **Anleitung anzeigen** sie zurückholt.
+1. **Die Spec.** Die drei Specs sind für dich geschrieben. Jede sagt, was zu bauen ist und woran man erkennt, dass sie fertig ist.
+2. **Die Rail.** Klicke auf **Erste Spec ausführen**. Das Beispiel ist günstig und begrenzt eingestellt: Schnellmodus, das günstigste verfügbare Modell und ein weiches Limit pro Lauf (der Lauf pausiert und fragt nach, bevor er 1 $ überschreitet). Hast du eine lokale Engine eingerichtet, kannst du sie stattdessen wählen – ohne API-Kosten.
+3. **Das Review.** Nichts wird von allein gemergt. Wenn der Lauf endet, zeigt ein **Review-Paket**, was sich geändert hat, und lässt dich es annehmen oder verwerfen.
+## Kein KI-Anbieter bereit?
+Bevor der Lauf angeboten wird, prüft specrails, ob ein Anbieter installiert und angemeldet ist. Ist keiner bereit, bekommst du stattdessen **Aufgezeichneten Lauf ansehen**: die Wiedergabe eines fertigen Laufs, die bei einem Review-Paket endet. Sie ist deutlich als Aufzeichnung gekennzeichnet; nichts läuft und nichts wird berechnet. Installiere einen Anbieter oder melde dich an und wähle **Erneut prüfen**, um zu einem echten Lauf zu wechseln.
+## Danach: dein eigenes Projekt
+Die Anleitung endet mit **Jetzt eigenes Projekt hinzufügen**. Wenn du mit dem Beispiel fertig bist, entfernt **Beispiel entfernen** es mit einem Klick. Der Ordner bleibt auf der Festplatte, außer du hakst **Beispielordner auch löschen** an – das lässt sich nicht rückgängig machen.
+## Die Plattform-Tour wiederholen
+Die Tour ist nicht mehr auf dem Startbildschirm. Öffne **Docs** und wähle **Tour wiederholen**, oder öffne die Befehlspalette und tippe „Tour wiederholen“. Sie steht auch unter **Einstellungen ▸ Darstellung**.
+Weiter: [Erstes Projekt hinzufügen](adding-your-first-project).