fix(site): align hosted native smoke and wasm with protocol 0.9

[phall1]

Cause

site-deploy-worker failed on main after #689:

• Run: https://github.com/no-phux/phux/actions/runs/34957405348
• SHA: 60b63a9 (fix(site): pin hosted native phux to workspace 0.37.0)
• Deploy + container rollout succeeded; live /healthz stayed OK
• Smoke died in ~2s at smoke-native.ts:170: native websocket closed before verification code=1000

This is the HELLO mismatch #689 warned about, confirmed from logs + wire bytes:

• Native image now builds phux 0.37.0 / protocol 0.9 (worker/Dockerfile)
• Smoke still sent a protocol 0.2 HELLO (phux-tui/test, protocol_minor=2) and ATTACH on open
• Committed browser wasm was the protocol-0.5 start_hosted backport (fe1f9563)
• Committed edge wasm still answered ATTACH with 0.5-style snapshots and ignored HELLO
• phux-server requires major.minor match; mismatch → ERROR + close, relayed as WS 1000

--exercise-fallback uses the same HELLO for native then edge, so smoke, edge, and the hosted browser client all had to move to 0.9 together. Native image pin is unchanged.

Fix

Surgical protocol alignment only. No architecture rewrite. Does not touch release #655.

• Smoke HELLO/ATTACH goldens are protocol 0.9 (ClientCapabilities::new(), CreateIfMissing name=default). Smoke waits for the session envelope, then HELLO_OK, then ATTACH. Parses RESOURCE_OUTPUT and BootstrapChunk. Fails on ERROR.
• phux-edge depends on in-tree phux-protocol 0.37.0 and speaks 0.9 HELLO_OK + READY-fenced bootstrap (greeting in BootstrapChunk).
• In-repo clients/phux-web grows start_hosted (wait for phux.session.v1 text, then HELLO). Committed site wasm rebuilt from this checkout instead of the 0.5 pin.
• build-client.sh builds from this repo.

How to verify

Local (already run on this branch):

RUSTFLAGS='' cargo test --manifest-path docs/site/edge/Cargo.toml
cd docs/site && bun run test && bun run worker:check

137 site tests pass; 11 edge tests pass, including HELLO 0.9 and smoke-byte lockstep.

Production path: merge to main retriggers both deploys.

• site-deploy-worker (paths include docs/site/worker/**, docs/site/edge/**, phux-wire.ts, smoke-native.ts) redeploys Worker + edge wasm and re-runs worker:smoke-fallback
• site-deploy (docs/**) republishes the 0.9 browser wasm so the live demo matches native

Native container image is unchanged from #689; only Worker/edge/smoke/browser wasm move. After merge, the site-deploy-worker smoke step is the live confirmation. No Cloudflare secrets were required for this in-repo fix.

  

---

^{Need help on this PR? Tag @codesmith-bot with what you need. Autofix is disabled.}

[linear-code]

PHA-453