From ff5f064436502316cb17bb27d0134075c17ec90a Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Milo=C5=A1=20Jovanovi=C4=87?= Date: Thu, 24 Sep 2026 20:02:32 -0700 Subject: [PATCH] add changes to todo --- TODO.md | 13 ------------- 1 file changed, 13 deletions(-) diff --git a/TODO.md b/TODO.md index 9ca2071..5b4a505 100644 --- a/TODO.md +++ b/TODO.md @@ -24,13 +24,6 @@ Guards: A bug that silently empties the cache takes out every reconcile until someone notices. -## 2. Delta sync at the start of each reconcile - -One request, usually returning nothing. Eliminates the whole class of -stale-cache confusion that came up four separate times during testing: -a new rep not yet cached, a rep whose flag was removed still being -chosen, a department change invisible to the reconciler. - ## 3. Small fixes, one commit - **`failed` in the reconcile summary.** Run 10 logged @@ -71,12 +64,6 @@ chosen, a department change invisible to the reconciler. their department's rep signed up also stay unassigned until something triggers that department again. Rep replacement was described as frequent, so this matters more than the member-churn case. -- **Round-robin split for co-repped departments.** 14 departments have - two reps, covering 302 members, 9 of them at chapter 607. The second - rep currently gets nobody and sees an empty list with no error. - `RepsFor` already returns every rep sorted by ID, so this is a change - to how the agent is picked, not a restructuring. Blocked by the - fill-only rule, not by complexity. - **Raise the fill-only consequence upstream.** The rule came from outside the project. The concrete cost is now measurable: 14 reps at three campuses will open the app to an empty list.