1.1.2: Add Codex stall detection to Planner and Evaluator skills

Author: Jeehut

.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "tandemkit",
-  "version": "1.1.1",
+  "version": "1.1.2",
   "description": "Describe your goal, approve the spec, then step away — Claude and Codex loop together until it's right.",
   "author": {
     "name": "Cihat Gündüz",

skills/evaluator/SKILL.md

@@ -79,6 +79,18 @@ Interpret `at-fault side`:
 - **If the Generator is at-fault and your watcher is dead:** re-arm it immediately (Step 6 of this SKILL — both watchers) so their eventual signal doesn't get missed a second time.
 - **If the diagnosis says your watcher is alive but the Generator is stuck:** re-run with `--touch` to refresh State.json's mtime. That re-fires the Generator's live watcher if theirs is still alive. If that doesn't wake them, their session is dead — only the user can nudge it directly.
 
+## Codex Stall Detection (never block longer than 20 min)
+
+Codex can silently stall: the Agent wrapper may report "completed" with an empty/missing output file, or the process hangs with no error for arbitrary durations. Forward progress must never depend on Codex behaving.
+
+**Rules when waiting on Codex:**
+
+1. **Work in parallel.** Do Claude's own evaluation while Codex runs — don't idle waiting.
+2. **10-min liveness check.** If no completion notification after 10 min, check the Agent's JSONL transcript mtime (`stat -f "%Sm"` on the JSONL at `/private/tmp/claude-501/.../subagents/agent-<id>.jsonl`). If it hasn't updated in ≥5 min, treat as stalled.
+3. **20-min hard ceiling.** Abandon Codex unconditionally after 20 min, regardless of liveness signals.
+4. **Validate output before trusting.** On "completed" notification, require the target file to exist with size > 500 bytes and mtime newer than Agent launch. Tiny/missing = failed write.
+5. **Proceed Claude-only on stall.** Write a `Codex-NN.md` placeholder noting the reason (rate limit / quota / mid-write stall / liveness-failure / 20-min ceiling), copy Claude's evaluation as the final `Round-NN.md`, and signal the Generator. Do NOT retry within the same round — stalls don't self-heal within minutes.
+
 ## Mindset + Anti-Bias Rules
 
 - **Assume the Generator made mistakes.** Your job is to find them.

skills/planner/SKILL.md

@@ -39,6 +39,18 @@ Goal received → Read Planner.md → Suggest name → Confirm name → **Print
 2. **Read Planner.md before any investigation or name suggestion** — Config.json check is the only prerequisite
 3. **Launch Codex immediately AFTER the mission folder exists** — Claude must not start its own investigation before Codex is launched
 
+## Codex Stall Detection (never block longer than 20 min)
+
+Codex can silently stall: the Agent wrapper may report "completed" with an empty/missing output file, or the process hangs with no error for arbitrary durations. Forward progress must never depend on Codex behaving.
+
+**Rules when waiting on Codex:**
+
+1. **Work in parallel.** Do Claude's own investigation while Codex runs — don't idle waiting.
+2. **10-min liveness check.** If no completion notification after 10 min, check the Agent's JSONL transcript mtime (`stat -f "%Sm"` on the JSONL at `/private/tmp/claude-501/.../subagents/agent-<id>.jsonl`). If it hasn't updated in ≥5 min, treat as stalled.
+3. **20-min hard ceiling.** Abandon Codex unconditionally after 20 min, regardless of liveness signals.
+4. **Validate output before trusting.** On "completed" notification, require the target file to exist with size > 500 bytes and mtime newer than Agent launch. Tiny/missing = failed write (often a double-background — see Step 9 rules; distinguish from a genuine stall before treating as one).
+5. **Proceed Claude-only on stall.** Write a `Codex-NN.md` placeholder noting the reason (rate limit / quota / mid-write stall / liveness-failure / 20-min ceiling), and continue to Step 2 with Claude's investigation only. Tell the user the round went Claude-only and why. Do NOT retry within the same session — stalls don't self-heal within minutes.
+
 ## Mindset
 
 - **You are an investigator and architect, NOT an implementer.** Your output is requirements, not code. The spec describes **WHAT** to build and **WHY** — never **HOW** to write it.