2026-10-01 — Reconcile 13 stale registry contract_sha values to the live contract blob
rank: decision outranks: []
Section titled “rank: decision outranks: []”2026-10-01 — Reconcile 13 stale registry contract_sha values to the live contract blob
Section titled “2026-10-01 — Reconcile 13 stale registry contract_sha values to the live contract blob”Date: 2026-10-01 Status: closed Verb: petrova_act_registry_edit Slug: stratt-hq, choco-hq, devarno-cloud, traceo-mcp-server, grace-hq, rocky-hq, eva-hq, smo1-io, devaqua-blue, so1-console, sparki-tools, yao-agent, null0-toll MR-compliance: MR-7, MR-12, MR-14
Rationale
Section titled “Rationale”registry.yaml pins each consumer’s .petrova/contract.yaml by
contract_sha, the first 12 hex of its git-blob-sha1
(docs/decisions/2026-05-24-contract-sha-hash-method-fix-hermes.md). On
2026-10-01 a scan of every registry entry against the contract blob on its
default_branch found 13 entries where the two differ. Every one is a
legitimate change to the contract that the registry never followed; none is
an unexplained edit.
Method: for each entry, walk git log -- .petrova/contract.yaml on the
default branch and look for a commit whose blob matches the registry value.
Registry value found in the file’s own history (11)
Section titled “Registry value found in the file’s own history (11)”The contract changed after registration through ordinary PRs (cairnet re-vendors, schema conformance fixes, disposition updates).
| slug | repo | registry | live | blob matched at | changes since |
|---|---|---|---|---|---|
| stratt-hq | stratt-hq/stratt-run | c28049228261 | 4c40b537f2b7 | c52abf5 (2026-05-08, #61) | 10 commits, latest 861143a 2026-09-11 |
| choco-hq | choco-hq/choco-hq | 2bd09aa4e2c2 | 0ae4bd7e3b14 | 6a0ccd6 (2026-05-15) | cairnet v2–v4, #157 governance batch |
| devarno-cloud | devarno-cloud/devarno-cloud | 433b9aca8afc | fcec35c9cb87 | a5a99bd (2026-05-06) | cairnet onboard + v3/v4 (#48–#50) |
| traceo-mcp-server | traceo-cat/traceo-mcp-server | 0c3008e90309 | 99df3d222d0f | 73f7008 (2026-05-21, #187) | 14ccce4 schema-valid fix (#285, 2026-10-01) |
| grace-hq | grace-hq/grace | 02688056c7ff | b16870c0758e | fd851ea (2026-08-06, #34) | 6e83fe5 ares → not_applicable (#203) |
| rocky-hq | erid-tech/rocky | be2aa3cecbad | 8273e815e913 | 5c1fd8a (2026-05-13, #28) | b2a04c0, 74adf49 cairnet self-host (operator, May) |
| eva-hq | eva-hq/eva | 87482edb076c | 50a578036d5c | 46bd99a (2026-05-08) | cairnet #34–#36, e81e11d consumer side |
| smo1-io | smo1-io/smo1-io | f09488e48743 | e0c1fc84c90d | cd1a865 (2026-05-08) | cairnet #12–#14, #34 lock sync, #36 review dates |
| so1-console | so1-io/so1-console | 631e37c6ea63 | 64be227d68fb | d40f052 (2026-07-07, #323) | 4d6e615 schema fix (#342) |
| sparki-tools | sparki-tools/platform-docs | 0a537498696b | 918ce3d1a810 | d3431c4 (2026-08-12, onboard) | d387272 schema-valid fix (#9, 2026-10-01) |
| null0-toll | null0-toll/toll | 167f29b6e06c | 8f5c2f09bbc2 | e7b59e7 (2026-08-25, #96) | 173e391 derived dispositions (#109) |
Registry value is the wrong hash family (2)
Section titled “Registry value is the wrong hash family (2)”These values match no blob in history. Both are the sha256 of the file
(sha256(bytes)[:12], the petrova doctor family that
2026-10-01-one-contract-hash-family.md retires), not the git-blob-sha1.
| slug | repo | registry | sha256 of | live (git-blob) |
|---|---|---|---|---|
| devaqua-blue | devaqua-blue/devaqua.blue | a1e37eed14d6 | 8c64f08 (2026-07-14) | 581fe41c0c27 (7a95bd6, #73) |
| yao-agent | asgard-codes/yao-agent | ffdcf0c4caf2 | a69a563 (current, #242) | 6a33a40b49de |
The yao-agent value was set by
2026-09-26-registry-edit-yao-agent-contract-reconciliation.md, which
computed it “the same way cli/src/verbs/doctor.ts does”. That doc’s
content stands; only the hash family was wrong.
Change
Section titled “Change”Only the 13 contract_sha: lines in registry.yaml. No notes, no
applicability, no other field.
Not in scope
Section titled “Not in scope”Entries with no contract_sha (skyflow-hq, oompa-tools, chronicle-hq,
tektree and others still pending petrova_onboard, several with no
contract file yet). Filling those is onboarding (MR-14), not reconcile.
Verification
Section titled “Verification”After merge, re-run the scan: 0 entries where registry contract_sha and
the default-branch blob differ. The next state sweep should show no
contract drift for these 13 slugs.
Sign-off
Section titled “Sign-off”- Human: flight@arno.host
Countersigned by human:flight@arno.host on 2026-10-01 — sign-off line added
in commit 9d843ce0 (#503), authored by the human. Status flipped open→closed
on 2026-10-01 by an agent as scribe (MR-7).