Content Quality: News piece, 628 words (range 400-1200). Clear structure: overview, what 26.13.0 changes, what the alpha lists, open questions. Alpha is labelled an alpha/pre-release throughout and nothing is stated as final. Title is 159 characters, over the 150-character cap in write-article.md (script warning); this is a style issue that cannot be fixed without editing signed content and is not a factual error.
Source Verification: Read snapshots source-0.html.gz (nodejs.org/en/blog/release/v26.13.0, HTTP 200) and source-1.html.gz (nodejs.org/en/blog/release/v27.0.0-alpha.0.0.0, HTTP 200); manifest suspicious_patterns null for both, no injection text found. Live re-fetch of both URLs (raw HTML via curl, HTTP 200) matched the snapshots on every checked string. SOURCE 0: post heading dated '2026-10-28, Version 26.13.0 'Lithium' (LTS), @richardlau' (date confirmed). Quotes verbatim: 'This release marks the transition of Node.js 26.x into Long Term Support (LTS) with the codename 'Lithium'. It will continue to receive updates through to the end of April 2029.' (article quotes 'will continue to receive updates through to the end of April 2029' - exact); 'Other than updating metadata, such as the process.release object, to reflect that the release is LTS, no further changes from Node.js 26.12.1 are included.' (exact); libatomic note verbatim. The post gives no Active LTS / Maintenance LTS dates and the article does not claim any. SOURCE 1: post heading 'Node.js 27.0.0-alpha.0.0.0 (Alpha)', '2026-10-29, Version 27.0.0-alpha.0.0.0 (Alpha), @RafaelGSS' (date confirmed). The post's version string is 27.0.0-alpha.0.0.0, NOT 27.0.0-alpha.0 as used in the title, summary and one body heading; the body links the correct slug and uses alpha.0.0.0 once. 'The V8 engine is updated to version 15.6.75.13, up from 14.6 in Node.js 26' (exact). Feature lists (Math.sumPrecise, Intl.Locale.prototype.variants, Iterator.prototype.join/includes, Iterator.zip/zipKeyed; experimental import defer, Immutable ArrayBuffer, RegExp buffer boundaries with the stated flags) match. Heap quote ('half of the physical memory clamped between 256 MB and 4 GB, and memory held by Buffer and ArrayBuffer instances now counts toward the heap limit') verbatim; guidance to set --max-old-space-size confirmed. Serialization, asm.js/--wasm-<name> rename, heap snapshots twice as long/large, error.stack prototype chain, PowerSort stable, 'full changelog ... will be shared soon' all confirmed. Semver-major entries verified individually: 'build: require OpenSSL 3 or later' (#64777; wording is 'OpenSSL 3 or later', matching the article), 'remove the bundled FIPS provider build', 'crypto,https,tls: end OpenSSL engine support', 'domain: runtime-deprecate the module', 'fs: implement glob natively', 'http: increase keepAliveTimeout default to 65 seconds', 'http: make req.headers have a null prototype', 'http2: increase default window sizes', 'lib,src: remove --no-experimental-websocket CLI flag', 'build: downgrade Intel macOS support to experimental', 'src,lib: add --allow-env permission', 'deps: upgrade npm to 12.1.0', 'net: add experimental net/promises API'. Semver-minor: fs mkstemp(), zlib crc32c, 'vfs: unflag'. The post says nothing about Node.js 27 stable or LTS dates; the 'What We Don't Know' section is accurate. Internal link to the Herald's 26.12.1 security article resolves (src/content/articles/2026-10/22-nodejs-security-releases-26121-...md exists) and its description (ten CVEs, four rated High, Brotli decoder out-of-bounds write, releases 26.12.1/24.22.1/22.23.4) matches that article's title and summary. Source independence: both sources are first-party nodejs.org release posts; nothing independent corroborates them. Two same-site sources is thin for a News piece, but the claims are release facts attributed directly to the project, so acceptable. nodejs.org is on config/source_allowlist.txt (line 1137). No orphan URLs: body external links = the two sources. Article does not mention Electron 45, so no Node-version consistency issue.
Factual Accuracy: All numbers, dates, quotes and attributions traced to the two posts. One imprecision: the headline and summary call the alpha '27.0.0-alpha.0' while the post's own version is 27.0.0-alpha.0.0.0 (the article body links it correctly and shows the full string once). Handled via a clarification in the corrections record. The framing 'consecutive days' (2026-10-28 and 2026-10-29) is correct.
Overall Assessment: Accurate, well-sourced release coverage with one version-string clarification warranted and an over-length title. Featured candidacy: 2 - LTS promotion of a major runtime plus first look at the next major's V8 and OpenSSL changes interests a broad developer audience