tlc-claude-code 2.9.0 → 2.9.1

package/.claude/commands/tlc/build.md

@@ -174,50 +174,85 @@ If orchestrator is down, dispatch directly via tmux on the host:
 
 ```bash
 tmux new-session -d -s <task-id> -c $(pwd)
-tmux send-keys -t <task-id> "/opt/homebrew/bin/codex --full-auto '<prompt>'" Enter
+tmux send-keys -t <task-id> "/opt/homebrew/bin/codex --dangerously-bypass-approvals-and-sandbox '<prompt>'" Enter
 ```
 
-### Step O4: Report and Free
+### Step O4: Report and Monitor
 
-After dispatching all tasks, report:
+After dispatching all tasks, report the initial state:
 
 ```
 Dispatched N tasks to orchestrator:
-  ses_abc123  Task 1: Create schema         codex  running  monitor=running
-  ses_def456  Task 2: Add validation        codex  running  monitor=running
+  ses_abc123  Task 1: Create schema         codex  running
+  ses_def456  Task 2: Add validation        codex  running
 
-Run /tlc:status to check progress.
-I'm free — what would you like to work on?
+Monitoring for completion...
 ```
 
-Include each session's current monitor state in the status display. When available, prefer the same session-status formatting used by orchestration status views so monitor values stay consistent across commands.
+**Do NOT stop here. Do NOT say "I'm free". Enter the monitoring loop immediately.**
 
-**STOP HERE.** Do not write code. Do not execute inline mode. Claude is the PM, not the coder.
+### Step O5: Auto-Monitor Loop (Mandatory)
 
-### Step O5: Monitor (When User Asks)
+After dispatching, poll all sessions every 30 seconds until all reach terminal states. This loop runs automatically — do not wait for the user to ask.
 
-When the user asks for status or agents complete, check:
+```
+Poll cycle:
+1. For each dispatched session, check: GET /sessions/:id/status (or tmux capture-pane)
+2. Classify each session:
+   - completed → ready for merge-back
+   - stuck → send Enter once, re-check next cycle. After 3 attempts, ask user: "Session stuck. Retry or cancel?"
+   - budget_exhausted → ask user: "Budget exhausted. Re-dispatch or skip?"
+   - crashed / errored → log error, mark task as failed, continue with others
+   - timed_out → log timeout, mark task as failed
+   - running → continue monitoring
+3. When ANY session completes, report immediately: "✅ ses_abc123 Task 1 complete"
+4. When ALL dispatched sessions reach terminal states, exit the loop
+```
 
-```bash
-# Check all sessions
-curl -s http://localhost:3100/sessions | node -e "
-const d=require('fs').readFileSync('/dev/stdin','utf8');
-JSON.parse(d).forEach(s=>console.log(s.id, s.status, s.project));
-"
+**Use Bash `sleep 30` between poll cycles. Do not use background tasks for this — poll sequentially in the main conversation so results are visible.**
 
-# Check specific session output (inside container)
-docker exec tlc-agent-runner tmux capture-pane -t <session_id> -p -S -20
-```
+Surface progress at natural milestones:
+- When a session completes: one-line status update
+- When all sessions in a parallel batch complete: summary + trigger next batch
+- When a session fails: immediate report with error details
 
-Auto-approve any prompts found in tmux sessions:
+### Step O5a: Dispatch Dependent Tasks
+
+When a batch of tasks completes, check the dependency graph for newly unblocked tasks. Dispatch them immediately without asking.
 
-```bash
-docker exec tlc-agent-runner tmux send-keys -t <session_id> Enter
 ```
+Example:
+  Tasks 1+2 dispatched (parallel, no deps)
+  Task 1 completes → check if any task depends only on Task 1 → dispatch it
+  Task 2 completes → check if remaining tasks are unblocked → dispatch them
+  Tasks 3+4 now unblocked → dispatch immediately
+  ...continue until all tasks dispatched and completed
+```
+
+### Step O5b: Auto Merge-Back
+
+When all tasks in the phase complete (or all non-failed tasks complete):
+
+1. Pull all commits from container worktrees to the host phase branch
+2. Run the full test suite: `cd server && npx vitest run` (or project's test command)
+3. If tests pass → continue to Step O5c
+4. If tests fail → report failures, attempt auto-fix (one round), re-run tests
+
+### Step O5c: Auto Review + PR
+
+After tests pass:
+
+1. Run auto-review (same checks as Step 10 in Inline Mode)
+2. If review passes → push branch and create PR (ask user before pushing per project rules)
+3. If review fails → fix issues, re-run tests, re-review (max 3 iterations)
 
 ### Step O6: Cleanup
 
-When all tasks complete, remove `.tlc/.build-routing-active` and report results.
+After PR is created (or phase completes):
+- Remove `.tlc/.build-routing-active`
+- Remove `.tlc/.active-sessions.json`
+- Mark completed tasks `[x]` in PLAN.md
+- Report final summary
 
 ## INLINE MODE
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "tlc-claude-code",
-  "version": "2.9.0",
+  "version": "2.9.1",
   "description": "TLC - Test Led Coding for Claude Code",
   "bin": {
     "tlc-claude-code": "./bin/install.js",