feat: migrate SDK API endpoints to boltapp.com domain

[alanthai]

Description

Corrective release PR to actually publish the boltapp.com domain migration as 0.10.0.

Background: PR #108 migrated the domain and manually bumped package.json to 0.10.0, but it merged as a chore: squash commit. Releases here are driven by @release-it/conventional-changelog (bumpStrict: true), where chore is hidden and triggers no version bump — so the release workflow logged "No new version to release" and skipped npm publish. The manual bump also broke the workflow's publish gate (VERSION_BEFORE != VERSION_AFTER), since package.json already read 0.10.0.

This PR:

• Reverts package.json 0.10.0 → 0.9.11, letting release-it own the version bump.
• Merges with a feat: subject so release-it computes a minor bump 0.9.11 → 0.10.0 on merge, changing package.json and thus satisfying the publish gate.

Plain feat: (no ! / BREAKING CHANGE) is intentional — a breaking marker pre-1.0 risks a 1.0.0 bump; we want exactly 0.10.0.

No source/domain changes here — those already landed in #108.

Testing

• yarn test / yarn typecheck / yarn lint unaffected (only package.json version changes). Release behavior is verified by the Release & Publish workflow on merge: it should log Version bumped: 0.9.11 → 0.10.0, then build and publish @boltpay/react-native@0.10.0.

Security Review

• I have considered and reviewed security implications of this PR and included the summary below.

Security Impact Summary

Version/release-metadata change only; no logic or data-handling changes. Publish still occurs via npm Trusted Publishing (OIDC) with provenance.

Link to Devin session: https://app.devin.ai/sessions/57bf0ac839ea4ade9dcea0391d96df2c
Requested by: @alanthai

[devin-ai-integration]

🤖 Devin AI Engineer

I'll be helping with this pull request! Here's what you should know:

✅ I will automatically:

• Address comments on this PR. Add '(aside)' to your comment to have me ignore it.
• Look at CI failures and help fix them

Note: I can only respond to comments from users who have write access to this repository.

⚙️ Control Options:

• Disable automatic comment, CI, and merge conflict monitoring

[snyk-io]

✅ Snyk checks have passed. No issues have been found so far.

Status	Scan Engine	Critical	High	Medium	Low	Total (0)
✅	Open Source Security	0	0	0	0	0 issues
✅	Licenses	0	0	0	0	0 issues
✅	Code Security	0	0	0	0	0 issues

💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse.

[davidminin]

LGTM — correct release-it re-arm: 0.9.11 in tree so a feat: merge can bump to 0.10.0 and satisfy the publish gate.

Merge note: keep the squash/merge subject as feat:…. A chore: squash will reproduce the #108 skip.

[devin-ai-integration]

keep the squash/merge subject as feat:…

Agreed, thanks @davidminin — the feat: subject is load-bearing; a chore: squash would reproduce the #108 skip. Left it without !/BREAKING CHANGE on purpose so release-it lands exactly on 0.10.0 and not 1.0.0. Will confirm the release run logs 0.9.11 → 0.10.0 and publishes once merged.