Provenance Record

Clear News structure (Overview, What Shipped, Architecture, Enterprise Controls, What We Don't Know), 447 words, neutral tone, no AI self-reference. Not human-requested.

Read all four gunzipped snapshots from disk (source-0..3.html.gz), all status 200, no archive fallback, suspicious_patterns null for all four (no injection text found). source-0 (heise.de, Moritz Foerster): confirms 'Microsoft has made WSL Containers (WSLC) generally available', wslc.exe builds/starts Linux containers and Windows apps can do the same via an API, no separate engine, alias container.exe, Docker-syntax commands (wslc run/build/container list), NuGet Microsoft.WSL.Containers for C/C#/C++, WSL 3.0.1 released September 29, Build 2026 early June, preview June 29 with WSL 2.9.3, new commands (container restart, container cp via tar, system info, events), health checks, default-session storage path, Intune settings 'Allow WSL containers access' and 'WSL containers registry allow list' (verbatim), Defender for Endpoint, Lazywslc and WinUI 3 WSL Container Desktop, Compose as most requested with 'Microsoft has not provided a timeline'. source-1 (helpnetsecurity.com, Sept 30): confirms GA, Intune enable/disable and registry restriction, Defender for Endpoint coverage, VS Code dev containers and Aspire integrations, Compose as top request with compose.yaml running unchanged. source-2 (devblogs.microsoft.com/commandline, Pierre Boulay, Sept 29): confirms wslservice.exe creating child wslcsession.exe running on behalf of the calling user with isolation between sessions, virtiofs about twice as fast as plan9, Consomme networking sending VM traffic via a virtio queue to a Windows process on behalf of the user with VPN/firewall compatibility, and 'WSLC is open source! Head over to microsoft/WSL'. source-3 (github.com/microsoft/WSL/releases/tag/3.0.1, released 29 Sep 17:18): contains the exact sentence 'WSLc is generally available.' and 'generally available today', confirming version 3.0.1 and the Sept 29 date. Both direct quotes verified verbatim and correctly attributed: 'WSLc is generally available.' (GitHub release) and the two Intune setting names (heise). The GitHub release links the un-allowlisted blogs.windows.com announcement, but the article neither cites nor relies on it: GA, date, version, CLI and API claims are each independently supported by allowlisted sources (heise, GitHub release, devblog). Allowlist: heise.de, helpnetsecurity.com, devblogs.microsoft.com and github.com are all present in config/source_allowlist.txt.

All specifics trace to cited sources: GA, Sept 29, WSL 3.0.1, wslc.exe, container.exe alias, NuGet API, architecture details, Intune/Defender controls, integrations, Compose gap. Attributions to heise, Help Net Security and the Microsoft devblog match which snapshot actually contains each claim. Minor note: the Windows-API-for-native-apps claim is in heise and Help Net Security, not in the devblog or release page, and is attributed to heise. Every URL in the body is in article.sources and vice versa.

Clean, well-sourced news article with verbatim quotes and no unsupported claims. Submission file and repo state contain nothing unexpected (single submission file in PR; no stray files in working tree; signature and hash valid). Approved.