sheetom 0.1.0-rc.6 → 0.1.0-rc.7

package/README.md

@@ -20,14 +20,21 @@ After the first stable release, use `npm install sheetom@next` to opt into an
 active prerelease. Until then, the `latest` and `next` dist-tags both identify
 the active release candidate.
 
-The package has no JavaScript runtime or peer dependencies. Its native engine
-includes a pinned, locally maintained Lightning CSS source snapshot; consumers
-do not install a second parser, provide globals, or select a fallback engine.
+The root package has no JavaScript runtime or peer dependencies and contains no
+native addon. It pins one matching `@sheetom/native-*` implementation as an
+optional dependency, so npm installs only the binary for the current operating
+system, CPU, and Linux libc. Installing with `--omit=optional` is unsupported
+and produces an explicit missing-binding error rather than a behavioral
+fallback. The native engine includes a pinned, locally maintained Lightning CSS
+source snapshot; consumers do not install a second parser, provide globals, or
+select a fallback engine.
 SheetOM owns observable-value serialization and shorthand expansion rather
 than delegating CSSOM state to a browser-DOM emulation package.
 
-Node.js 22 and 24 are tested on Linux x64, Windows x64, and macOS arm64. Bun
-1.3.1 and Deno 2.9.5 are tested on Linux x64. Deno must use a local
+Node.js 22 executes the exact published package on macOS arm64/x64, Windows
+arm64/x64/x86, Linux glibc arm64/ARMv7/x64/ppc64le/s390x, and Linux musl
+arm64/ARMv7/x64. Node.js 24 is additionally tested on Linux x64, Windows x64,
+and macOS arm64. Bun 1.3.1 and Deno 2.9.5 are tested on Linux x64. Deno must use a local
 `node_modules` directory and grant SheetOM's native binding FFI and
 system-information permissions:
 
@@ -37,6 +44,29 @@ deno run --node-modules-dir=manual --allow-ffi --allow-sys app.ts
 
 SheetOM exports browser-named classes but never modifies `globalThis`.
 
+Browser applications can install the separate, ESM-only WebAssembly backend:
+
+```sh
+npm install @sheetom/wasm
+```
+
+```ts
+import { createSheetOM } from "@sheetom/wasm";
+
+const { CSSStyleSheet } = await createSheetOM();
+const sheet = new CSSStyleSheet();
+sheet.replaceSync(".card { color: red; }");
+```
+
+`createSheetOM()` resolves the `.wasm` file relative to its own module and
+shares concurrent default initialization within one JavaScript realm. Passing
+an explicit `URL`, `Response`, `ArrayBuffer`, or `WebAssembly.Module` creates
+an independent facade with distinct class identity. The WASM backend uses the
+same Rust parser, Engine ABI Identity, Resource Budget, and CSSOM facade as the
+native package; it is never an automatic fallback for a missing native addon.
+See [`@sheetom/wasm` usage](./packages/wasm/README.md) for server and worker
+requirements.
+
 ## Use
 
 ```ts
@@ -159,7 +189,10 @@ SheetOM targets standards and shared browser behavior first, with Chromium
 behavior used only as the final measured divergence fallback. Versioned JSON
 Operation Fixtures execute through SheetOM and native browser adapters;
 applicable WPT subtests retain their pinned source path, title, and blob SHA.
-Every release ships its machine-readable Compatibility Report.
+Every release ships its machine-readable Compatibility Report. RC7-or-later
+reports distinguish native and WebAssembly backend evidence; the WASM dimension
+records direct HTTP, worker, bundler, memory-soak, and Publisher-shaped browser
+results instead of inferring them from the shared Rust engine.
 
 Modern or implementation-dependent value grammar is bounded by the checked-in
 [`Value Capability Corpus`](./compatibility/value-capabilities.json). Each