[Dashboard] Mark historical resource states and endpoint links as snapshots

[IEvangelist]

Is there an existing issue for this?

• I have searched the existing issues

Describe the bug

After selecting a completed run, resources still display states such as Running, and their previous endpoint URLs remain normal clickable links. Mutation commands are disabled, but the state and links do not communicate that they are historical snapshots.

The old endpoint may be offline or later reused by another process.

Expected Behavior

Historical resource states and URLs should be clearly identified as snapshots. Historical endpoint values should not appear equivalent to currently active endpoints.

Steps To Reproduce

1. Start an AppHost and note a running resource and its endpoint.
2. Stop the AppHost normally, then start it again.
3. Select the completed run from the Dashboard run selector.
4. The resource still displays Running, and the old endpoint remains an active link.

Exceptions (if any)

N/A

Aspire doctor output

Aspire CLI 13.6.0-pr.18924.g5ee63941
Windows 10.0.26200

Anything else?

Related to #18924. Source: src/Aspire.Dashboard/Components/Controls/ResourceDetails.razor:267-310 and src/Aspire.Dashboard/Model/ResourceMenuBuilder.cs:148-200. Reproduced in the real Dashboard and still present on current main.

[joperezr]

🤖 Aspire triage pass — 2026-08-28 19:30 UTC

Area: area-dashboard
Kind: bug
Repro: yes-minimal — see the Steps To Reproduce section
Affected version(s): 13.6.0-pr.18924 (pre-release; feature unshipped — latest shipped line: 13.5.x)
Severity: S3 — historical run shows live-looking states/links; misleading UX, no data loss

Urgency: ⚪ backlog — no milestone
Reason: UX polish on the unshipped persistence feature (PR #18924); not a regression, no shipped-scenario break. Backlog while 13.6 stabilizes (open milestones: Backlog / 13.5.x / 13.6 / 14.0).

Suggested owner(s): James Newton-King (@JamesNK) (primary), backup Adam Ratzman (@adamint)
Evidence:

• James Newton-King (@JamesNK) is the top recent contributor in area-dashboard — merged Add SQLite persistence and run history to the Dashboard #18924 (the persistence/resume feature these follow-ups derive from), plus Harden Markdown URL validation #19698, Use SQLite for dashboard telemetry filtering #19661, Fix dashboard resource subscription race #19534 and ~37 more in the last 90d
• James Newton-King (@JamesNK) closed [15.5] Filtering metrics by dimensions doesn't work as expected #19046, File input: Localize validation messages in InteractionsInputDialog #18660, Streaming Http Telemetry API doesn't work if you start streaming before telemetry arrives. #17802 (and 14 more) as completed in area-dashboard (last 180d)
• backup Adam Ratzman (@adamint): 10 recent area-dashboard merges (Revert "Update parent resource state from replicas (#18642)" #19545, Fix Dashboard HTML language under invariant culture #19331, Fix dashboard accessibility regressions #19027 …) and 10 closed-completed issues
• CODEOWNERS has no path-specific entry for these files

Confidence: high
Needs human?: no

[JamesNK]

Maybe give urls in old runs an opacity? I don’t think we want to disable them completely.

If we really care then we could have a confirmation popup.

[JamesNK]

Done.