Complete WBV2 feature parity evidence epoch

docs/status/WBV2-P8-004.md

@@ -8,3 +8,6 @@
 - nextTask: `NONE`
 
 The project owner approved the new provenance baseline. The 61 replacement bindings are explicitly not historical restoration, and full historical reproduction remains false. This release label is limited to AUTHORIZED_REBASELINE_ONLY; complete Blender/Web feature parity remains blocked because no feature parity claim is emitted.
+- authorized continuation: `WBV2-P9-000`
+
+Feature parity work may continue under a new manifest root. This does not change the authorized-rebaseline-only release scope or historical reproduction limitation.

docs/status/WBV2-P9-000.md

@@ -0,0 +1,6 @@
+# WBV2-P9-000 status
+
+- task: `WBV2-P9-000`; parent: `WBV2-P8-004`; status: `done`
+- nextTask: `WBV2-P9-001`
+
+Feature parity continuation is authorized after provenance epoch 2. Work is limited to evidenced Mesh, Modifier, and Asset Catalog behavior in Chromium; full historical reproduction remains false.

docs/status/WBV2-P9-001.md

@@ -0,0 +1,9 @@
+# WBV2-P9-001 status
+
+- task: `WBV2-P9-001`; parent: `WBV2-P9-000`; status: `done`
+- Mesh Chromium receipt: `DESKTOP + WASM`
+- delta: `(0.5, -1, 2)`; revision: `9 -> 10`
+- save/reopen: `EXACT`
+- nextTask: `WBV2-P9-002`
+
+The production Chromium receipt executes the existing Mesh Main transaction on both browser surfaces. Malformed, stale-revision, and unknown-vertex commands are rejected without mutating the Main. This is a bounded current implementation claim and does not assert historical byte reproduction.

docs/status/WBV2-P9-002.md

@@ -0,0 +1,9 @@
+# WBV2-P9-002 status
+
+- task: `WBV2-P9-002`; parent: `WBV2-P9-001`; status: `done`
+- Modifier Chromium receipt: `DESKTOP + WASM`
+- enabled transition: `false -> true`; revision: `7 -> 8`
+- save/reopen: `EXACT`
+- nextTask: `WBV2-P9-003`
+
+The production Chromium receipt executes the existing Modifier Main transaction on both browser surfaces. Malformed, stale-revision, and unknown-modifier commands are rejected without mutating the Main. This is a bounded current implementation claim and does not assert historical byte reproduction.

docs/status/WBV2-P9-003.md

@@ -0,0 +1,9 @@
+# WBV2-P9-003 status
+
+- task: `WBV2-P9-003`; parent: `WBV2-P9-002`; status: `done`
+- Asset Catalog Chromium receipt: `DESKTOP + WASM`
+- resource: `EXTERNAL_LIBRARY/library.blend`; hash-bound
+- append revision: `4 -> 5`; save/reopen: `EXACT`
+- nextTask: `WBV2-P9-004`
+
+The production Chromium receipt executes the existing Asset Catalog Main and resource resolver. Duplicate, stale, malformed, and missing-resource commands are rejected without a late mutation. This is a bounded current implementation claim and does not assert historical byte reproduction.

docs/status/WBV2-P9-004.md

@@ -0,0 +1,10 @@
+# WBV2-P9-004 status
+
+- task: `WBV2-P9-004`; parent: `WBV2-P9-003`; status: `done`
+- evidenced feature claims: `3`
+- claims: `CAP-MESH-POSITIVE-EDIT`, `CAP-MODIFIER-STATE-MUTATION`, `CAP-ASSET-CATALOG-MUTATION`
+- provenance: epoch `2`, `AUTHORIZED_REBASELINE_ONLY`
+- fullHistoricalReproduction: `false`
+- 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.