Repository navigation
Keep schedule reads complete and prepare production rollout review - #972
Merged
NewWorldVenture merged 7 commits intoOct 8, 2026
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub. |
NewWorldVenture
changed the title
NewWorldVenture
changed the title
NewWorldVenture
merged commit Oct 8, 2026
4389350
into
codex/audit-goal-followups-20261004
9 checks passed
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
2 participants
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.
Calendar, sports and school readers could return incomplete or incorrect schedules: saved DST-fold seeds shifted, recurrence expansion stopped silently, sports missed old active series, and school A/B selection used the UTC date. Preserve exact seed instants, require complete bounded expansion, page counted reads with stable scope/order, and resolve school weeks in the family timezone. School exports now use the full A/B roster within their declared cap rather than only the current week; invalid/unrepresentable date windows return service errors.
The money-boundary audit could credit an unrelated command, role or non-manager predicate as protection. Automated and hand-run diagnostics now require matching command/role coverage and direct manager predicates. Ten isolated PostgreSQL cases verify agreement. These remain conservative metadata screens, not live exploit proofs.
The production rollout review in docs/final-audit/rollout-20261008 retains read-only catalog and aggregate preflights, deterministic checksums, staged gates and recovery requirements. Existing release checksums match, but unchanged preflight gates reject the current ledger/inventory. Fresh metadata confirms missing allowance/investment guards. Aggregate counts identify existing family/wallet and investment-amount inconsistencies; no individual records, identifiers or amounts were returned. Their provenance and disposition remain unresolved. An unallocated NOT VALID composite-FK candidate passes an isolated structural fixture, preserves historical rows and remains outside every apply workflow. It is not an approved or representative full-schema production release. Existing migration allocations are untouched.
Validation on Node24.21: the timetable batch passes the full UTC suite (1,956 files, 27,126 tests, two expected failures, 75 skips). The subsequent export repair passes 91 focused tests in UTC, Los Angeles and Tokyo, full TypeScript and scoped lint. Final money/register checks pass47 tests; query audit retains four held RPCs and one unresolved dynamic call; migration filename audit remains451. The earlier calendar batch also passed12 synthetic browser fixtures. Exact-new-head hosted CI is running; earlier full hosted success on20d9d447f does not certify this head.
Draft stacked on #969. Root is the sole finalaudit.md writer. Inventory reconciliation preserves prior IDs/history and adds18 support obligations:344/14,556 closed (2.36%), Production Ready NO. Existing-data reconciliation, production dependency/role/trigger rehearsal, held contracts, public attachments, source-zone/exception persistence and prior worker/device/provider acceptance holds remain. No merge, deployment, production write/configuration/credential change or financial action occurred.