Advance WBV2 through native engine module matrix

docs/status/WBV2-P10-000.md

@@ -0,0 +1,6 @@
+# WBV2-P10-000 status
+
+- task: `WBV2-P10-000`; parent: `WBV2-P9-004`; status: `done`
+- nextTask: `WBV2-P10-001`
+
+Native engine parity continuation is authorized after P9 bounded Chromium evidence. P10 first reconciles the known WBV2 inventory drift, then requires receipts from the compiled Blender native binary and web_engine.wasm. Full historical reproduction remains false.

docs/status/WBV2-P10-001.md

@@ -0,0 +1,9 @@
+# WBV2-P10-001 status
+
+- task: `WBV2-P10-001`; parent: `WBV2-P10-000`; status: `done`
+- plan drift: `1` authorized mutable plan hash
+- dependency packages: `144`; lockfile/roots/closure: `STABLE`
+- historical P0 hashes: preserved
+- nextTask: `WBV2-P10-002`
+
+The current WBV2 plan hash is recorded as an additive epoch-1 baseline. The historical P0-002 source-hashes.json and all historical manifests remain unchanged. Dependency roots, lockfile, package closure, and package count remain stable.

docs/status/WBV2-P10-002.md

@@ -0,0 +1,9 @@
+# WBV2-P10-002 status
+
+- task: `WBV2-P10-002`; parent: `WBV2-P10-001`; status: `done`
+- compiled native: `Blender 5.2.0 LTS`; compiled WASM: `web_engine.wasm`
+- real Main mutations: `Mesh + Modifier + Asset Catalog`
+- deterministic Chromium runs: `2`; save/reopen: `3/3 EXACT`
+- nextTask: `WBV2-P10-003`
+
+The Chromium Worker loaded the checked-in WebEngine WASM and executed the native ABI through WebEngineClient. Mesh translation, modifier state, and library append all changed the real WASM Main, persisted through save/reopen, and rejected stale or malformed inputs without a late mutation. This evidence is engine-bound and still does not claim full historical reproduction.

docs/status/WBV2-P10-003.md

@@ -0,0 +1,9 @@
+# WBV2-P10-003 status
+
+- task: `WBV2-P10-003`; parent: `WBV2-P10-002`; status: `done`
+- module cases: `9`; positive Main mutations: `3`; retained negatives: `6`
+- shards: `2`; one catalog hash; exit codes: `0/0`
+- inventory: `6900` total, `6900` explicitly remaining; no false completion claim
+- nextTask: `NONE`
+
+The data-driven Mesh, Modifier, and Asset Catalog matrix re-runs the real WebEngine WASM Main path with one catalog hash. Positive cases change Main and pass save/reopen; stale, malformed, unknown, and collision cases remain explicit retained negatives. The matrix does not claim all inventory entries are complete or reproduce unavailable historical bytes. P10-003 is the terminal pointer until a separately authorized continuation is created.

docs/status/WBV2-P9-004.md

@@ -8,3 +8,6 @@
 - nextTask: `NONE`
 
 The gate emits only claims backed by deterministic Chromium production receipts with exact save/reopen evidence. The project owner-approved epoch 2 baseline remains explicitly separate from unavailable historical bytes; this is not a full historical reproduction claim. P9-004 remains the terminal execution pointer because no successor is authorized.
+- authorized continuation: `WBV2-P10-000`
+
+Native Blender/WASM engine parity may continue under a new manifest root. This does not change the bounded P9 claims or the authorized-rebaseline-only release scope.