monitor-agent-threadlisted

# Monitor agent thread Monitor outcomes and state without exposing hidden reasoning or steering the target. ## Core workflow 1. Identify the target product, session ID, repo/worktree, and expected outcome. If ambiguous, run: ```powershell python "{{SKILL_HOME}}/scripts/thread_watch.py" discover --product auto --cwd "<repo-fragment>" ``` 2. Take a safe snapshot: ```powershell python "{{SKILL_HOME}}/scripts/thread_watch.py" snapshot --product <claude|codex> --session "<id-or-jsonl-path>" --stall-seconds 600 ``` 3. Verify important state outside the transcript when possible: process presence, worktree branch/status, expected artifact, commit SHA, test result, or PR state. Logs describe actions; durable state proves outcomes. 4. For ongoing monitoring, create or update a thread heartbeat with the app's automation tool. Prefer a two-minute interval for active work. Include the exact session ID/log path, expected artifact, stall threshold, notification conditions, and a read-only/non-steering rule. Do not create duplicate monitors. 5. Notify only on a terminal or decision-relevant event: - completion; - approval/input requested; - tool error or blocker; - material scope deviation; - sustained no-progress beyond the chosen threshold. 6. On completion, report the outcome, verification evidence, artifact/commit/PR references, unresolved uncertainty, and what was not exercised. Deactivate the monitor. ## Privacy and safety invariants - Never