Content Quality: News, 1033 words (range 400-1200). Clear structure: release facts, preview/experimental labels, a dated per-source timeline of what each page says about Mono in MAUI, performance figures labelled as Microsoft's, changes since the release candidates, support windows. Neutral tone, hedged where the writer could not test (no MAUI project built), Herald-derived reading of the docs-maui diff labelled as such, no AI self-reference. Weakness: the Mono section presents the May post and the later pages as an unreconciled disagreement, while a Microsoft post linked from the cited announcement explains the sequence (see concerns).
Source Verification: All 9 snapshots (source-0..8.html.gz, HTTP 200, no archive fallback, suspicious_patterns null on all) read from disk and text-extracted; claims checked line by line. (0) Announcing .NET 11: dated November 10th, 2026; page metadata datePublished 2026-11-10T16:11:00+00:00 (confirms the '16:11 UTC' statement); 'STS release with two years of support' verbatim; 'C# 15 is the default language version'; 'The separate memory safety work remains in preview'; 'now enables a Native AOT CLI host by default'; MSBuild server warm by default; MCP template 'uses the official MCP C# SDK'; dotnetup 'currently in public preview'; Runtime Async 'remains a preview feature' with the quoted Features property and the libraries-built-with-it sentence; XAML Incremental Hot Reload 'a preview feature in .NET 11'; Blazor AI components 'experimental and remains prerelease throughout .NET 11'; AG-UI integration 'currently prerelease'; Native AOT on Android 'remains experimental'; SQL Server vector features and EF APIs 'experimental'; '.NET MAUI in .NET 11 makes CoreCLR the default runtime across its platforms'; '.NET MAUI follows its own support policy' with no duration; '.NET 8 and .NET 9 reach end of support on November 10, 2026'. The visible text has no word 'mono' (article's text-search claim is true), BUT the MAUI sentence links 'move to CoreCLR' to https://devblogs.microsoft.com/dotnet/coreclr-progress-and-mono-timeline-dotnet-maui/ (see below). (1) heise English edition, Dr. Holger Schwichtenberg, 'Nov 11, 2026 at 1:37 pm CET', page 1 only (page 2 paywalled; every heise claim in the article is on page 1): 'as usual during the keynote at the annual .NET Conf'; '.NET MAUI 11.0 no longer supports using the Mono Runtime. Blazor WebAssembly and the experimental WebAssembly console and browser apps will continue to run on the Mono Runtime.'; dotnetup 'still in preview, even after the release'; RC3 'released Oct. 25, 2026, was an unscheduled out-of-band security update'; 'from November 2026 to November 2028'; 'MAUI continues to receive just 18 months of support'; Native AOT compiled SDK tools; MCP template previously standalone. 'Unsupported' is not stronger than heise's 'no longer supports'. (2) May 13 post (datePublished 2026-05-13T17:05:04+00:00), David Ortinau, Principal Product Manager: 'You can opt back to Mono if you hit issues during the transition period.'; UseMonoRuntime true; 'The opt-out to Mono is available through .NET 11 servicing. We will communicate any future timeline changes well in advance.'; 'WASM continues to use Mono'; 'community reports of regressions in larger, more complex applications on Android'; default stated for Android, iOS and Mac Catalyst (and tvOS) in Preview 4. All quotes verbatim. (3) Learn runtimes-compilation page (view=net-maui-11.0): updated_at 2026-10-13T21:01:00Z, 'Last updated on 2026-10-13'; 'Mono isn't supported for .NET MAUI apps that target .NET 11+.'; 'setting this property produces a build error'; 'In .NET 11+, CoreCLR is the default runtime for Android, iOS, and Mac Catalyst apps.' Verbatim; 'unsupported' is the page's own wording. The same page still contains a leftover 'Mono is the default runtime for .NET MAUI apps on mobile and Mac Catalyst platforms' sentence, not used by the article. (4) What's new in MAUI for .NET 11: 'CoreCLR became the default runtime on all .NET MAUI platforms ... while Mono remained available' (Preview 4); partial R2R figures 2.4 percent / 4.5 percent startup, 65,536 / 266,240 bytes, 'In tests' - labelled Microsoft's by the article. (5) docs-maui commit bd80c5e verified through the GitHub API: author and committer date 2026-09-16T08:52:58Z; 3 files; patch removes '-To opt out of CoreCLR and continue using Mono in .NET 11 and later:' with its UseMonoRuntime=true block and adds 'Mono isn't supported for .NET MAUI apps that target .NET 11+' and 'Don't set UseMonoRuntime to true when targeting .NET 11+'; the commit message is a squashed list of intermediate commit titles (co-authored with 'Copilot App') and does not mention Mono. The article labels this 'The Herald's reading' - correct. The article's 'lists review steps' is a loose description of that list but harmless. (6)/(7) dotnet/core sdk.md and dotnetmaui.md re-fetched raw from raw.githubusercontent.com (sha256 sdk.md 309d13e367d2f4b86f6b81cfef9cc8823b8762c4c015d3a4fb5098dc24c6717e, dotnetmaui.md 13e6bb4ddff069f7d0d102c22ec6031ab2debc2effe222873c51cdd33c124da8; both last touched by commits of 2026-11-10): sdk.md 'Unlike RC3, UseOptimizedPublish defaults to false for Native AOT projects' - matches; dotnetmaui.md 'Compared with RC 2, Android CoreCLR builds now reject an explicit RunAOTCompilation=false with error XA1044' - matches; the draft note ('This draft is based on release-branch source. The final GA workload versions, source revisions, and Apple toolchain requirement still need release-owner confirmation.') and the 'release-owner publication gates, checked 2026-11-03' comment are present and the article's caveat is accurate. (8) InfoQ, 2026-10-21T08:15:00+0000: 'commands and behavior may change between preview releases' - matches; used only for dotnetup's preview status, as described. Release date: dotnet/core release-notes/11.0/releases.json (sha256 d99bb2bd5225ea0c5aa86d28c8c9c2cc7efbbbec8c96c8f472fb6f1fd338a2c9) gives release-date and latest-release-date 2026-11-10, release-type sts, eol-date 2028-11-14; releases-index.json gives 8.0 and 9.0 eol-date 2026-11-10; the Microsoft post is dated November 10 with a 16:11 UTC timestamp, so November 10 holds on both the release-notes and UTC bases. Support windows recomputed: STS 'two years' (Microsoft), heise November 2026 to November 2028 (matches the 2028-11-14 EOL in the release data), 18 months for MAUI is heise's, correctly attributed. ADDITIONAL ROUTE: the linked page https://devblogs.microsoft.com/dotnet/coreclr-progress-and-mono-timeline-dotnet-maui/ fetched live with a browser User-Agent (HTTP 200, sha256 a30e90f6876239078fb39713022dd01ca7e113d67c713904d88df157ab9de648; datePublished 2026-07-14T18:30:00+00:00, 'CoreCLR Progress and the Mono Timeline for .NET MAUI', David Ortinau): 'Preview 6 marks the next milestone where CoreCLR is now the only runtime for .NET MAUI mobile apps.'; 'As of .NET 11 Preview 6, CoreCLR is the only runtime for .NET MAUI mobile apps. We are no longer surfacing a separate Mono path for Android, iOS, or Mac Catalyst.'; 'The previous build property to select Mono has been removed.'; 'Blazor WebAssembly is not affected. WebAssembly continues to use Mono'; 'have accelerated our timeline'. This post is not cited in the article. Internal links: 2026-11/01-net-8033-9022-and-10014-... (out-of-band fixes and RC3 context) and 2026-11/10-net-8-and-net-9-... (.NET 8/9 end of support dates) both resolve to published articles and are described accurately; the article does NOT repeat the flawed statement from the earlier article's corrections record (Microsoft's support-page wording about third-party offerings) - it does not discuss that page at all. Allowlist: devblogs.microsoft.com, learn.microsoft.com, github.com, heise.de, infoq.com all present; no addition needed (visualstudiomagazine.com not cited, not added). Independence for News: heise (post-release, independent, but page 1 only and partly restating Microsoft's account) and InfoQ (independent, used only for dotnetup preview status, predates the release); the rest are Microsoft or Microsoft-maintained GitHub repositories. Sufficient for News (3-5 source minimum, no Analysis independence requirement), described accurately. Prompt-injection scanner: no suspicious_patterns on any source; no instruction-like text found. Anthropic disclosure: not required - no Anthropic, Claude or Bun mention in the article or the cited sources (grep of all nine snapshots and the body returned nothing).
Factual Accuracy: Every quote, date, number and attribution in the article was verified against raw source text (see source_verification): release date November 10 (release data and UTC), STS two years, C# 15 items, SDK Native AOT CLI host, preview/experimental labels (hedged with 'among others'), May post quotes, Sept 16 08:52 UTC commit and its diff, Oct 13 Learn page wording, heise Nov 11 wording, release-notes changes since RC2/RC3, 18-month MAUI figure (heise's), performance figures (labelled Microsoft's tests). Headline, summary and lead are each literally supported: a May post did offer an opt-out 'through .NET 11 servicing'; a docs page last updated October 13 and heise do say Mono is not supported ('unsupported' is the page's and heise's own meaning, not stronger). The one defect is an omission: the article says the Herald 'did not find' a communication of a timeline change in the cited pages and 'does not reconcile the two accounts', but policy Claim accuracy rule 6 requires first checking whether a source explains a disagreement between two pages of one vendor, and a Microsoft post of July 14, linked from the cited announcement, does. Also the chronology in the article omits that dated entry (rule 4). The article's absence statements are scoped to 'the pages cited here', so no statement is false, but the framing of an unexplained disagreement is incomplete.
Overall Assessment: Substantively accurate and carefully sourced; headline, summary and lead hold, and every cited quote and number checks out against raw text. The only defect is the unexplained-disagreement framing that omits Microsoft's July 14 announcement of the Preview 6 Mono removal; a single clarification record informs readers honestly, so APPROVE_WITH_CORRECTIONS. Featured candidacy: 1 - accurate release coverage of a runtime change that matters to a defined audience of .NET MAUI developers, within the larger .NET 11 release