chore(registry): regenerate REGISTRY.a2ml after Wave-0 source edits

Wave-0 edits to files inside the a2ml and rhodium-standard-repositories
spec trees changed their content source_hash, so the generated registry
drifted (the recurring standards#381 failure). Regenerated deterministically
via scripts/build-registry.sh; TOPOLOGY.md unchanged. A pre-commit regen
hook + CI remediation hint lands in Wave 1 to stop this recurring.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_0114ps6mY5jAH4SzbGxeuYjc

Author: claude

.machine_readable/REGISTRY.a2ml

@@ -36,7 +36,7 @@ name = "A2ML — Attested Markup Language"
 stream = "foundation"
 home = "a2ml/"
 canonical_doc = "a2ml/README.adoc"
-source_hash = "sha256:5f070c778ad112229878e2d551b564e2ec885d2239c6f348c0a96b700091d84a"
+source_hash = "sha256:27768075cf2287320778f35f0e11666ff32e69d28cc2ae6cd5f21051f9dc4630"
 route = "the typed/verified machine-readable document format"
 
 [[spec]]
@@ -216,7 +216,7 @@ name = "RSR — Rhodium Standard Repositories"
 stream = "governance"
 home = "rhodium-standard-repositories/"
 canonical_doc = "rhodium-standard-repositories/README.adoc"
-source_hash = "sha256:01e6373ae01939b5ed24c72e1c4ace7ea55559b3fc765a956bc2e7ad722b244b"
+source_hash = "sha256:3e721ecb348d176a2e1ba82bb6ea6b9365e8375c4ca80f1f3f4c9e9e343269f8"
 route = "the repository-compliance standard every repo is graded against"
 
 [[spec]]