[2026 API] Generate a typed frontend client from the OpenAPI spec

[Nanle-code]

Objective

Remove hand-written fetch calls to the dashboard API and catch contract changes at compile time.

Target area

src/api, docs/api, scripts/generate-api-docs.mjs

Context

The frontend calls the dashboard API with hand-written fetch wrappers, so server changes break the UI at runtime instead of at build time.

Acceptance criteria

• A script generates a typed client from the OpenAPI spec into src/api/generated/.
• Existing API calls move to the generated client, including auth headers and idempotency keys.
• CI regenerates the client and fails if the committed output is stale.
• Errors map to the app's error taxonomy ([2026 Platform] Standardize error boundary messaging across all dashboard routes #822).
• Automated tests cover the primary flow, at least one boundary case, and at least one failure case.
• User-facing documentation or developer guidance is updated, including compatibility, security, or migration notes where applicable.

Pull request requirements

• All continuous integration checks must pass before a pull request may be merged.
• The branch must be free of merge conflicts with the target branch at the time of merge.
• Do not request merge with failing workflows, skipped required checks, or unresolved conflicts.

[drips-wave]

@Nanle-code This issue could not be added to the Stellar Wave Program because the per-repo points budget would be exceeded (25000 / 25000 points already used). The label has been automatically removed.

The budget resets at the end of each Wave. You can review the remaining budget for your repos on the Orgs & Repos page.

ℹ️ Learn more about points budgets