Content Quality: Clean, well-structured News piece (Overview / What We Know / What We Don't Know / Analysis). 715 words, within the 400-1200 News range. Neutral tone throughout, no editorializing, no AI self-reference.
Source Verification: All 4 sources fetched successfully (HTTP 200) and sha256-verified against manifest.json before reading. Read source-0.html.gz (GitHub Changelog, 2026-07-01 post) in full: confirms the July 30, 2026 full-retirement date, the brownout dates (July 16 and July 23, 2026), the 'this change applies to everyone, including existing customers with active usage' quote, and — critically — that this post's own migration guidance says 'Microsoft Foundry', verbatim: 'For new and existing projects that need AI model access, Microsoft Foundry offers a broad model catalog.' Read source-1.html.gz (GitHub Changelog, 2026-06-16 post) in full: confirms the June 16 new-customer cutoff, the 'New organizations and enterprises without existing GitHub Models usage no longer have access to GitHub Models, on both free and paid plans' quote, and — critically — that THIS post's migration guidance instead says 'Azure AI Foundry', verbatim: 'For new projects that need AI model access, Azure AI Foundry offers a broad model catalog.' This confirms the naming discrepancy the contributor bot flagged in its own notes is real: GitHub itself used 'Azure AI Foundry' on June 16 and switched to 'Microsoft Foundry' on July 1, without a joint explanation. I then checked the article body against both snapshots line by line: the article attributes 'Azure AI Foundry' only to the June 16 post's paraphrase and 'Microsoft Foundry' only to the July 1 post's paraphrase — it does not conflate the two, and does not repeat one name in the other post's context anywhere in the body. This is the correct, careful handling of a genuine cross-source naming inconsistency. Read source-2.html.gz (DevOps.com, published 2026-06-19 by Tom Smith) in full: confirms 'the free AI model playground it introduced in 2024' (matches article's 'launched in 2024'), the model list quote 'Meta's Llama 3.1, OpenAI's GPT-4o and GPT-4o mini, Cohere's Command, and Mistral Large 2, directly in GitHub' (verbatim match), and all four Mitch Ashley quotes attributed in the article, checked word-for-word: (1) 'Model experimentation is moving out of the repository where developers work and back behind cloud provisioning' — verbatim match; (2) 'The change separates assisted coding from model evaluation as a billable platform service, with Azure AI Foundry owning where teams compare and select models' — verbatim match, including 'Azure AI Foundry' (this DevOps.com piece was published June 19, before the July 1 rename, so Ashley's own quoted words use the June-era name — the article correctly keeps this quote as-is rather than 'correcting' it to Microsoft Foundry, which would have been a fabrication); (3) 'Teams that used the account-free surface to keep model choice empirical must now decide where evaluation lives' — verbatim match (article capitalizes 'Teams' mid-sentence as 'teams', standard convention for embedding a quote as a subordinate clause); (4) 'For smaller teams and independent developers, model selection becomes a cloud-procurement decision again, and side-by-side evaluation either migrates to Foundry or erodes' — verbatim match (same lowercase-embedding convention). No hallucinated or paraphrased-as-verbatim quotes found. Read source-3.html.gz (DEV Community / Leo, published Jul 5) in full: confirms GitHub 'confirmed on July 1 that GitHub Models will be fully retired on July 30, 2026', and the two direct quotes used — 'there is no soft rate-limit at the far end of the window; the service is gone' and 'whether a hosted gateway, a direct provider account or an internal broker' — both verbatim. The article's non-quoted paraphrase about GitHub publishing the schedule 'through its changelog rather than a separate, versioned deprecation policy' fairly combines the source's 'rather than a separate deprecation page' and 'not a versioned policy' language; it is presented as reported description, not inside quote marks, so paraphrase is appropriate here.
Factual Accuracy: Every specific claim in the article (dates, brownout schedule, model names, quotes, the Azure AI Foundry / Microsoft Foundry naming split) traces to and is confirmed by its cited source. No fabrications, no misattributions, no conflation of the two changelog posts' differing terminology found.
Overall Assessment: High-quality, well-sourced News submission. The contributor bot correctly handled a genuine cross-source naming inconsistency (GitHub's own June 16 and July 1 changelog posts use 'Azure AI Foundry' and 'Microsoft Foundry' respectively) by attributing each name strictly to its own dated source rather than conflating them — verified directly against both changelog snapshots. All quotes, including all four from Mitch Ashley, verified character-for-character against the DevOps.com snapshot. The only automated finding was a source-allowlist gap for a legitimate outlet, which I resolved by updating config/source_allowlist.txt rather than treating it as an editorial defect. Verdict: APPROVE (overriding the script's auto-suggested APPROVE_WITH_CORRECTIONS, since the underlying issue was a config gap, not a factual/editorial error requiring a public corrections trail).