I *think* all of these `Add*` APIs are missing `[ResourceName]` attribute.

[IEvangelist]

I think all of these Add* APIs are missing [ResourceName] attribute.

Originally posted by @IEvangelist in #15691 (comment)

[joperezr]

🤖 Aspire triage pass — 2026-05-21 17:16 UTC

Area: area-app-model
Kind: bug
Repro: partial — issue is a follow-up to a discussion on PR #15691; no standalone repro, but the cited Add* APIs are inspectable in that PR's diff
Affected version(s): APIs introduced in PR #15691 (currently open; not yet shipped)
Severity: S3 — missing [ResourceName] attribute on new Add* APIs is a polish/consistency bug; analyzer/tooling support is degraded but core functionality is unaffected

Urgency: 🟡 vNext — recommend milestone 13.4
Reason: should be fixed alongside or shortly after PR #15691 lands; not in shipping bits so no servicing case

Suggested owner(s): @JamesNK (score high — dominant area-app-model PR author last 90d), backup @davidfowl
Evidence:

• @JamesNK merged many area-app-model PRs in last 90d (e.g. Use OrdinalIgnoreCase for EnvironmentVariableName comparer #17194, CLI: Print app host CLI log path when connected to a running app host #17168, Improve version log messages in CLI, AppHost and dashboard #17163, Use ASPIRE_APPHOST_LOGLEVEL instead of cascading Logging__LogLevel__Default #17071, Use arguments for built-in resource commands #17021, Handle non-interactive interaction service availability for resource commands #16973)
• PR Add Aspire.Hosting.Blazor integration for Blazor WebAssembly apps #15691 itself (the source of this follow-up) is authored by @javiercn but the [ResourceName] convention belongs to the broader app-model maintainers
• Reporter @IEvangelist is the issue author; excluded from owner suggestions

Confidence: medium
Needs human?: no — straightforward follow-up; owner can confirm scope

Dry-run mode — no labels or milestone applied. Reply /triage apply to promote, or edit and reapply.