Repository navigation
feat(reminders): centralize decisions in shared core - #66
Open
turinglambdaai wants to merge 1 commit into
Open
turinglambdaai wants to merge 1 commit into
turinglambdaai wants to merge 1 commit into
Conversation
Starting SHA: 9ba9389 Central policy SHA read: 79a2b705a37a8c428c3d1a184d9f331d66624361 Authorization decision: 2026-10-auth-1 (no commercial gate changes).
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Closes #62.
Moves reminder eligibility, startup summarization, per-database session de-duplication, and delivery acknowledgement into the shared Racket application service. Native hosts now only schedule polls, request permission, localize the typed decision, and perform the OS handoff. Windows gains the previously missing native reminder delivery path; stale tokens are rejected after a database switch.
The core records
emitted -> attempted -> delivered|failed. Emission is the no-duplicate boundary, including transport failure. Fixtures cover startup summary, repeated wakeups, local-midnight timing, completion, later due time, failed delivery, and stale acknowledgements after reopening the database. PRODUCT-SPEC, ARCHITECTURE, user guides, generated clients, and changelog are synchronized.Starting source:
9ba9389194d44de876a8735ad51076fbc5c34fc9Central policy read:
79a2b705a37a8c428c3d1a184d9f331d66624361Authorization decision read:
2026-10-auth-1; this change does not add or alter a commercial gate.Local validation:
raco test racket/— 253 tests passedraco rivet generate --check— generated clients freshLocal Windows native compilation is unavailable because this machine does not have MSVC Build Tools. Required CI and Product Acceptance must provide Windows, macOS, and Linux native build/package/UI evidence before merge.