Content Quality: Well-structured News piece using the standard Overview / What We Know / User Reaction / What We Don't Know format. Neutral, factual tone throughout; no editorializing. All three body sections are clearly tied to one of the three cited sources, and the article correctly frames the story's second half (user backlash) around Figma's own staff acknowledgment that the missing-preview complaint was 'the single most common piece of feedback since folders shipped' -- so the headline's 'wave of complaints' framing is directly sourced, not editorializing.
Source Verification: Read all 3 source snapshots in full from sources/2026-09/figma-ships-nested-folders-then-fields-a-wave-of-complaints-over-lost-file-previews/ after gunzip and sha256 integrity verification (all three hashes matched the manifest exactly; all three fetched at 200 status, none via archive_fallback). (1) source-0.html.gz (figma.com/blog/code-craft-and-the-making-of-nested-folders/) -- confirmed the Ethan Adams, Cai Charniga, and Friends-of-Figma quotes verbatim, and the 'long-requested feature ... rethinking Figma's underlying content and permissions model' quote verbatim. Also found and decoded a ~1768-character run of zero-width Unicode characters (U+200B/U+200C/U+200D/U+FEFF) embedded in the raw HTML around the figure caption; decoding as 2-bit-per-character base-4 yields the literal JSON string {"origin":"sanity.io","href":"https://figma.sanity.studio/intent/edit/mode=presentation;id=1ea3313d-..."} -- this is Sanity CMS's documented 'stega' visual-editing metadata encoding (maps rendered DOM text back to CMS field paths for Figma's editorial team), not an instruction directed at an AI agent and not a prompt-injection attempt; it contains no imperative language of any kind, only a CMS content-authoring URL. Manifest correctly shows suspicious_patterns: null for this source since the regex scanner does not target zero-width steganography and this payload contains no injection-style phrasing to match anyway. Noting for the record since it could look alarming on casual inspection. (2) source-1.html.gz (help.figma.com file-management article) -- confirmed the 10-level nesting depth, the Starter/Professional/Organization/Enterprise plan tiers, the removal of the 'View only' access tier, and the Inherited/Limited replacement states, all verbatim. (3) source-2.html.gz (forum.figma.com thread) -- confirmed Tom Reem's Aug 3 and Aug 17 posts verbatim, and checked every user quote/date pair against the raw thread: Tim_hfg1 (Aug 6), Angel Martin (Aug 10), Irine (Aug 10), Apolline (Aug 11), Alejandro Mejias (Aug 13), Arthur (Aug 16) all verbatim and correctly dated. One discrepancy found: MattFannin's Aug 11 quote is rendered in the article as 'The folder colours feature does me feel a little colour blind...' but the source text reads 'The folder colours feature does make me feel a little colour blind...' -- the word 'make' was dropped from a direct quote. This is a body-section quote (User Reaction), not part of the headline/summary/lead, and is a single, isolated word-drop rather than a pattern of fabrication -- treated as a corrections-eligible misquote per the APPROVE_WITH_CORRECTIONS criteria in review-submission.md ('a direct quote inside quote marks paraphrases rather than reproduces the source exactly').
Factual Accuracy: All numeric/structural specifics (10-level nesting depth, Starter=1 folder, Aug 3 2026 rollout start date, 'a few weeks to roll out to all users', the two-state Inherited/Limited permissions model, the specific API endpoints and 404 behavior reported by Arthur) trace exactly to the cited sources. No hallucinated statistics or unsourced specifics found. The single factual issue is the MattFannin misquote documented above.
Overall Assessment: Substantively strong, well-sourced News piece with accurate specifics and neutral tone. Verdict is APPROVE_WITH_CORRECTIONS on the strength of one isolated word-drop inside a direct quote (MattFannin) -- not because of the automated allowlist warning, which was verified as a false concern after manually confirming all three sources are Figma's own legitimate primary sources for a story about Figma itself. A single corrections note fully and honestly covers the one issue found; nothing here rises to REJECT.