Sequencing note
v2 — not required for the v1 launch. v1 serves the artifact through the existing adapter surface (slug sn74-registry, get_adapter); this issue graduates it to dedicated schema-first endpoints with tri-surface parity once the surface has settled.
Problem
Once ingested (sibling sub-issue), registry parameters need contract-first API surfaces consistent with the rest of the explorer.
Scope
- Endpoints: registry overview (all repos, current emission_share / maintainer_cut / scoring summary), per-repo detail (full current config), and per-repo parameter timeline (change events with dates + source commits)
- Schema-first per repo conventions: schemas/ updated,
npm run build, regenerated artifacts committed together
- Tri-surface parity: REST + GraphQL + MCP tool coverage per the established pattern
- Provenance fields (commit SHA, upstream path) included in every response
Acceptance
All three surfaces serve identical registry-economics data; every value carries provenance; contract-drift gate green.
Sequencing note
v2 — not required for the v1 launch. v1 serves the artifact through the existing adapter surface (slug
sn74-registry,get_adapter); this issue graduates it to dedicated schema-first endpoints with tri-surface parity once the surface has settled.Problem
Once ingested (sibling sub-issue), registry parameters need contract-first API surfaces consistent with the rest of the explorer.
Scope
npm run build, regenerated artifacts committed togetherAcceptance
All three surfaces serve identical registry-economics data; every value carries provenance; contract-drift gate green.