Six rows were resurrected before the previous fix landed: tombstoned slug, cleared retirement flag, sitting beside the correct record derived from the same file. Nothing can see them. They are not retired, so they are not stale; they path-match their own file, so every reset reports `noop` and they persist indefinitely. The stamp in the slug is itself evidence that a retirement happened, so a row carrying the mark with a cleared flag is a contradiction to repair rather than a live record. Such a row is now skipped by the heuristics like any retired one, which makes it visible as a retirement candidate again. 747 pass. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Assistant: claude-code Assistant-Model: opus Assistant-Process: 2583210@bnt-lap001 Assistant-Session: f2bff2d5-e9b2-4338-92ca-10282a927006 |
||
|---|---|---|
| .. | ||
| edge | ||
| events | ||
| models | ||
| routers | ||
| schemas | ||
| services | ||
| classification.py | ||
| config.py | ||
| database.py | ||
| doi_engine.py | ||
| flow_defs.py | ||
| main.py | ||
| task_status.py | ||
| workplan_status.py | ||