Repository navigation
fix(failure-memory): drop the akms release from fingerprints; re-freeze the pack - #42
Merged
Merged
Conversation
…ze the pack The published consumer-contract pack failed its own verify_pack.py: its lessons.json, the six generated lesson nodes and both recording files had been edited for publication, and verify_pack.py reformatted, without re-freezing their digests. Nothing caught it because test_consumer_contract skipped the whole suite unless akms.__version__ was 0.6.1, and it could not simply be re-frozen: toolchain_sha256 hashed the installed akms release, so the pinned fingerprints moved on every lockstep release. - provider: the installed akms release version is no longer a toolchain_sha256 input. akms_schema_version and PROVIDER_VERSION still capture contract changes, and the version a project pins in its own [toolchain] table still counts through config_sha256. - test_consumer_contract: the version gate is gone, so all 28 conformance tests run on every release; EXPECTED_PACK_SHA256 is the new digest. - tests/refreeze_consumer_pack.py: maintainer script that recompiles generated/, recomputes every pinned value the way the suite checks it, and rewrites the manifest checksums. Deterministic: a second run changes nothing. - Pack re-frozen (pack revision amendment-2, digest bd1c2dc3...). Only digests and the generated source-hash header lines moved; behaviours, requests and lessons are unchanged. The manifest's pack_root and documented commands now use the public layout. Consumers that pin the pack must update to the new digest. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
SOSOVSKI
force-pushed
the
fix/consumer-pack-refreeze
branch
from
November 1, 2026 18:35
3b87411 to
4dfa68e
Compare
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.
The published consumer-contract pack failed its own verify_pack.py: its lessons.json, the six generated lesson nodes and both recording files had been edited for publication, and verify_pack.py reformatted, without re-freezing their digests. Nothing caught it because test_consumer_contract skipped the whole suite unless akms.version was 0.6.1, and it could not simply be re-frozen: toolchain_sha256 hashed the installed akms release, so the pinned fingerprints moved on every lockstep release.
Consumers that pin the pack must update to the new digest.