chore(expo-example): update expo example to consume latest SDK version

[tolgahan-arikan]

Summary

Updates the standalone Expo example to consume @0xsequence/oms-react-native-sdk@0.1.0-alpha.2 from npm. Keeps the README dependency snippet aligned with the example manifest.

Changes

• Bump @0xsequence/oms-react-native-sdk from 0.1.0-alpha.1 to 0.1.0-alpha.2 in examples/expo-example/package.json.
• Refresh examples/expo-example/package-lock.json for the alpha.2 tarball and package metadata.
• Update the Expo example README snippet to alpha.2.

Testing

• git diff --check
• cd examples/expo-example && npm run typecheck

Notes

This PR is independent from the Swift SDK CocoaPods README metadata PR.

[github-actions]

Claude finished @tolgahan-arikan's task —— View job

---

Pull Request Review ✅

Review Checklist

• Read changed files and understand the scope
• Check TypeScript API surface changes
• Verify API.md update requirements
• Check native layer consistency
• Validate conventional commits format
• Look for bugs and edge cases
• Provide final review feedback

Review Results

✅ APPROVED - This is a clean and correct version bump with no issues found.

Analysis

1. Scope: Updates the standalone Expo example from @0xsequence/oms-react-native-sdk@0.1.0-alpha.1 to 0.1.0-alpha.2

2. TypeScript API Surface: ✅ No changes to src/index.tsx - this is purely a consumer update

3. API.md Updates: ✅ Not required - no exports changed in the library itself

4. Native Layer Consistency: ✅ Not applicable - this only updates the example app's npm dependency

5. Conventional Commits: ✅ Perfect format: chore(expo-example): update SDK alpha

6. Consistency Check: ✅ All three locations properly updated:

   • examples/expo-example/package.json:15 - dependency version
   • examples/expo-example/package-lock.json - lockfile metadata + integrity hash
   • examples/expo-example/README.md:11 - documentation snippet

7. Version Alignment: ✅ This correctly follows the recent 0.1.0-alpha.2 release (commit 571ae0d)

Additional Notes

• The package-lock.json shows the updated integrity hash and resolves from the correct npm registry
• Lockfile also shows the workspace configuration update (!examples/expo-example) which is expected
• The PR description correctly mentions this is independent from other SDK metadata PRs
• Author performed appropriate testing (typecheck + git diff --check)

No issues found. Ready to merge.

---