net dashboard: cancel stale detail requests and proactively expire snapshots

[Patrick W. Healy (phealy)]

Purpose

Cancel selection-owned requests immediately, coalesce browser waiters, preserve still-valid data on refresh failure, and release expired payloads using browser-safe timers.

Compatibility

Based on #782. Expiry, navigation, and reconnect never trigger a new diagnostic collection. Long configured TTLs rearm timers rather than expire prematurely.

Validation

20 frontend tests, TypeScript check, and Vite build passed. Immediate-parent diff: 108 added+deleted lines.

Part of the draft lightweight-status stack based on #745. Default activation remains pending.

Lightweight status draft stack

Base: #745. Each layer targets the preceding branch and remains draft.

#746 -> #747 -> #748 -> #750 -> #751 -> #752 -> #753 -> #754 -> #755 -> #756 -> #757 -> #758 -> #759 -> #760 -> #761 -> #762 -> #763 -> #764 -> #765 -> #766 -> #767 -> #768 -> #769 -> #770 -> #771 -> #772 -> #773 -> #774 -> #775 -> #776 -> #777 -> #778 -> #779 -> #780 -> #781 -> #782 -> #783 -> #784 -> #785 -> #786 -> #787 -> #788 -> #789 -> #790 -> #791 -> #792 -> #793 -> #794 -> #795 -> #796 -> #797 -> #798 -> #799

[Patrick W. Healy (phealy)]

This PR was mistaken churn from splitting the lightweight-status work into unnecessarily small PRs. That was my mistake, not a requirement from the user.

Its changes are preserved in #764, #766 within the user-approved, consolidated 12-PR draft stack. Closing this superseded PR; the implementation is not being discarded, and nothing has been merged into main.