5 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	c84015f67b	Multi-user: email sign-in, invite/open registration, admin calls ... - kv-proto: email on setup, AccountInfo.email/is_admin, ServerInfo.registration, admin DTOs. - kv-sync: prelogin by email or account id (setup QR / Emergency Kit), register with email, set_email, /v1/admin/* client calls. - kv-ffi: register_account(code, email), login(.., email), account_details, set_account_email, admin_create_invite. kv-wasm: the same plus the full admin API for the web vault. - Live test: two users on one server stay isolated; a new device signs in by email. Co-Authored-By: Claude Opus 5.5 <[email protected]>	2026-10-24 07:35:23 +07:00
samiandClaude Opus 5.5	2e2c8cd26f	kv-wasm: onboarding (setup codes, enrollment tickets, scan-to-join) for the web vault ... Mirrors kv-ffi's docs/10 §5 API in WebCore and binds it under the names the web app codes against: setupPayloadForKit, addDevicePayload, revokeEnrollmentTicket, loginWithSetup, joinStart/joinPoll/joinCancel, joinApprove, joinSend, and the free function parseSetupPayload (also callable through the worker client). Unlike kv-ffi, the Secret Key is not persisted: every unlock on the web takes it, so it is kept zeroized in the unlocked state and dropped on lock. loginWithSetup refuses a code for a different server than the configured origin (the browser only talks to its own origin). Tests: ticket enrollment and scan-to-join in both roles against kv-ffi via the kv-sync test server, a swapped-approver rejection, a Chrome test (IndexedDB never holds the Secret Key, JS shapes, error codes) and a Node smoke check of the built package. Co-Authored-By: Claude Opus 5.5 <[email protected]>	2026-10-18 06:58:13 +09:00
samiandClaude Opus 5.5	f9f2d14aa2	kv-wasm: ItemSummary carries tags and modifiedAt for the web vault's filters and sort ... Co-Authored-By: Claude Opus 5.5 <[email protected]>	2026-10-17 23:59:58 +09: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