fix: sync generation-21 agent policy kernel - #118
Merged
Conversation
willgriffin
enabled auto-merge
July 30, 2026 10:36
auto-merge was automatically disabled
July 30, 2026 10:38
Pull request was closed
Regenerate the managed hv-managed-policy block from the generation-21 kernel. The org lock moved to generation 21 while this block was still stamped at generation 17, so lifecycle failed on every event with a stale managed policy block and blocked merge-queue admission repo-wide. Block bytes reproduce hv-agent managed_block() exactly: same kernel file, same sha256-of-file stamp, 15 bullets, nothing outside the markers changed. Refs #117
willgriffin
force-pushed
the
claude/117-gen21-policy-sync
branch
from
July 30, 2026 10:38
2157b1a to
79d441a
Compare
willgriffin
changed the title
Contributor
Release PreviewWhen this PR is squash-merged, @happyvertical/pdf will receive a patch version bump based on the PR title's conventional commit format. What happens on merge?
No manual intervention needed. |
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.
Summary
Regenerates the managed
hv-managed-policyblock inAGENTS.mdfrom the generation-21 policy kernel.The org policy lock moved to generation 21 (
happyvertical/have-config@a61f995) while this repository's block was still stamped at the generation-17 kernel (9a4cf725…). With 21 promoted to stable,lifecyclevalidates this repository against the generation-21 kernel and fails withstale or edited managed policy blockon every event — which poisons head-commit status rollups and makes the managed merge queue refuse admission repo-wide.hv-agent'smanaged_block()exactly: same kernel file, same sha256-of-file stamp (2524e6ee…), 15 bullets.hv-managed-policymarkers is touched.This repository is one of five with
lifecycle_ruleset: required.smrtalready synced (happyvertical/smrt#2141) andhappyvertical/.githubvalidates on the sanctioned compatibility-grace block; The other required repositories receive the same fix.Validation
Block regenerated by the same algorithm the policy runtime validates against, then verified byte-for-byte against
hv-agent'smanaged_block()output for the generation-21 kernel. Thelifecyclecheck on this PR is the authoritative confirmation.Closes #117
{ "schema": "hv-agent-run:v1", "runtime": "claude", "session": "73215460-b04f-41f6-a256-838ebf8e5d37", "issue": 117, "linked_issue": "https://github.com/happyvertical/pdf/issues/117", "policy_revision": "1.0.0", "status": "review", "validation": "managed block reproduced byte-for-byte from the generation-21 kernel via managed_block(); lifecycle check on this head is the authoritative validation" }