## Abandonment Watchdog — Automated Repair Task
Task **[Senate] Knowledge growth metrics snapshot** (`05b6876b-61a`) has been abandoned 14 consecutive times.
### Error Analysis
- **Dominant pattern:** other
- **Error breakdown:** {"other": 14}
- **Recent errors:**
- `Traceback (most recent call last):
File "/home/ubuntu/scidex/metrics.py", line 15, in
_mod.run_snapshot_cycle()
File "/home/ubuntu/sc`
- `Traceback (most recent call last):
File "/home/ubuntu/scidex/metrics.py", line 15, in
_mod.run_snapshot_cycle()
File "/home/ubuntu/sc`
- `Traceback (most recent call last):
File "/home/ubuntu/scidex/metrics.py", line 15, in
_mod.run_snapshot_cycle()
File "/home/ubuntu/sc`
- `Traceback (most recent call last):
File "/home/ubuntu/scidex/metrics.py", line 15, in
_mod.run_snapshot_cycle()
File "/home/ubuntu/sc`
- `Traceback (most recent call last):
File "/home/ubuntu/scidex/metrics.py", line 15, in
_mod.run_snapshot_cycle()
File "/home/ubuntu/sc`
### 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 05b6876b-61a` 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 05b6876b-61a9-4a49-8881-17e8db81746c --status done`
If the task is **impossible** (bad spec, removed API, etc.), archive it: `orchestra update --id 05b6876b-61a9-4a49-8881-17e8db81746c --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.