dr-init-id-collision-window

To fix task ID collisions, the losing session performs batched sed updates across artifact bodies and audit logs, coordinates git renames, and updates thin-index files to move the entire derived chain to the next free ID.

Duplicate artifact paths occur due to a TOCTOU window between /dr-init reservation and /dr-archive completion, where two concurrent sessions reserve the same task ID before either detects the conflict.

To rename task artifacts safely, perform batched in-file ID rewrites across artifact bodies and audit logs simultaneously with coordinated git renames, ensuring filenames match frontmatter task_id keys to prevent partial rename desynchronization.

Yes, you can use batched sed updates to rewrite task IDs across archived documentation and audit logs, followed by chmod restoration for verify audit logs and post-rename validation to confirm only historical evidence remains.

The TOCTOU window is the race condition timeframe between /dr-init reservation and /dr-archive completion where duplicate task IDs can be assigned, requiring collision closure via retroactive ID relabeling and full canonical probing for hot-fix branches.

Yes, collision detection probes both active task state and all archived artifacts across subdirectories including tasks, backlog, active context, and documentation/archive sets to determine whether an ID already exists outside the current session's scope.