@cluesmith/codev 2.0.0-rc.57 → 2.0.0-rc.58

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@cluesmith/codev",
-  "version": "2.0.0-rc.57",
+  "version": "2.0.0-rc.58",
   "description": "Codev CLI - AI-assisted software development framework",
   "type": "module",
   "bin": {
@@ -26,8 +26,10 @@
     "dev": "tsx src/cli.ts",
     "start": "node dist/cli.js",
     "test": "vitest",
-    "test:e2e": "vitest run --config vitest.e2e.config.ts",
+    "test:e2e": "npm run build && vitest run --config vitest.e2e.config.ts",
     "test:e2e:watch": "vitest --config vitest.e2e.config.ts",
+    "test:e2e:playwright": "npx playwright test",
+    "test:e2e:bats": "npm run build && npm pack && E2E_TARBALL=$(ls cluesmith-codev-*.tgz | tail -1) ../../tests/lib/bats-core/bin/bats ../../tests/e2e/",
     "postinstall": "node -e \"try{require('fs').chmodSync(require('path').join(require.resolve('node-pty'),'..','..','prebuilds',process.platform+'-'+process.arch,'spawn-helper'),0o755)}catch{}\"",
     "prepublishOnly": "npm run build"
   },
@@ -38,21 +40,17 @@
     "chalk": "^5.3.0",
     "commander": "^12.1.0",
     "glob": "^11.0.0",
-    "http-proxy": "^1.18.1",
     "js-yaml": "^4.1.0",
     "node-pty": "^1.1.0",
     "open": "^10.1.0",
