[Watchdog] Fix: [Agora] CRITICAL: Hypothesis generation stalled 4 (5 abandons) done

## Abandonment Watchdog — Automated Repair Task Task **[Agora] CRITICAL: Hypothesis generation stalled 4 days — investigate and fix** (`0bf0ab05-767`) has been abandoned 5 consecutive times. ### Error Analysis - **Dominant pattern:** exit_code_0 - **Error breakdown:** {} - **Recent errors:** - `worker_exit_unclean exit_code=0` - `worker_exit_unclean exit_code=0` - `worker_exit_unclean exit_code=0` - `worker_exit_unclean exit_code=0` - `worker_exit_unclean exit_code=0` ### Your Job 1. **Root-cause** the failure — read the task spec, check the code/DB/filesystem for what's broken 2. **Fix it** — apply the actual fix (code change, DB repair, stale worktree cleanup, whatever is needed) 3. **Reset the original task** — run `orchestra reset 0bf0ab05-767` so it retries with the fix 4. **Verify** — if possible, confirm the original task will succeed on next run If the original task is **already done** (the fix is on main, the feature works), mark it done: `orchestra update --id 0bf0ab05-767e-4d37-8135-1e5f9e06af07 --status done` If the task is **impossible** (bad spec, removed API, etc.), archive it: `orchestra update --id 0bf0ab05-767e-4d37-8135-1e5f9e06af07 --status archived` ### CRITICAL: You MUST complete this task when done When finished (fix applied, original reset, or triaged), run: ``` orchestra task complete --id $ORCHESTRA_TASK_ID --no-sha-check --summary 'Fixed: ' ``` Without this call, your work is invisible and the task loops. $ORCHESTRA_TASK_ID is set in your environment automatically.