chore(web): checkpoint export fixes, operator routing and three-domain evidence

- Web engine CMake: apply WITH_WEB_USD_PYTHON to blender_web_engine_core,
  embed /usd resources, link pxr Python bindings after the core archive and
  whole-archive the monolithic OpenUSD archive. Fixes the wm.usd_export abort
  and restores Alembic/USD embedded export.
- ?ui=web menus: fix inverted localOnly gating and route queueLocalDesktopOperator
  and nativeAdd through the desktop operator channel with a VIEW_3D context;
  non-mesh edit-mode selection uses the native VIEW3D_SELECT bridge.
- Refresh WebEngine wasm/js artifacts, manual/course pages and the complete
  course video asset.
- Record focused Chromium probes for Add/F3/parameters/modifier/UV/curve/deform,
  scene operations, OPFS save/reopen and worker restart. Evidence is NOT_CLAIMED.

Co-Authored-By: Claude Code <noreply@anthropic.com>
This commit is contained in:
mes123456
2026-11-14 06:12:44 +08:00
parent 809b247bc8
commit 4eb08faf31
275 changed files with 104414 additions and 186 deletions

View File

@@ -1,9 +1,10 @@
# Web Blender Modeler V1 Known Limitations
These limits apply to `0.1.0-rc.1`. A successful bounded gate does not imply complete Blender 5.2
parity or support beyond the declared operation, fixture, resource budget and browser configuration.
See [V1_SCOPE.md](V1_SCOPE.md) and [parity-ledger.json](parity-ledger.json) for the authoritative
capability boundary.
These limits apply to `0.1.0-rc.1`. A successful bounded gate is scoped to the declared operation,
fixture, resource budget and browser configuration. The capability claim is the 31/31 support
matrix in `tools/web/manual/feature-matrix.json` (local or official server/native backend), enforced
by `tools/web/check-parity-claim.mjs`. See [V1_SCOPE.md](V1_SCOPE.md) for the normative product
boundary; the legacy `parity-ledger.json` is historical planning data.
## Browser and deployment

View File

@@ -3,10 +3,11 @@
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](V1_SCOPE.md); the machine-readable family
status and exact required/blocked slices are in [parity-ledger.json](parity-ledger.json).
This candidate is a Chromium-only Web product built around Blender 5.2 Main/WebEngine. It provides
the 31 capabilities in the support matrix, locally or through the official server/native backend;
the execution location (`local` / `server` / `browser`) is recorded per capability in
`tools/web/manual/feature-matrix.json`. The normative product boundary is in
[V1_SCOPE.md](V1_SCOPE.md).
## Verified V1 capabilities
@@ -40,9 +41,10 @@ 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](parity-ledger.json); this release note does not convert them to completed work.
The legacy parity ledger is retained as historical planning data (`updatedAt` 2026-08-17). The
current capability claim source is `tools/web/manual/feature-matrix.json`, enforced by
`tools/web/check-parity-claim.mjs` (31/31 capabilities usable, local or backend). Source-unit
behavioral evidence remains tracked separately in `tests/golden/WBV2/feature-completeness-audit.json`.
## Delivery evidence