@cluesmith/codev 2.0.0-rc.69 → 2.0.0-rc.70

package/dist/terminal/shepherd-replay-buffer.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"shepherd-replay-buffer.d.ts","sourceRoot":"","sources":["../../src/terminal/shepherd-replay-buffer.ts"],"names":[],"mappings":"AAAA;;;;;;;;;GASG;AAEH,qBAAa,oBAAoB;IAC/B,OAAO,CAAC,MAAM,CAAgB;IAC9B,OAAO,CAAC,UAAU,CAAK;IACvB,OAAO,CAAC,QAAQ,CAAC,QAAQ,CAAS;IAClC,OAAO,CAAC,SAAS,CAAK;IAEtB;;;OAGG;gBACS,QAAQ,GAAE,MAAe;IAIrC;;;OAGG;IACH,MAAM,CAAC,IAAI,EAAE,MAAM,GAAG,MAAM,GAAG,IAAI;IA0CnC;;;OAGG;IACH,aAAa,IAAI,MAAM;IAMvB,sCAAsC;IACtC,IAAI,IAAI,IAAI,MAAM,CAEjB;IAED,0CAA0C;IAC1C,IAAI,KAAK,IAAI,MAAM,CAElB;IAED,+BAA+B;IAC/B,KAAK,IAAI,IAAI;CAKd"}

package/dist/terminal/shepherd-replay-buffer.js

@@ -0,0 +1,94 @@
+/**
+ * Standalone replay buffer for the shepherd process.
+ *
+ * Unlike RingBuffer (which stores lines), this stores raw byte chunks
+ * to preserve exact terminal output including escape sequences. It tracks
+ * the total bytes stored and evicts oldest chunks when the limit is exceeded.
+ *
+ * This module has NO dependencies beyond Node.js built-ins so the shepherd
+ * process doesn't need to pull in the full package dependency tree.
+ */
+export class ShepherdReplayBuffer {
+    chunks = [];
+    totalBytes = 0;
+    maxLines;
+    lineCount = 0;
+    /**
+     * @param maxLines Maximum number of lines to retain. Lines are delimited
+     *   by newline characters in the raw data stream.
+     */
+    constructor(maxLines = 10_000) {
+        this.maxLines = maxLines;
+    }
+    /**
+     * Append raw PTY output data to the buffer.
+     * Evicts oldest chunks if the line count exceeds maxLines.
+     */
+    append(data) {
+        const buf = typeof data === 'string' ? Buffer.from(data, 'utf-8') : data;
+        if (buf.length === 0)
+            return;
+        // Count newlines in this chunk
+        let newLines = 0;
+        for (let i = 0; i < buf.length; i++) {
+            if (buf[i] === 0x0a)
+                newLines++;
+        }
+        this.chunks.push(buf);
+        this.totalBytes += buf.length;
+        this.lineCount += newLines;
+        // Evict oldest chunks if we've exceeded the line limit
+        while (this.lineCount > this.maxLines && this.chunks.length > 1) {
+            const oldest = this.chunks[0];
+            let removedLines = 0;
+            for (let i = 0; i < oldest.length; i++) {
+                if (oldest[i] === 0x0a)
+                    removedLines++;
+            }
+            this.chunks.shift();
+            this.totalBytes -= oldest.length;
+            this.lineCount -= removedLines;
+        }
+        // Handle edge case: single chunk exceeds line limit.
+        // Trim from the front to keep only the last maxLines lines.
+        if (this.lineCount > this.maxLines && this.chunks.length === 1) {
+            const chunk = this.chunks[0];
+            let linesToSkip = this.lineCount - this.maxLines;
+            let offset = 0;
+            while (linesToSkip > 0 && offset < chunk.length) {
+                if (chunk[offset] === 0x0a)
+                    linesToSkip--;
+                offset++;
+            }
+            this.chunks[0] = chunk.subarray(offset);
+            this.totalBytes = this.chunks[0].length;
+            this.lineCount = this.maxLines;
+        }
+    }
+    /**
+     * Get all buffered data as a single concatenated Buffer.
+     * Used for the REPLAY frame on reconnection.
+     */
+    getReplayData() {
+        if (this.chunks.length === 0)
+            return Buffer.alloc(0);
+        if (this.chunks.length === 1)
+            return this.chunks[0];
+        return Buffer.concat(this.chunks);
+    }
+    /** Current number of bytes stored. */
+    get size() {
+        return this.totalBytes;
+    }
+    /** Approximate number of lines stored. */
+    get lines() {
+        return this.lineCount;
+    }
+    /** Clear all buffered data. */
+    clear() {
+        this.chunks = [];
+        this.totalBytes = 0;
+        this.lineCount = 0;
+    }
+}
+//# sourceMappingURL=shepherd-replay-buffer.js.map

