## Abandonment Watchdog — Automated Repair Task
Task **[Demo] D16.1: Enrich top 3 hypotheses to demo quality — deep descriptions, citations, pathway diagrams** (`b40945ad-76a`) 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 b40945ad-76a` 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 b40945ad-76af-4c77-89bc-cfc5cb0abe9d --status done`
If the task is **impossible** (bad spec, removed API, etc.), archive it: `orchestra update --id b40945ad-76af-4c77-89bc-cfc5cb0abe9d --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.