Public: anyone can read this; the crew can change it.
small: The review page's finished screen also says how many reminders were held until tomorrow #257
Check · Review · Land · Live done — Landed and live in production.
The finished screen on the review page now adds "N held until tomorrow." when any reminders were held today, and adds nothing when none were. The new tests and src/settled.test.ts pass.
shipped production is serving it deploy d2eada7
The finished screen on the review page now adds "N held until tomorrow." when any reminders were held today, and adds nothing when none were. The new tests and src/settled.test.ts pass. I could not run the other checks: tsc printed its usage text because the clone has no tsconfig, and scripts/gate.ts and scripts/design-lint.ts do not exist here, so I skipped those three. The forge's check will run on the push. I did not touch src/web/.
- What moved:
src/settled.tsgains aheldcount next tosentanddeclined, andsettledLinewrites it as its own sentence. The page and route are unchanged, because #251 already passessettledthrough. - Examples: "You approved 3 and declined 1 today. 2 held until tomorrow." With only holds, it reads "1 held until tomorrow."
- How "today" is counted: holds are counted where
held_onequals the agent's local day. This is the same day as the sent and declined counts, and it is read from the records, not the query string. A hold that is released or later sent is deleted, so it drops out of the count. A hold placed on a reminder that is already held counts once, under its latest hold day. - Tests:
src/settled.test.tscovers the new wording, including the held-only case.src/review.test.tsholds a reminder through the page and checks the finished screen's count goes up by one. It also checks the count survives adone=9query string. - Existing assertions changed:
src/settled.test.tsalready builtSettledobjects by hand. I addedheld: 0to those so they type-check, and left their expected strings alone. - Not done: I did not add a held count to the "approved/declined" sentence itself, and did not change what the queue shows.
🤖 Generated with Claude Code
Clean, small change. settledOn counts reminder_hold rows with held_on = the agent local day using a parameterised query; the line is escaped by the page; no contract, route or dependency change. Tests cover the wording (singular/plural, held-only, none) and the page flow, and would fail without the change. Minor note, not blocking: a re-hold of an already-held reminder can push until beyond tomorrow, so the wording is approximate in that case.
The finished screen on the review page now adds "N held until tomorrow." when any reminders were held today, and adds nothing when none were. The new tests and
src/settled.test.tspass. I could not run the other checks:tscprinted its usage text because the clone has notsconfig, andscripts/gate.tsandscripts/design-lint.tsdo not exist here, so I skipped those three. The forge's check will run on the push. I did not touchsrc/web/.src/settled.tsgains aheldcount next tosentanddeclined, andsettledLinewrites it as its own sentence. The page and route are unchanged, because #251 already passessettledthrough.held_onequals the agent's local day. This is the same day as the sent and declined counts, and it is read from the records, not the query string. A hold that is released or later sent is deleted, so it drops out of the count. A hold placed on a reminder that is already held counts once, under its latest hold day.src/settled.test.tscovers the new wording, including the held-only case.src/review.test.tsholds a reminder through the page and checks the finished screen's count goes up by one. It also checks the count survives adone=9query string.src/settled.test.tsalready builtSettledobjects by hand. I addedheld: 0to those so they type-check, and left their expected strings alone.🤖 Generated with Claude Code
Closes #255