specrails-core 3.3.0 → 3.3.1

package/README.md

@@ -17,18 +17,6 @@ npx specrails-core@latest init --root-dir .
 
 > **Requirements:** [Claude Code](https://docs.anthropic.com/en/docs/claude-code) or [Codex CLI](https://github.com/openai/codex) (choose one), Node 18+, git
 
-<!--
-  BOARD: Add demo GIF here — this is the #1 conversion driver on Product Hunt and npm.
-  Record a 60-90s screen capture showing:
-    1. `npx specrails-core@latest init --root-dir .` running
-    2. The `/setup` wizard completing (phases 1-5)
-    3. `/sr:implement "add dark mode"` → agents working → PR created
-  Recommended tools: Loom or QuickTime to record; Kap (https://getkap.co) to export as GIF.
-  Then replace this comment with:
-
-  ![specrails-core demo](./assets/demo.gif)
--->
-
 ---
 
 ## How it works
@@ -80,7 +68,7 @@ That's it. The pipeline takes over.
 |----------|-------|---------|
 | **Agents** | `.claude/agents/*.md` | 14 specialized AI agents |
 | **Personas** | `.claude/agents/personas/*.md` | VPC user profiles, generated from your users |
-| **Commands** | `.claude/commands/sr/*.md` | 17 workflow commands: `/sr:implement`, `/sr:product-backlog`, `/sr:health-check`, `/sr:why`, and more |
+| **Commands** | `.claude/commands/sr/*.md` | 17 workflow commands: `/sr:implement`, `/sr:product-backlog`, `/sr:why`, and more |
 | **Rules** | `.claude/rules/*.md` | Per-layer coding conventions, loaded by file path |
 | **Memory** | `.claude/agent-memory/` | Persistent knowledge — agents learn across sessions |
 | **Config** | `.claude/settings.json`, `CLAUDE.md` | Permissions, architecture reference |
@@ -182,7 +170,7 @@ AI product discovery using your personas. Evaluates ideas, creates tickets (loca
 
 specrails-core ships with a built-in ticket system — no GitHub account or external tools required.
 
-Tickets live in `.claude/local-tickets.json` alongside your code. They're plain JSON, git-friendly, and bidirectionally synced with specrails-hub in real time.
+Tickets live in `.claude/local-tickets.json` alongside your code. They're plain JSON and git-friendly.
 
 **Local tickets are the default.** The `/setup` wizard defaults to local tickets and skips GitHub/JIRA credential setup unless you opt in.
 
@@ -281,8 +269,6 @@ Yes. Everything runs locally through Claude Code. No external services beyond th
 
 ## Also in the SpecRails ecosystem
 
-- **[specrails-hub](https://github.com/fjpulidop/specrails-hub)** — GUI for specrails-core. Manage your agents, run commands, and view pipeline results from a web interface.
-- **[specrails.dev](https://specrails.dev)** — Official website and documentation.
 - **Product Hunt** — [Vote for SpecRails on launch day](https://www.producthunt.com) _(link goes live on launch day — star this repo to get notified)_
 
 ---

package/VERSION

@@ -1 +1 @@
-2.1.0
+3.3.0

package/bin/perf-check.sh

@@ -0,0 +1,21 @@
+#!/bin/bash
+# Performance regression check for specrails-core.
+# This is a template/installer repo — no runtime benchmarks apply.
+# Reports NO_PERF_IMPACT so the CI workflow exits cleanly.
+set -euo pipefail
+
+FILES="${MODIFIED_FILES_LIST:-}"
+CONTEXT="${2:-}"
+
+# Determine if any performance-sensitive files were modified.
+# For specrails-core (a shell installer + markdown template repo), there are
+# no runtime execution paths to benchmark. All changes are to installer scripts
+# or template files that have no measurable latency or throughput impact.
+
+echo "specrails-core performance check"
+echo "Modified files: ${FILES:-<none>}"
+echo ""
+echo "This repository contains shell installer scripts and Markdown templates."
+echo "No runtime benchmarks apply — skipping performance regression analysis."
+echo ""
+echo "PERF_STATUS: NO_PERF_IMPACT"

package/bin/specrails-core.js

@@ -8,6 +8,7 @@ const COMMANDS = {
   init: "install.sh",
   update: "update.sh",
   doctor: "bin/doctor.sh",
+  "perf-check": "bin/perf-check.sh",
 };
 
 const args = process.argv.slice(2);
@@ -17,9 +18,10 @@ if (!subcommand) {
   console.log(`specrails-core — Agent Workflow System for Claude Code
 
 Usage:
-  specrails-core init   [--root-dir <path>]     Install into a repository
-  specrails-core update [--only <component>]    Update an existing installation
-  specrails-core doctor                         Run health checks
+  specrails-core init       [--root-dir <path>]     Install into a repository
+  specrails-core update     [--only <component>]    Update an existing installation
+  specrails-core doctor                             Run health checks
+  specrails-core perf-check [--files <list>]        Performance regression check (CI)
 
 More info: https://github.com/fjpulidop/specrails-core`);
   process.exit(0);
@@ -29,7 +31,7 @@ const script = COMMANDS[subcommand];
 
 if (!script) {
   console.error(`Unknown command: ${subcommand}\n`);
-  console.error("Available commands: init, update, doctor");
+  console.error("Available commands: init, update, doctor, perf-check");
   process.exit(1);
 }
 
@@ -40,6 +42,7 @@ const ALLOWED_FLAGS = {
   init: ["--root-dir", "--yes", "-y"],
   update: ["--only"],
   doctor: [],
+  "perf-check": ["--files", "--context"],
 };
 
 const subargs = args.slice(1);

package/commands/setup.md

@@ -56,7 +56,7 @@ Read the following files to understand the current installation state:
    ```bash
    ls $SPECRAILS_DIR/setup-templates/commands/sr/
    ```
-   Command template files include `implement.md`, `batch-implement.md`, `health-check.md`, `compat-check.md`, `refactor-recommender.md`, `why.md`, `product-backlog.md`, `update-product-driven-backlog.md`.
+   Command template files include `implement.md`, `batch-implement.md`, `compat-check.md`, `refactor-recommender.md`, `why.md`, `product-backlog.md`, `update-product-driven-backlog.md`.
    If this directory does not exist, skip command template checking for this update.
 
 6. Read `$SPECRAILS_DIR/backlog-config.json` if it exists — contains stored provider configuration needed for command placeholder substitution.
@@ -130,7 +130,6 @@ Display the combined analysis to the user:
 - refactor-recommender.md
 
 ### Commands — Unchanged (keeping current)
-- health-check.md
 - compat-check.md
 - why.md
 ```
@@ -419,7 +418,6 @@ Core commands (always install if missing):
 - `implement.md`
 - `batch-implement.md`
 - `propose-spec.md`
-- `health-check.md`
 - `compat-check.md`
 - `why.md`
 - `product-backlog.md`
@@ -463,7 +461,7 @@ Remove `commands/setup.md` from `.claude/commands/` if it was copied there by th
 After generating all files, display the setup complete message.
 
 Then, based on `QS_IS_EXISTING_CODEBASE`:
-- **Existing codebase** (`true`): recommend `/sr:health-check`
+- **Existing codebase** (`true`): recommend `/sr:refactor-recommender`
 - **New project** (`false`): recommend `/sr:product-backlog`
 
 If `QS_IS_RERUN=false`, display:
@@ -473,7 +471,7 @@ If `QS_IS_RERUN=false`, display:
 Try your first command:
   > /sr:product-backlog
 ```
-(Replace `/sr:product-backlog` with `/sr:health-check` for existing codebases.)
+(Replace `/sr:product-backlog` with `/sr:refactor-recommender` for existing codebases.)
 
 If `QS_IS_RERUN=true`, display the gap-fill summary and stop:
 ```
@@ -950,7 +948,6 @@ If automatic, also check if `gh` is authenticated (for PR creation). If not, war
 | /sr:propose-spec | Interactively propose and refine a feature spec, then create a GitHub issue | GitHub CLI |
 | /sr:product-backlog | View prioritized backlog with VPC scores | sr-product-analyst + Backlog provider |
 | /sr:update-product-driven-backlog | Generate new feature ideas via product discovery | sr-product-manager + Backlog provider |
-| /sr:health-check | Run tests, linting, coverage, complexity, and dependency audit | None |
 | /sr:compat-check | Snapshot API surface and detect breaking changes | None |
 | /sr:refactor-recommender | Scan for refactoring opportunities ranked by impact/effort | None |
 | /sr:why | Search past architectural decisions from agent memory | None |
@@ -1086,7 +1083,6 @@ For each selected command, read the template and adapt.
 - `setup-templates/commands/sr/propose-spec.md` → `.claude/commands/sr/propose-spec.md`
 - `setup-templates/commands/sr/product-backlog.md` → `.claude/commands/sr/product-backlog.md` (if `BACKLOG_PROVIDER != none`)
 - `setup-templates/commands/sr/update-product-driven-backlog.md` → `.claude/commands/sr/update-product-driven-backlog.md` (if `BACKLOG_PROVIDER != none`)
-- `setup-templates/commands/sr/health-check.md` → `.claude/commands/sr/health-check.md`
 - `setup-templates/commands/sr/compat-check.md` → `.claude/commands/sr/compat-check.md`
 - `setup-templates/commands/sr/refactor-recommender.md` → `.claude/commands/sr/refactor-recommender.md`
 - `setup-templates/commands/sr/why.md` → `.claude/commands/sr/why.md`
@@ -1097,7 +1093,6 @@ For each selected command, read the template and adapt.
 - `setup-templates/commands/sr/propose-spec.md` → `.agents/skills/sr-propose-spec/SKILL.md` (wrap with YAML frontmatter if no skill template exists)
 - `setup-templates/commands/sr/product-backlog.md` → `.agents/skills/sr-product-backlog/SKILL.md` (if `BACKLOG_PROVIDER != none`; wrap with frontmatter)
 - `setup-templates/commands/sr/update-product-driven-backlog.md` → `.agents/skills/sr-update-product-driven-backlog/SKILL.md` (if `BACKLOG_PROVIDER != none`; wrap with frontmatter)
-- `setup-templates/skills/sr-health-check/SKILL.md` → `.agents/skills/sr-health-check/SKILL.md`
 - `setup-templates/skills/sr-compat-check/SKILL.md` → `.agents/skills/sr-compat-check/SKILL.md`
 - `setup-templates/skills/sr-refactor-recommender/SKILL.md` → `.agents/skills/sr-refactor-recommender/SKILL.md`
 - `setup-templates/skills/sr-why/SKILL.md` → `.agents/skills/sr-why/SKILL.md`
@@ -1381,7 +1376,6 @@ Display the complete installation summary:
 | /sr:propose-spec | .claude/commands/sr/propose-spec.md |
 | /sr:product-backlog | .claude/commands/sr/product-backlog.md |
 | /sr:update-product-driven-backlog | .claude/commands/sr/update-product-driven-backlog.md |
-| /sr:health-check | .claude/commands/sr/health-check.md |
 | /sr:compat-check | .claude/commands/sr/compat-check.md |
 | /sr:refactor-recommender | .claude/commands/sr/refactor-recommender.md |
 | /sr:why | .claude/commands/sr/why.md |
@@ -1393,7 +1387,6 @@ Display the complete installation summary:
 | $sr-propose-spec | .agents/skills/sr-propose-spec/SKILL.md |
 | $sr-product-backlog | .agents/skills/sr-product-backlog/SKILL.md |
 | $sr-update-product-driven-backlog | .agents/skills/sr-update-product-driven-backlog/SKILL.md |
-| $sr-health-check | .agents/skills/sr-health-check/SKILL.md |
 | $sr-compat-check | .agents/skills/sr-compat-check/SKILL.md |
 | $sr-refactor-recommender | .agents/skills/sr-refactor-recommender/SKILL.md |
 | $sr-why | .agents/skills/sr-why/SKILL.md |
@@ -1460,9 +1453,9 @@ Try your first spec:
 
 Try your first spec:
 [If cli_provider == "claude":]
-  > /sr:health-check
+  > /sr:refactor-recommender
 [If cli_provider == "codex":]
-  > $sr-health-check
+  > $sr-refactor-recommender
 ```
 
 Then stop.

package/docs/deployment.md

@@ -18,7 +18,7 @@ SpecRails runs locally — no cloud infrastructure required. Choose the setup th
 The fastest way to get started. No install required.
 
 ```bash
-npx specrails-core@latest setup
+npx specrails-core@latest init --root-dir .
 ```
 
 This will:
@@ -35,10 +35,10 @@ This will:
 Clone the repository for full control and the ability to customize agents.
 
 ```bash
-git clone https://github.com/specrails-ai/specrails-core
+git clone https://github.com/fjpulidop/specrails-core
 cd specrails-core
 npm install
-npm run setup
+./install.sh --root-dir <your-project>
 ```
 
 ### Updating
@@ -90,7 +90,7 @@ docker compose run specrails setup
 ### Building locally
 
 ```bash
-git clone https://github.com/specrails-ai/specrails-core
+git clone https://github.com/fjpulidop/specrails-core
 cd specrails-core
 docker build -t specrails:local .
 docker run -it \

package/docs/getting-started.md

@@ -10,16 +10,18 @@ Think of it as hiring a full engineering team that lives inside your CLI.
 
 ## Prerequisites
 
-You only need two things:
+You need:
 
+- **Node.js 18+** — required for the installer (`node --version` to check)
 - **Git** — your project must be a git repository
 - **[Claude Code](https://claude.ai/claude-code)** — Anthropic's CLI tool
 
 Optional (recommended):
 
-- **npm** — for installing the Pipeline Monitor dashboard
 - **[GitHub CLI](https://cli.github.com/)** (`gh`) — for automatic PR creation and issue tracking
 
+> **Using OpenAI Codex instead of Claude Code?** See [Installation](user-docs/installation.md) for Codex-specific setup.
+
 ## Install
 
 Pick your preferred method:
@@ -33,8 +35,8 @@ npx specrails-core@latest init --root-dir <your-project>
 **git clone**
 
 ```bash
-git clone https://github.com/fjpulidop/specrails.git
-./specrails/install.sh --root-dir <your-project>
+git clone https://github.com/fjpulidop/specrails-core.git
+./specrails-core/install.sh --root-dir <your-project>
 ```
 
 The installer will:
@@ -114,4 +116,6 @@ Now that you're running, learn how the system thinks:
 
 ---
 
+**Looking for step-by-step guides?** See [Quick Start](user-docs/quick-start.md) for a walkthrough of your first feature, or [Installation](user-docs/installation.md) for detailed install options including Codex support.
+
 [← Back to Docs](README.md) · [Core Concepts →](concepts.md)

package/docs/installation.md

@@ -8,6 +8,7 @@ This guide covers the complete installation process in detail. For the quick ver
 
 | Tool | Why | Install |
 |------|-----|---------|
+| **Node.js 18+** | Required for the installer | [nodejs.org](https://nodejs.org/) or via [nvm](https://github.com/nvm-sh/nvm) |
 | **Git** | SpecRails operates on git repositories | [git-scm.com](https://git-scm.com/) |
 | **Claude Code** | The AI CLI that runs the agents | `npm install -g @anthropic-ai/claude-code` |
 
@@ -15,9 +16,7 @@ This guide covers the complete installation process in detail. For the quick ver
 
 | Tool | Why | Install |
 |------|-----|---------|
-| **npm** | Pipeline Monitor dashboard, OpenSpec CLI | Via [nvm](https://github.com/nvm-sh/nvm) |
 | **GitHub CLI** | Auto-create PRs, manage issues | `brew install gh` or [cli.github.com](https://cli.github.com/) |
-| **OpenSpec CLI** | Structured spec workflow | `npm install -g @openspec/cli` |
 
 ### Optional
 
@@ -42,8 +41,8 @@ No cloning required. Downloads the latest version and runs the installer automat
 If you prefer to clone the repo first:
 
 ```bash
-git clone https://github.com/fjpulidop/specrails.git
-./specrails/install.sh --root-dir <your-project>
+git clone https://github.com/fjpulidop/specrails-core.git
+./specrails-core/install.sh --root-dir <your-project>
 ```
 
 ### From curl
@@ -51,7 +50,7 @@ git clone https://github.com/fjpulidop/specrails.git
 Alternatively, pipe the installer directly:
 
 ```bash
-curl -sL https://raw.githubusercontent.com/fjpulidop/specrails/main/install.sh | bash
+curl -sL https://raw.githubusercontent.com/fjpulidop/specrails-core/main/install.sh | bash
 ```
 
 > **Important:** Always run the installer from the **target repository** — the project where you want SpecRails installed. If you run it from inside the SpecRails source repo, the installer will detect this and prompt you for the correct target path.
@@ -62,8 +61,7 @@ curl -sL https://raw.githubusercontent.com/fjpulidop/specrails/main/install.sh |
 2. **Detects existing setup** — warns if `.claude/agents/`, `.claude/commands/`, or `openspec/` already exist
 3. **Installs artifacts:**
    - `.claude/commands/setup.md` — the `/setup` wizard
-   - `.claude/setup-templates/` — all template files
-   - `.claude/web-manager/` — Pipeline Monitor dashboard
+   - `.claude/setup-templates/` — agent and command templates (temporary, removed after `/setup`)
    - `.claude/security-exemptions.yaml` — security scanner config
    - OpenSpec initialization (if CLI available)
 4. **Tracks version** — writes `.specrails-version` and `.specrails-manifest.json`
@@ -75,7 +73,6 @@ The installer only copies files. It does not:
 - Modify your existing code
 - Create commits
 - Push to any remote
-- Install npm dependencies (you do this manually for the web manager)
 
 ---
 
@@ -203,7 +200,7 @@ The quick path — three questions, sensible defaults, done in under a minute.
 | Item | Detail |
 |------|--------|
 | Core agents | sr-architect, sr-developer, sr-reviewer, sr-product-manager |
-| All workflow commands | `/sr:implement`, `/sr:health-check`, `/sr:product-backlog`, and 14 more |
+| All workflow commands | `/sr:implement`, `/sr:product-backlog`, and 14 more |
 | Backlog storage | Local tickets (`.claude/local-tickets.json`) — no GitHub or JIRA required |
 | CLAUDE.md | Project-level context for agents |
 
@@ -211,27 +208,6 @@ You can run the full wizard later to deepen configuration: personas, stack analy
 
 ---
 
-## Pipeline Monitor (optional)
-
-SpecRails includes a web dashboard for visualizing pipeline execution.
-
-### Install
-
-```bash
-cd .claude/web-manager && npm install
-cd client && npm install
-```
-
-### Run
-
-```bash
-cd .claude/web-manager && npm run dev
-```
-
-Opens at `http://localhost:4201` by default.
-
----
-
 ## Verify installation
 
 After setup, verify everything is in place:

package/docs/local-tickets.md

@@ -12,7 +12,7 @@ Tickets live in `.claude/local-tickets.json` at your project root. Because it's
 - **Offline-first** — no network calls, no rate limits
 - **Tool-agnostic** — readable by any script or editor
 
-The file is shared between specrails-core (which reads and writes tickets during command execution) and specrails-hub (which provides a visual ticket panel with real-time sync).
+The file is read and written by specrails-core during command execution.
 
 ---
 
@@ -120,7 +120,7 @@ npx specrails-core@latest init --root-dir .
 
 ## Concurrency model
 
-Both CLI agents and specrails-hub can modify `local-tickets.json` simultaneously. The system uses two complementary mechanisms:
+Multiple agents can modify `local-tickets.json` simultaneously. The system uses two complementary mechanisms:
 
 ### Advisory file lock
 
@@ -141,7 +141,7 @@ The lock is deleted immediately after the write completes. The window is minimal
 
 ### Revision counter
 
-Every write increments `revision`. Readers that want to detect external changes compare the `revision` they last saw against the current value. This is how specrails-hub avoids echoing its own writes back through the file watcher.
+Every write increments `revision`. Readers that want to detect external changes compare the `revision` they last saw against the current value.
 
 ---
 
@@ -187,32 +187,6 @@ The ticket captures the full proposal as its description and is tagged `source:
 
 ---
 
-## integration-contract.json
-
-The `ticketProvider` section tells specrails-hub where to find and how to use the ticket store:
-
-```json
-{
-  "ticketProvider": {
-    "type": "local",
-    "storageFile": "local-tickets.json",
-    "lockFile": "local-tickets.json.lock",
-    "capabilities": ["crud", "labels", "status", "priorities", "dependencies", "comments"]
-  }
-}
-```
-
-| Field | Description |
-|-------|-------------|
-| `type` | `"local"` — file-based storage (the only supported type currently) |
-| `storageFile` | Filename relative to the project's specrails dir (`.claude/` or `.codex/`) |
-| `lockFile` | Advisory lock filename, same directory |
-| `capabilities` | Features the hub enables based on what the provider supports |
-
-specrails-hub reads this file when it loads a project. If the file is missing or the `ticketProvider` key is absent, hub falls back to safe defaults (`type: "local"`, `storageFile: "local-tickets.json"`).
-
----
-
 ## Migrating from GitHub Issues or JIRA
 
 See the [Migration Guide](./migration-guide.md).

package/docs/migration-guide.md

@@ -11,7 +11,6 @@ Switching is optional. GitHub Issues and JIRA remain fully supported. Local tick
 **Switch to local tickets if:**
 - Your team prefers a simple, zero-dependency setup
 - You want tickets version-controlled alongside your code
-- You use specrails-hub and want the visual ticket panel
 - You don't need GitHub/JIRA for other workflows (project boards, external stakeholders)
 
 **Stay on GitHub Issues / JIRA if:**

package/docs/testing/test-matrix-codex.md

@@ -40,7 +40,6 @@ Epic: [SPEA-505](/SPEA/issues/SPEA-505) — Codex Compatibility Approach B
 | SKILL.md format `.claude/skills/sr-*/` | ✅ | ✅ |
 | `sr:implement` skill | ✅ | ✅ |
 | `sr:product-backlog` skill | ✅ | ✅ |
-| `sr:health-check` skill | ✅ | ✅ |
 | `sr:compat-check` skill | ✅ | ✅ |
 | `sr:why` skill | ✅ | ✅ |
 | `sr:refactor-recommender` skill | ✅ | ✅ |

package/docs/user-docs/cli-reference.md

@@ -174,18 +174,6 @@ The Product Manager researches your competitive landscape, generates 2–4 featu
 
 ## Analysis and inspection
 
-### `/sr:health-check` ✅ Both
-
-Run a comprehensive codebase quality analysis.
-
-```
-/sr:health-check
-```
-
-Analyzes code quality, test coverage, technical debt, complexity, and dependency health. Compares with previous runs to detect regressions.
-
----
-
 ### `/sr:refactor-recommender` ✅ Both
 
 Scan the codebase for refactoring opportunities, ranked by impact/effort ratio.

package/docs/user-docs/codex-vs-claude-code.md

@@ -31,7 +31,6 @@ SpecRails Skills use `SKILL.md` format, which is shared between Codex and Claude
 
 - `/sr:implement` — full pipeline (design → code → review → PR)
 - `/sr:product-backlog` — VPC-ranked backlog view
-- `/sr:health-check` — codebase quality analysis
 - `/opsx:ff` — OpenSpec fast-forward
 - All other workflow skills
 

package/docs/user-docs/installation.md

@@ -4,6 +4,8 @@ Install SpecRails into any git repository in two steps: run the installer, then
 
 SpecRails supports both **Claude Code** and **OpenAI Codex**. The installer detects which CLI you have and configures accordingly. See [Codex vs Claude Code](codex-vs-claude-code.md) for a feature comparison.
 
+> **Looking for the comprehensive reference?** See [Installation & Setup](../installation.md) for full wizard phase details and advanced configuration.
+
 ## Requirements
 
 | Tool | Version | Notes |
@@ -63,7 +65,6 @@ your-project/
     ├── skills/                   # Workflow skills (/sr:*, /opsx:*)
     ├── agents/                   # Agent definitions
     ├── rules/                    # Per-layer coding conventions
-    ├── web-manager/              # Pipeline Monitor dashboard (optional)
     └── settings.json             # Permissions
 ```
 
@@ -183,4 +184,4 @@ npx specrails-core@latest init --root-dir . --provider codex
 
 ---
 
-[Quick Start →](quick-start.md) · [Getting Started (Codex) →](getting-started-codex.md) · [CLI Reference →](cli-reference.md)
+[← Getting Started](../getting-started.md) · [Quick Start →](quick-start.md) · [Getting Started (Codex) →](getting-started-codex.md) · [CLI Reference →](cli-reference.md)

package/docs/user-docs/quick-start.md

@@ -159,4 +159,4 @@ Agents record their reasoning as they work. `/sr:why` searches those records in
 
 ---
 
-[← Installation](installation.md) · [CLI Reference →](cli-reference.md) · [FAQ →](faq.md)
+[← Getting Started](../getting-started.md) · [← Installation](installation.md) · [CLI Reference →](cli-reference.md) · [FAQ →](faq.md)

package/docs/workflows.md

@@ -170,18 +170,6 @@ Generate new feature ideas through product discovery. The Product Manager (Opus)
 
 ---
 
-## `/sr:health-check`
-
-Run a comprehensive codebase quality analysis.
-
-```
-/sr:health-check
-```
-
-Analyzes code quality, test coverage, technical debt, and dependency health. Compares with previous runs to detect regressions.
-
----
-
 ## `/sr:refactor-recommender`
 
 Scan for refactoring opportunities ranked by impact/effort ratio.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "specrails-core",
-  "version": "3.3.0",
+  "version": "3.3.1",
   "description": "AI agent workflow system for Claude Code — installs 12 specialized agents, orchestration commands, and persona-driven product discovery into any repository",
   "bin": {
     "specrails-core": "bin/specrails-core.js"

package/update.sh

@@ -419,7 +419,6 @@ do_migrate_sr_prefix() {
         "batch-implement"
         "product-backlog"
         "update-product-driven-backlog"
-        "health-check"
         "compat-check"
         "refactor-recommender"
         "why"