Prove OpenSSL PQ crypto in browser WASI and document the migrationfeature/private-chat

1 files changed, 27 insertions, 36 deletions

diff --git a/crates/chat-crypto/README.txt b/crates/chat-crypto/README.txt
index ba78cea..d09ff82 100644
--- a/crates/chat-crypto/README.txt
+++ b/crates/chat-crypto/README.txt
@@ -23,44 +23,35 @@ CHAT CRYPTOGRAPHY COMPATIBILITY PROBE
 
     Fixed encryption: RFC 9980 ML-KEM-1024 + X448, OpenPGP v6.
     Tested signing: ML-DSA-87 + Ed448, OpenPGP v6.
-    No algorithm substitution or security-advisory ignore is permitted.
+    Backend: Sequoia 2.4.2 with OpenSSL 3.6.5. No algorithm substitution or
+    vulnerability-advisory exception was used. The first checkpoint's Rust
+    backend is historical and no longer selected.
 
-    See ../../docs/CHAT-SECURITY-REVIEW.txt for the blocking dependency review,
-    and ../../docs/CHAT-DESIGN.txt for the intended application and limitations.
+    See ../../docs/CHAT-OPENSSL-MIGRATION.txt for the complete decision record,
+    pinned source hashes, build flags, capability boundaries, dependency-policy
+    exceptions, observed results, limitations, and reproduction commands.
+    ../../docs/CHAT-SECURITY-REVIEW.txt records the original dependency findings.
+    ../../docs/CHAT-DESIGN.txt describes the planned application.
 
-REPRODUCE THE NATIVE TEST
+QUICK CHECKS FROM THE STACK ROOT
 
         cargo test --locked -p stack-chat-crypto
-        cargo clippy --locked -p stack-chat-crypto --all-targets
-
-REPRODUCE THE BROWSER TEST
-
-    From the stack root, install development-only tools under .tools:
-
-        rustup target add wasm32-unknown-unknown
-        cargo install --locked --version 0.2.130 wasm-bindgen-cli --root .tools
-        npm install --prefix .tools/browser --save-exact playwright@1.64.1
-        PLAYWRIGHT_BROWSERS_PATH="$PWD/.tools/browsers" .tools/browser/node_modules/.bin/playwright install chromium
-
-    Build and bind the Rust module, then run it in actual Chromium:
-
-        cargo build --locked --release -p stack-chat-crypto --target wasm32-unknown-unknown
-        .tools/bin/wasm-bindgen --target web --out-dir .tools/chat-proof target/wasm32-unknown-unknown/release/stack_chat_crypto.wasm
+        cargo run --locked -p stack-chat-crypto
+        sh infra/chat/build-openssl-wasi.sh
         PLAYWRIGHT_BROWSERS_PATH="$PWD/.tools/browsers" node crates/chat-crypto/tests/browser.mjs
-
-    The harness serves only a blank test document and the generated JS/WASM on
-    an ephemeral loopback port. It checks the actual browser cryptographic
-    result and verifies that the probe creates no cookies, web storage, or
-    IndexedDB databases and sends no requests to external hosts.
-
-    This does not establish the storage or network behavior of a future chat
-    application, which has not been built yet. LibreJS acceptance has not been
-    tested; there is no public application or compliance badge for this probe.
-    The test password is a public fixture, not a real configured secret.
-
-AUDIT
-
-        .tools/bin/cargo-deny --workspace --all-features check
-
-    This audit is intentionally blocking. Consult the security review rather
-    than trusting a functional round trip as evidence of production security.
+        cargo stack check
+
+    Native checks require OpenSSL >=3.5 development files and libclang.
+    The cross-build script currently supports Linux x86_64 development hosts.
+    Browser tooling installation is documented in the migration record.
+
+    The harness serves only a blank document, a readable AGPL JavaScript WASI
+    bridge, and the new WASI binary on an ephemeral loopback port. It verifies
+    the actual OpenSSL backend, cryptographic round trips, tampering and invalid
+    credential rejection, repeated fresh instances, and failure without CSPRNG.
+    It checks for external requests and persistent browser application state.
+
+    The application itself, private chat-file envelope, and session workflow
+    remain unimplemented. LibreJS acceptance has not been tested; there is no
+    public chat page or compliance badge. The fixture password is public test
+    data, not a configured secret. No .env file or user private key is needed.