[docs] Clarify ResourceStoppedEvent fires once per stop, not per restart

[aspire-repo-bot]

Documents changes from microsoft/aspire#20279

@JamesNK

Targeting release/13.6 based on the source PR milestone 13.6.

Why this doc is needed

The source PR (microsoft/aspire#20279) fixes a bug where OnResourceStopped handlers could receive duplicate callbacks when the handler itself triggered a restart. The PR body's "User-facing scenario" section explicitly calls out the fixed, user-observable behavior: a restart-triggering OnResourceStopped handler no longer gets invoked twice for the same stop.

ResourceStoppedEvent is documented in app-host/eventing.mdx, but the docs previously didn't clarify the once-per-stop semantics, which could otherwise read as ambiguous to a reader relying on the event to gate restart logic.

What changed

• src/frontend/src/content/docs/app-host/eventing.mdx: Added a note under the "Resource stopped event" section clarifying that ResourceStoppedEvent fires once per stop, and that a restart triggered from within a handler does not cause a duplicate firing for the same stop.

Files modified

• src/frontend/src/content/docs/app-host/eventing.mdx (updated existing page)

No new pages were created; this is a targeted clarification to an existing page.

Generated by PR Documentation Check for #20279 · copilot · auto · 67.4 AIC · ⌖ 10.2 AIC · ⊞ 18.5K · ◷

[aspire-repo-bot]

Frontend HTML artifact ready

The latest frontend build uploaded the frontend-dist artifact for PR #1705. Use the VS Code button below to open this PR with GitHub Artifacts Explorer and browse the built HTML locally.

This comment updates automatically when a new frontend build artifact is uploaded.