specrails-desktop 2.56.0 → 2.57.0

package/cli/dist/args.js

@@ -9,14 +9,7 @@ exports.DEFAULT_PORT = 4200;
 exports.KNOWN_VERBS = new Set([
     'implement',
     'batch-implement',
-    'why',
-    'get-backlog-specs',
-    'auto-propose-backlog-specs',
-    'propose-spec',
-    'refactor-recommender',
-    'health-check',
-    'compat-check',
-    'enrich',
+    'retry',
 ]);
 function parseArgs(argv) {
     // argv is process.argv.slice(2)

package/cli/dist/help.js

@@ -45,13 +45,7 @@ ${(0, output_1.bold)('Project Required:')}
 ${(0, output_1.bold)('Usage:')}
   specrails-desktop implement #42                Run a known specrails verb (prepends /specrails:)
   specrails-desktop batch-implement #40 #41      Batch implementation across issues
-  specrails-desktop why                          Explain recent changes
-  specrails-desktop get-backlog-specs            View prioritized spec backlog
-  specrails-desktop auto-propose-backlog-specs   Generate new spec ideas
-  specrails-desktop propose-spec                 Explore an idea and produce a spec
-  specrails-desktop refactor-recommender        Find refactoring opportunities
-  specrails-desktop health-check                Run codebase health check
-  specrails-desktop compat-check                Check for breaking API changes
+  specrails-desktop retry                        Resume the saved implementation run
   specrails-desktop "any raw prompt"             Pass a raw prompt directly to claude
   specrails-desktop --status                     Print manager status and exit
   specrails-desktop --jobs                       Print recent job history and exit

package/docs/internals/core-runtime-updates.md

@@ -7,14 +7,16 @@ read-only discovery; it does not execute a PATH shim or install a global package
 An explicit `SPECRAILS_CORE_BIN` wins when it resolves to a usable compatible
 package. Otherwise Desktop selects the newest compatible package from its
 activated managed installation, bundled resources, local dependency and external
-CLI on PATH. Core 4 and 5 remain supported. A runtime older than the active
+CLI on PATH. Supported Core majors are 4, 5 and 6 (`SUPPORTED_CORE_MAJORS` in
+`server/core-package.ts`). A runtime older than the active
 framework is rejected rather than silently replacing an update.
 
 ## Persistence and publication
 
-The release bundle pins Core 5.6.0 in `desktop-release.yml` and
-`scripts/assemble-bundled-core.lock.json`. This includes scoped runtime recovery
-and the Opus 5.5 alias. Update both pins together and check compatibility against
+The release bundle pins Core 6.0.0 in `desktop-release.yml` and
+`scripts/assemble-bundled-core.lock.json`. Core 6 is the Desktop-only engine: it
+publishes integration contract 5.0 (no standalone `update`) and ships only the
+implement, batch-implement and retry workflows. Update both pins together and check compatibility against
 the staged published package; retained runs still use their original runtime.
 
 Desktop updates retain the complete npm installation, including dependencies,

package/package.json

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

package/server/dist/core-compat.js

@@ -22,13 +22,7 @@ const WHICH_CMD = process.platform === 'win32' ? 'where' : 'which';
 const DESKTOP_KNOWN_COMMANDS = new Set([
     'implement',
     'batch-implement',
-    'why',
-    'product-backlog',
-    'update-product-driven-backlog',
-    'refactor-recommender',
-    'health-check',
-    'compat-check',
-    'enrich',
+    'retry',
 ]);
 function isRecord(value) {
     return typeof value === 'object' && value !== null && !Array.isArray(value);
@@ -46,11 +40,14 @@ function isRenderedProviderContract(provider, value) {
         return false;
     // Core 5 has a deterministic installer. Enrichment no longer exists and is
     // therefore not evidence of provider availability on this contract shape.
-    if (value.initCommand === 'init' && value.updateCommand === 'update') {
+    // Core 6 (contract 5.0) dropped the standalone `update` command: Desktop
+    // refreshes installs through init and the offline framework lifecycle.
+    if (value.initCommand === 'init' && (value.updateCommand === undefined || value.updateCommand === 'update')) {
         if (!isRecord(value.cli) || !isRecord(value.workflows))
             return false;
-        if (!isStringArray(value.cli.initArgs) || !isStringArray(value.cli.updateArgs)
-            || !value.cli.initArgs.includes('init') || !value.cli.updateArgs.includes('update'))
+        if (!isStringArray(value.cli.initArgs) || !value.cli.initArgs.includes('init'))
+            return false;
+        if (value.updateCommand === 'update' && (!isStringArray(value.cli.updateArgs) || !value.cli.updateArgs.includes('update')))
             return false;
         const workflows = value.workflows;
         if (!['implement', 'batch-implement', 'retry'].every(name => typeof workflows[name] === 'string' && workflows[name]))

package/server/dist/core-package.js

@@ -1,10 +1,14 @@
 "use strict";
 Object.defineProperty(exports, "__esModule", { value: true });
-exports.CORE_PACKAGE_SPEC = void 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';
+exports.CORE_PACKAGE_SPEC = exports.SUPPORTED_CORE_MAJORS = void 0;
+exports.isSupportedCoreVersion = isSupportedCoreVersion;
+/** Core majors this Desktop can drive. Core 6 publishes integration contract
+ * 5.0 (no standalone `update`); Cores 4 and 5 remain readable for installed
+ * apps. The runtime resolver selects the newest usable compatible package and
+ * never downgrades a newer activated framework. */
+exports.SUPPORTED_CORE_MAJORS = [4, 5, 6];
+function isSupportedCoreVersion(version) {
+    return exports.SUPPORTED_CORE_MAJORS.includes(Number(version.split('.')[0]));
+}
+/** Online fallback selects the Core 6 lifecycle, the same major the desktop bundles. */
+exports.CORE_PACKAGE_SPEC = 'specrails-core@^6.0.0';

package/server/dist/core-runtime.js

@@ -15,6 +15,7 @@ const fs_1 = __importDefault(require("fs"));
 const path_1 = __importDefault(require("path"));
 const artifact_registry_1 = require("./artifact-registry");
 const bundled_core_1 = require("./bundled-core");
+const core_package_1 = require("./core-package");
 const semver_lite_1 = require("./semver-lite");
 const VERSION = /^\d+\.\d+\.\d+(?:-[0-9A-Za-z.-]+)?(?:\+[0-9A-Za-z.-]+)?$/;
 function managedCoreRoot(home) {
@@ -114,8 +115,8 @@ function resolveCoreRuntime(home, external) {
         const runtime = packageForBinary(override, 'override');
         if (!runtime)
             throw new Error('SPECRAILS_CORE_BIN does not resolve to a usable specrails-core package.');
-        if (![4, 5].includes(Number(runtime.version.split('.')[0])))
-            throw new Error('The explicit Core package is not compatible with this Desktop. Supported Core majors: 4 and 5.');
+        if (!(0, core_package_1.isSupportedCoreVersion)(runtime.version))
+            throw new Error(`The explicit Core package is not compatible with this Desktop. Supported Core majors: ${core_package_1.SUPPORTED_CORE_MAJORS.join(', ')}.`);
         if (current && (0, semver_lite_1.compareVersions)(runtime.version, current) < 0)
             throw new Error(`The explicit Core ${runtime.version} is older than active framework ${current}; Desktop will not downgrade it.`);
         return runtime;
@@ -135,10 +136,7 @@ function resolveCoreRuntime(home, external) {
             candidates.push(managed);
     }
     candidates.push(...(external ?? (home === undefined ? discoverExternalCoreRuntimes() : [])));
-    const compatible = candidates.filter(candidate => {
-        const major = Number(candidate.version.split('.')[0]);
-        return major >= 4 && major <= 5;
-    }).sort((a, b) => (0, semver_lite_1.compareVersions)(b.version, a.version));
+    const compatible = candidates.filter(candidate => (0, core_package_1.isSupportedCoreVersion)(candidate.version)).sort((a, b) => (0, semver_lite_1.compareVersions)(b.version, a.version));
     const selected = compatible[0] ?? null;
     if (current && (!selected || (0, semver_lite_1.compareVersions)(selected.version, current) < 0)) {
         throw new Error(`Core framework ${current} is installed, but its runtime package is unavailable. Reinstall Core ${current} or a newer compatible version; Desktop will not downgrade it.`);

package/server/dist/core-update-manager.js

@@ -13,6 +13,7 @@ const semver_lite_1 = require("./semver-lite");
 const win_spawn_1 = require("./util/win-spawn");
 const bundled_core_1 = require("./bundled-core");
 const core_runtime_1 = require("./core-runtime");
+const core_package_1 = require("./core-package");
 const artifact_registry_1 = require("./artifact-registry");
 /** Voluntary Core updates retain the complete npm package and dependencies,
  * publish its framework, then await every project refresh. Partial refreshes
@@ -117,8 +118,8 @@ class CoreUpdateManager {
         if (!requested || !(0, semver_lite_1.isValidVersion)(requested)) {
             return { ok: false, error: 'No valid target version to update to. Check for updates first.' };
         }
-        if (!/^\d+\.\d+\.\d+(?:-[0-9A-Za-z.-]+)?$/.test(requested) || ![4, 5].includes(Number(requested.split('.')[0]))) {
-            return { ok: false, error: 'This Desktop supports Core 4 and 5. Update Desktop before installing another major version.' };
+        if (!/^\d+\.\d+\.\d+(?:-[0-9A-Za-z.-]+)?$/.test(requested) || !(0, core_package_1.isSupportedCoreVersion)(requested)) {
+            return { ok: false, error: `This Desktop supports Core ${core_package_1.SUPPORTED_CORE_MAJORS.join(', ')}. Update Desktop before installing another major version.` };
         }
         const current = (0, framework_manager_1.readCurrentFrameworkVersion)(this.home);
         if (current && !(0, semver_lite_1.isNewer)(requested, current) && !(requested === current && ((0, core_runtime_1.getCoreRuntimeStatus)(this.home).error || this.pendingVersion === requested))) {

package/.claude/commands/specrails/compat-check.md

@@ -1,271 +0,0 @@
----
-name: "Compatibility Impact Analyzer"
-description: "Snapshot the current API surface and detect breaking changes against a prior baseline. Generates a migration guide when breaking changes are found."
-category: Workflow
-tags: [workflow, compatibility, breaking-changes, migration]
----
-
-Analyze the API surface of **specrails-desktop** for backwards compatibility. Extracts the current contract surface (CLI flags, template placeholders, command names, argument flags, agent names, config keys), compares against a stored baseline, classifies each change by severity, and generates a migration guide when breaking changes are found.
-
-**Input:** `$ARGUMENTS` — optional flags:
-- `--diff` — compare current surface to most recent snapshot (default when snapshots exist)
-- `--snapshot` — capture current surface and save without diffing (default on first run)
-- `--since <date>` — diff against snapshot from this date (ISO format: YYYY-MM-DD)
-- `--propose <change-dir>` — diff proposed changes in `openspec/changes/<change-dir>/` against current surface
-- `--dry-run` — run all phases but skip saving the snapshot
-
----
-
-## Phase 0: Argument Parsing
-
-Parse `$ARGUMENTS` to set runtime variables.
-
-**Variables to set:**
-
-- `MODE` — string, one of `"snapshot"`, `"diff"`, `"propose"`. Default: `"diff"` if `.claude/compat-snapshots/` contains any `.json` files; `"snapshot"` otherwise.
-- `COMPARE_DATE` — string (ISO date) or empty string. Default: `""` (use most recent snapshot).
-- `PROPOSE_DIR` — string or empty string. Default: `""`.
-- `DRY_RUN` — boolean. Default: `false`.
-
-**Parsing rules:**
-
-1. Scan `$ARGUMENTS` for `--snapshot`. If found, set `MODE=snapshot`.
-2. Scan for `--diff`. If found, set `MODE=diff`.
-3. Scan for `--since <date>`. If found, set `COMPARE_DATE=<date>` and (if `MODE` not already set to `snapshot`) set `MODE=diff`.
-4. Scan for `--propose <change-dir>`. If found, set `PROPOSE_DIR=<change-dir>` and `MODE=propose`.
-   - Verify `openspec/changes/<change-dir>/` exists. If not: print `Error: no change found at openspec/changes/<change-dir>/` and stop.
-5. Scan for `--dry-run`. If found, set `DRY_RUN=true`.
-6. Apply default-mode logic if `MODE` is not yet set: check whether `.claude/compat-snapshots/` exists and contains `.json` files. If yes: `MODE=diff`. If no: `MODE=snapshot`.
-
-**Verify prerequisites:**
-
-- Check whether `templates/` directory exists. If not: print `Error: templates/ not found — is this a specrails repo?` and stop.
-- Check whether `bin/specrails-core.mjs` exists. If not: set `INSTALLER_AVAILABLE=false` (installer flags category will be skipped). Otherwise set `INSTALLER_AVAILABLE=true`.
-
-**Print active configuration:**
-
-```
-Mode: <MODE> | Compare date: <COMPARE_DATE or "latest"> | Dry-run: <true/false>
-```
-
----
-
-## Phase 1: Extract Current Surface
-
-Read the codebase and build the surface snapshot. Print one progress line as each category completes.
-
-**Surface category: installer_flags**
-
-If `INSTALLER_AVAILABLE=false`: print `  installer_flags: skipped (bin/specrails-core.mjs not found)` and record as unavailable.
-
-Otherwise: read `bin/specrails-core.mjs`. Extract every `--<word>` flag pattern that is accepted by the CLI dispatcher. For each flag, record the flag string and line number.
-
-Print: `  installer_flags: N found`
-
-**Surface category: template_placeholders**
-
-Read all files matching `templates/**/*.md`. For each file, extract all `` patterns (regex: `\{\{[A-Z][A-Z0-9_]*\}\}`). Deduplicate across files. For each unique key, record the list of source files it appears in.
-
-Note: Skip patterns inside code fences that are used as documentation examples (i.e., patterns that appear inside triple-backtick blocks describing placeholder syntax rather than actual template usage). Use judgment to distinguish real template placeholders from documented examples.
-
-Print: `  template_placeholders: N unique keys found`
-
-**Surface category: command_names and command_arguments**
-
-Read each file in `templates/commands/`. For each:
-- Extract `name:` value from the YAML frontmatter (between the first `---` and second `---`)
-- Extract the display name from the frontmatter `name:` field (the quoted string)
-- Find all `--<word>` flag patterns in the `$ARGUMENTS` section or argument description prose
-- Record command name, display name, source file, and flags list
-
-Print: `  command_names: N commands found`
-Print: `  command_arguments: N commands with flags documented`
-
-**Surface category: agent_names**
-
-Read each file in `templates/agents/`. Extract `name:` value from the YAML frontmatter.
-
-Print: `  agent_names: N agents found`
-
-**Surface category: config_keys**
-
-Read `openspec/config.yaml`. Extract all top-level YAML keys (lines matching `^<key>:` at zero indentation).
-
-Print: `  config_keys: N keys found`
-
-**Build the surface object:**
-
-Assemble all extracted data into a snapshot object matching the schema:
-
-```json
-{
-  "schema_version": "1",
-  "captured_at": "<ISO 8601 datetime>",
-  "git_sha": "<git rev-parse HEAD or 'unknown'>",
-  "git_branch": "<git rev-parse --abbrev-ref HEAD or 'unknown'>",
-  "surfaces": {
-    "installer_flags": [...],
-    "template_placeholders": [...],
-    "command_names": [...],
-    "command_arguments": [...],
-    "agent_names": [...],
-    "config_keys": [...]
-  }
-}
-```
-
-Set `CURRENT_SURFACE` to this object.
-
-If `MODE=snapshot`: proceed directly to Phase 5 (skip Phases 2–4 diff logic, but still print a surface summary).
-
----
-
-## Phase 2: Load Baseline
-
-Applies in `diff` and `propose` modes only.
-
-**For `diff` mode:**
-
-1. Check whether `.claude/compat-snapshots/` exists and contains `.json` files.
-   - If empty or missing: print `Advisory: no prior snapshot found. Switching to snapshot mode.` Set `MODE=snapshot`. Proceed to Phase 5.
-2. If `COMPARE_DATE` is empty: select the most recently modified `.json` file.
-3. If `COMPARE_DATE` is set: find the snapshot whose filename date is closest to `COMPARE_DATE` without exceeding it. If no match within 7 days: print `Warning: no snapshot found near <COMPARE_DATE>. Falling back to most recent.` Use most recent.
-4. Load the selected file as `BASELINE_SURFACE`.
-5. Print: `Baseline: <YYYY-MM-DD> (<sha from filename>)`
-
-**For `propose` mode:**
-
-1. Load the most recent snapshot from `.claude/compat-snapshots/` as `BASELINE_SURFACE` (same selection logic as `diff` mode with `COMPARE_DATE` empty).
-2. Additionally read `openspec/changes/<PROPOSE_DIR>/design.md` to understand the projected surface changes.
-   - If `design.md` does not exist: print `Warning: no design.md found in openspec/changes/<PROPOSE_DIR>/. Proceeding with surface extraction only (no projection).`
-   - If it exists: read also `openspec/changes/<PROPOSE_DIR>/tasks.md` if present.
-3. Use the proposed changes to project the "after" surface: identify which elements would be added, removed, or modified based on the design document.
-4. Print: `Propose mode: analyzing openspec/changes/<PROPOSE_DIR>/`
-
-Set `BASELINE_SURFACE` and `PROJECTED_CHANGES` (in propose mode).
-
----
-
-## Phase 3: Diff and Classify
-
-Applies in `diff` and `propose` modes. Skipped in `snapshot` mode.
-
-For each surface category (`installer_flags`, `template_placeholders`, `command_names`, `command_arguments`, `agent_names`, `config_keys`):
-
-1. Build identifier sets from baseline and current (or projected, in propose mode).
-2. Compute:
-   - `removed = identifiers in baseline but not in current`
-   - `added = identifiers in current but not in baseline`
-   - `common = identifiers in both`
-3. For common elements: check whether attributes changed (display name, flags list, file list). Classify attribute changes as Category 3 (Signature Change) if they affect the interface.
-4. Classify each removal:
-   - If a similar-looking name appears in `added`: classify as **Category 2: Rename** (BREAKING — MAJOR)
-   - Otherwise: classify as **Category 1: Removal** (BREAKING — MAJOR)
-5. Classify additions as non-breaking (new additions do not break existing callers).
-6. Classify behavioral changes detected from the design document (in propose mode) as **Category 4: Behavioral Change** (ADVISORY).
-
-Build two lists:
-- `BREAKING_CHANGES` — list of `{ category, element, surface, severity, description }` objects (Categories 1, 2, 3)
-- `ADVISORY_CHANGES` — list of `{ category, element, surface, description }` objects (Category 4)
-
----
-
-## Phase 4: Generate Report
-
-Print the full compatibility report.
-
-```
-## Compatibility Impact Report — specrails-desktop
-Date: <ISO date> | Commit: <git_short_sha or "unknown">
-
-### Surface Snapshot
-| Category | Elements Found |
-|----------|---------------|
-| Installer flags | N |
-| Template placeholders | N |
-| Command names | N |
-| Command argument flags | N |
-| Agent names | N |
-| Config keys | N |
-
-### Breaking Changes (N found)
-<if BREAKING_CHANGES is empty:>
-None detected.
-
-<if BREAKING_CHANGES is non-empty, for each:>
-- [Category <N>: <category-name>] <surface>: `<element>` — <description>
-
-### Advisory Changes (N found)
-<if ADVISORY_CHANGES is empty:>
-None detected.
-
-<if ADVISORY_CHANGES is non-empty, for each:>
-- [Category 4: Behavioral Change] <surface>: `<element>` — <description>
-```
-
-**Migration Guide** (only when `len(BREAKING_CHANGES) > 0`):
-
-For each breaking change, append a Migration Guide block:
-
-```
-## Migration Guide
-
-**Change type:** <Removal | Rename | Signature Change>
-**Severity:** BREAKING
-**Affects:** <who is affected>
-
-### What Changed
-<one paragraph describing before and after>
-
-### Before
-<concrete example of old usage>
-
-### After
-<concrete example of new usage>
-
-### Remediation Options
-
-**Option A — Backwards-compatible alias (recommended)**
-<how to add an alias or shim>
-
-**Option B — Clean break with changelog**
-<what to put in CHANGELOG.md>
-
-### Version Strategy
-<MAJOR bump if removing/renaming; MINOR if signature-only>
-```
-
----
-
-## Phase 5: Save Snapshot
-
-**If `DRY_RUN=true`:**
-
-Print: `Snapshot not saved — dry-run mode`
-
-Skip the save. Still perform the housekeeping check and `.gitignore` check below.
-
-**If `DRY_RUN=false`:**
-
-1. Determine filename: `<YYYY-MM-DD>-<git_short_sha>.json`. If git is unavailable: `<YYYY-MM-DD>-unknown.json`.
-2. Create `.claude/compat-snapshots/` if it does not exist.
-3. Write `CURRENT_SURFACE` serialized as JSON to `.claude/compat-snapshots/<filename>`.
-4. Print: `Snapshot saved: .claude/compat-snapshots/<filename>`
-
-**Housekeeping notice:**
-
-Count `.json` files in `.claude/compat-snapshots/`. If count > 30, print:
-
-```
-Note: .claude/compat-snapshots/ has N snapshots. Consider pruning old ones with:
-  ls -t .claude/compat-snapshots/ | tail -n +31 | xargs -I{} rm .claude/compat-snapshots/{}
-```
-
-**.gitignore suggestion:**
-
-Check whether `.claude/compat-snapshots/` appears in `.gitignore` (if `.gitignore` exists). If it does not appear, print:
-
-```
-Tip: compat snapshots are local artifacts. Add to .gitignore:
-  echo '.claude/compat-snapshots/' >> .gitignore
-```

package/.claude/commands/specrails/doctor.md

@@ -1,62 +0,0 @@
-# Doctor: specrails Health Check
-
-Run the specrails health check to validate that all prerequisites are correctly configured for this repository.
-
----
-
-## What it checks
-
-| Check | Pass condition |
-|-------|---------------|
-| Claude Code CLI | `claude` binary found in PATH |
-| Claude API key | `claude config list` shows a key OR `ANTHROPIC_API_KEY` env var set |
-| Agent files | Generated agent files exist under `.claude/agents/` |
-| CLAUDE.md | `CLAUDE.md` present in the repo root |
-| Git initialized | `.git/` directory present |
-| npm | `npm` binary found in PATH |
-
-## How to run
-
-This command uses the Node-native doctor runtime. Run it directly with:
-
-```
-npx specrails-core@latest doctor
-```
-
-If `specrails-core` is already on your `PATH`, this works too:
-
-```
-specrails-core doctor
-```
-
-## Output
-
-Each check is displayed as ✅ (pass) or ❌ (fail with fix instruction).
-
-On all checks passed:
-```
-All 6 checks passed. Run /specrails:get-backlog-specs to get started.
-```
-
-On failure:
-```
-❌ API key: not configured
-   Fix: Run: claude config set api_key <your-key>  |  Get a key: https://console.anthropic.com/
-
-1 check(s) failed.
-```
-
-## Exit codes
-
-- `0` — all checks passed
-- `1` — one or more checks failed
-
-## Log file
-
-Each run appends a timestamped summary to `~/.specrails/doctor.log`:
-
-```
-2026-03-20T10:00:00Z  checks=6 passed=6 failed=0
-```
-
-The `~/.specrails/` directory is created automatically if it does not exist.