Repository navigation
feat: Node/JUnit acceptance and source-bound product readiness - #12
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
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.
Node.js projects and runners producing JUnit can now use the same fixed, per-test acceptance workflow as Python: reproduce a real assertion failure, verify the repair, reject regressions or changed acceptance tests, and export independently inspectable evidence.
This adds native
node:testand strict generic JUnit adapters, timeout/recovery and evidence identity checks, and pinned ms / boltons JUnit reference and negative controls. Explicit live-model trial plans, independent-user walkthrough materials, and a source-bound release-readiness check prepare the remaining product acceptance. The last CI job records the exact source commit/tree and all 14 prerequisite job outcomes.Node 22 declaration-ordered events and Node 24 native IDs preserve nested/concurrent case identity. Reporter module URLs support Windows and encoded paths. Git baselines use stable LF settings so global CRLF preferences cannot alter acceptance source bytes.
Validation:
External product acceptance remains pending: no paid/live model trial, three independent real-user walkthroughs, or maintainer license choice is claimed. Synthetic fixtures test record validation only. Provider spending caps and human independence are operator declarations; the harness does not claim billing enforcement or identity authentication. See the acceptance guide and support/upgrade boundaries.
Tested tree:
27ebb6ab97a4f86643006fcbc96562b28126a5c7. Previous mainbf77f7f0d0f80e7d9013fd64ad84c6c09366797dremains in the ancestry.Merged main:
7cc95ee6a5b1b9d12a0cc455bdfb6cc25d48def5; its tree matches the tested tree above. This is v0.11 beta code; no stable release, paid/live model acceptance or real-user sign-off has been published.