specrails-core 4.1.1 → 4.2.0

package/docs/updating.md

@@ -7,79 +7,54 @@ SpecRails includes an update system that pulls new templates while preserving yo
 The update system uses a **manifest-based approach**:
 
 1. During installation, SpecRails generates `.specrails/specrails-manifest.json` — a checksum of every installed file
-2. On update, it compares the manifest against current files to detect what you've customized
-3. Customized files are preserved; unchanged files are updated to the latest version
+2. On update, the new templates from the latest specrails-core release are re-applied
+3. Reserved paths (`.specrails/profiles/**`, `.claude/agents/custom-*.md`) are preserved by construction — the installer never touches them
 
 ## Running an update
 
 ```bash
-curl -sL https://raw.githubusercontent.com/fjpulidop/specrails/main/update.sh | bash
+npx specrails-core@latest update
 ```
 
-Or from a local clone:
-
-```bash
-bash /path/to/specrails/update.sh
-```
+Cross-platform (macOS, Linux, Windows). No bash, no python required — the installer is native Node since v4.2.0.
 
 ### What happens
 
-1. **Backup** — creates `.claude.specrails.backup/` with your current files
-2. **Version check** — compares installed version (`.specrails/specrails-version`) with latest
-3. **Update files** — replaces unchanged files, preserves customized ones
-4. **Merge settings** — additively merges `settings.json` (your permissions are kept)
-5. **Update version** — writes new version and manifest
+1. **Version check** — reads existing `.specrails/specrails-version`; aborts if no specrails install is detected
+2. **Provider resolution** — detects whether the project uses Claude (`.claude/`) or Codex (`.codex/`)
+3. **Re-scaffold** — re-applies templates from the latest specrails-core into `.specrails/setup-templates/` and the provider directory
+4. **Reserved paths** — `.specrails/profiles/**` and `.claude/agents/custom-*.md` are skipped; your team profiles and custom agents survive untouched
+5. **Manifest refresh** — rewrites `specrails-manifest.json` and `specrails-version` to the new core version
 
-If anything fails, the backup is restored automatically.
+## Selective updates (`--only`)
 
-## Selective updates
+The `--only <component>` flag is recognised but currently warns and applies the full scaffold. Granular component selection is tracked as a follow-up — the Node installer's transactional behaviour makes a targeted re-apply almost equivalent to a full one for the common case (core version bump).
 
-Update only specific components with the `--only` flag:
+## Dry run
 
 ```bash
-# Update core files (setup command, templates, prompts, skills)
-bash update.sh --only core
-
-# Update Pipeline Monitor dashboard
-bash update.sh --only web-manager
-
-# Regenerate agents (prompts for confirmation if templates changed)
-bash update.sh --only agents
-
-# Full update (default)
-bash update.sh --only all
+npx specrails-core@latest update --dry-run
 ```
 
+Prints what the update would do without writing any files. Useful for inspecting `previousVersion → currentVersion` before committing.
+
 ## What gets preserved
 
 | File type | Behavior |
 |-----------|----------|
-| **Agent prompts** (`.claude/agents/`) | Preserved if customized; updated if unchanged |
-| **Commands** (`.claude/commands/`) | Updated (commands are orchestration, not customized) |
-| **Rules** (`.claude/rules/`) | Preserved if customized |
-| **Settings** (`settings.json`) | Merged additively (your permissions kept, new ones added) |
-| **Agent memory** (`.claude/agent-memory/`) | Always preserved |
-| **Personas** (`.claude/agents/*.md`) | Always preserved |
-| **Security exemptions** | Always preserved |
-
-## Legacy installations
-
-If you installed SpecRails before the versioning system (pre-v0.1.0):
-
-- The updater detects missing `.specrails/specrails-version` and treats it as a legacy install
-- It migrates your installation to the versioned system
-- A manifest is generated from your current files
-- Future updates use the standard manifest comparison
+| **Agent prompts** (`.claude/agents/sr-*.md`) | Re-written from latest templates |
+| **Custom agents** (`.claude/agents/custom-*.md`) | **Always preserved** (reserved path) |
+| **Profile JSON** (`.specrails/profiles/**`) | **Always preserved** (reserved path) |
+| **Commands** (`.claude/commands/specrails/`) | Re-written |
+| **Rules** (`.claude/rules/`) | Re-written from latest templates |
+| **Agent memory** (`.claude/agent-memory/`) | Untouched (created on first install only) |
+| **install-config.yaml** | Untouched |
 
 ## Rolling back
 
