#484 Preserve package-script obligations through verifier formation - #486
Merged
Merged
Conversation
Kewton
marked this pull request as ready for review
September 14, 2026 05:15
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.
Tracks #484
Form root
package.jsonscript observations into strict comparisons using fixed literals captured from the original model/host obligations. The comparison preserves successful stdout and runtime failures, records source and replacement hashes, and remains a structural check without business-Test or implementation-artifact credit. Ambiguous sources, changed expectations, wrappers, and unsupported syntax remain refused.The saved model and host instructions together exceed the existing instruction limit. Preserve both verbatim through a narrowly validated, ordered pair of package writers followed by the complete original check group; retain the source, ownership, and ordering checks. Keep the existing limits and guardrail baselines, with the setup-command predicate moved into a leaf module.
Validation: 13 focused tests using saved runner proposals and real Node, #478/#479/#480 regressions, corpus and generality guardrails, formatting, all-target Clippy, and the complete Cargo suite including integration/doc-tests. Detailed evidence and the earlier failures resolved during development are recorded in
dev-reports/issue-484/verification.md. Exact-head CI/UAT and post-merge release verification are tracked by the orchestrator before starting #485 and #452.