2 Commits

Include renames

Author	SHA1	Message	Date
samiandClaude Opus 5.5	20d465185d	Sign in with Google, Apple…: item field, bridge save and identities ... Items record sign_in_with {provider, account}; the browser bridge reports it with the site's identities and saves it after the usual app prompt. Items now keep fields they don't know, so editing in an older app never drops what a newer one added. Co-Authored-By: Claude Opus 5.5 <[email protected]>	2026-10-24 15:19:14 +07:00
samiandClaude Opus 5.5	b5ced32be3	Add kv-wasm: the core compiled to WebAssembly for the web vault ... New crate crates/kv-wasm runs the same crypto, item model and sync engine in the browser: - WebStore: in-memory replica of kv-store's Store, each changed entry written to IndexedDB (ciphertext only) before the JS call resolves. - Device key: non-extractable WebCrypto ECDSA P-256 key in IndexedDB (raw r||s signatures). - WebCore mirrors kv-ffi's VaultCore; wasm-bindgen surface in camelCase with TypeScript types, plus a Web Worker wrapper (connectVault) so Argon2id never blocks the page. - Tests: Chrome (IndexedDB, WebCrypto, RFC 9421 verify), shared envelope fixtures both ways with kv-ffi, native sync with kv-ffi via the test server, Node smoke of the built package. Small changes to shared crates so they build for wasm32: - kv-store: SqliteStore moved to a native-only module. - kv-sync: rustls/pinning/tokio native only (fetch on wasm); DeviceSigner::sign_async (default wraps sign) used by ApiClient; unix_now() instead of SystemTime/now_utc. - kv-model: Public Suffix List behind a default `psl` feature (kv-ffi keeps it; the web build drops ~0.9 MB of code and matches same-host only). - wasm-release profile (opt-level z, Argon2 at 3) and a wasm CI job. Co-Authored-By: Claude Opus 5.5 <[email protected]>	2026-10-17 23:58:07 +09:00