Repository navigation
feat(schedules): project one declared UTC occurrence - #73
Merged
Merged
Conversation
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.
Add catalogue adapter v3 for an explicit integer repeat_count=1 declaration. It publishes one original UTC deadline/run identity and never advances to a second occurrence. Invalid/mixed forms refuse; the existing durable outbox and scheduled receiver continue to own deduplication, execution and publication. Versions1/2 retain their field contracts.
Validation: full739 tests +46 subtests passed under the HOME escape guard; Ruff passed. Controls cover real reader subprocesses, changed counts/identity, disabled/missing declarations and original-event deduplication across restarts. The new module is explicitly included in the wheel.
Demo: recording and reproduction caption. Base64e4845 refuses v3; candidatea25716e keeps the same event identity after the first deadline. This is fixture config/projection behavior, not live signed execution or activation.
Companions: intigraph/shantytown#601 supplies the typed declaration; intigraph/shuttle#38 restricts signed admission to that one slot. No job, graph write, key, service or schedule is enrolled here.