Repository navigation
feat(history): verify explicit weekly calendar occurrences - #14
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 an opt-in calendar signed-history reader beside the unchanged fixed ScheduledHistory path. The reader takes explicit Chaski occurrence slots, next-occurrence deadlines and pinned zone, validates local-week/DST coverage, then reuses existing public registration/signature/event verification. It never calls the fixed cadence measure method.
A missing target is MISSED only after a successful same-scope signed control. Future/stale slots, gaps/both fold occurrences, cross-month control/start/completion windows, partial/corrupt/truncated evidence and unavailable transport remain UNKNOWN. No timer, CLI, private-key access, writer, profile or runtime action is added. Fixed reader/9l1 paths are byte unchanged.
Validation: guarded full suite97PASS, HOME157paths+5resources CLEAN; existing state.py ResourceWarnings retained. Private actual Chaski WeeklyScheduledProjection event_id/next_checks/pinned-zone mapping produces the expected occurrence and paired MISSED->SUCCEEDED with real temporary signatures and mocked graph transport. The projection JSON is not a flat occurrence object; docs spell out that handoff.
Demo: recording, timing, reproduced with
python scripts/demo-calendar-history.py. Download and use scriptreplay. Watch signed-control/missing-target MISSED -> signed-target SUCCEEDED -> empty-history UNKNOWN. Source fixtures only, no installed/natural delivery claim.Rollback: inverse the six added paths to the recorded parent. No runtime state or key is changed.