Brummel
77a92a1a0d
The previous one-liner 'notify when done and nothing left to do' left 'done' under-defined. Concrete failure mode (2026-05-12, this session): test suite for an open milestone landed, I notified on the user-specified stop trigger, but the milestone still had two follow-up iters (DESIGN.md anchor + audit) plainly in scope. The user's intent behind the trigger was 'wake me when there's nothing else to do', not 'wake me at this checkpoint'. The expanded section codes two states (done-state, problem-state), explicitly names sub-goal completion as NOT a notify event, and calibrates user-specified stop triggers: hit only if the trigger leaves the queue truly empty.