pynchy-developmentlisted

# Pynchy Development Run commands directly—don't tell the user to run them. ## Am I on pynchy? Check `hostname`. If it returns `pynchy-server`, you're on the server and can access services at `localhost`. Otherwise, reach pynchy over Tailscale (e.g., `ssh pynchy-server`). ## Commands ```bash uv run pynchy # Run the app uv run pytest tests/ # Run tests uv run ruff check --fix src/ # Lint + autofix uv run ruff format src/ # Format uvx pre-commit run --all-files # Run all pre-commit hooks ./src/pynchy/agent/build.sh # Rebuild agent container ``` ## Documentation Lookup When you need documentation for a library or framework, use the context7 MCP server to get up-to-date docs. Don't rely on training data for API details that may have changed. ## Testing Philosophy Write tests that validate **actual business logic**, not just line coverage. See [references/testing-philosophy.md](references/testing-philosophy.md) for what makes a good test vs. coverage theater. ## Known Issues (2026-02-08) 1. **[FIXED] Resume branches from stale tree position** — subagent CLI processes write to the same session JSONL; on resume, the CLI may pick a stale branch tip. Fix: pass `resumeSessionAt` with the last assistant message UUID. 2. **IDLE_TIMEOUT == CONTAINER_TIMEOUT (both 30 min)** — both timers fire together, so containers exit via hard SIGKILL (code 137) instead of graceful `_close` shutdown. Idle timeout should be shorter (~5 min). 3. **Cursor advanced be