tegwick
b2efadf254
The ad-hoc requalification changed 30 identifiers while deliberately keeping the filenames, per canon. The matcher's path fallback therefore matched every old row to its new record and updated it in place — so the files said CUST-WP-ADHOC-2026-08-25 while the hub still said adhoc-2026-08-25, with the row's UUID still encoding the old identifier. Exactly the file/hub identity divergence ADR-007 exists to prevent. Path matching cannot distinguish a re-key from a rename when the path does not change. Identity can: a derived row is UUIDv5 over the record id, so a changed id is a different record — the old row retires and the new one is created. Rows predating derived identity carry v4 UUIDs, where the identifier is a label rather than the identity; those keep path matching, so rename detection still works where it is the right answer. The unmatched old row keeps its own slug as key, so it lands in `stale` and becomes a retirement candidate rather than disappearing from the outcome. 720 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 | ||