feat(release): produce fresh public harness evidence from independent trust - #141
Merged
Merged
Conversation
…dent trust Signed-off-by: rldyourmnd <danil@nddev.it.com>
Signed-off-by: rldyourmnd <danil@nddev.it.com>
This was referenced Sep 12, 2026
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.
Stable release evidence could not be produced from the private consumer without disclosing its identity, and the previous producer refreshed signer validity and report age itself. Move the generic producer into this public module and retain private configuration in the consumer.
Require the exact six successful native jobs for every active harness, bind their IDs, attempt, commit and completion timestamps, reject stale or future results, and bound expiration by both observed runtime age and the independently supplied signing key. Preserve signer roles, status and validity. Prepare the 0.9.2 source line and regenerate affected projections.
Validation: complete
scripts/validate_release.shpassed (actual child exit 0), including reproducibility/cross-platform checks, source freshness, public artifact boundary, Go race/assurance and 56 Python tests. A real public Codex evidence run satisfied the six-job contract. Failed 0.9.1 remains immutable; this PR does not publish a release.