Auto-generate Stellar contract reference from contract source

[truthixify]

Tier: L (1-2 weeks) Type: tooling

Context

docs/contracts/stellar.mdx is hand-maintained and drifts. The contract source has all the type info. Generate the reference section automatically from contract WASM or TypeScript bindings.

Scope

Build scripts/generate-stellar-reference.ts:

• Reads bindings from wraith-protocol/contracts/stellar/bindings/typescript/ (or queries deployed contracts via stellar contract inspect)
• For each contract emits MDX section: title + addresses, function table (name, params, types, return, auth-required), event signatures, storage keys
• Inserts between marker comments in docs/contracts/stellar.mdx, preserving hand-written prose around the markers
• CI fails when generated section is stale

Acceptance criteria

• Script runs locally against current testnet deployments
• Marker-based insertion preserves prose
• CI drift-check job in place
• Documented in docs/CONTRIBUTING.md (when changing a Stellar contract, run this)

Files to start with

• New: scripts/generate-stellar-reference.ts
• docs/contracts/stellar.mdx

[heymide]

@heymide has applied to work on this issue as part of the Stellar Wave Program's 6th wave.

This issue aligns well with my experience. I can work on it and submit a polished PR for review.

ℹ️ Repo Maintainers: To accept this application, review their application or assign @heymide to this issue.

[truthixify]

@heymide Assigned. Welcome to wave 6.

Quick expectations to make this smooth for both sides:

1. Branch from develop (not main). PRs target develop.
2. Open a draft PR within ~3 days of pickup so we can see direction early.
3. Update at least every 5 days. Silence is the only thing that costs you the assignment; if you get stuck or context changes, just say so on the PR.
4. Read the issue body's acceptance criteria carefully. Hitting those is the merge bar.

If anything is ambiguous, ask before building.

[drips-wave]

Congratulations, @heymide! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on June 30, 2026.

🧑‍💻 @heymide: 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 🌊