-    "qrcode-terminal": "^0.12.0",
     "tree-kill": "^1.2.2",
     "ws": "^8.18.0"
   },
   "devDependencies": {
     "@playwright/test": "^1.58.0",
     "@types/better-sqlite3": "^7.6.13",
-    "@types/http-proxy": "^1.17.17",
     "@types/js-yaml": "^4.0.9",
     "@types/node": "^22.10.1",
-    "@types/qrcode-terminal": "^0.12.2",
     "@types/ws": "^8.18.1",
     "playwright": "^1.58.0",
     "tsx": "^4.19.2",

package/skeleton/porch/prompts/defend.md

@@ -1,6 +1,6 @@
 # Defend Phase Prompt
 
-You are the **Tester** hat in a Ralph-SPIDER loop.
+You are the **Tester** hat in a Ralph-SPIR loop.
 
 ## Your Mission
 

package/skeleton/porch/prompts/evaluate.md

@@ -1,6 +1,6 @@
 # Evaluate Phase Prompt
 
-You are the **Verifier** hat in a Ralph-SPIDER loop.
+You are the **Verifier** hat in a Ralph-SPIR loop.
 
 ## Your Mission
 
@@ -66,7 +66,7 @@ Create or update evaluation notes in the status file:
 ```markdown
 ## Evaluation Report
 
-**Evaluator**: Ralph-SPIDER Verifier
+**Evaluator**: Ralph-SPIR Verifier
 **Date**: {date}
 **Phase**: {phase-name}
 

package/skeleton/porch/prompts/implement.md

@@ -1,6 +1,6 @@
 # Implement Phase Prompt
 
-You are the **Implementer** hat in a Ralph-SPIDER loop.
+You are the **Implementer** hat in a Ralph-SPIR loop.
 
 ## Your Mission
 

package/skeleton/porch/prompts/plan.md

@@ -1,6 +1,6 @@
 # Plan Phase Prompt
 
-You are the **Planner** hat in a Ralph-SPIDER loop.
+You are the **Planner** hat in a Ralph-SPIR loop.
 
 ## Your Mission
 

package/skeleton/porch/prompts/review.md

@@ -1,10 +1,10 @@
 # Review Phase Prompt
 
-You are the **Reviewer** hat in a Ralph-SPIDER loop.
+You are the **Reviewer** hat in a Ralph-SPIR loop.
 
 ## Your Mission
 
-Create the final deliverables: PR and review document. This is the capstone of the SPIDER protocol.
+Create the final deliverables: PR and review document. This is the capstone of the SPIR protocol.
 
 ## Input Context
 
@@ -27,7 +27,7 @@ Create `codev/reviews/{project-id}-{name}.md` with:
 - **ID**: {project-id}
 - **Spec**: `codev/specs/{project-id}-{name}.md`
 - **Plan**: `codev/plans/{project-id}-{name}.md`
-- **Protocol**: ralph-spider
+- **Protocol**: ralph-spir
 - **Completed**: {date}
 
 ## Summary
@@ -78,7 +78,7 @@ One paragraph summarizing what was built and why.
 2. Pattern that worked well
 
 ### Process Insights
-1. What worked well in the SPIDER process
+1. What worked well in the SPIR process
 2. What could be improved
 
 ## Recommendations

package/skeleton/porch/prompts/specify.md

@@ -1,6 +1,6 @@
 # Specify Phase Prompt
 
-You are the **Spec Writer** hat in a Ralph-SPIDER loop.
+You are the **Spec Writer** hat in a Ralph-SPIR loop.
 
 ## Your Mission
 

package/skeleton/porch/prompts/understand.md

@@ -30,7 +30,7 @@ TICK is appropriate when:
 - [ ] Requirements are clear
 - [ ] No architectural changes needed
 
-If NOT appropriate, signal: `<signal>NEEDS_SPIDER</signal>`
+If NOT appropriate, signal: `<signal>NEEDS_SPIR</signal>`
 
 ### 3. Document Understanding
 
@@ -58,4 +58,4 @@ When understanding is complete:
 
 - DO NOT start implementing
 - DO NOT create new spec files (amend existing)
-- Keep scope small - if > 300 LOC, recommend SPIDER instead
+- Keep scope small - if > 300 LOC, recommend SPIR instead

package/skeleton/protocol-schema.json

@@ -2,7 +2,7 @@
   "$schema": "https://json-schema.org/draft/2020-12/schema",
   "$id": "https://codev.dev/protocol-schema.json",
   "title": "Codev Protocol Definition",
-  "description": "Schema for porch protocol definitions (SPIDER, TICK, BUGFIX, etc.)",
+  "description": "Schema for porch protocol definitions (SPIR, TICK, BUGFIX, etc.)",
   "type": "object",
   "required": ["name", "phases"],
   "properties": {
@@ -12,12 +12,12 @@
     },
     "name": {
       "type": "string",
-      "description": "Protocol name (e.g., 'spider', 'tick', 'bugfix')",
+      "description": "Protocol name (e.g., 'spir', 'tick', 'bugfix')",
       "pattern": "^[a-z][a-z0-9-]*$"
     },
     "alias": {
       "type": "string",
-      "description": "Alternative name for the protocol (e.g., 'spir' for spider)"
+      "description": "Alternative name for the protocol (e.g., 'spider' for spir)"
     },
     "version": {
       "type": "string",

package/skeleton/protocols/bugfix/builder-prompt.md

@@ -39,7 +39,7 @@ Follow the BUGFIX protocol: `codev/protocols/bugfix/protocol.md`
 
 If the fix is too complex (> 300 LOC or architectural changes), notify the Architect via:
 ```bash
-af send architect "Issue #{{issue.number}} is more complex than expected. [Reason]. Recommend escalating to SPIDER/TICK."
+af send architect "Issue #{{issue.number}} is more complex than expected. [Reason]. Recommend escalating to SPIR/TICK."
 ```
 {{/if}}
 

package/skeleton/protocols/experiment/protocol.md

@@ -10,7 +10,7 @@ Disciplined experimentation: Each experiment gets its own directory with `notes.
 
 **Use for**: Testing approaches, evaluating models, prototyping, proof-of-concept work, research spikes
 
-**Skip for**: Production code (use SPIDER), simple one-off scripts, well-understood implementations (use TICK)
+**Skip for**: Production code (use SPIR), simple one-off scripts, well-understood implementations (use TICK)
 
 ## Structure
 
@@ -141,7 +141,7 @@ What should be done based on findings?
 
 ## Integration with Other Protocols
 
-### Experiment → SPIDER
+### Experiment → SPIR
 When an experiment validates an approach for production use:
 
 1. Create a specification referencing the experiment
@@ -225,5 +225,5 @@ Determine if Redis caching improves API response times for repeated queries.
 - Memory usage: 50MB for 10k cached responses
 
 ## Next Steps
-Create SPIDER spec for production caching implementation.
+Create SPIR spec for production caching implementation.
 ```

package/skeleton/protocols/experiment/templates/notes.md

@@ -88,7 +88,7 @@ Based on these findings:
 
 1. **Immediate**: What should happen right after this experiment?
 2. **Follow-up experiments**: What new questions emerged?
-3. **Production path**: If validated, what's needed for production? (SPIDER spec?)
+3. **Production path**: If validated, what's needed for production? (SPIR spec?)
 
 ## References
 

package/skeleton/protocols/maintain/protocol.md

@@ -479,7 +479,7 @@ MAINTAIN is an **operational protocol**, not a feature development protocol:
 | Review | No |
 | 3-Way Consultation | **Yes** (before creating PR) |
 
-**Exception**: If MAINTAIN reveals need for architectural changes, those should follow SPIDER.
+**Exception**: If MAINTAIN reveals need for architectural changes, those should follow SPIR.
 
 ---
 

package/skeleton/protocols/protocol-schema.json

@@ -8,7 +8,7 @@
   "properties": {
     "name": {
       "type": "string",
-      "description": "Protocol identifier (e.g., 'spider', 'tick', 'bugfix')"
+      "description": "Protocol identifier (e.g., 'spir', 'tick', 'bugfix')"
     },
     "version": {
       "type": "string",

package/skeleton/protocols/{spider → spir}/builder-prompt.md

@@ -21,7 +21,7 @@ You are running in STRICT mode. This means:
 {{/if}}
 
 ## Protocol
-Follow the SPIDER protocol: `codev/protocols/spider/protocol.md`
+Follow the SPIR protocol: `codev/protocols/spir/protocol.md`
 Read and internalize the protocol before starting any work.
 
 {{#if spec}}

package/skeleton/protocols/{spider → spir}/prompts/implement.md

@@ -1,6 +1,6 @@
 # IMPLEMENT Phase Prompt
 
-You are executing the **IMPLEMENT** phase of the SPIDER protocol.
+You are executing the **IMPLEMENT** phase of the SPIR protocol.
 
 ## Your Goal
 

package/skeleton/protocols/{spider → spir}/prompts/plan.md

@@ -1,6 +1,6 @@
 # PLAN Phase Prompt
 
-You are executing the **PLAN** phase of the SPIDER protocol.
+You are executing the **PLAN** phase of the SPIR protocol.
 
 ## Your Goal
 
@@ -76,7 +76,7 @@ After completing the plan draft, signal completion. Porch will run 3-way consult
 
 Create the plan file at `codev/plans/{{project_id}}-{{title}}.md`.
 
-Use the plan template from `codev/protocols/spider/templates/plan.md` if available.
+Use the plan template from `codev/protocols/spir/templates/plan.md` if available.
 
 ### Plan Structure
 

package/skeleton/protocols/{spider → spir}/prompts/review.md

@@ -1,6 +1,6 @@
 # REVIEW Phase Prompt
 
-You are executing the **REVIEW** phase of the SPIDER protocol.
+You are executing the **REVIEW** phase of the SPIR protocol.
 
 ## Your Goal
 
@@ -88,7 +88,7 @@ Brief description of what was implemented.
 - [Insight 2]
 
 ### Methodology Improvements
-- [Suggested improvement to SPIDER protocol]
+- [Suggested improvement to SPIR protocol]
 - [Suggested improvement to tooling]
 
 ## Technical Debt

package/skeleton/protocols/{spider → spir}/prompts/specify.md

@@ -1,6 +1,6 @@
 # SPECIFY Phase Prompt
 
-You are executing the **SPECIFY** phase of the SPIDER protocol.
+You are executing the **SPECIFY** phase of the SPIR protocol.
 
 ## Your Goal
 

package/skeleton/protocols/{spider → spir}/protocol.json

@@ -1,7 +1,7 @@
 {
   "$schema": "../../protocol-schema.json",
-  "name": "spider",
-  "alias": "spir",
+  "name": "spir",
+  "alias": "spider",
   "version": "2.2.0",
   "description": "SPIR: Specify → Plan → Implement → Review with build-verify cycles",
   "input": {

package/skeleton/protocols/{spider → spir}/protocol.md

@@ -1,7 +1,5 @@
-# SPIR Protocol (formerly SPIDER)
+# SPIR Protocol
 
-> **Also known as**: SPIDER (legacy name)
->
 > **SPIR** = **S**pecify → **P**lan → **I**mplement → **R**eview
 >
 > Each phase has one build-verify cycle with 3-way consultation.
@@ -20,17 +18,17 @@
 ### Multi-Agent Consultation (ENABLED BY DEFAULT)
 
 **DEFAULT BEHAVIOR:**
-Multi-agent consultation is **ENABLED BY DEFAULT** when using SPIDER protocol.
+Multi-agent consultation is **ENABLED BY DEFAULT** when using SPIR protocol.
 
 **DEFAULT AGENTS:**
 - **GPT-5 Codex**: Primary reviewer for architecture, feasibility, and code quality
 - **Gemini Pro**: Secondary reviewer for completeness, edge cases, and alternative approaches
 
 **DISABLING CONSULTATION:**
-To run SPIDER without consultation, say "without consultation" when starting work.
+To run SPIR without consultation, say "without consultation" when starting work.
 
 **CUSTOM AGENTS:**
-The user can specify different agents by saying: "use SPIDER with consultation from [agent1] and [agent2]"
+The user can specify different agents by saying: "use SPIR with consultation from [agent1] and [agent2]"
 
 **CONSULTATION BEHAVIOR:**
 - DEFAULT: MANDATORY consultation with GPT-5 and Gemini Pro at EVERY checkpoint
@@ -596,12 +594,12 @@ Implements bcrypt-based password hashing with configurable rounds
 
 ### Branch Naming
 ```
-spider/####-<spec-name>/<phase-name>
+spir/####-<spec-name>/<phase-name>
 ```
 
 Example:
 ```
-spider/0001-user-authentication/database-schema
+spir/0001-user-authentication/database-schema
 ```
 
 

package/skeleton/protocols/{spider → spir}/templates/review.md

@@ -106,7 +106,7 @@
 
 ## Methodology Feedback
 
-### SP(IDE)R Protocol Effectiveness
+### SPIR Protocol Effectiveness
 - **Specification Phase**: [Was it thorough enough? Too detailed?]
 - **Planning Phase**: [Were estimates accurate? Phases well-sized?]
 - **Implementation Loop**: [Did IDE cycle work well?]

package/skeleton/protocols/tick/builder-prompt.md

@@ -22,7 +22,7 @@ You are running in STRICT mode. This means:
 ## Protocol
 Follow the TICK protocol: `codev/protocols/tick/protocol.md`
 
-TICK is for amendments to existing SPIDER specifications. You will:
+TICK is for amendments to existing SPIR specifications. You will:
 1. Identify the target spec to amend
 2. Update the spec with the amendment
 3. Update the plan

package/skeleton/protocols/tick/protocol.md

@@ -3,16 +3,16 @@
 
 ## Overview
 
-TICK is an **amendment workflow** for existing SPIDER specifications. Rather than creating new standalone specs, TICK modifies existing spec and plan documents in-place, tracking changes in an "Amendments" section.
+TICK is an **amendment workflow** for existing SPIR specifications. Rather than creating new standalone specs, TICK modifies existing spec and plan documents in-place, tracking changes in an "Amendments" section.
 
-**Core Principle**: TICK is for *refining* existing specs. SPIDER is for *creating* new specs.
+**Core Principle**: TICK is for *refining* existing specs. SPIR is for *creating* new specs.
 
-**Key Insight**: TICKs are not small SPIDERs - they're amendments to existing SPIDERs. This eliminates the "TICK vs SPIDER" decision problem and keeps related work together.
+**Key Insight**: TICKs are not small SPIRs - they're amendments to existing SPIRs. This eliminates the "TICK vs SPIR" decision problem and keeps related work together.
 
 ## When to Use TICK
 
 ### Use TICK when:
-- Making **amendments to an existing SPIDER spec** that is already `integrated`
+- Making **amendments to an existing SPIR spec** that is already `integrated`
 - Small scope (< 300 lines of new/changed code)
 - Requirements are clear and well-defined
 - No fundamental architecture changes
@@ -23,7 +23,7 @@ TICK is an **amendment workflow** for existing SPIDER specifications. Rather tha
   - Utility function additions to existing modules
   - Refactoring within an existing feature
 
-### Use SPIDER instead when:
+### Use SPIR instead when:
 - Creating a **new feature from scratch** (no existing spec to amend)
 - Major architecture changes (scope too large for amendment)
 - Unclear requirements needing exploration
@@ -31,8 +31,8 @@ TICK is an **amendment workflow** for existing SPIDER specifications. Rather tha
 - Multiple stakeholders need alignment
 
 ### Cannot Use TICK when:
-- No relevant SPIDER spec exists (create a new SPIDER spec instead)
-- Target spec is not yet `integrated` (complete the SPIDER cycle first)
+- No relevant SPIR spec exists (create a new SPIR spec instead)
+- Target spec is not yet `integrated` (complete the SPIR cycle first)
 
 ## Amendment Workflow
 
@@ -162,9 +162,9 @@ The format `[TICK ####-NNN]` identifies:
 - `####`: Parent spec number (e.g., 0002)
 - `NNN`: TICK amendment number (e.g., 001, 002, 003)
 
-## Key Differences from SPIDER
+## Key Differences from SPIR
 
-| Aspect | SPIDER | TICK |
+| Aspect | SPIR | TICK |
 |--------|--------|------|
 | Purpose | Create new features | Amend existing features |
 | File creation | Creates new spec/plan/review | Modifies spec/plan, creates review |
@@ -178,16 +178,16 @@ The format `[TICK ####-NNN]` identifies:
 
 ```
 Is there an existing spec to amend?
-├── NO → Use SPIDER (create new spec)
+├── NO → Use SPIR (create new spec)
 └── YES → Is it integrated?
-    ├── NO → Complete SPIDER cycle first
+    ├── NO → Complete SPIR cycle first
     └── YES → Is the change small (<300 LOC)?
         ├── YES → Use TICK (amend existing spec)
-        └── NO → Use SPIDER (scope too large)
+        └── NO → Use SPIR (scope too large)
 ```
 
 **Mental Model**:
-- SPIDER = Create new feature from scratch
+- SPIR = Create new feature from scratch
 - TICK = Refine/extend existing feature
 
 ## Example TICK Workflow
@@ -251,7 +251,7 @@ Existing standalone TICK projects (created before this protocol change) are gran
 1. **Single source of truth**: Spec file shows complete feature evolution
 2. **Clear history**: Amendments section documents all changes chronologically
 3. **Reduced fragmentation**: Related work stays together
-4. **Simpler mental model**: "New vs amendment" is clearer than "SPIDER vs TICK"
+4. **Simpler mental model**: "New vs amendment" is clearer than "SPIR vs TICK"
 5. **Preserved context**: Looking at a spec shows all refinements
 
 ## Limitations
@@ -264,14 +264,14 @@ Existing standalone TICK projects (created before this protocol change) are gran
 ## Best Practices
 
 1. **Verify spec is integrated**: Never TICK a spec that isn't complete
-2. **Keep TICKs small**: If scope grows, consider new SPIDER spec
+2. **Keep TICKs small**: If scope grows, consider new SPIR spec
 3. **Clear summaries**: Amendment entries should be self-explanatory
 4. **Test before review**: Always test functionality before presenting
 5. **Honest documentation**: Document all deviations in review
 
 ## Templates
 
-TICK uses the standard SPIDER templates with amendments sections:
-- Spec template: `codev/protocols/spider/templates/spec.md` (includes Amendments section)
-- Plan template: `codev/protocols/spider/templates/plan.md` (includes Amendment History section)
+TICK uses the standard SPIR templates with amendments sections:
+- Spec template: `codev/protocols/spir/templates/spec.md` (includes Amendments section)
+- Plan template: `codev/protocols/spir/templates/plan.md` (includes Amendment History section)
 - Review template: `codev/protocols/tick/templates/review.md` (TICK-specific)

package/skeleton/protocols/tick/templates/review.md

@@ -77,7 +77,7 @@
 
 ## TICK Protocol Feedback
 - **Autonomous execution**: [Worked well / Issues encountered]
-- **Single-phase approach**: [Appropriate / Should have used SPIDER]
+- **Single-phase approach**: [Appropriate / Should have used SPIR]
 - **Speed vs quality trade-off**: [Balanced / Too fast / Too slow]
 - **End-only consultation**: [Caught issues / Missed opportunities]
 

package/skeleton/resources/commands/overview.md

@@ -91,7 +91,7 @@ Agent Farm is configured via `af-config.json` at the project root. Created durin
 
 ## Related Documentation
 
-- [SPIDER Protocol](../protocols/spider/protocol.md) - Multi-phase development workflow
+- [SPIR Protocol](../protocols/spir/protocol.md) - Multi-phase development workflow
 - [TICK Protocol](../protocols/tick/protocol.md) - Fast amendment workflow
 - [Architect Role](../roles/architect.md) - Architect responsibilities
 - [Builder Role](../roles/builder.md) - Builder responsibilities

package/skeleton/resources/workflow-reference.md

@@ -1,6 +1,6 @@
 # Architect-Builder Workflow Reference
 
-Quick reference for the 7-stage project workflow. For protocol details, see `codev/protocols/spider/protocol.md`.
+Quick reference for the 7-stage project workflow. For protocol details, see `codev/protocols/spir/protocol.md`.
 
 ## Workflow Overview
 
@@ -236,7 +236,7 @@ af cleanup -p XXXX --force
 
 ## Related Documentation
 
-- Full SPIDER protocol: `codev/protocols/spider/protocol.md`
+- Full SPIR protocol: `codev/protocols/spir/protocol.md`
 - Builder role: `codev/roles/builder.md`
 - Architect role: `codev/roles/architect.md`
 - Consultant role: `codev/roles/consultant.md`

package/skeleton/roles/architect.md

@@ -95,7 +95,7 @@ The builder stops at gates requiring approval:
 **spec-approval** - After builder writes the spec
 ```bash
 # Review the spec in the builder's worktree
-cat worktrees/spider_0042_user-authentication/codev/specs/0042-user-authentication.md
+cat worktrees/spir_0042_user-authentication/codev/specs/0042-user-authentication.md
 
 # Approve if satisfactory
 porch approve 0042 spec-approval
@@ -104,7 +104,7 @@ porch approve 0042 spec-approval
 **plan-approval** - After builder writes the plan
 ```bash
 # Review the plan
-cat worktrees/spider_0042_user-authentication/codev/plans/0042-user-authentication.md
+cat worktrees/spir_0042_user-authentication/codev/plans/0042-user-authentication.md
 
 # Approve if satisfactory
 porch approve 0042 plan-approval

package/skeleton/roles/builder.md

@@ -60,7 +60,7 @@ You must:
 
 ### What You DON'T Do in Strict Mode
 
-- **Don't manually follow SPIDER steps** - Porch handles this
+- **Don't manually follow SPIR steps** - Porch handles this
 - **Don't run consult directly** - Porch runs 3-way reviews
 - **Don't edit status.yaml phase/iteration** - Only porch modifies state
 - **Don't call porch approve** - Only humans approve gates
@@ -80,7 +80,7 @@ cat codev/specs/XXXX-*.md
 cat codev/plans/XXXX-*.md
 
 # Read the protocol
-cat codev/protocols/spider/protocol.md
+cat codev/protocols/spir/protocol.md
 
 # Start implementing
 ```

package/skeleton/templates/AGENTS.md

@@ -8,7 +8,7 @@ This project uses **Codev** for AI-assisted development.
 
 ## Available Protocols
 
-- **SPIDER**: Multi-phase development with consultation (`codev/protocols/spider/protocol.md`)
+- **SPIR**: Multi-phase development with consultation (`codev/protocols/spir/protocol.md`)
 - **TICK**: Fast autonomous implementation (`codev/protocols/tick/protocol.md`)
 - **EXPERIMENT**: Disciplined experimentation (`codev/protocols/experiment/protocol.md`)
 - **MAINTAIN**: Codebase maintenance (`codev/protocols/maintain/protocol.md`)

package/skeleton/templates/CLAUDE.md

@@ -6,7 +6,7 @@ This project uses **Codev** for AI-assisted development.
 
 ## Available Protocols
 
-- **SPIDER**: Multi-phase development with consultation (`codev/protocols/spider/protocol.md`)
+- **SPIR**: Multi-phase development with consultation (`codev/protocols/spir/protocol.md`)
 - **TICK**: Fast autonomous implementation (`codev/protocols/tick/protocol.md`)
 - **EXPERIMENT**: Disciplined experimentation (`codev/protocols/experiment/protocol.md`)
 - **MAINTAIN**: Codebase maintenance (`codev/protocols/maintain/protocol.md`)

package/skeleton/templates/cheatsheet.md

@@ -41,7 +41,7 @@ Just like structuring a human team—clear roles, defined processes, explicit ha
 
 | Component | Purpose |
 |-----------|---------|
-| Protocols | Define HOW work happens (SPIDER, TICK, etc.) |
+| Protocols | Define HOW work happens (SPIR, TICK, etc.) |
 | Roles | Define WHO does what (Architect, Builder, Consultant) |
 | Parallelism | Scale by running multiple builders simultaneously |
 
@@ -60,7 +60,7 @@ A **protocol** is a structured workflow that defines how work progresses from id
 
 | Protocol | Use For | Phases |
 |----------|---------|--------|
-| **SPIDER** | New features | Specify → Plan → Implement → Defend → Evaluate → Review |
+| **SPIR** | New features | Specify → Plan → Implement → Review |
 | **TICK** | Amendments to existing specs | Task Identification → Coding → Kickout |
 | **MAINTAIN** | Codebase hygiene | Dead code removal, documentation sync |
 | **EXPERIMENT** | Research & prototyping | Hypothesis → Experiment → Conclude |
@@ -145,7 +145,7 @@ Multi-agent consultation. Used by both humans and agents—**mostly agents** dur
 
 ## Quick Reference
 
-### SPIDER Checklist
+### SPIR Checklist
 
 ```
 [ ] Specify - Write spec in codev/specs/XXXX-name.md

package/skeleton/templates/projectlist.md

@@ -142,6 +142,6 @@ To see high-priority work, search for `priority: high`.
 Before starting a project, verify its dependencies are at least `implemented`.
 
 ### Protocol Selection
-- **SPIDER**: Most projects (formal spec → plan → implement → review)
+- **SPIR**: Most projects (formal spec → plan → implement → review)
 - **TICK**: Small, well-defined tasks (< 300 lines) or amendments to existing specs
 - **EXPERIMENT**: Research/prototyping before committing to a project

package/templates/dashboard/js/main.js

@@ -99,7 +99,7 @@ function renderInfoHeader() {
     <div class="projects-info">
       <h1 style="font-size: 20px; margin-bottom: 12px; color: var(--text-primary);">Agent Farm Dashboard</h1>
       <p>Coordinate AI builders working on your codebase. The left panel shows the Architect terminal – tell it what you want to build. <strong>Tabs</strong> shows open terminals (Architect, Builders, utility shells). <strong>Files</strong> lets you browse and open project files. <strong>Projects</strong> tracks work as it moves from conception to integration.</p>
-      <p>Docs: <a href="#" onclick="openProjectFile('codev/resources/cheatsheet.md'); return false;">Cheatsheet</a> · <a href="#" onclick="openProjectFile('codev/resources/lifecycle.md'); return false;">Lifecycle</a> · <a href="#" onclick="openProjectFile('codev/resources/commands/overview.md'); return false;">CLI Reference</a> · <a href="#" onclick="openProjectFile('codev/protocols/spider/protocol.md'); return false;">SPIDER Protocol</a> · <a href="https://github.com/cluesmith/codev#readme" target="_blank">README</a> · <a href="https://discord.gg/mJ92DhDa6n" target="_blank">Discord</a></p>
+      <p>Docs: <a href="#" onclick="openProjectFile('codev/resources/cheatsheet.md'); return false;">Cheatsheet</a> · <a href="#" onclick="openProjectFile('codev/resources/lifecycle.md'); return false;">Lifecycle</a> · <a href="#" onclick="openProjectFile('codev/resources/commands/overview.md'); return false;">CLI Reference</a> · <a href="#" onclick="openProjectFile('codev/protocols/spir/protocol.md'); return false;">SPIR Protocol</a> · <a href="https://github.com/cluesmith/codev#readme" target="_blank">README</a> · <a href="https://discord.gg/mJ92DhDa6n" target="_blank">Discord</a></p>
     </div>
   `;
 }