chore(deps): fork 链更新到 gpui-pre fork-0.3.110 + gpui-kit 8caa3aee，shell 依赖链支持 32 位 Windows - #254

Description

Three dependency-only commits that refresh the gpui-* fork chain and make the gpui-shell / shell-plugins dependency chain buildable on i686-pc-windows-msvc. No application logic changes.

1. Split the QuickJS runtime by pointer width (abb055843)

gpui-shell's QuickJS runtime now resolves rquickjs-jit with the compiler feature only on 64-bit macOS/Windows/Linux; every other target gets it without compiler and runs interpreter-only. The JIT path on 32-bit targets is a real 64-bit assumption (quickjs-ng nan-boxing), so the fork generates separate i686-pc-windows-msvc bindings, pins the exit-kind constants to u32 with const assertions, and makes build() fall back to the interpreter when native execution is unavailable instead of failing at the missing-bindings include!.

• gpui-kit: 6df86ef8 → 329a064a
• quickjs-jit: 51c57e3c → 1a5b7fa

gpui-wry, gpui-kit and the rquickjs [patch] entry move to the same revision — otherwise two copies of gpui-kit / quickjs-jit coexist and their ModuleDef / Ctx / Error types stop unifying. The extension engine's host version follows the crate version (crates/extension-runtime/src/extension/manifest/shell_validation.rs).

2. Refresh the gpui-pre snapshot to fork-0.3.110 (19fd01a71)

The fork's gpui-pre-release branch is merged with upstream/main (zed ed16e536e7) and republished, so all [patch] entries point at fork-0.3.110 (single resolved revision befc48fd).

The merge changes the crate set once: upstream deleted crates/media (4b47ceb9d3 — "gpui_macos: Migrate screen capture to objc2"), so the snapshot no longer publishes gpui-pre-media and that patch entry is dropped. Nothing in Navop or in the snapshot still depends on it. The dynamic-texture API (Window::update_dynamic_texture, Window::paint_dynamic_texture, DynamicTexture) is preserved by the merge; remote_desktop_view keeps using it.

3. Adapt gpui-component to the factory-based inspector API (07dba58f0)

Upstream turned App::register_inspector_element into a factory closure (Fn(&mut Window, &mut App) -> F), because the registry memoizes one renderer per (inspector, element-state type) pair and builds it lazily on first render. gpui-component's registration now creates the DivInspector entity inside the factory instead of behind a process-wide OnceCell, following upstream's own call site in crates/inspector_ui/src/inspector.rs. Without this, gpui-component does not compile against the refreshed snapshot (error[E0593]: closure is expected to take 2 arguments, but it takes 4 arguments). gpui-kit moves 329a064a → 8caa3aee.

Break Changes

Extension manifests that declare gpui_shell: "0.2.0" are now rejected. The host version constant moves with the gpui-shell crate version, 0.2.0 → 0.6.1, and for a 0.x requirement the validator requires the minor to match exactly:

-const GPUI_SHELL_VERSION: &str = "0.2.0";
+const GPUI_SHELL_VERSION: &str = "0.6.1";

requires gpui-shell 0.2.0, host provides 0.6.1

Extension authors should declare 0.6.x. The in-repo fixtures and the design doc are updated accordingly.

How to Test

Run from navop/ (macOS aarch64, rustc 1.98.1):

• cargo check -p remote_desktop_view — Finished dev profile [unoptimized + debuginfo] target(s) in 27.71s, 0 errors. This is the integration check: it compiles gpui-pre (fork-0.3.110), gpui-kit (8caa3aee), gpui-component, gpui-shell and the Navop crate that drives dynamic textures.
• cargo metadata --format-version 1 — resolves to exactly one gpui-pre source (…gpui-pre.git?tag=fork-0.3.110#befc48fd) and one gpui-kit revision (8caa3aee); no leftover fork-0.3.109 / 329a064a entries in Cargo.lock.
• zed merge (fork side): cargo check -p gpui -p gpui_apple -p gpui_wgpu --all-targets — Finished, 0 errors on the macOS/Metal path.
• 32-bit fork side: cargo xwin check -p quickjs-jit-runtime -p quickjs-jit --target i686-pc-windows-msvc — 0 errors.

Not verified locally: a full i686 build of gpui-component cannot complete on macOS (its build script fails with llvm-rc: file not found : resources/windows/gpui.manifest.xml), so 32-bit Windows compilation relies on the Windows CI job, which now also checks gpui-shell and gpui-component-shell for i686-pc-windows-msvc. This PR deliberately leaves release.yml untouched: the 32-bit Windows release still excludes shell-plugins, and flipping that switch is a separate change once the CI check is green.