Content Quality: Concise, well-structured Briefing (547 words, within the 300-800 range) with Overview, What We Know, The Two Previewed APIs and What We Don't Know sections. Neutral, attributed to WebKit throughout; no AI self-reference.
Source Verification: Read source-0.html.gz (webkit.org/blog/18486/webkit-features-for-safari-27-1/, HTTP 200) and source-1.html.gz (developer.mozilla.org/en-US/docs/Web/API/Device_Posture_API, HTTP 200) from the committed snapshots, then re-fetched both live via WebFetch; live results matched the snapshots. suspicious_patterns is null for both sources; no injection-like text found. Hostnames webkit.org (config/source_allowlist.txt line 844) and developer.mozilla.org (line 2732) are on the allowlist by exact hostname. WEBKIT (first-party, Apple-maintained project blog): byline reads 'Oct 23, 2026 by Jen Simmons' - matches the article (date and author). Verbatim quotes confirmed: 'Today iPhone Duo arrives, and with it, Safari 27.1.'; 'big news' (post: 'The "big news" here is no news'); 'the same WebKit engine and the same web technologies as every other iPhone'; 'there may still be time to evolve how they work'; 'a better way' (post: 'if there's a better way to accomplish the same result'). Post sentence: 'Safari 27.1 on iPhone Duo includes a preview of the Device Posture API and the Viewport Segments API, available behind feature flags' and 'Both are supported in Safari 27.1 on iPhone Duo as a developer preview behind feature flags' - supports 'Previews ... Behind Feature Flags' in the title. Viewport: 'the viewport width (in CSS pixels) in Safari 27.1 can range from 382 to 951. And the height can range from 368 to 902' - confirmed; 382 is outer display portrait (SVH 580, LVH 618), 951 is inner display landscape with one tab (SVH 585, LVH 620), two side-by-side windows 385 (571/609); all table values in the article match. The range is across both displays and poses, as the article states. Enable path 'Settings > Apps > Safari > Advanced > Feature Flags' with 'Device Posture API' and 'Viewport Segments API' - confirmed. PDF two-page behavior, Xcode 27.1 Device Hub simulator, UA-sniffing advice, folded/continuous definitions, device-posture media query, navigator.devicePosture, horizontal/vertical-viewport-segments media queries, six env variables (width, height, top, right, bottom, left; column then row index) and window.viewport.segments returning DOMRect array - all confirmed. Open question: the post says web content 'does not currently extend to fill the space behind these controls' on the outer display, names viewport-fit="cover" as one possibility and says 'We are investigating if there's a better way' and 'stay tuned' - correctly presented as undecided, no date given. No ship date for unflagged APIs is given - confirmed. MDN (live page, last modified Jan 5, 2026 by MDN contributors): carries 'Limited availability' (not Baseline) and 'Experimental' banners; states 'Current browser developer tools enable emulating foldable devices, but don't include emulation of partially folded devices - only fully open or closed - so they will always return continuous'; spec entry 'Device Posture API #dom-deviceposture'; See also links to Viewport Segments API. The article's MDN-based claims (experimental; devtools always return continuous) match the page as it reads now. The article makes no claim about browser support or spec status beyond that; MDN's compatibility table is JavaScript-rendered and not in the snapshot, and the article does not rely on it. The MDN page predates Safari 27.1 and does not mention Safari; the article does not claim otherwise. Release status: the post itself states 'Today iPhone Duo arrives', so describing the device as arrived/released is source-supported. Internal link /article/2026-10/06-apple-opens-app-store-submissions-for-iphone-duo-apps-and-points-developers-to-xcode-271 resolves to a published article (src/content/articles/2026-10/06-apple-opens-app-store-submissions-...-xcode-271.md) whose summary says apps can be submitted ahead of the October 23 launch; described accurately as App Store submissions opening. Orphan check: body URLs (two external, both in article.sources) and one internal link; no orphan URLs and no unused sources.
Factual Accuracy: Every number, date, quote, attribution and API name traced to the WebKit post; the two MDN-based statements match the current MDN page. Headline, summary and lead are each backed by the WebKit post. No unsourced claims found. Minor note: the article uses the phrase 'previously covered' for the internal link, which is accurate.
Overall Assessment: Accurate, well-attributed Briefing on a first-party WebKit post with one supporting MDN reference; all claims, quotes and figures verified against raw text and live re-fetch. Approve. Featured candidacy: 1 - solid, accurate coverage of a first-party Safari/WebKit post for web developers targeting a new foldable, but a niche, preview-stage story