2026-05-10 — Resync registry contract_sha pointers (6 repos)
Date: 2026-05-10 Status: closed Supersedes: none Superseded-by: none — current
Context
Section titled “Context”Phase 6a’s first sweep (petrova sweep-state) surfaced contract_sha drift between registry.yaml and the actual .petrova/contract.yaml blob on the default branch of six consumer repos:
| slug | registered | actual (git blob sha-1, 12-char) |
|---|---|---|
| petrova-codes | b42fd97de120 | eeee930702c1 |
| kahn-hq | 25428e8836a7 | ce740d92ae1e |
| choco-hq | cc468f150e4d | c9768b7f5ca5 |
| devarno-cloud | 2fab2dcfe1a5 | 433b9aca8afc |
| grace-hq | ad5ba1e2a74f | 17df2b8fdfe9 |
| eva-hq | 9487260efd59 | 87482edb076c |
These represent accumulated edits to the consumer-side contract files since each repo was last bumped in registry.yaml. Spot-checking each contract’s integrations.<name>.status against the matching integrations_applicability row in registry.yaml shows no applicability semantics changed — applicability (registry’s “what governance expects”) and status (consumer’s “what is wired”) remained internally consistent. The drift is therefore housekeeping, not a contract-shape change.
Decision
Section titled “Decision”Bump contract_sha for the six listed repos in registry.yaml to the actual git blob SHA observed by the sweeper. No integrations_applicability row changes; no role/profile changes. update: field bumped to 2026-05-10 with a one-line note.
Alternatives considered
Section titled “Alternatives considered”- Open six per-repo decision docs. The previous bump pattern (
94c2496for stratt-hq) used a single per-repo doc. That made sense when bumps coincided with semantic ADRs upstream. These six are a batch resync from a tooling rollout (Phase 6a sweep), not driven by upstream decisions, so a single doc is the lower-friction match. - Bump only the drifts that block other work. Rejected: leaving drifted SHAs in the registry permanently lights up the dashboard
≠ contract driftchip and trains operators to ignore the signal. Reset to clean now.
Consequences
Section titled “Consequences”For code:
- 6 lines edited in
registry.yaml. petrova sweep-statenext run produces no drift on these slugs (state files updated automatically;contract_drift: false).
For docs:
- This doc.
For in-flight phases:
- None — phase machinery on these repos is untouched.
For invariants:
- No MR-N changes.
References
Section titled “References”- Plan:
docs/superpowers/plans/2026-05-10-state-freshness.md(Phase 6a) - Prior bump (single-repo precedent):
94c2496(stratt-hq, 2026-05-08) - Sweep verb:
cli/src/verbs/sweep_state.ts
Sign-off
Section titled “Sign-off”- Subagent: Claude Code (
chore/reconcile-contract-drift-2026-05-10branch) - Human: alex@devarno.com — 2026-05-10