Fix AI-generated content in .NET 11 Preview 1 runtime release notes

[Copilot]

Fix AI-generated content in .NET 11 Preview 1 Release Notes

• Review current runtime.md release notes
• Address PR feedback r2790358337 about CoreCLR WebAssembly section
  • Shrunk section to single mention that it's foundational work not yet ready for use
  • Updated overview section to be consistent
  • Removed WebAssembly interop and performance sections (also part of foundational work)
  • Folded WebAssembly JIT section into CoreCLR on WebAssembly section
• Simplified Interpreter (CoreCLR) section to match foundational work pattern
  • Reworded to concise statement about foundational work not ready for use
  • Removed detailed PR lists and subsections
  • Updated feature overview bullets to match actual content
• Add links to epic issues:
  • Runtime async epic: .NET Runtime-Async Feature runtime#109632
  • CoreCLR WASM epic: .NET WebAssembly on CoreCLR interpreter runtime#121511
  • CoreCLR interpreter epic: CoreCLR Interpreter runtime#112748
  • WASM-targeting JIT tracking issue: [User Story] RyuJIT for WebAssembly (Wasm) runtime#121141
• Improve clarity and remove AI slop
  • Removed "New cDAC APIs for profiling and inspection" section
  • Removed entire "Diagnostics (DAC / cDAC)" section
  • Established consistent pattern for foundational work sections
• Validate changes with markdown linting
• Validate links work correctly (all return HTTP 200)
• Fix minor consistency issues (Features header)
• Add clarification about core libraries not using runtime-async in Preview 1

Summary

This PR addresses feedback about AI-generated content in the .NET 11 Preview 1 runtime release notes by:

1. Establishing a consistent pattern for foundational work: Sections for WebAssembly (CoreCLR) and Interpreter (CoreCLR) now follow the same concise format - clearly stating they are foundational work not ready for general use in Preview 1, with links to epic issues for tracking progress.

2. Removing implementation details: Deleted detailed PR lists and subsections (WebAssembly interop/performance, Interpreter subsections, cDAC APIs, entire Diagnostics section) that provided no value to users who cannot try these features yet.

3. Adding clarity: Added epic issue links throughout, clarified that core runtime libraries are not yet compiled with runtime-async support, and ensured feature overview bullets match actual section content.

4. Improving readability: The release notes now focus on what users can actually experiment with (Runtime Async with detailed guidance) versus what's still foundational work (WebAssembly, Interpreter).

Original prompt

---

This section details on the original issue you should resolve

<issue_title>.NET 11 preview 1 release notes</issue_title>
<issue_description>### URL(s)

https://devblogs.microsoft.com/dotnet/dotnet-11-preview-1/

Description

It seems like with every .NET release the announcements are getting changed, and this year is no difference 😅

Announcement

I had to see the new .NET 11 preview release on Discord, because there was no post in https://github.com/dotnet/announcements
For all the .NET 10 releases, we had an announcement (dotnet/announcements#344); does this mean we won't get these anymore with .NET 11?

Release notes itself

The release notes are AI generated, an you can tell without even looking at the PR.
I can see in the PR (#10221) that there were some comments, but for the runtime the comments came too late I think (#10221 (review)).

.NET 10 had meaningful changes, and showed examples:
https://github.com/dotnet/core/blob/main/release-notes/10.0/preview/preview1/runtime.md

.NET 11 combines all the PR's (e.g. with CoreCLR and WebAssembly) without any information. "CoreCLR is now a target in the WebAssembly SDK and browser-hosted CoreCLR"; what does this mean in preview 1? Is it already done? How can I try this out? Do I need to open all these PR links to figure out how it works?

At this point it's easier to look at Epic issues then reading the release notes, because this gives an insight what works and what still needs to be done...:

• Runtime async: .NET Runtime-Async Feature runtime#109632
• CoreCLR WebAssembly: .NET WebAssembly on CoreCLR interpreter runtime#121511

Comments

With .NET 10 releases we could comment in GitHub discussions: #9763
With .NET 11 we can only comment in the devblogs.microsoft.com? The problem is that I don't want to sign in with my Microsoft account to place a comment, and there is no way to sign in with GitHub. Hence why I made this issue.</issue_description>

<agent_instructions>Fix AI slop in .NET 11 preview 1 release:

• Address .NET 11 Preview 1 Release Notes #10221 (comment)
• Add links to epic issues for CoreCLR wasm, interpreter, and runtime-async
  </agent_instructions>

Comments on the Issue (you are @copilot in this section)

@jamesmontemagno Thanks for the feedback. I have created the discussion: https://github.com//discussions/10260

Simply forgot the /announcements, wont forget in the future. dotnet/announcements#382</comment_new>
<comment_new>@jamesmontemagno
Will give feedback to the team on the release notes themselves. Appreciate the feedback.</comment_new>
<comment_new>@agocke
Note: the runtime async section does give extra info and I wrote it the old fashioned way (hence the typo 🙃). In particular the environment variable requirement for .net 10 is no longer necessary for 11</comment_new>

• Fixes .NET 11 preview 1 release notes #10258

---

💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.

[agocke]

LGTM, thanks for the issue link to runtime-async