TypeDoc `@category` sweep + reference landing page

[truthixify]

Tier: S (1-2 days) | Type: docs

Context. Wave 6 shipped the auto-generated TypeDoc site (PR #110) but the landing page dumps every export in one alphabetical wall. typedoc.json is 8 lines with no categoryOrder or custom template, and no source file carries @category today (verified via grep). Api-extractor uses @internal on non-public symbols but does not enforce @public on the rest (ae-missing-release-tag is set to none). We can group exports by concern (keys, addresses, scanning, transactions, errors) so a first-time reader can find deriveStealthKeys without ctrl-F.

Scope.

• Add @category tags to every public export across src/index.ts and each chain entry.
• Add @example blocks to the top 15 most-used exports (identified from README + guides).
• Configure typedoc.json with a categoryOrder and a custom index template.
• Regenerate and eyeball the output for each chain page.

Acceptance.

• pnpm docs output groups exports under Keys / Addresses / Scanning / Transactions / Errors / Advanced
• Every @public symbol has a category
• At least 15 exports carry a runnable @example
• CI check ensures a new @public export without a @category fails the build

Files. src/index.ts, src/chains/*/index.ts, typedoc.json, .github/workflows/ci.yml.

[lamborghini21]

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

Hello boss, I'd love to work on this issue and I promise to deliver results in 24 hours.

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

[helenahelenavanbeek-png]

@helenahelenavanbeek-png has applied to work on this issue as part of the Stellar Wave Program's 8th wave.

I’m a full-stack software developer experienced in both enterprise applications and Web3 projects, with four hackathon wins and hands-on work across frontend, backend, APIs, databases, and blockchain integrations. I will first review the issue and existing codebase, then implement a clean, well-tested solution and submit a clear PR within the agreed timeline. Kindly assign.

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

[annacodervibe]

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

I would love to work on this issue, already reviewed the description and have experience with it , please assign me

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

[chinecherem58]

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

Hi maintainer I will like to work on this issue please

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

[Good-terminal]

@Good-terminal has applied to work on this issue as part of the Stellar Wave Program's 8th wave.

Hi maintainer I will like to work on this issue please

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

[boalambo]

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

Hello maintainer, I would like to work on this issue

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

[elijahbok14-sudo]

@elijahbok14-sudo has applied to work on this issue as part of the Stellar Wave Program's 8th wave.

Hi maintainer can i work on this issue

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

[ComputerOracle]

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

ASSIGN ME TO THIS ISSUE OR PERISH

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