specrails-core 3.5.0 → 3.5.1

package/README.md

@@ -196,7 +196,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 and git-friendly.
+Tickets live in `.specrails/local-tickets.json` alongside your code. They're plain JSON and git-friendly.
 
 **Local tickets are the default.** The `/specrails:setup` wizard defaults to local tickets and skips GitHub/JIRA credential setup unless you opt in.
 

package/commands/setup.md

@@ -699,7 +699,7 @@ Ask the user how they want to manage their product backlog. Default is local —
 Use local ticket management or connect an external provider?
 
 1. **Local tickets** (default, recommended) — lightweight JSON-based ticket management built into the project.
-   No external tools or accounts required. Tickets stored in `.claude/local-tickets.json`, version-controlled and diffable.
+   No external tools or accounts required. Tickets stored in `.specrails/local-tickets.json`, version-controlled and diffable.
 2. **External provider** — connect GitHub Issues, JIRA, or disable backlog commands
 ```
 
@@ -713,7 +713,7 @@ If the user selects **2**: display the secondary menu:
 Which external provider?
 
 1. **Local tickets** (recommended) — lightweight JSON-based ticket management built into the project.
-   No external tools required. Tickets stored in `.claude/local-tickets.json`, version-controlled and diffable.
+   No external tools required. Tickets stored in `.specrails/local-tickets.json`, version-controlled and diffable.
 2. **GitHub Issues** — uses `gh` CLI to read/create issues with labels and VPC scores
 3. **JIRA** — uses JIRA CLI or REST API to read/create tickets in a JIRA project
 4. **None** — skip backlog commands (you can still use /implement with text descriptions)
@@ -895,7 +895,7 @@ Ask:
 
 Set `EPIC_LINK_FIELD` to `parent` or `customfield_10014`. Default: `parent`.
 
-Store the full configuration in `.claude/backlog-config.json`:
+Store the full configuration in `.specrails/backlog-config.json`:
 ```json
 {
   "provider": "jira",

package/docs/installation.md

@@ -231,7 +231,7 @@ The quick path — three questions, sensible defaults, done in under a minute.
 |------|--------|
 | Core agents | sr-architect, sr-developer, sr-reviewer, sr-product-manager |
 | All workflow commands | `/specrails:implement`, `/specrails:get-backlog-specs`, and 14 more |
-| Backlog storage | Local tickets (`.claude/local-tickets.json`) — no GitHub or JIRA required |
+| Backlog storage | Local tickets (`.specrails/local-tickets.json`) — no GitHub or JIRA required |
 | CLAUDE.md | Project-level context for agents |
 
 You can run the full wizard later to deepen configuration: personas, stack analysis, layer-specific conventions.

package/docs/local-tickets.md

@@ -6,7 +6,7 @@ specrails-core ships with a built-in, file-based ticket management system. It is
 
 ## Overview
 
-Tickets live in `.claude/local-tickets.json` at your project root. Because it's a plain JSON file, tickets are:
+Tickets live in `.specrails/local-tickets.json` at your project root. Because it's a plain JSON file, tickets are:
 
 - **Version-controlled** — tracked by git, diffable in PRs
 - **Offline-first** — no network calls, no rate limits
@@ -18,7 +18,7 @@ The file is read and written by specrails-core during command execution.
 
 ## Storage format
 
-`.claude/local-tickets.json`:
+`.specrails/local-tickets.json`:
 
 ```json
 {
@@ -99,7 +99,7 @@ Use local ticket management or connect an external provider?
 2. External provider — connect GitHub Issues, JIRA, or disable backlog commands
 ```
 
-Pressing **Enter** or selecting **1** initializes `.claude/local-tickets.json` with an empty ticket store and writes `.claude/backlog-config.json`:
+Pressing **Enter** or selecting **1** initializes `.specrails/local-tickets.json` with an empty ticket store and writes `.specrails/backlog-config.json`:
 
 ```json
 {
@@ -123,7 +123,7 @@ Multiple agents can modify `local-tickets.json` simultaneously. The system uses
 
 ### Advisory file lock
 
-Before every write, the agent creates `.claude/local-tickets.json.lock`:
+Before every write, the agent creates `.specrails/local-tickets.json.lock`:
 
 ```json
 {

package/docs/migration-guide.md

@@ -22,7 +22,7 @@ Switching is optional. GitHub Issues and JIRA remain fully supported. Local tick
 
 ## Step 1: Switch the provider
 
-Edit `.claude/backlog-config.json` in your project root:
+Edit `.specrails/backlog-config.json` in your project root:
 
 ```json
 {
@@ -42,7 +42,7 @@ Then initialize the ticket store if it doesn't exist yet:
 Or create the file manually:
 
 ```bash
-cat > .claude/local-tickets.json << 'EOF'
+cat > .specrails/local-tickets.json << 'EOF'
 {
   "schema_version": "1.0",
   "revision": 0,

package/docs/workflows.md

@@ -126,7 +126,7 @@ View your prioritized product backlog, ranked by VPC fit and effort.
 
 ### What it shows
 
-The Product Analyst reads your backlog (local tickets in `.claude/local-tickets.json` by default, or GitHub Issues labeled `product-driven-backlog` if configured) and produces:
+The Product Analyst reads your backlog (local tickets in `.specrails/local-tickets.json` by default, or GitHub Issues labeled `product-driven-backlog` if configured) and produces:
 
 - **Backlog table** per area — sorted by Total Persona Score
 - **Top 3 recommendations** — ranked by VPC score / effort ratio, filtered to Wave 1 of the safe implementation order

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "specrails-core",
-  "version": "3.5.0",
+  "version": "3.5.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/templates/commands/specrails/setup.md

@@ -699,7 +699,7 @@ Ask the user how they want to manage their product backlog. Default is local —
 Use local ticket management or connect an external provider?
 
 1. **Local tickets** (default, recommended) — lightweight JSON-based ticket management built into the project.
-   No external tools or accounts required. Tickets stored in `.claude/local-tickets.json`, version-controlled and diffable.
+   No external tools or accounts required. Tickets stored in `.specrails/local-tickets.json`, version-controlled and diffable.
 2. **External provider** — connect GitHub Issues, JIRA, or disable backlog commands
 ```
 
@@ -713,7 +713,7 @@ If the user selects **2**: display the secondary menu:
 Which external provider?
 
 1. **Local tickets** (recommended) — lightweight JSON-based ticket management built into the project.
-   No external tools required. Tickets stored in `.claude/local-tickets.json`, version-controlled and diffable.
+   No external tools required. Tickets stored in `.specrails/local-tickets.json`, version-controlled and diffable.
 2. **GitHub Issues** — uses `gh` CLI to read/create issues with labels and VPC scores
 3. **JIRA** — uses JIRA CLI or REST API to read/create tickets in a JIRA project
 4. **None** — skip backlog commands (you can still use /implement with text descriptions)
@@ -895,7 +895,7 @@ Ask:
 
 Set `EPIC_LINK_FIELD` to `parent` or `customfield_10014`. Default: `parent`.
 
-Store the full configuration in `.claude/backlog-config.json`:
+Store the full configuration in `.specrails/backlog-config.json`:
 ```json
 {
   "provider": "jira",