Release @fundable/sdk 0.1.0

[Utilitycoder]

Summary

• promote @fundable/sdk from 0.1.0-alpha.3 to the first stable 0.1.0 release
• link package, repository, README, and documentation to the public GitBook site
• add stable release notes and compatibility guidance
• record GitBook sync and desktop publication acceptance
• include CHANGELOG.md in clean-package verification

Public documentation

https://fundable-finance.gitbook.io/fundable-finance-docs/

Verification

• pnpm package:verify
• pnpm test:testnet (3 tests passed)
• clean npm consumer compiled and loaded the packed 0.1.0 package

Post-merge release sequence

1. create and push annotated tag v0.1.0 on the reviewed merge commit
2. verify the trusted-publishing workflow publishes npm latest
3. create the matching GitHub release
4. install and compile the registry package from a fresh project
5. migrate stellar_client from the alpha package to 0.1.0

Remaining acceptance note

Mobile rendering remains unchecked because the connected browser did not honor its mobile viewport override; it must be verified separately before closing the final delivery checklist.

[coderabbitai]

Warning

Review limit reached

@Utilitycoder, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 29 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: 971ff570-95b2-4762-b39b-c533c1086c51

📥 Commits

Reviewing files that changed from the base of the PR and between b41ae96 and 8f254b9.

📒 Files selected for processing (8)

• CHANGELOG.md
• README.md
• docs/README.md
• docs/delivery-checklist.md
• docs/troubleshooting-and-versioning.md
• package.json
• scripts/verify-packed-package.mjs
• src/index.ts

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch release/sdk-0.1.0

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}