build: move onto the published 0.4 engine

[pathscale]

Chuzz could not see any engine work. This moves it onto the published 0.4 engine, and onto a tauri-runtime-blitz that builds.

Why the old pins could not move

ps-blitz-* = "^0.3.0-beta.6". A prerelease requirement only matches its own prerelease line — it accepts 0.3.0-beta.* and nothing else. Not 0.3.6, not 0.4.0. The pin was nine releases behind and could not be moved by cargo update.

It is also why scripts/local-engine.sh appeared to do nothing. Cargo reported

patch ... was not used in the crate graph

and carried on with the registry copy, so editing a local engine checkout changed no behaviour. That reads as a broken patch table; the cause was an unsatisfiable pin.

tauri-runtime-blitz ^0.1.0 is the second half. It does not compile on rustc 1.97.1 (error[E0658]: use of unstable library feature 'str_as_str') and only survived here because a cached artifact existed in target/ — a cargo clean would have stranded the repo. 0.3.2 is the release that takes ps-blitz ^0.4, so both sides of the cascade agree.

What changed

	before	after
ps-blitz-*	^0.3.0-beta.6	^0.4
tauri-runtime-blitz	^0.1.0	^0.3.2
endpoint-libs	^2.1.5	^3

The endpoint-libs move is not optional. tauri-runtime-blitz 0.3.2 reaches it through blitz-control-protocol 0.4, which requires ^3; leaving this workspace on ^2.1.5 put both 2.1.5 and 3.0.0 in the graph — two crates exporting the same MCP framing types, the same shape of fault as two engines. The manifest already said these should be the same source and feature tauri-runtime-blitz uses; this makes that true rather than aspirational.

WireMessage::Text carries Utf8Bytes rather than String in 3.0, so three send sites convert. The receive sides read through Deref and needed no change.

API drift: there is none

The engine pin was nine releases behind and real work was expected here. There was none. With the graph resolving to a single engine, every crate compiled clean — the only errors in the workspace were the endpoint-libs conversions above.

Chuzz never matches on blitz_dom::net::Resource (the variant addition that forced the minor), and it uses Provider::new, which #79 left unchanged. No file under apps/chuzz/src/ was touched.

Verified

• cargo build -p chuzz-gui --release --features capture from a clean target — 4m 28s, clean. No cached-artifact crutch.
• cargo fmt --all -- --check — clean.
• cargo clippy -p chuzz-control --all-targets --all-features -- -D warnings — clean.
• cargo clippy -p chuzz-gui --all-targets -- -D warnings — clean.
• scripts/check-one-rev-per-git-source.sh — no git sources.
• cargo test --workspace — 47 passed, 0 failed (32 chuzz-gui, 15 chuzz-control). server::tests::a_client_gets_an_answer_and_teardown_removes_both_files exercises the changed Utf8Bytes send path over a real socket.

End to end, the probe from the handover:

scripts/render-check.sh probe1 <large production site>
  3860 nodes, 1531 with a box

Before #79 that panicked with `style` is not available on this node kind. It now completes and paints the page. That is the point of this change: engine fixes become visible here.

The remaining console lines are missing web APIs (HTMLVideoElement, ES module import.meta), which are H3/H4 territory, not engine drift.

Blocked on two publishes

This cannot merge until both are on crates.io:

1. tauri-runtime-blitz 0.3.2 — pathscale/tauri-runtime-blitz feat/ps-blitz-0.4, unmerged.
2. ps-dioxus-native 0.7.3 — release: publish dioxus-native at 0.7.3, against the 0.4 engine ps-blitz#80. The published 0.7.2 still requires ^0.3.0-beta.6 and drags a second engine in; it was missed by the 0.4.0 release.

Verification above was done with both redirected to local checkouts through an untracked .cargo/local-engine.toml. The engine sources compiled are ps-blitz ff31bb55, which is the 0.4.0 release commit.

Cargo.lock is deliberately unchanged — it cannot be regenerated against versions that do not exist yet. It must be refreshed once both publishes land. Nothing in ci.yml or release.yml passes --locked, so this does not break the build in the meantime.

[workspace.package] version is intentionally untouched: release.yml publishes whenever it changes, and a pin bump should not fire a CDN release as a side effect.

[pathscale]

Superseded by #33, which consolidates all chuzz work into one PR.