Remove Recent Activity from the UI

[enaboapps]

Closes #556

What changed

• removes the Recent activity panels from Home and Support
• prevents internal activity messages from surfacing in the Home connection banner
• provides deterministic discovery, connected, and recovery guidance for every Bluetooth state
• ignores stale connected-device names outside the connected state
• removes the unused activity-panel styles
• preserves AppState activity tracking, troubleshooting history, diagnostics, and optional telemetry

User impact

Routine internal status messages no longer occupy the Home or Support UI. Home still explains when Bluetooth needs recovery, and detailed sanitized troubleshooting information remains available in Support.

Validation

• npm run lint
• npm test (55 frontend tests plus 4 release-feed tests)
• npm run build
• cargo fmt --manifest-path src-tauri/Cargo.toml --check
• cargo clippy --locked --manifest-path src-tauri/Cargo.toml --all-targets -- -D warnings
• cargo test --locked --manifest-path src-tauri/Cargo.toml (135 tests plus config tests)
• updater verifier fmt, Clippy, and 2 Rust tests

[enaboapps]

@greptileai please run a full review of the current head, focusing on whether the UI removal preserves diagnostics, telemetry, and AppState compatibility.

[greptile-apps]

Greptile Summary

The Home and Support interfaces now provide Bluetooth-state-specific guidance, preserve the connected device name only for active connections, and remove obsolete Recent Activity panels while retaining diagnostic details in Support. The previously reported stale-name and generic-waiting behaviors were checked against recovery states and do not occur in the current implementation.

Confidence Score: 5/5

Safe to merge based on the reviewed Bluetooth-state rendering behavior.

No blocking failure remains.

T-Rex Logs

What T-Rex did

• Validated that no upload was attempted through an unavailable mechanism, and that local artifact paths are not represented as uploaded references.

_{Ran code and verified through T-Rex}

_{Reviews (4): Last reviewed commit: "Ignore stale device names during recover..." | Re-trigger Greptile}

[enaboapps]

@greptileai please rerun the full review on current head 6f144c0. Every Bluetooth state now has deterministic discovery/connected/recovery copy, with regression coverage proving internal activity remains hidden.

[enaboapps]

@greptileai please rerun the full review on the current head. The Home banner now trusts connectedDeviceName only while connected, and the table test injects a stale device name into every non-connected Bluetooth state.

[enaboapps]

Current head 2076231 is ready for user review:

• Greptile 5/5 on the latest commit
• all review threads resolved/outdated
• frontend CI passed
• macOS app/DMG CI passed
• Windows NSIS/UIAccess CI passed
• local lint, 55 frontend tests plus 4 feed tests, build, Rust fmt/Clippy, 135 Rust tests plus config tests, and updater-verifier checks passed

The PR remains draft and unmerged as requested.