Record the deletion-candidate reviews for M0–M5 retroactively (D68 cadence) #168

Open
opened 2026-08-27 19:21:24 +02:00 by thecrealm · 0 comments
Owner

Review finding 2026-08-27 (E4). D68 makes the "which abstraction would we delete" review a per-milestone D-entry and CLAUDE.md requires it at each milestone close, but none is recorded for M0–M5 — the only mention is D68 itself. Acceptance: one dated D-entry per closed milestone (candidate, why it stays or goes); the M6 entry lands with #133.

Review finding 2026-08-27 (E4). D68 makes the "which abstraction would we delete" review a per-milestone D-entry and CLAUDE.md requires it at each milestone close, but none is recorded for M0–M5 — the only mention is D68 itself. Acceptance: one dated D-entry per closed milestone (candidate, why it stays or goes); the M6 entry lands with #133.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
thecrealm/katrix#168
No description provided.