Customer-held Signal state: fenced sealed store and Signal operations

.github/workflows/wasm.yml

@@ -86,6 +86,46 @@ jobs:
       # r2d2's pool and tokio's `spawn_blocking` both panic on a page, and both
       # compile there, so nothing but this check keeps them from creeping back into
       # the store once the shim exists.
+      # The fenced, sealed record store backs a browser-held Signal store, so
+      # it must keep building for the page as well as the server.
+      - name: Build wacore-recordstore for wasm32 (release)
+        env:
+          RUSTFLAGS: '--cfg getrandom_backend="wasm_js"'
+        run: >
+          cargo build -p wacore-recordstore --lib --release
+          --target wasm32-unknown-unknown
+          --features wacore/js
+      - name: Build wacore-signal-ops for wasm32 (release)
+        env:
+          RUSTFLAGS: '--cfg getrandom_backend="wasm_js"'
+        run: >
+          cargo build -p wacore-signal-ops --lib --release
+          --target wasm32-unknown-unknown
+          --features wacore/js
+      # The JS bindings are only proven by running them: build, generate the
+      # Node glue with the wasm-bindgen CLI matching Cargo.lock, and drive two
+      # devices end to end from JavaScript.
+      - name: Install wasm-bindgen CLI
+        uses: taiki-e/install-action@v2
+        with:
+          tool: wasm-bindgen@0.2.128
+      - name: Use Node 24 for JavaScript binding tests
+        uses: actions/setup-node@949feb2413d6458794dcd2491c4babbbce0c15c1 # v7
+        with:
+          node-version: "24"
+          package-manager-cache: false
+      - name: Test wacore-signal-wasm bindings from Node
+        # Build the native fixture without the WASM-only randomness override.
+        env:
+          RUSTFLAGS: '--cfg getrandom_backend="wasm_js"'
+          SIGNAL_WASM_FIXTURE: ${{ github.workspace }}/target/debug/examples/fixture
+        run: |
+          RUSTFLAGS='' cargo build --locked -p wacore-signal-wasm --example fixture
+          cargo build -p wacore-signal-wasm --lib --release --target wasm32-unknown-unknown
+          wasm-bindgen --target nodejs --out-dir target/signal-wasm-node \
+            target/wasm32-unknown-unknown/release/wacore_signal_wasm.wasm
+          node --test wacore/signal-wasm/tests/node.test.mjs
+          npm exec --yes --package=typescript@6.0.3 -- tsc --noEmit --target es2022 --module esnext --moduleResolution bundler --lib esnext,dom --strict wacore/signal-wasm/tests/types.ts
       - name: Guard sqlite-storage's platform shim
         run: cargo xt ci workflow guard-sqlite-shim
       # The sans-IO VoIP core (wacore::voip: the CallEngine, the portable run_call driver,

Cargo.toml

@@ -42,6 +42,9 @@ members = [
     "wacore/derive",
     "wacore/libsignal",
     "wacore/noise",
+    "wacore/recordstore",
+    "wacore/signal-ops",
+    "wacore/signal-wasm",
     "waproto",
 ]
 default-members = [
@@ -55,6 +58,8 @@ default-members = [
     "wacore/derive",
     "wacore/libsignal",
     "wacore/noise",
+    "wacore/recordstore",
+    "wacore/signal-ops",
     "waproto",
 ]
 

wacore/recordstore/Cargo.toml

@@ -0,0 +1,26 @@
+[package]
+name = "wacore-recordstore"
+version = "0.1.0"
+edition = "2024"
+rust-version.workspace = true
+authors = ["Polymorfa"]
+license = "MIT"
+repository = "https://github.com/polymorfa/whatsapp-rust"
+description = "Fenced, sealed record storage for wacore Signal state"
+publish = false
+
+[features]
+# Reusable checks every RecordStore implementation must pass. Adapter crates
+# enable it in their dev-dependencies and call `conformance::run_all`.
+conformance = []
+
+[dependencies]
+aes-gcm = { workspace = true }
+async-trait = { workspace = true }
+bytes = { workspace = true }
+rand = { workspace = true }
+thiserror = { workspace = true }
+wacore = { workspace = true }
+
+[dev-dependencies]
+futures = { workspace = true, features = ["executor"] }