telegram-harnesslisted

# Telegram + tmux live harness `scripts/_harness/` runs **one process** that hosts a **fake Telegram Bot API** (FastAPI) *and* a **real** leashd Engine + TmuxAgent + WebConnector + MultiConnector, wired exactly like `main._run_multi`. You drive it over an HTTP `/control/*` plane and watch every outbound Bot API call with timestamps — so you can prove streaming, approvals, and plan/auto/task/goal/follow-up behavior against the real pipeline, no real bot needed. - `tmux_harness.py` — the server (fake Bot API + control plane + real engine). - `drive.py` — the driver/observer CLI. > Throwaway dev tooling (its docstring says "gitignored" but it **is** committed). It is not part of `pytest` / `make check`. ## ⚠️ Read before running - **The task store reads your REAL `~/.leashd/sessions.db`** — the v4 orchestrator's task DB is hardcoded to `~/.leashd/` and is **not** isolated by `storage_backend=memory`. With the orchestrator on (`TASK_ORCH=1`, default) it **recovers and re-runs your real stale `/task`s on startup.** Safest: run **`TASK_ORCH=0`**. If you must exercise the orchestrator, first confirm there's nothing to recover: ```bash sqlite3 ~/.leashd/sessions.db \ "SELECT count(*) FROM task_runs WHERE phase NOT IN ('completed','failed','escalated','cancelled')" # must print 0 (and check the log shows task recovery count 0 after HARNESS_READY) ``` A fake `HOME` does **not** reliably help — claude 2.1.x auth is macOS-keychain-based, so the pane ends up logged out