specrails 0.2.0 → 0.2.1

package/VERSION

@@ -1 +1 @@
-0.2.0
+0.2.1

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "specrails",
-  "version": "0.2.0",
+  "version": "0.2.1",
   "description": "Agent Workflow System installer for Claude Code",
   "bin": {
     "specrails": "bin/specrails.js"

package/templates/commands/sr/implement.md

@@ -65,6 +65,28 @@ Print a setup report:
 
 **Pass `TEST_CMD` (or equivalent) and `BACKLOG_AVAILABLE` forward** — all later phases must use these.
 
+#### 5. Web Manager (Pipeline Monitor)
+
+Check if the web manager is running:
+
+```bash
+curl -sf http://127.0.0.1:4200/api/state >/dev/null 2>&1
+```
+
+- If reachable: set `WEB_MANAGER=true`. Print: `| Pipeline Monitor | ok | http://127.0.0.1:4200 |`
+- If not reachable: set `WEB_MANAGER=false`. Print: `| Pipeline Monitor | off | start with: cd .claude/web-manager && npm run dev |`
+
+**Web Manager notification helper:** Throughout this pipeline, use the following pattern to notify the web manager of phase transitions. Always fire-and-forget — never let a notification failure block the pipeline.
+
+```bash
+# Only execute if WEB_MANAGER=true
+curl -sf -X POST http://127.0.0.1:4200/hooks/events \
+  -H 'Content-Type: application/json' \
+  -d '{"event":"<EVENT>","agent":"<PHASE>"}' >/dev/null 2>&1 || true
+```
+
+Where `<EVENT>` is one of `agent_start`, `agent_stop`, `agent_error` and `<PHASE>` is one of `architect`, `developer`, `reviewer`, `ship`.
+
 ---
 
 ## Phase 0: Parse input and determine mode
@@ -265,6 +287,8 @@ For `body_sha` rows in the table, display only the first 8 characters of each SH
 
 ## Phase 3a: Architect (parallel, in main repo)
 
+**Web Manager:** If `WEB_MANAGER=true`, notify: `{"event":"agent_start","agent":"architect"}`
+
 For each chosen idea, launch an **sr-architect** agent (`subagent_type: sr-architect`, `run_in_background: true`).
 
 Each architect creates OpenSpec artifacts in `openspec/changes/<name>/`.
@@ -331,8 +355,12 @@ Quick-check each architect's artifacts:
 3. File references are real (>70% must exist)
 4. Layer tags present on tasks
 
+**Web Manager:** If `WEB_MANAGER=true`, notify: `{"event":"agent_stop","agent":"architect"}`
+
 ## Phase 3b: Implement
 
+**Web Manager:** If `WEB_MANAGER=true`, notify: `{"event":"agent_start","agent":"developer"}`
+
 ### Pre-flight: Verify Bash permission
 
 Before launching any developer agent, run a trivial Bash command to confirm Bash is allowed.
@@ -371,6 +399,8 @@ For each feature, analyze the tasks' layer tags:
 
 Wait for all developers to complete.
 
+**Web Manager:** If `WEB_MANAGER=true`, notify: `{"event":"agent_stop","agent":"developer"}`
+
 ## Phase 3c: Write Tests
 
 Launch a **sr-test-writer** agent for each feature immediately after its developer completes.
@@ -540,6 +570,8 @@ Pass `MERGE_REPORT` to the Phase 4b reviewer agent prompt, listing any files in
 
 ### 4b. Layer Dispatch and Review
 
+**Web Manager:** If `WEB_MANAGER=true`, notify: `{"event":"agent_start","agent":"reviewer"}`
+
 #### Step 1: Layer Classification
 
 Before launching any reviewer, classify `MODIFIED_FILES_LIST` into layer-specific file sets.
@@ -610,6 +642,8 @@ Note: if total layer report length is very large, truncate each layer report to
 
 Launch the **sr-reviewer** agent (foreground, `run_in_background: false`). Wait for it to complete.
 
+**Web Manager:** If `WEB_MANAGER=true`, notify: `{"event":"agent_stop","agent":"reviewer"}`
+
 **If `DRY_RUN=true`**, add the following to the reviewer agent prompt:
 
 > Note: This is a dry-run review. Developer files are under .claude/.dry-run/\<feature-name\>/.
@@ -745,6 +779,8 @@ If conflicts exist: print the same conflict report format as Phase 3a.0 (with `P
 
 ### 4c. Ship — Git & backlog updates
 
+**Web Manager:** If `WEB_MANAGER=true`, notify: `{"event":"agent_start","agent":"ship"}`
+
 **Security gate:** If `SECURITY_BLOCKED=true`:
 1. Print all Critical findings from the security-reviewer output
 2. Do NOT create a branch, commit, push, or PR
@@ -961,12 +997,15 @@ Include the shipping mode in the report:
 - If automatic: show PR URL, CI status, backlog updates made
 - If manual: show summary of changes, suggested git commands, backlog updates pending
 
+**Web Manager:** If `WEB_MANAGER=true`, notify: `{"event":"agent_stop","agent":"ship"}`
+
 ---
 
 ## Error Handling
 
 - If a sr-product-manager fails: skip that area, continue with others
-- If a sr-architect fails: skip that area, report the failure
-- If a sr-developer fails: report which phase it failed at
-- If the sr-reviewer finds unfixable issues: report them, push what works
+- If a sr-architect fails: skip that area, report the failure. **Web Manager:** notify `{"event":"agent_error","agent":"architect"}`
+- If a sr-developer fails: report which phase it failed at. **Web Manager:** notify `{"event":"agent_error","agent":"developer"}`
+- If the sr-reviewer finds unfixable issues: report them, push what works. **Web Manager:** notify `{"event":"agent_error","agent":"reviewer"}`
+- If Phase 4c (ship) fails: **Web Manager:** notify `{"event":"agent_error","agent":"ship"}`
 - Never block the entire pipeline on a single agent failure. Always produce a final report.

package/templates/settings/settings.json

@@ -9,6 +9,7 @@
       "Agent",
       "Skill",
       "ToolSearch",
+      "Bash(curl -sf *127.0.0.1:4200*)",
       "{{PERMISSION_ENTRIES}}"
     ]
   }

package/templates/web-manager/README.md

@@ -12,7 +12,7 @@ The specrails web manager is a locally-run dashboard that monitors and controls
 ## Setup
 
 ```bash
-cd web
+cd .claude/web-manager
 npm install
 ```
 
@@ -20,8 +20,16 @@ This installs both the server dependencies (Express, WebSocket) and the client d
 
 ## Start
 
+**Always start from your project root**, not from inside the web-manager directory. This ensures the project name is detected correctly:
+
+```bash
+cd .claude/web-manager && npm run dev
+```
+
+Or specify the project name explicitly:
+
 ```bash
-npm run dev
+cd .claude/web-manager && SPECRAILS_PROJECT_NAME=my-project npm run dev
 ```
 
 This starts two processes concurrently:
@@ -36,7 +44,7 @@ The server accepts these CLI flags (used with `npm run dev:server` or `tsx serve
 
 | Flag | Default | Description |
 |------|---------|-------------|
-| `--project <name>` | `specrails` | Project name displayed in the dashboard header |
+| `--project <name>` | basename of `cwd` | Project name displayed in the dashboard header |
 | `--port <n>` | `4200` | Port the backend server listens on |
 
 Example:
@@ -45,36 +53,40 @@ Example:
 tsx server/index.ts --project my-app --port 4000
 ```
 
-## Hook Integration
+You can also set the project name via environment variable: `SPECRAILS_PROJECT_NAME=my-app npm run dev`
 
-The web manager accepts Claude Code hook events at `POST /hooks/events`. Configure hooks in the target project's `.claude/settings.json` to POST phase transitions as the pipeline runs.
+## How It Connects to the Pipeline
 
-Example `.claude/settings.json` entry for the target repo:
+The `/sr:implement` pipeline automatically detects whether the web manager is running and sends phase transition notifications. **No manual hook configuration is required.**
 
-```json
-{
-  "hooks": {
-    "PreToolUse": [],
-    "PostToolUse": []
-  }
-}
-```
+When you run `/sr:implement`, the orchestrator:
+1. Checks if `http://127.0.0.1:4200` is reachable (Phase -1 pre-flight)
+2. If yes, sends `POST /hooks/events` notifications at each phase transition:
+   - Architect starts/completes
+   - Developer starts/completes
+   - Reviewer starts/completes
+   - Ship starts/completes
+3. If not reachable, the pipeline runs normally without notifications
+
+All notifications are fire-and-forget — a failed notification never blocks the pipeline.
+
+## Manual Hook Testing
 
-To manually fire a hook event (useful for testing):
+To manually fire a hook event (useful for testing the dashboard):
 
 ```bash
 # Mark the architect phase as running
-curl -X POST http://localhost:4200/hooks/events \
+curl -sf -X POST http://127.0.0.1:4200/hooks/events \
   -H 'Content-Type: application/json' \
   -d '{"event":"agent_start","agent":"architect"}'
 
 # Mark the architect phase as done
-curl -X POST http://localhost:4200/hooks/events \
+curl -sf -X POST http://127.0.0.1:4200/hooks/events \
   -H 'Content-Type: application/json' \
   -d '{"event":"agent_stop","agent":"architect"}'
 
 # Mark the developer phase as errored
-curl -X POST http://localhost:4200/hooks/events \
+curl -sf -X POST http://127.0.0.1:4200/hooks/events \
   -H 'Content-Type: application/json' \
   -d '{"event":"agent_error","agent":"developer"}'
 ```

package/templates/web-manager/server/index.ts

@@ -1,4 +1,5 @@
 import http from 'http'
+import path from 'path'
 import express from 'express'
 import { WebSocketServer, WebSocket } from 'ws'
 import type { WsMessage } from './types'
@@ -6,8 +7,25 @@ import { ClaudeNotFoundError, SpawnBusyError } from './types'
 import { createHooksRouter, getPhaseStates, resetPhases } from './hooks'
 import { spawnClaude, isSpawnActive, getLogBuffer } from './spawner'
 
+// Resolve project name: env var > CLI flag > git root basename > cwd parent
+function resolveProjectName(): string {
+  if (process.env.SPECRAILS_PROJECT_NAME) {
+    return process.env.SPECRAILS_PROJECT_NAME
+  }
+  // The web-manager lives at <project>/.claude/web-manager/
+  // Walk up two levels to find the project root
+  const cwd = process.cwd()
+  const parentDir = path.basename(path.resolve(cwd, '../..'))
+  const immediateParent = path.basename(path.resolve(cwd, '..'))
+  // If we're inside .claude/web-manager, use the grandparent directory name
+  if (immediateParent === '.claude') {
+    return parentDir
+  }
+  return path.basename(cwd)
+}
+
 // Parse CLI args
-let projectName = process.env.SPECRAILS_PROJECT_NAME || require('path').basename(process.cwd())
+let projectName = resolveProjectName()
 let port = 4200
 
 for (let i = 2; i < process.argv.length; i++) {