-If something goes wrong, restore from the automatic backup:
+The Node installer is idempotent: re-running `init` (or pinning an older version with `npx specrails-core@<version> update`) restores the prior layout. Profile and custom-agent files are reserved, so nothing critical is destroyed by a forward-then-backward sequence.
 
-```bash
-# Backups are at .claude.specrails.backup/
-cp -r .claude.specrails.backup/.claude .claude
-cp .claude.specrails.backup/.specrails/specrails-version .specrails/specrails-version
-```
+If you need a true point-in-time rollback, the recommended path is git: commit before updating, `git checkout` to revert.
 
 ---
 

package/docs/user-docs/faq.md

@@ -12,7 +12,7 @@ The plugin method (`claude plugin install sr`) installs logic into Claude Code's
 
 **Do I need Node.js if my project is not JavaScript?**
 
-Not for the plugin method (`claude plugin install sr`). Node.js 18+ is only required for the scaffold method (`npx specrails-core@latest init`). Once installed, SpecRails works with any language or framework.
+Not for the plugin method (`claude plugin install sr`). Node.js 20+ is only required for the scaffold method (`npx specrails-core@latest init`). Once installed, SpecRails works with any language or framework, on macOS, Linux, or Windows.
 
 **Do I need GitHub Issues?**
 

package/docs/windows.md

