4.0 KiB
WBV2-P7-003 status
- task:
WBV2-P7-003; parent:WBV2-P7-002; status:blocked - gap:
workflow:full_parity_candidate_release_gate; implementationClass:LOCAL_BOUNDED - fixture:
tests/files/web/generated/WBV2-P7-003-workflow-full_parity_candidate_release_gate.blend
Decision
The release-gate receipt is complete and hash-bound, but the release decision is intentionally BLOCKED. The Web reader, save/reopen path, malformed-input boundary, and quick CI recovery are ready. Full Blender/Web feature parity is not: 6,900 inventory entries remain at L0, 9 of 45 atomic family/behavior tasks now have manifest-bound Chromium receipts, 36 remain without production receipts, and historical M12 SHA drift is preserved fail-closed. A Git-history immutable snapshot restores 22 of 84 entries; 62 entries remain BLOCKED_SOURCE_LOST because their original content is absent from the repository history. No positive parity claim or queue successor is emitted.
This is the safe terminal state for the supplied evidence. Resolving it requires new positive desktop + WASM mutation fixtures and an authoritative replacement for the lost M12 source snapshot; neither can be inferred or reconstructed from current files.
Evidence
- Desktop and WASM agree on the release receipt and all four input hashes.
- Fixture verification reruns preserve the existing
.blendbytes; the generator no longer rewrites a protected output during validation. c5-family-evidence-report.jsonunifies the C5 Mesh/Modifier/Asset shape. Each family reuses a hash-verified desktop positive, WASM/Main mutation and save/reopen exact report; Mesh is explicitly ordereddesktopPositive -> wasmMutation -> saveReopenExact.integration-readiness-report.jsonrecords those reusable family receipts, the first proposed Mesh behavior, and the exact blockers without mutating the queue.atomic-chromium-receipt-index.jsonbinds the real Chromium C3/C4 receipts to the nine available P7 family behaviors; it is exact reuse and makes no new parity claim.build-m12-git-snapshot.mjsproduces an authorizedIMMUTABLE_REPOSITORYsnapshot only from exact SHA-256 matches in Git history; it restores 22 entries and records 23 unresolved path/SHA pairs.M12-provenance-intake.jsonvalidates that snapshot. The remaining 62 drift entries stay fail-closed and no historical file is rewritten.- The isolated Vite development server disables inline React Fast Refresh injection so the deployment-equivalent CSP no longer produces a blank application shell.
- GLB import accepts only the five bounded
KHR_materials_*extensions emitted by the exporter while continuing to reject decoder-dependent extensions such as Draco. parityClosure=BLOCKED,evidenceHealth=BLOCKED,recoveryHealth=READY,releaseDecision=BLOCKED.- Save/reopen is exact; malformed blend rejects without Main mutation.
- Quick CI is
READY(7/7 lanes, 128 isolated unit files).
Commands
build_blender_5.2.0/bin/blender -b --factory-startup --python tools/web/generated/WBV2-P7-003.py -- tests/files/web/generated/WBV2-P7-003-workflow-full_parity_candidate_release_gate.blendbuild_blender_5.2.0/bin/blender -b --factory-startup --python tools/web/check-wbv2-p7-003-desktop.py -- tests/files/web/generated/WBV2-P7-003-workflow-full_parity_candidate_release_gate.blend tests/golden/WBV2-P7-003/release-gate-desktop-report.jsonnpm --prefix web run test:generated-gap -- --task WBV2-P7-003node tools/web/check-generated-gap.mjs --task WBV2-P7-003node tools/web/build-m12-git-snapshot.mjsnode tools/web/intake-m12-immutable-snapshot.mjs --snapshot tests/golden/corrective/rehydration/M12-git-history-snapshot --writenpm --prefix web run test:e2e -- --workers=1 tests/e2e/corrective-family-runner.spec.tsnode tools/web/generate-wbv2-atomic-chromium-receipts.mjsnode tools/web/generate-wbv2-integration-readiness.mjsnpm --prefix web run typecheck && npm --prefix web run lint
Handoff
- nextTask:
NONE; queue remains atWBV2-P7-003until authoritative parity evidence and M12 source provenance are supplied.