chore(agent-policy): promote channel revision 22

[hv-agent-promoter]

Automated protected policy-channel transition.

• Action: promote
• Revision: 22
• Evidence SHA-256: 88718635887140bcef150b6008c02dca005eab90b74d918dedba734e44358342
• Signed bundle SHA-256: dfd30c5ee5eaa50359399c6279a52fbfd3d5ad936822b4f922035f3fdad4825d

Closes #98

Promotes the canary candidate to stable: org policy lock generation 17 → 20
(ghcr.io/happyvertical/agent-policy@sha256:591a3a6e…, source db310fe), with
the signed revision-22 canary evidence bundle committed alongside. Canary ring
(happyvertical/.github, happyvertical/smrt) collected green after smrt#2141
refreshed its managed kernel block to the generation-20 stamp; the earlier
revision-22 abort (#97) recorded the pre-refresh sequencing race and is
superseded by this transition.

{
  "schema": "hv-agent-run:v1",
  "runtime": "claude",
  "session": "73215460-b04f-41f6-a256-838ebf8e5d37",
  "issue": 98,
  "linked_issue": "https://github.com/happyvertical/.github/issues/98",
  "policy_revision": "1.0.0",
  "status": "review",
  "validation": "signed canary evidence bundle 88718635… over the exact default-head ring; lock diff verified 17→20 against published artifact digest; local check-pr replay clean"
}

[willgriffin]

Superseded. Generation 20 cannot be promoted at all: its own artifact carries the gap-pin binding that rejects the very transition installing it (happyvertical/have-config#360), and artifacts are immutable. The candidate-20 canary was aborted via #97, so this PR's revision-22 transition is also consumed. Generation 21 (happyvertical/have-config#361) republishes the same five-PR payload plus the fix and takes its place.