workinf_Blender_Wasm/docs/web/RELEASE_NOTES.md

Web Blender Modeler V1 0.1.0-rc.1 Release Notes

Release candidate identity: web-blender-0.1.0-rc.1, engine blender-wasm-0.1.0-rc.1.

This candidate is a Chromium-only browser modeler built around a bounded Blender 5.2 Main/WebEngine subset. It is not a browser port of the complete Blender desktop application. The normative product boundary and capability definitions are in V1_SCOPE.md; the machine-readable family status and exact required/blocked slices are in parity-ledger.json.

Verified V1 capabilities

• Import .blend, edit the declared Object, Mesh and Principled material subset, undo, redo, save atomically, restart the Storage and WebEngine Workers, reopen, and export a semantically checked GLB.
• Preserve stable object, mesh and material identities across save/reopen and verify both the main-thread WebGL and OffscreenCanvas Worker production viewports with non-empty pixels.
• Select integrity-checked single-thread or pthread WebEngine artifacts from one versioned engine manifest. The pthread variant is used only when the isolated platform prerequisites pass.
• Store projects, snapshots and bounded assets in origin-bound OPFS/IndexedDB, including tested interruption, Worker restart, quota failure and recovery behavior.
• Exercise bounded 100k, 1M and 10M geometry, 4K/8K textures, 600-frame simulation cache and one-million-frame media indexing gates.
• Exercise deterministic WASM, OPFS, GPU and NanoVDB out-of-memory recovery, WebGL device loss, network interruption, malformed .blend input and malicious archive rejection.
• Deliver deterministic offline binary and corresponding-source archives with SHA-256 checksums, SPDX SBOM, licenses, source offer, deployment contract and operations diagnostics.
• Reproduce quick, Chromium and release CI lanes with lockfile, source, engine, archive and per-command log hash bindings.

Capability boundaries

LOCAL_EXACT and LOCAL_BOUNDED mean only the fixtures, operations and budgets declared in V1_SCOPE.md and parity-ledger.json. Unsupported operations must remain blocked or preserved; the release does not infer support from a readable Blender data block.

SERVER covers validated request/result boundaries for work such as Cycles rendering, complex physics bakes and final video encoding. This offline candidate does not bundle or configure those services and does not claim local-equivalent execution.

EXCLUDED includes arbitrary Python/Text autorun, add-on installation, native desktop windows and native CUDA, Metal, HIP or OptiX backends. The UI must not report those operations as successful.

All 12 V1 family release slices are READY, while all 12 complete Blender 5.2 family parity states are BLOCKED. The exact blocked and excluded slice names remain authoritative in parity-ledger.json; this release note does not convert them to completed work.

Delivery evidence

Verify SHA256SUMS.txt, then verify RC_MANIFEST.json.sha256 and RC_MANIFEST.json before deployment. The manifest binds the RC version, base commit, engine release ID, package lock, ledger, embedded release metadata, SBOM, binary/source archives and operations reports.

Read Known limitations before deployment, especially the browser, engine variant, origin-bound storage, quota, WASM and GPU budget boundaries.

Use Release recovery to verify delivery evidence, export project backups and handle pre-switch failures, compatible rollback or blocked schema downgrade.

Deployment requirements and operator commands are in DEPLOYMENT.md. Stable error signals and recovery boundaries are in operations-diagnostics.json.