Real Grok updater observation (Linux x86_64, web client, 1280x800 CSS px, DPR 2, light theme). No simulated provider update or mocked updater was used. Base: 1b8ac6d77ee35ab8ce27d875352805db01bf791f Head: 78853f24aafce373f5192992557bd6ef1295b312 Initial binary: official @xai-official/grok-linux-x64 npm package 1.0.77 Initial binary SHA256: b702950aa5827d855e493278ab6215a4e0f5bceb5bba6c6243a9f55cdd143b0a BASE .grok/bin/grok --version => grok 1.0.77 (50ca579fa996) [stable] .grok/bin/grok symlink => grok-1.0.77 .grok-hub/bin/grok --version => grok 1.0.88 (2fe3608f7398) [stable] .grok-hub/bin/grok symlink => ../downloads/grok-1.0.88-linux-x86_64 HEAD .grok/bin/grok --version => grok 1.0.88 (2fe3608f7398) [stable] .grok/bin/grok symlink => ../downloads/grok-1.0.88-linux-x86_64 .grok-hub/bin/grok => absent UI observations: Base: Update now leaves v1.0.77; sidebar says Grok still needs an update; update popover says Update command completed, but T3 Code still detects an outdated provider version. Head: Update now installs v1.0.88 at binaryPath; sidebar says Grok updated: v1.0.88; update indicator disappears. Supplementary same-layout Update all run (only Grok outdated): base shows Provider update failed; head shows Provider updated / New sessions will use the updated provider. Both runs list Codex, Claude, Grok and Replay (dev), in that order. Each uploaded still passed an exact-byte comparison of two screenshots taken 500 ms apart. Only machine labels were redacted; fixture paths are synthetic.