Add VS Code-style developer status bar to dev and staging builds

[ComputelessComputer]

Summary

Problem: Dev and staging builds have no at-a-glance runtime signal in the window itself. Checking which build you are on, whether the UI is dropping frames, how chatty the frontend is with the Rust side, or whether memory is drifting means opening Web Inspector or the separate Devtools panel window. React Scan runs in dev, but as its own floating toolbar that is disconnected from the rest of the app chrome.

Fix: Mount a slim, Linear/VS Code-style status bar at the bottom of the main window whenever show_devtool is true (debug builds, dev/devtools features, and the com.hyprnote.staging bundle). Stable builds render nothing and the layout wrapper is the same one the Windows title bar already used. Segments, left to right:

• Channel badge — DEV / STAGING with version and short git hash; whole bar is tinted per channel (blue = dev, amber = staging). Clicking it opens the existing Devtools panel window (macOS-only, same as the Settings → Developers button).
• FPS — rAF-based, with a 30s sparkline pinned to 60.
• IPC — Tauri traffic per second: ↑ invokes, ↓ callbacks (invoke responses, events, channel messages). Tauri freezes __TAURI_INTERNALS__, so this is observed from the outside: invokes are fetch calls to the ipc scheme, deliveries go through the exposed callbacks Map whose get we shadow. The bar's own memory poll is excluded.
• RENDERS (Vite dev only) — React Scan component renders per second; click toggles re-render outlines. The bar's own components are marked ignored so it does not outline or count itself.
• MEM — host process RSS via a new misc plugin command get_process_memory_bytes (sysinfo); sparkline is min/max scaled so slow growth is visible.
• react scan (Vite dev only) — toggles React Scan's own toolbar (inspector, slowdown notifications). The toolbar is now hidden by default since FPS and renders live in the bar.

Developer status bar in the running dev build

Zoomed status bar: DEV 0.0.0 7df7853, FPS 62, IPC, RENDERS 0, MEM 313MB

React Scan bootstrapping moved out of main.tsx into devtools-bar/react-scan.ts. Note that React Scan only attaches in Vite dev because it relies on the devtools hook React Refresh installs before React evaluates; staging (production bundle) shows the bar without the React Scan segments. Enabling it there would need react-scan/install-hook loaded ahead of React behind a build-time channel flag, which is left as a follow-up.

Copy is English-only on purpose: the bar never ships in stable, so it is kept out of the Lingui catalogs.

Verification

• pnpm -F desktop typecheck, pnpm -F @anlg/plugin-misc typecheck
• pnpm -F desktop test — 430 files / 3692 tests pass, including new devtools-bar/metrics.test.ts and devtools-bar/index.test.tsx, and an updated main/shell-frame.test.tsx
• pnpm exec oxlint --quiet --format=github apps/desktop/src/ — 0 errors
• pnpm -F desktop i18n:check — no catalog diff
• pnpm exec dprint fmt / dprint check on changed files
• cargo test -p tauri-plugin-misc (regenerates bindings.gen.ts and autogenerated permissions, committed) and cargo clippy -p tauri-plugin-misc --tests -- -D warnings
• Manual: ran turbo dev:desktop on Linux (WebKitGTK), skipped onboarding, confirmed the bar renders in the main shell, FPS/IPC/MEM update every second, RENDERS toggles to off and back, the react scan button mounts/unmounts React Scan's toolbar, and the bar no longer outlines itself while idle (RENDERS stays at 0).
• Not run locally: cargo check -p desktop --features direct-distribution|app-store (the dev build compiled and ran; only the misc plugin's internal surface changed and init() is unchanged).

_{To show artifacts inline, enable in settings.}

  

[netlify]

✅ Deploy Preview for anarlog canceled.

Name	Link
🔨 Latest commit	561f111
🔍 Latest deploy log	https://app.netlify.com/projects/anarlog/deploys/6a9850eb2ba20d0008d06435

[cla-assistant]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
_{You have signed the CLA already but the status is still pending? Let us recheck it.}

[cursor]

Cursor Bugbot has reviewed your changes using default effort and found 1 potential issue.

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}

^{Reviewed by Cursor Bugbot for commit f60c556. Configure here.}