[enaboapps]

Closes #1071

Summary

The download progress callback emitted the full AppState for every network chunk: two snapshots, diagnostics and telemetry observers, a tray set_text, and a full webview re-render. A ~155 MB installer meant thousands of these, which could freeze the app.

• Counting: updater::ProgressCounter counts bytes in AtomicU64s outside the shared state mutex.
• Event: a new update-progress event carries { downloadedBytes, totalBytes }.
• Throttle: updater::ProgressThrottle (pure, injectable Instant) emits the first sample, then only when ≥250 ms have passed and the whole percent has changed (time alone when the total is unknown). The completing sample is always emitted once.
• State emission: full publish_update / emit_state now happens only on transitions (downloading, ready, failed, cancelled). The final byte count and total go into AppState.updater at ready. UpdateView::add_progress is removed.
• Tray: TrayController::sync skips set_text / set_enabled when the native menu already shows the value. Each value is recorded only after its setter succeeds, so a failed call is retried on the next sync.
• Diagnostics: a downloading updater entry is recorded when a download starts.
• Frontend: App (always mounted) calls useUpdateProgress once, giving a single api.onUpdateProgress listener. It passes the merged updater state to the UpdateBanner and, through SettingsView, to UpdatesSection, so opening Updates mid-download shows the latest sample. Stale samples are cleared when a download ends. The UI text is unchanged.

Validation

Latest head, Node 24.19.0, Rust 1.97.1, Windows 11:

• npm run prediction-model: verified offline neural model and workers
• npm run lint: pass
• npm test: vitest 13 files / 299 tests passed; node tests 12/12 passed
• npm run build: pass
• cargo fmt --manifest-path src-tauri/Cargo.toml --check: pass
• cargo clippy --manifest-path src-tauri/Cargo.toml --all-targets -- -D warnings: pass
• cargo test --manifest-path src-tauri/Cargo.toml: 790 passed, 5 ignored; 7 passed in the integration suite

New tests:

• Rust throttle tests: the interval gate, the whole-percent gate, the completion flush, an unknown total, and a bound on events for a simulated 155 MB download.
• A fake-artifact download test checks the throttled events and the final count. The existing fake-artifact cancellation test still passes.
• Event payload serialization.
• Tray tests: unchanged values are skipped, and a value whose setter failed is retried.
• Frontend tests:
  • the progress event updates the bar and the banner, and the ready state comes from AppState;
  • opening Updates mid-download shows the last sample, with a single listener;
  • a download that is cancelled or fails and is then retried starts at 0 before the first new sample.

🤖 Generated with Claude Code