From 35948b09e90f8276250ad1a3df595c3f766eae7b Mon Sep 17 00:00:00 2001
From: hyperpolymath <6759885+hyperpolymath@users.noreply.github.com>
Date: Mon, 5 Oct 2026 04:54:34 +0000
Subject: [PATCH] chore(registry): regenerate the K9 home hash after the
 contract was formatted
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

`source_hash` covers every tracked file in a home, so `nickel format` on
`1-formats/k9/spec/contract/k9_contract.ncl` moved the `1-formats/k9/` hash
again — one commit after the earlier regeneration. Registry Verify caught it on
main (`aa1c4dd`), which is the check doing its job.

`bash scripts/build-registry.sh --check` passes again; the only changed line is
the `1-formats/k9/` source_hash. Scorecards and the compliance dashboard were
already in sync.

Follow-up to #1149 (M1 · #A, M7 · #F).

Co-authored-by: arena-agent <297053741+arena-agent@users.noreply.github.com>
---
 .machine_readable/REGISTRY.a2ml | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/.machine_readable/REGISTRY.a2ml b/.machine_readable/REGISTRY.a2ml
index 552cabc9b..376bea97b 100644
--- a/.machine_readable/REGISTRY.a2ml
+++ b/.machine_readable/REGISTRY.a2ml
@@ -45,7 +45,7 @@ name = "K9 Self-Validating Components"
 stream = "foundation"
 home = "1-formats/k9/"
 canonical_doc = "1-formats/k9/README.adoc"
-source_hash = "sha256:e35752dba0b50684e97c37a4634f6fe08e175ef80b2f44f754b5726cb6c2d157"
+source_hash = "sha256:6115d0242f7ab14372d48ecd97452d7737ddc878dec8a00ffe24bc1d9da7dd03"
 route = "the K9 specification, security analysis and adoption guidance (implementations live in hyperpolymath/k9-ecosystem)"
 
 [[spec]]