Release TestForge2.0.0 with explicit assessor compatibility boundary - #21
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.
TestForge2.0.0 assigns the accepted maintained behavior its own release identity. The original1.1.7 customer ZIP exposed the assessor JSON field
plan_sha256; current source omits it, so the major version documents possible external caller breakage and tells callers to stop requiring the field. Capacity arithmetic, spend safeguards, and trusted dispatcher authority remain unchanged.The original1.1.7 release assets and sidecars are restored from verified backups, with its tag preserved. New2.0.0 customer, plugin, and separately packaged skill distributions and delivery sidecars are sealed from reviewed source. The operator's mandatory metered guidance remains reachable through its conditional reference.
Validation: independent version/migration review passed; all existing native workflow commands passed locally (102tests, package/eval/manifest checks, line-ending policy). This PR runs one genuine public4-job native check set. No private hosted Actions or synthetic status publication is used. Merge commit includes
[skip ci]to avoid duplicate push checks; the existing single-job Pages deployment follows release publication separately.