Repository navigation
PREWAVE-BE-009 — Publish Generated OpenAPI Clients and Fixture Artifacts #604
Description
Problem context
The post-Wave-9 audit requires a reproducible Optimism Sepolia path. The current open backlog does not isolate this boundary as an independently reviewable contributor task.
Technical scope
- Generate a versioned TypeScript client and deterministic fixtures from the reviewed OpenAPI contract.
- Bind artifacts to API commit, schema checksum, release compatibility, and generation command.
- Publish breaking-change detection and changelog evidence.
- Prevent hand-maintained frontend DTO drift.
Security and architecture constraints
- Contracts and finalized canonical events remain authoritative for protocol state.
- Missing, stale, ambiguous, or wrong-release data must fail closed.
- Never log secrets, authorization material, protected rationale, or non-public evidence.
- Bind all chain-derived data to chain ID, release ID, deployment block, and artifact checksum.
Required tests
- Reproducible-generation and clean-tree tests.
- Breaking/non-breaking schema classification tests.
- Consumer smoke test against the frontend adapter boundary.
Acceptance criteria
- Two clean generations are byte-identical.
- Breaking changes fail CI without an explicit version change.
- Generated artifacts contain no secrets or environment endpoints.
- Frontend can pin one immutable artifact version.
Dependencies
- STAB-BE-005 — Restore the Post-Wave-9 Install and CI Baseline #584
- PREWAVE-BE-005 (PREWAVE-BE-005 — Publish Versioned Claim List and Claim Detail Read Models #600)
- PREWAVE-BE-006 (PREWAVE-BE-006 — Publish Verifier Eligibility and Commit-Reveal Projections #601)
- PREWAVE-BE-007 (PREWAVE-BE-007 — Publish Dispute, Appeal, and Settlement Read Models #602)
- Frontend implementation matrix
Non-goals
- Deploying to mainnet.
- Inventing contract interfaces or frontend behavior.
- Applying
Stellar Waveor assigning a contributor.
Complexity and points
- High — 200 points
Candidate only; activation remains maintainer-controlled.
Activity
Alisadev-dev commentedon Oct 15, 2026
@Alisadev-dev has applied to work on this issue as part of the Stellar Wave Program's 10th wave.
ℹ️ Repo Maintainers: To accept this application, review their application or assign @Alisadev-dev to this issue.
drips-wave commentedon Oct 16, 2026
Congratulations, @habeebullahabubakar61-debug! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on October 22, 2026.
🧑💻 @habeebullahabubakar61-debug: Please resolve the issue such that the repo's maintainers have enough time to review your contribution before the due date. You'll earn Points for completing the issue on-time, which will make you eligible for a share of the Stellar Wave Program's reward pool.
Warning
When opening a PR, please link it to this issue to ensure it gets tracked accurately. Points are awarded when this issue is marked as completed by the maintainer.
🤠 Repo maintainers: Please keep an eye on the contributor's progress and review their work before the due date. You can manage this issue, including adjusting its complexity and points, here.
🌊 Happy Wave 🌊
femiolutayo commentedon Oct 20, 2026
@femiolutayo has applied to work on this issue as part of the Stellar Wave Program's 10th wave.
ℹ️ Repo Maintainers: To accept this application, review their application or assign @femiolutayo to this issue.
Stanley-Owoh commentedon Oct 21, 2026
@Stanley-Owoh has applied to work on this issue as part of the Stellar Wave Program's 10th wave.
ℹ️ Repo Maintainers: To accept this application, review their application or assign @Stanley-Owoh to this issue.