chore(agent-policy): promote channel revision 24 - #103
Merged
Conversation
This was referenced Jul 30, 2026
Open
Closed
Closed
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.
Automated protected policy-channel transition.
promote2489e5849232a1735e75e51490eba0c7db1b5270591ba72cf73b74c0ea70af47778e9844e9a5dcb4b7578f66cee3ad1f3fff5f45c9910c653516001ff6de98eed1Closes #102
Promotes the canary candidate to stable: org policy lock generation 17 → 21
(
ghcr.io/happyvertical/agent-policy@sha256:a19abb22…, sourcea61f995), withthe signed revision-24 canary evidence committed alongside. This carries the
consolidated payload of happyvertical/have-config #349, #352, #354, #339 and
#321 plus the gap-pin binding fix (#361) that made a promotion PR validatable
at all — generation 20 rejected its own promotion (#99, aborted via #97), and
this transition is the fix proving itself: the same shape now passes.
Canary ring (
happyvertical/.github,happyvertical/smrt) collected green;.githubvalidates on the sanctioned compatibility-grace block and smrt on thegeneration-21 kernel stamp it already carries.
{ "schema": "hv-agent-run:v1", "runtime": "claude", "session": "73215460-b04f-41f6-a256-838ebf8e5d37", "issue": 102, "linked_issue": "https://github.com/happyvertical/.github/issues/102", "policy_revision": "1.0.0", "status": "review", "validation": "signed canary evidence 89e58492 over the exact default-head ring; lock diff verified 17→21 against the published artifact digest; local check-pr replay clean" }