Repository navigation
feat(released-truth): make release evidence the default - #110
Conversation
MaidSafe-Hermes
left a comment
There was a problem hiding this comment.
APPROVE — #110 at head facfb90bff4b70f5eadbbaaf21a6fdbef7fdaa1f. I found no material defect in the implementation, migration policy, or routine changes.
Coverage: 2/2 review seats across all 3 changed-file evidence scopes (sol-1 gpt-6.1-sol xhigh; glm-1 z-ai/glm-5.3; GLM scope 2 completed on one narrowed retry). The Sol receipts were marked UNCERTAIN while each scope was isolated and asked for the remaining scopes; after reviewing all scopes together, those scope-coverage limits are resolved. GLM returned APPROVE on all three scopes. I do not claim reviewer consensus.
Verified on the frozen head: 107 unit tests passed; scripts/validate_release_baselines.py passed; scripts/adr-governance.py passed; git diff --check passed. Current GitHub checks are all successful.
Summary
target-manifest.ymlthe default for new and refreshed public claimscurrent-merged-truthblocks as explicitmigration_backlogentries without moving-ref lookupVerification
python3 -B -m unittest discover -s scripts/tests -p "test_*.py"— 107 passedpython3 -I scripts/validate_release_baselines.py— passedpython3 -I scripts/adr-governance.py— passed with 1 ADR checkedgit diff --check— passedScope protection
No changes under
docs/**,.github/**,target-manifest.yml, either registry, orscripts/validate_release_baselines.py.Review status
The controlled clean-context launcher blocked before reviewing the project with
guard or CLI data invalid; details withheld. This is not recorded as a pass. Jim deferred the required clean-context review to Hermes/Claude on this pull request before any merge decision.