Repository navigation
Harden v0.1.1 under adversarial stress - #1
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.
What changed
Requires plain own-property session data, binds source hashes to the exact analyzed ledger, narrows package contents, and adds serialized rollback-safe report output.
All GitHub Actions are pinned to immutable release commits, and package, citation, changelog, and generated-artifact versions move coherently to 0.1.1.
Why
Independent adversarial review found edge cases that ordinary happy-path tests did not exercise: malformed trust-boundary data, extreme numeric or schema inputs, package-source incompleteness, and multi-file publication failures. This patch closes those gaps without inflating the public product claims.
Impact
Malformed or resource-expensive inputs now fail in controlled, documented ways. Report publication is safer for cooperating writers, release packages are self-contained, and existing deterministic offline demos remain stable. Some formerly permissive invalid inputs are intentionally rejected.
Validation
25/25 tests on Node 22 and 24; clean tarball install/import/CLI checks, zero npm vulnerabilities, prototype/source-binding/load, and writer-race audit passed.
The branch remains draft until GitHub CI confirms the exact remote diff.