@@ -0,0 +1,53 @@
+# Windows support
+
+specrails-core runs natively on Windows 10 (1809+) and Windows 11, on both x64 and ARM64 (via the built-in x64 emulation layer). There is **no dependency on `bash`, `python3`, or any POSIX-only tooling** — the installer is pure Node.
+
+## Requirements
+
+- **Windows 10 1809+** or **Windows 11** (x64 or ARM64)
+- **Node.js ≥ 20** — install from [nodejs.org](https://nodejs.org/)
+- **git ≥ 2.25** — install from [git-scm.com](https://git-scm.com/)
+- **Claude Code** (`claude.cmd`) — install from [claude.ai/download](https://claude.ai/download)
+
+`npm install -g @anthropic-ai/claude-code` installs the Claude CLI as `claude.cmd` into your global npm bin (`%APPDATA%\npm\`). Make sure that directory is on your PATH so `where claude` resolves it.
+
+## Install
+
+From PowerShell or cmd.exe:
+
+```powershell
+cd C:\path\to\your\project
+npx specrails-core@latest init
+```
+
+The installer:
+- probes PATH with `where` (instead of the POSIX `which`),
+- spawns `.cmd` shims (`claude.cmd`, `npm.cmd`, `gh.cmd`) with `shell: true` — required by Node.js since CVE-2024-27980,
+- writes all files with LF line endings regardless of `core.autocrlf` to keep the bundled templates portable.
+
+## PowerShell execution policy
+
+If `npm` errors with `npm.ps1 cannot be loaded because running scripts is disabled on this system`, relax the policy for your user:
+
+```powershell
+Set-ExecutionPolicy -Scope CurrentUser -ExecutionPolicy RemoteSigned
+```
+
+`RemoteSigned` is the MSFT-recommended minimum for dev tooling.
+
+## Known limitations
+
+- **PATH refresh after installing new tools.** Windows GUI shells (Explorer, launcher-started apps) do not re-read PATH until logout/login. If you install `claude.cmd` and launch specrails-hub immediately, the hub's sidecar may not see it. Restart the app after changes to the Env Vars dialog, or launch from a fresh PowerShell.
+- **CRLF checkouts.** If you clone specrails-core with `core.autocrlf=true`, the repo's `.gitattributes` forces LF on every text file at checkout so the Node installer writes byte-identical artefacts across platforms. Running `git add --renormalize .` once after cloning fixes any pre-existing CRLF contamination.
+- **ARM64.** The x64 Node binary runs under Windows 11's native x64 emulation. All native dependencies we use (`better-sqlite3`, `node-pty`, etc.) resolve to their x64 prebuilts; performance hit is ~10-20% vs native ARM64 but fully functional.
+
+## CI
+
+The specrails-core GitHub Actions workflow runs the vitest suite on `windows-latest` in a matrix with `ubuntu-latest` and `macos-latest`, on Node 20 and Node 22. Any PR that regresses Windows behaviour fails CI immediately.
+
+## Reporting Windows-specific bugs
+
+[GitHub Issues](https://github.com/fjpulidop/specrails-core/issues). Include:
+- Windows version (`winver`)
+- Node version (`node --version`)
+- Full output of `npx specrails-core doctor` (run inside the affected project)

package/{templates/settings/integration-contract.json → integration-contract.json}

@@ -80,7 +80,7 @@
     }
   },
   "legacyCompat": {
-    "setupCommandAlias": true,
-    "note": "During transition, /specrails:setup may still be installed as an alias in some repos. Hub should prefer /specrails:enrich."
+    "setupCommandAlias": false,
+    "note": "The Node-native installer ships /specrails:enrich only. Existing repos should prune any leftover /specrails:setup alias during re-install or update."
   }
 }

package/package.json

@@ -1,23 +1,25 @@
 {
   "name": "specrails-core",
-  "version": "4.1.1",
+  "version": "4.2.0",
   "description": "AI agent workflow system for Claude Code — installs 12 specialized agents, orchestration commands, and persona-driven product discovery into any repository",
+  "type": "module",
   "bin": {
-    "specrails-core": "bin/specrails-core.js"
+    "specrails-core": "bin/specrails-core.mjs"
   },
   "files": [
     "bin/",
-    "install.sh",
-    "update.sh",
+    "dist/",
     "templates/",
     ".claude/skills/",
     "commands/",
     "docs/",
     "schemas/",
-    "VERSION"
+    "VERSION",
+    "integration-contract.json",
+    "pinned-versions.json"
   ],
   "engines": {
-    "node": ">=18.0.0"
+    "node": ">=20.0.0"
   },
   "repository": {
     "type": "git",
@@ -50,17 +52,30 @@
     "url": "https://github.com/fjpulidop/specrails-core/issues"
   },
   "scripts": {
-    "test": "bash tests/run-all.sh",
-    "test:coverage": "bash tests/run-coverage.sh"
+    "build": "tsc -p tsconfig.json",
+    "build:watch": "tsc -p tsconfig.json --watch",
+    "typecheck": "tsc -p tsconfig.test.json --noEmit",
+    "test": "npm run typecheck && npm run build && vitest run",
+    "test:watch": "vitest",
+    "test:coverage": "vitest run --coverage",
+    "prepare": "npm run build",
+    "prepack": "npm run build"
   },
   "specrails": {
     "openspecVersion": "1.2.0"
   },
   "dependencies": {
-    "@inquirer/prompts": "^7.0.0"
+    "@inquirer/prompts": "^7.0.0",
+    "js-yaml": "^4.1.0",
+    "picocolors": "^1.1.1"
   },
   "devDependencies": {
-    "ajv": "^8.18.0"
+    "@types/js-yaml": "^4.0.9",
+    "@types/node": "^22.10.2",
+    "@vitest/coverage-v8": "^2.1.8",
+    "ajv": "^8.18.0",
+    "typescript": "^5.7.2",
+    "vitest": "^2.1.8"
   },
   "license": "MIT",
   "author": "fjpulidop"

package/pinned-versions.json

@@ -0,0 +1,4 @@
+{
+  "$comment": "Pinned versions of third-party tools the installer fetches via npx. Edit and commit to bump deliberately.",
+  "openspec": "1.3.1"
+}

package/schemas/profile.v1.json

@@ -38,7 +38,7 @@
       "type": "array",
       "minItems": 1,
       "items": { "$ref": "#/$defs/agentEntry" },
-      "description": "Ordered chain of agents that participate in the pipeline when this profile is active.",
+      "description": "Ordered chain of agents that participate in the pipeline when this profile is active. Every profile (default + custom) must include the baseline quartet (sr-architect, sr-developer, sr-reviewer, sr-merge-resolver) — the pipeline depends on all four. Custom profiles add optional agents on top of the baseline.",
       "allOf": [
         {
           "description": "Required baseline agent: sr-architect",
@@ -63,13 +63,21 @@
             "properties": { "id": { "const": "sr-reviewer" } },
             "required": ["id"]
           }
+        },
+        {
+          "description": "Required baseline agent: sr-merge-resolver",
+          "contains": {
+            "type": "object",
+            "properties": { "id": { "const": "sr-merge-resolver" } },
+            "required": ["id"]
+          }
         }
       ]
     },
     "routing": {
       "type": "array",
-      "minItems": 1,
-      "description": "Ordered routing rules. The first rule whose `tags` intersects the task's tag set wins. Exactly one terminal entry with `default: true` MUST appear as the last element.",
+      "minItems": 0,
+      "description": "Ordered routing rules. The first rule whose `tags` intersects the task's tag set wins. If a `default: true` entry is present it MUST be the last element. Custom profiles may omit routing entirely — tasks then fall through to the first developer-shaped agent in the chain.",
       "items": { "$ref": "#/$defs/routingRule" }
     }
   },

package/templates/agents/sr-architect.md

@@ -86,7 +86,7 @@ After producing the task breakdown and before finalizing output:
 1. **Extract the proposed surface changes** from your implementation design: which commands, agents, placeholders, flags, or config keys are being added, removed, renamed, or modified?
 
 2. **Compare against the current surface** by reading:
-   - `install.sh` for CLI flags
+   - `bin/specrails-core.mjs` for CLI flags
    - `templates/commands/*.md` for command names and argument flags
    - `templates/agents/*.md` for agent names
    - `templates/**/*.md` for `{{PLACEHOLDER}}` keys

package/templates/agents/sr-reviewer.md

@@ -59,7 +59,7 @@ These are the most common reasons code passes locally but fails in CI:
 
 The orchestrator runs specialized layer reviewers in parallel before you launch. Their reports are injected here. A value of `"SKIPPED"` means no files of that layer type were in the changeset.
 
-**These are NOT `/specrails:setup` placeholders. They use `[injected]` notation, not `{{...}}` notation.** The `[injected]` markers below are replaced by the actual report text when the orchestrator launches you.
+**These are NOT `/specrails:enrich` placeholders. They use `[injected]` notation, not `{{...}}` notation.** The `[injected]` markers below are replaced by the actual report text when the orchestrator launches you.
 
 FRONTEND_REVIEW_REPORT:
 [injected]

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

@@ -40,7 +40,7 @@ Parse `$ARGUMENTS` to set runtime variables.
 **Verify prerequisites:**
 
 - Check whether `templates/` directory exists. If not: print `Error: templates/ not found — is this a specrails repo?` and stop.
-- Check whether `install.sh` exists. If not: set `INSTALLER_AVAILABLE=false` (installer flags category will be skipped). Otherwise set `INSTALLER_AVAILABLE=true`.
+- 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:**
 
@@ -56,9 +56,9 @@ Read the codebase and build the surface snapshot. Print one progress line as eac
 
 **Surface category: installer_flags**
 
-If `INSTALLER_AVAILABLE=false`: print `  installer_flags: skipped (install.sh not found)` and record as unavailable.
+If `INSTALLER_AVAILABLE=false`: print `  installer_flags: skipped (bin/specrails-core.mjs not found)` and record as unavailable.
 
-Otherwise: read `install.sh`. Find all `case` blocks that parse CLI arguments. Extract every `--<word>)` flag pattern. For each flag, record the flag string and line number.
+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`
 

package/templates/commands/specrails/doctor.md

@@ -10,23 +10,23 @@ Run the specrails health check to validate that all prerequisites are correctly
 |-------|---------------|
 | 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 | `agents/` directory exists with at least 1 `AGENTS.md` file |
+| 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 delegates to the standalone health check script installed at `.specrails/bin/doctor.sh`. Run it directly:
+This command uses the Node-native doctor runtime. Run it directly with:
 
 ```
-Bash tool: bash .specrails/bin/doctor.sh
+npx specrails-core@latest doctor
 ```
 
-Or via the npm CLI wrapper:
+If `specrails-core` is already on your `PATH`, this works too:
 
 ```
-npx specrails-core@latest doctor
+specrails-core doctor
 ```
 
 ## Output

package/templates/commands/specrails/enrich.md

@@ -2,7 +2,7 @@
 
 Interactive wizard to configure the full agent workflow system for this repository. Analyzes the codebase, discovers target users, generates VPC personas, and creates all agents, commands, rules, and configuration adapted to this project. Supports config-driven mode for direct installation from a pre-built config file.
 
-**Prerequisites:** Run `specrails/install.sh` first to install templates.
+**Prerequisites:** Ensure this repo was initialized with `npx specrails-core@latest init` (or via specrails-hub) so `.specrails/setup-templates/` exists.
 
 ### Hub Checkpoint Protocol
 
@@ -69,7 +69,7 @@ To resolve the model for any given agent:
 
 ### FC2: Provider Setup
 
-Read `.specrails/setup-templates/.provider-detection.json` if present, to get `cli_provider` and `specrails_dir`. If `FC_provider` differs from the detected value, use `FC_provider` (config takes precedence).
+Use `FC_provider` from the config as the source of truth. Set `CLI_PROVIDER = FC_provider`, and set `SPECRAILS_DIR` to `.codex` when `CLI_PROVIDER == "codex"`, otherwise `.claude`.
 
 Set `SPECRAILS_DIR` and `CLI_PROVIDER` from resolved provider.
 
@@ -139,12 +139,12 @@ Read the following files to understand the current installation state:
    }
    ```
    If this file does not exist, inform the user:
-   > "No `.specrails/specrails-manifest.json` found. This looks like a pre-versioning installation. Run `update.sh` first to initialize the manifest, then re-run `/specrails:enrich --update`."
+   > "No `.specrails/specrails-manifest.json` found. This repo predates the Node-native installer. Re-run `npx specrails-core@latest init` to refresh the install, then re-run `/specrails:enrich --update`."
    Then stop.
 
 2. Read `.specrails/specrails-version` — contains the current version string (e.g., `0.2.0`). If it does not exist, treat version as `0.1.0 (legacy)`.
 
-3. Determine `$SPECRAILS_DIR` by reading `.specrails/setup-templates/.provider-detection.json`. Extract `cli_provider` and `specrails_dir`. If not found, default to `cli_provider = "claude"`, `specrails_dir = ".claude"`.
+3. Determine `$SPECRAILS_DIR` from the existing install layout. If `.codex/` exists, use `cli_provider = "codex"` and `specrails_dir = ".codex"`. Otherwise use `cli_provider = "claude"` and `specrails_dir = ".claude"`.
 
 4. List all template files in `.specrails/setup-templates/agents/` — these are the NEW agent templates from the update:
    ```bash
@@ -1029,7 +1029,7 @@ How should we interact with JIRA?
 
 Set `BACKLOG_WRITE=true/false`.
 
-<!-- no separate template — this file IS the source (install.sh copies commands/setup.md directly) -->
+<!-- This command is mirrored from commands/enrich.md for staged installs. -->
 
 #### Project Label
 
@@ -1155,7 +1155,7 @@ Wait for final confirmation.
 
 Read each template from `.specrails/setup-templates/` and generate the final files adapted to this project. Use the codebase analysis from Phase 1, personas from Phase 2, and configuration from Phase 3.
 
-**Provider detection (required before any file generation):** Read `.specrails/setup-templates/.provider-detection.json` to determine `cli_provider` (`"claude"` or `"codex"`) and `specrails_dir` (`.claude` or `.codex`). All output paths in Phase 4 use `$SPECRAILS_DIR` as the base directory. If the file is missing, fall back to `cli_provider = "claude"` and `specrails_dir = ".claude"`.
+**Provider detection (required before any file generation):** Determine `cli_provider` from the existing install layout: use `"codex"` when `.codex/` exists, otherwise `"claude"`. Set `specrails_dir` to `.codex` or `.claude` accordingly. All output paths in Phase 4 use `$SPECRAILS_DIR` as the base directory.
 
 ### 4.1 Generate agents
 
@@ -1388,7 +1388,7 @@ Each rule file must:
 
 ### 4.6 Generate settings
 
-Read `.specrails/setup-templates/.provider-detection.json` (written by `install.sh`) to determine `cli_provider` (`"claude"` or `"codex"`).
+Resolve `cli_provider` from the existing install layout (`.codex/` => `codex`, otherwise `claude`).
 
 **If `cli_provider == "claude"` (default):**
 
@@ -1448,7 +1448,7 @@ rm -rf .specrails/setup-templates/
 rm -f .claude/commands/enrich.md
 
 # 3. Remove the specrails/ directory from the repo if it exists at the root
-#    (it was only needed for install.sh and templates — everything is now in .claude/)
+#    (it was only needed for the retired shell installer and staging templates — everything is now in .claude/)
 #    NOTE: Only remove if it's inside this repo. Ask the user if unsure.
 ```
 
@@ -1485,7 +1485,7 @@ Apply the user's choice.
 After cleanup, verify that only the intended files remain:
 
 ```bash
-# These should exist (the actual system) — use $SPECRAILS_DIR from .provider-detection.json:
+# These should exist (the actual system) — use the resolved $SPECRAILS_DIR:
 # If cli_provider == "claude":
 ls .claude/agents/sr-*.md
 ls .claude/agents/personas/*.md

package/templates/commands/specrails/reconfig.md

@@ -8,8 +8,8 @@ Reads `.specrails/agents.yaml` and updates the `model:` frontmatter field in all
 
 Determine `$SPECRAILS_DIR`:
 
-1. Read `.specrails/setup-templates/.provider-detection.json` to get `cli_provider` and `specrails_dir`.
-2. If the file does not exist, default to `cli_provider = "claude"` and `specrails_dir = ".claude"`.
+1. If `.codex/agents/` exists, set `cli_provider = "codex"` and `specrails_dir = ".codex"`.
+2. Otherwise set `cli_provider = "claude"` and `specrails_dir = ".claude"`.
 3. Set `$AGENTS_DIR = $SPECRAILS_DIR/agents`
 
 ## Step 2: Read agent config

package/templates/commands/specrails/refactor-recommender.md

@@ -40,7 +40,7 @@ Always exclude the following from all analysis:
 
 ## Phase 1.5: VPC Context
 
-Check whether persona files exist at `.claude/agents/personas/`. This path is present in any repo that has run `/specrails:setup`.
+Check whether persona files exist at `.claude/agents/personas/`. This path is present in any repo that has run `/specrails:enrich`.
 
 ```bash
 ls .claude/agents/personas/ 2>/dev/null
@@ -208,5 +208,5 @@ Issues created: {N}  (or "dry-run: no issues created")
 ```
 
 Where:
-- `{vpc_header}` is `VPC personas loaded: {persona names}` when `VPC_AVAILABLE=true`, or `VPC personas: not found (run /specrails:setup to enable)` otherwise.
+- `{vpc_header}` is `VPC personas loaded: {persona names}` when `VPC_AVAILABLE=true`, or `VPC personas: not found (run /specrails:enrich to enable)` otherwise.
 - `{vpc_detail}` is `**VPC Value**: {vpc_value}/5 — {vpc_persona}: {vpc_rationale}` when `VPC_AVAILABLE=true`, omitted otherwise.

package/templates/commands/specrails/vpc-drift.md

@@ -57,7 +57,7 @@ If no persona files are found in either location:
 Error: No VPC persona files found.
 Expected location: .claude/agents/*.md or {{PERSONA_DIR}}/*.md
 Each persona file must contain a ## Value Proposition Canvas section.
-Run /specrails:setup to generate persona files from templates.
+Run /specrails:enrich to generate persona files from templates.
 ```
 
 Stop.

package/templates/skills/sr-compat-check/SKILL.md

@@ -44,7 +44,7 @@ Parse `$ARGUMENTS` to set runtime variables.
 **Verify prerequisites:**
 
 - Check whether `templates/` directory exists. If not: print `Error: templates/ not found — is this a specrails repo?` and stop.
-- Check whether `install.sh` exists. If not: set `INSTALLER_AVAILABLE=false` (installer flags category will be skipped). Otherwise set `INSTALLER_AVAILABLE=true`.
+- 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:**
 
@@ -60,9 +60,9 @@ Read the codebase and build the surface snapshot. Print one progress line as eac
 
 **Surface category: installer_flags**
 
-If `INSTALLER_AVAILABLE=false`: print `  installer_flags: skipped (install.sh not found)` and record as unavailable.
+If `INSTALLER_AVAILABLE=false`: print `  installer_flags: skipped (bin/specrails-core.mjs not found)` and record as unavailable.
 
-Otherwise: read `install.sh`. Find all `case` blocks that parse CLI arguments. Extract every `--<word>)` flag pattern. For each flag, record the flag string and line number.
+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`
 

package/templates/skills/sr-refactor-recommender/SKILL.md

@@ -44,7 +44,7 @@ Always exclude the following from all analysis:
 
 ## Phase 1.5: VPC Context
 
-Check whether persona files exist at `.claude/agents/personas/`. This path is present in any repo that has run `/specrails:setup`.
+Check whether persona files exist at `.claude/agents/personas/`. This path is present in any repo that has run `/specrails:enrich`.
 
 ```bash
 ls .claude/agents/personas/ 2>/dev/null
@@ -212,5 +212,5 @@ Issues created: {N}  (or "dry-run: no issues created")
 ```
 
 Where:
-- `{vpc_header}` is `VPC personas loaded: {persona names}` when `VPC_AVAILABLE=true`, or `VPC personas: not found (run /specrails:setup to enable)` otherwise.
+- `{vpc_header}` is `VPC personas loaded: {persona names}` when `VPC_AVAILABLE=true`, or `VPC personas: not found (run /specrails:enrich to enable)` otherwise.
 - `{vpc_detail}` is `**VPC Value**: {vpc_value}/5 — {vpc_persona}: {vpc_rationale}` when `VPC_AVAILABLE=true`, omitted otherwise.