[botoddly]

Closes #587.

Problem

Every browser build failed with PIXELY0006 unless the project set WasmCachePath to a writable copy of the wasm-tools workload's Emscripten cache. XdlSharp's browser package linked emdawnwebgpu through Emscripten's port, which compiles webgpu.cpp into the cache at link time, and the workload's cache is read-only.

Change

• PixelyXdlSharpVersion is 3.4.20.2. Its browser package links the emdawnwebgpu that XDL v3.4.20-9 ships prebuilt (Ship emdawnwebgpu prebuilt in the browser zip so .NET apps link without a writable Emscripten cache XDL#27, Link XDL's prebuilt emdawnwebgpu instead of the port, so browser apps need no writable Emscripten cache XdlSharp#3), so the link uses the workload's cache as is.
• The PIXELY0006 target is gone.
• docs/hosting.md, DECISIONS.md, AGENTS.md and the browser harness README no longer ask for a writable WasmCachePath.
• The 3.4.20.2 desktop packages carry XDL v3.4.20-9 instead of v3.4.20-4.

Tested locally

• dotnet publish tutorials/Pixely.Tutorials.Browser -r browser-wasm -c Release with 3.4.20.2 from nuget.org and no WasmCachePath. The workload's Emscripten cache is unchanged afterwards.
• tests/Pixely.Browser.Harness rendered the tutorial in Chromium on a hardware adapter, and the app exited with code 0.
• A Debug relink with the same exports also succeeded without touching the cache.

Not run locally: the desktop test suites with the newer XDL runtime.

[github-actions]

📦 Development package Pixely 0.0.162 is available.

Workflow run (attempt 1)

[github-actions]

✅ Development package validation passed on all platforms.

Workflow run (attempt 1)