Fix backdated balance propagation across opening checkpoints - #21
Merged
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
AFR0011
marked this pull request as ready for review
September 15, 2026 22:06
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.
Summary
Fixes the case where a newly recorded backdated transfer/exchange is saved in history but does not change current balances because its business date predates an opening checkpoint.
Ledger semantics
openingcheckpoints are treated as baseline snapshots of records that existed when the opening was created.reconciliationcheckpoints remain absolute observations and keep the existing historical/same-day ordering behavior.Regression coverage
Scope / known limitation
This patch fixes newly created backdated activity. It intentionally does not attempt to reconstruct edits to legacy records that were already baked into an opening snapshot, because Ravel does not retain the pre-edit value required to calculate that historical delta safely.
Verification status
Static review completed against the branch diff. Automated tests have not been executed in this environment: no GitHub Actions run is currently available for the branch, and the local execution environment cannot resolve GitHub to clone/install the repository. Keep this PR in draft until the normal lint/typecheck/unit/build/E2E gates are run.