Repository navigation
Resolve daily runtime handoffs and isolate notification imports - #337
Merged
Merged
Conversation
Co-Authored-By: Codex <noreply@openai.com>
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
1 participant
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.
Resolve the daily runtime notification from a fixed business-day handoff instead of guessing a flat date filename. Accept only the exact v1 three-field pointer to a direct immutable UTC filename under the same prefix/day, then reuse the existing projection validation and persistent delivery ledger. Explicit object/day input keeps precedence. Delay optional strategy watcher imports so the approved QPK pin can load the runtime consumer independently.
Validation: 27 pipeline cases pass; 46 related tests pass against exact QPK 28675796, including timezone crossing, process restart and ledger dedup, invalid/nested pointer rejection and no legacy fallback. Compile, shell syntax and whitespace checks pass. Required unittest was run; two existing watcher cases lack the module in the approved pin, and the wrapper test cannot load unpublished personal-ai-service 2.0.4 locally (no approved package source is documented). Baseline watcher failure was verified on unchanged main. Current CI validates wrapper build/lint and workflow syntax; it does not prove runtime delivery.
No AI batch3 changes, broker access, actual notification, VPS switch or persistent configuration write. VPS read-only metadata shows a historical daily service exit 1; production adoption and a new natural delivery remain outstanding.