Repository navigation
feat(artifacts): add offline acceptance reports with record locators - #17
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.
Saved deliveries can now produce an offline acceptance page with
artifacts --format html. It displays declared checks, failed or incomplete reconciliation, Receipt/file binding, affected CSV data-record positions and practical review actions without disclosing record identities or amounts. Existing text and JSON behavior remains compatible.Actual retained synthetic deliveries demonstrate the business distinction: a correct allocation passes, while a shifted allocation reports two value mismatches even though the files are physically intact. CSV positions count logical data records, including quoted multiline records, and remain bounded when repeated identities or large inputs are encountered.
Validation: 603 tests passed; one optional local Docker test was skipped. Type checks, lint, build, packaged CLI checks, documentation checks and actual desktop/mobile Chrome report checks passed. Sixteen focused cases cover the HTML and record evidence. Independent static review found no blocking issue.
The report is escaped, redacted, bounded and standalone, with no scripts or external resources. Positions are collected only for HTML; invalid or incomplete checks cannot retain partial evidence. This is source 0.1.7 with no new tag, npm publication or live provider use.