Repository navigation
feat: reconcile artifact integers per record key - #15
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
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.
Artifact contracts can now compare each exact record key's accumulated integer value across two distinct CSV files. Split deliveries pass; balanced totals with incorrect per-record allocation fail, and overflow or exhausted bounded indexes preserve unknown results without exposing keys or amounts.
Existing physical, scalar, reference, target-coverage and summary checks remain authoritative. Invalid same-file declarations fail before artifact reads. CLI/report versions now share installed package metadata. Source 0.1.5 includes reproducible synthetic fixtures and a complete expansion roadmap; published GitHub0.1.4/npm0.1.0 stay unchanged.
Validation: 575 tests passed / 1 opt-in Docker test skipped, plus types, lint and build. A fresh local tarball (335 entries) passed the shipped CLI/fixture and same-file rejection checks with existing locked dependencies. Independent read-only review confirmed the correction and found no blocking issue. Physical reports retain
execution: not-runandprovenance: not-authenticated.No external provider, account, payment, tag or registry publication is included. Merge only through the existing required regression/verify checks; ordinary revert restores the source change.