package/dist/terminal/shepherd-replay-buffer.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"shepherd-replay-buffer.js","sourceRoot":"","sources":["../../src/terminal/shepherd-replay-buffer.ts"],"names":[],"mappings":"AAAA;;;;;;;;;GASG;AAEH,MAAM,OAAO,oBAAoB;IACvB,MAAM,GAAa,EAAE,CAAC;IACtB,UAAU,GAAG,CAAC,CAAC;IACN,QAAQ,CAAS;IAC1B,SAAS,GAAG,CAAC,CAAC;IAEtB;;;OAGG;IACH,YAAY,WAAmB,MAAM;QACnC,IAAI,CAAC,QAAQ,GAAG,QAAQ,CAAC;IAC3B,CAAC;IAED;;;OAGG;IACH,MAAM,CAAC,IAAqB;QAC1B,MAAM,GAAG,GAAG,OAAO,IAAI,KAAK,QAAQ,CAAC,CAAC,CAAC,MAAM,CAAC,IAAI,CAAC,IAAI,EAAE,OAAO,CAAC,CAAC,CAAC,CAAC,IAAI,CAAC;QACzE,IAAI,GAAG,CAAC,MAAM,KAAK,CAAC;YAAE,OAAO;QAE7B,+BAA+B;QAC/B,IAAI,QAAQ,GAAG,CAAC,CAAC;QACjB,KAAK,IAAI,CAAC,GAAG,CAAC,EAAE,CAAC,GAAG,GAAG,CAAC,MAAM,EAAE,CAAC,EAAE,EAAE,CAAC;YACpC,IAAI,GAAG,CAAC,CAAC,CAAC,KAAK,IAAI;gBAAE,QAAQ,EAAE,CAAC;QAClC,CAAC;QAED,IAAI,CAAC,MAAM,CAAC,IAAI,CAAC,GAAG,CAAC,CAAC;QACtB,IAAI,CAAC,UAAU,IAAI,GAAG,CAAC,MAAM,CAAC;QAC9B,IAAI,CAAC,SAAS,IAAI,QAAQ,CAAC;QAE3B,uDAAuD;QACvD,OAAO,IAAI,CAAC,SAAS,GAAG,IAAI,CAAC,QAAQ,IAAI,IAAI,CAAC,MAAM,CAAC,MAAM,GAAG,CAAC,EAAE,CAAC;YAChE,MAAM,MAAM,GAAG,IAAI,CAAC,MAAM,CAAC,CAAC,CAAC,CAAC;YAC9B,IAAI,YAAY,GAAG,CAAC,CAAC;YACrB,KAAK,IAAI,CAAC,GAAG,CAAC,EAAE,CAAC,GAAG,MAAM,CAAC,MAAM,EAAE,CAAC,EAAE,EAAE,CAAC;gBACvC,IAAI,MAAM,CAAC,CAAC,CAAC,KAAK,IAAI;oBAAE,YAAY,EAAE,CAAC;YACzC,CAAC;YACD,IAAI,CAAC,MAAM,CAAC,KAAK,EAAE,CAAC;YACpB,IAAI,CAAC,UAAU,IAAI,MAAM,CAAC,MAAM,CAAC;YACjC,IAAI,CAAC,SAAS,IAAI,YAAY,CAAC;QACjC,CAAC;QAED,qDAAqD;QACrD,4DAA4D;QAC5D,IAAI,IAAI,CAAC,SAAS,GAAG,IAAI,CAAC,QAAQ,IAAI,IAAI,CAAC,MAAM,CAAC,MAAM,KAAK,CAAC,EAAE,CAAC;YAC/D,MAAM,KAAK,GAAG,IAAI,CAAC,MAAM,CAAC,CAAC,CAAC,CAAC;YAC7B,IAAI,WAAW,GAAG,IAAI,CAAC,SAAS,GAAG,IAAI,CAAC,QAAQ,CAAC;YACjD,IAAI,MAAM,GAAG,CAAC,CAAC;YACf,OAAO,WAAW,GAAG,CAAC,IAAI,MAAM,GAAG,KAAK,CAAC,MAAM,EAAE,CAAC;gBAChD,IAAI,KAAK,CAAC,MAAM,CAAC,KAAK,IAAI;oBAAE,WAAW,EAAE,CAAC;gBAC1C,MAAM,EAAE,CAAC;YACX,CAAC;YACD,IAAI,CAAC,MAAM,CAAC,CAAC,CAAC,GAAG,KAAK,CAAC,QAAQ,CAAC,MAAM,CAAC,CAAC;YACxC,IAAI,CAAC,UAAU,GAAG,IAAI,CAAC,MAAM,CAAC,CAAC,CAAC,CAAC,MAAM,CAAC;YACxC,IAAI,CAAC,SAAS,GAAG,IAAI,CAAC,QAAQ,CAAC;QACjC,CAAC;IACH,CAAC;IAED;;;OAGG;IACH,aAAa;QACX,IAAI,IAAI,CAAC,MAAM,CAAC,MAAM,KAAK,CAAC;YAAE,OAAO,MAAM,CAAC,KAAK,CAAC,CAAC,CAAC,CAAC;QACrD,IAAI,IAAI,CAAC,MAAM,CAAC,MAAM,KAAK,CAAC;YAAE,OAAO,IAAI,CAAC,MAAM,CAAC,CAAC,CAAC,CAAC;QACpD,OAAO,MAAM,CAAC,MAAM,CAAC,IAAI,CAAC,MAAM,CAAC,CAAC;IACpC,CAAC;IAED,sCAAsC;IACtC,IAAI,IAAI;QACN,OAAO,IAAI,CAAC,UAAU,CAAC;IACzB,CAAC;IAED,0CAA0C;IAC1C,IAAI,KAAK;QACP,OAAO,IAAI,CAAC,SAAS,CAAC;IACxB,CAAC;IAED,+BAA+B;IAC/B,KAAK;QACH,IAAI,CAAC,MAAM,GAAG,EAAE,CAAC;QACjB,IAAI,CAAC,UAAU,GAAG,CAAC,CAAC;QACpB,IAAI,CAAC,SAAS,GAAG,CAAC,CAAC;IACrB,CAAC;CACF"}

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@cluesmith/codev",
-  "version": "2.0.0-rc.69",
+  "version": "2.0.0-rc.70",
   "description": "Codev CLI - AI-assisted software development framework",
   "type": "module",
   "bin": {

package/skeleton/.claude/skills/codev/SKILL.md

@@ -31,7 +31,7 @@ Adds codev to the **current directory**. Detects existing CLAUDE.md/AGENTS.md an
 Updates framework files (protocols, roles, skills) from the installed `@cluesmith/codev` package. **Never touches user data** (specs, plans, reviews). If you've customized a framework file, creates a `.codev-new` version for manual merge.
 
 ### codev doctor
-Checks that all required dependencies are installed: Node.js (>=18), tmux (>=3), git (>=2.5), gh (authenticated), and at least one AI CLI (Claude, Gemini, or Codex).
+Checks that all required dependencies are installed: Node.js (>=18), git (>=2.5), gh (authenticated), and at least one AI CLI (Claude, Gemini, or Codex).
 
 ## Common Mistakes
 

package/skeleton/DEPENDENCIES.md

@@ -37,26 +37,6 @@ sudo apt install -y nodejs
 node --version  # Should show v18.x or higher
 ```
 
-### tmux
-
-| Requirement | Value |
-|-------------|-------|
-| Minimum Version | 3.0 |
-| Purpose | Terminal multiplexer for managing builder sessions |
-
-**Installation:**
-
-```bash
-# macOS
-brew install tmux
-
-# Ubuntu/Debian
-sudo apt install tmux
-
-# Verify
-tmux -V  # Should show tmux 3.x or higher
-```
-
 ### git
 
 | Requirement | Value |
@@ -169,7 +149,6 @@ codex --version
 | Dependency | Minimum Version | Required? |
 |------------|-----------------|-----------|
 | Node.js | 18.0.0 | Yes |
-| tmux | 3.0 | Yes |
 | git | 2.5.0 | Yes |
 | gh | latest | Yes |
 | Claude Code | latest | At least one AI CLI |
@@ -186,7 +165,7 @@ All dependencies are available via Homebrew:
 
 ```bash
 # Install all core dependencies at once
-brew install node tmux gh
+brew install node gh
 
 # Git is included with Xcode command line tools
 xcode-select --install
@@ -198,7 +177,7 @@ Most dependencies are available via apt:
 
 ```bash
 # Core dependencies
-sudo apt install nodejs npm tmux git
+sudo apt install nodejs npm git
 
 # gh requires adding GitHub's apt repository (see above)
 ```
@@ -230,17 +209,6 @@ echo $PATH
 export PATH="$PATH:$(npm config get prefix)/bin"
 ```
 
-### tmux version too old
-
-Ubuntu LTS versions often have older tmux. Install from source or use a PPA:
-
-```bash
-# Add tmux PPA for newer versions
-sudo add-apt-repository ppa:pi-rho/dev
-sudo apt update
-sudo apt install tmux
-```
-
 ### Terminal connection issues
 
 Ensure no firewall is blocking the ports (default: 4200-4299):

package/skeleton/consult-types/impl-review.md

@@ -1,38 +1,38 @@
 # Implementation Review Prompt
 
 ## Context
-You are reviewing implementation work at Stage 4 (IMPLEMENTING) of the workflow. A builder has completed a phase (Implement + Defend) and needs feedback before proceeding. Your job is to verify the implementation matches the spec and plan.
+You are reviewing implementation work during the Implement phase. A builder has completed a plan phase and needs feedback before proceeding. Your job is to verify the implementation matches the spec and plan.
+
+## CRITICAL: Verify Before Flagging
+
+Before requesting changes for missing configuration, incorrect patterns, or framework issues:
+1. **Check `package.json`** for actual dependency versions — framework conventions change between major versions
+2. **Read the actual config files** (or confirm their deliberate absence) before flagging missing configs
+3. **Do not assume** your training data reflects the version in use — verify against project files
+4. If "Previous Iteration Context" is provided, read it carefully before re-raising concerns that were already disputed
 
 ## Focus Areas
 
 1. **Spec Adherence**
    - Does the implementation fulfill the spec requirements for this phase?
    - Are acceptance criteria met?
-   - Are there deviations from the spec that need explanation?
 
 2. **Code Quality**
    - Is the code readable and maintainable?
    - Are there obvious bugs or issues?
    - Are error cases handled appropriately?
-   - Does it follow project conventions?
 
 3. **Test Coverage**
    - Are the tests adequate for this phase?
    - Do tests cover the main paths AND edge cases?
-   - Are tests testing the right things (behavior, not implementation)?
-   - Would the tests catch regressions?
 
 4. **Plan Alignment**
    - Does the implementation follow the plan?
-   - Are there deviations that make sense?
    - Are there plan items skipped or partially completed?
 
 5. **UX Verification** (if spec has UX requirements)
    - Does the actual user experience match what the spec describes?
    - If spec says "async" or "non-blocking", is it actually async?
-   - If spec says "immediate response", does user get one quickly?
-   - Do any flow diagrams in the spec match the actual behavior?
-   - **CRITICAL:** A synchronous implementation that passes tests can completely fail UX requirements
 
 ## Verdict Format
 

package/skeleton/consult-types/integration-review.md

@@ -1,7 +1,7 @@
 # Integration Review Prompt
 
 ## Context
-You are performing an integration review at Stage 6 (COMMITTED) of the workflow. The builder has created a PR and you are evaluating whether this change fits well into the broader system. This is the architect's review, focusing on how the change integrates rather than whether it works.
+You are performing an integration review of a pull request. The builder has created a PR and you are evaluating whether this change fits well into the broader system. This is the architect's review, focusing on how the change integrates rather than whether it works.
 
 ## Focus Areas
 

package/skeleton/consult-types/plan-review.md

@@ -1,7 +1,7 @@
 # Plan Review Prompt
 
 ## Context
-You are reviewing an implementation plan at Stage 2 (SPECIFIED) of the workflow. The spec has been approved - now you must evaluate whether the plan adequately describes HOW to implement it.
+You are reviewing an implementation plan during the Plan phase. The spec has been approved - now you must evaluate whether the plan adequately describes HOW to implement it.
 
 ## Focus Areas
 

package/skeleton/consult-types/pr-ready.md

@@ -1,7 +1,7 @@
 # PR Ready Review Prompt
 
 ## Context
-You are performing a final self-check at Stage 5 (IMPLEMENTED) of the workflow. The builder has completed all implementation phases and is about to create a PR. This is the last check before the work goes to the architect for integration review.
+You are performing a final self-check during the Review phase. The builder has completed all implementation phases and is about to create a PR. This is the last check before the work goes to the architect for integration review.
 
 ## Focus Areas
 

package/skeleton/consult-types/spec-review.md

@@ -1,7 +1,7 @@
 # Specification Review Prompt
 
 ## Context
-You are reviewing a feature specification at Stage 1 (CONCEIVED) of the workflow. Your role is to ensure the spec is complete, correct, and feasible before it moves to human approval.
+You are reviewing a feature specification during the Specify phase. Your role is to ensure the spec is complete, correct, and feasible before it moves to human approval.
 
 ## Focus Areas
 

package/skeleton/protocols/bugfix/prompts/pr.md

@@ -4,7 +4,7 @@ You are executing the **PR** phase of the BUGFIX protocol.
 
 ## Your Goal
 
-Create a pull request and notify the architect. The architect handles review, merge, and cleanup.
+Create a pull request, run CMAP review, and address feedback.
 
 ## Context
 
@@ -42,9 +42,28 @@ EOF
 )"
 ```
 
-### 2. Notify Architect
+### 2. Run CMAP Review
 
-After the PR is created, notify the architect and signal completion. The architect handles review, merge, and cleanup from here.
+Run 3-way parallel consultation on the PR:
+
+```bash
+consult --model gemini pr <PR_NUMBER> &
+consult --model codex pr <PR_NUMBER> &
+consult --model claude pr <PR_NUMBER> &
+```
+
+All three should run in the background (`run_in_background: true`).
+
+### 3. Address Feedback
+
+Review the consultation results:
+- Fix any issues identified by reviewers
+- Push updates to the PR branch
+- Re-run CMAP if substantial changes were made
+
+### 4. Notify Architect
+
+After CMAP review is complete and feedback is addressed, notify the architect:
 
 ```bash
 af send architect "PR #<number> ready for review (fixes issue #{{issue.number}})"
@@ -52,7 +71,7 @@ af send architect "PR #<number> ready for review (fixes issue #{{issue.number}})
 
 ## Signals
 
-When PR is created and architect is notified:
+When PR is created and reviews are complete:
 
 ```
 <signal>PHASE_COMPLETE</signal>

package/skeleton/protocols/maintain/protocol.md

@@ -186,8 +186,8 @@ Scan the actual codebase and update `codev/resources/arch.md`:
 - **Location**: path/to/component
 - **How It Works**:
   - Step-by-step explanation of the mechanism
-  - Key technologies used (e.g., "uses tmux for terminal multiplexing")
-  - Runtime behavior (e.g., "spawns a tmux session per builder")
+  - Key technologies used (e.g., "uses shepherd processes for terminal persistence")
+  - Runtime behavior (e.g., "spawns a shepherd process per builder terminal")
   - State management (e.g., "state stored in SQLite at .agent-farm/state.db")
 - **Key Files**:
   - `file.ts` - does X
@@ -222,7 +222,7 @@ For each major component, arch.md MUST explain the implementation mechanism, not
 
 | Bad (just WHAT) | Good (includes HOW) |
 |-----------------|---------------------|
-| "Agent Farm manages builders" | "Agent Farm spawns builders in isolated git worktrees. Each builder runs in a tmux session (named `builder-{id}`). The dashboard uses ttyd to expose terminals via HTTP on ports 4201-4299. State is persisted in SQLite." |
+| "Agent Farm manages builders" | "Agent Farm spawns builders in isolated git worktrees. Each builder runs in a shepherd-backed terminal session. The Tower dashboard exposes terminals via WebSocket. State is persisted in SQLite." |
 | "Consult tool queries AI models" | "Consult shells out to external CLIs (gemini-cli, codex, claude). It writes the consultant role to a temp file, sets environment variables, and streams stdout/stderr back to the user." |
 
 This level of detail enables rapid onboarding and debugging.

package/skeleton/resources/commands/agent-farm.md

@@ -43,7 +43,7 @@ af dash start [options]
 Starts the agent-farm dashboard with:
 - Architect terminal (Claude session with architect role)
 - Web-based UI for monitoring builders
-- tmux session management
+- Terminal session management (shepherd processes)
 
 The dashboard is accessible via browser at `http://localhost:<port>`.
 
@@ -132,8 +132,7 @@ af dash stop
 **Description:**
 
 Stops all running agent-farm processes including:
-- tmux sessions
-- ttyd processes
+- Terminal sessions (shepherd processes)
 - Dashboard servers
 
 Does NOT clean up worktrees - use `af cleanup` for that.

package/skeleton/resources/commands/codev.md

@@ -95,7 +95,6 @@ Verifies that all required dependencies are installed and properly configured:
 
 **Core Dependencies (required):**
 - Node.js (>= 18.0.0)
-- tmux (>= 3.0)
 - ttyd (>= 1.7.0)
 - git (>= 2.5.0)
 - gh (GitHub CLI, authenticated)
@@ -123,7 +122,6 @@ Codev Doctor - Checking your environment
 Core Dependencies (required for Agent Farm)
 
   ✓ Node.js      20.10.0
-  ✓ tmux         3.4
   ✓ ttyd         1.7.4
   ✓ git          2.42.0
   ✓ gh           authenticated

package/skeleton/roles/architect.md

@@ -160,7 +160,7 @@ af cleanup -p 0042
 ### ALWAYS Do These:
 1. **Reserve project numbers first** - Update projectlist.md before spawning
 2. **Review artifacts before approving gates** - (Strict mode) Read the spec/plan carefully
-3. **Use PR comments for feedback** - Not tmux send-keys
+3. **Use PR comments for feedback** - Not terminal send-keys
 4. **Let builders own their work** - Guide, don't take over
 
 ## Project Tracking

package/skeleton/roles/consultant.md

@@ -5,16 +5,16 @@ You are a consultant providing a second perspective to support decision-making.
 ## Responsibilities
 
 1. **Understand context** - Grasp the problem and constraints being presented
-2. **Offer insights** - Provide alternatives or considerations that may have been missed
-3. **Be constructive** - Help improve the solution, don't just critique
-4. **Be direct** - Give honest, clear feedback without excessive hedging
-5. **Collaborate** - Work toward the best outcome alongside the primary agent
+2. **Verify before flagging** - Check actual project files (package.json, configs) before claiming something is wrong or missing. Framework conventions change between major versions.
+3. **Offer insights** - Provide alternatives or considerations that may have been missed
+4. **Be constructive** - Help improve the solution, don't just critique
+5. **Be direct** - Give honest, clear feedback without excessive hedging
 
 ## You Are NOT
 
 - An adversary or gatekeeper
 - A rubber stamp that just agrees
-- A code generator (unless specifically asked for snippets)
+- A source of generic advice that ignores actual project context
 
 ## Relationship to Other Roles
 
@@ -24,4 +24,4 @@ You are a consultant providing a second perspective to support decision-making.
 | Builder | Implements in isolation |
 | Consultant | Provides perspective, supports decisions |
 
-You think alongside the other agents, helping them see blind spots.
+You think alongside the other agents, helping them see blind spots. You have filesystem access — use it to verify your claims against the actual codebase.