feat: add browser wasm package

[beeman]

What

Add the @open-wallet-standard/web package with WASM bindings, browser storage adapters, and TypeScript declarations.

Document the browser SDK, include it in package tables, and add CI coverage for cargo check, wasm-pack build, and JS store tests.

Gate xrpl-rust behind native targets and provide wasm-compatible XRPL address and signing helpers for the web build.

Why

Making OWS available in the browser lets web apps reuse the same audited wallet, policy, and signing semantics as other OWS runtimes. That can improve security over ad hoc browser implementations and avoid backend key custody, while still respecting the browser’s security limits.

Closes #

Testing

• cargo test --workspace passes
• cargo clippy --workspace -- -D warnings is clean
• npm test passes (if Node bindings changed)
• Tested manually with ows CLI

Notes

0. There may be a follow-up cleanup opportunity in ows/crates/ows-signer/src/chains/xrpl.rs. This PR keeps the XRPL changes minimal for browser support, but the native/wasm split could probably be made cleaner in a separate pass. Let me know if you want it in this PR.

1. Working on a simple web based demo to show how this works.

[vercel]

@beeman is attempting to deploy a commit to the MoonPay Team on Vercel.

A member of the Team first needs to authorize it.

[socket-security]

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	cargo/​wasm-bindgen@​0.2.118
	cargo/​uuid@​1.23.1

View full report

[njdawn]

hi! could you share web app + concrete use case?

[beeman]

Hi @njdawn - thanks for looking at this!

I'm considering to use this in samui-wallet.

It seems way better to use a proven structure and toolset to store the secrets vs an ad-hoc implementation.