TranslateKit component stuck at 0.0.0.0 "Update error" on 151.0.4129.107 — on-device translation unusable (repros on Windows x64 and macOS arm64)

[wooii]

Summary
On Edge 151.0.4129.107, the Chrome TranslateKit component (the shared
engine all Translator API language pairs depend on) is stuck at version
0.0.0.0 with status "Update error" in edge://components, and never
successfully installs. MEI Preload is stuck the same way. As a result
Translator.create() never succeeds for any language pair, even ones
whose language packs show "Installed" in
edge://on-device-translation-internals.

Environment

• Machine A: Windows, x64, Edge 151.0.4129.107 — was working before
  updating to this version, broke immediately after
• Machine B: macOS, arm64, Edge 151.0.4129.107 — same failure
• Same two components (Chrome TranslateKit, MEI Preload) fail on both,
  everything else in edge://components is up to date

Steps to reproduce

1. On 151.0.4129.107, open edge://components
2. Check "Chrome TranslateKit" — version 0.0.0.0, status "Update error"
3. Click "Check for Update" — no change
4. Trigger Translator.create() for any language pair (e.g. via the
   Translator API) — hangs / never resolves to available

Expected
Chrome TranslateKit installs normally and Translator.create() succeeds
for available language pairs.

Actual
Component permanently fails to update; on-device translation is
completely unavailable.

Already ruled out

• Not a local profile/permissions issue — reproduces identically on a
  second, unrelated machine on a different OS and CPU architecture
• Not a network/firewall issue — reproduces on separate networks
• Full browser restart, "Check for Update" on the component, and a
  fresh profile do not resolve it

Impact
Any extension or site using the Translator API on this build gets no
on-device translation and silently falls back to server-side
alternatives, defeating the point of the on-device API for affected
users.