pr-babysit

# PR Babysit ## Doctrine A subscription is not finished until the PR is MERGED or CLOSED. Webhook events do not cover everything that matters — CI success, new pushes from other collaborators, and merge-conflict transitions can all happen silently with no event firing. Pair the event subscription with a scheduled self check-in (~60 min) so nothing goes stale between events. Never poll with sleep — use the harness's scheduling primitive to re-arm the next check-in. ## Trigger - Immediately after creating a pull request. - When asked to watch, babysit, or autofix a PR. ## Inputs - Owner, repo, PR number. ## Loop steps 1. **Subscribe** to PR activity using the harness's subscribe tool. 2. **On every event or check-in**, fetch current state: check-runs and review threads (github MCP `pull_request_read` with `get_check_runs` and `get_review_comments`). 3. **Triage** what changed: - CI failure → pull the failing job log, diagnose the cause, fix it per the `agentic-delegation` workflow templates (Haiku for research/gates, Sonnet for bulk writing, orchestrator verifies and commits), then push to the PR branch. - Review comment → if the fix is unambiguous, make the fix, reply once with the commit hash, and resolve the thread. If ambiguous, ask the user with full context rather than guessing. - Duplicate or no-action events → skip silently. 4. **After any push**, run the `definition-of-done` skill before committing. 5. **Re-arm** the next check-i...