Content Quality: Well-structured News article (Overview / What We Know / What We Don't Know / Technical Note), 673 words (within the News 400-1200 range), neutral and professional tone throughout, no AI self-reference, no sensationalism. Appropriate internal link to prior Herald coverage of Biome v2's type-aware linting, correctly using the singular /article/ path form that resolves.
Source Verification: Context: a prior submission on this exact topic (PR for 'ESLint Adds an Official Shell Script Linting Plugin...', submission 2026-11-20T12-33-44Z) was REJECTed for a pattern of quote-fidelity failures: one fully fabricated quote attributed to github.com/mvdan/sh, a quote misattributed to the wrong cited source, two altered quotes from the blog, and a spliced closing quote with four separate alterations, plus a rule-count error (claimed 10 but body text said 11 elsewhere) and only 9 of 10 rules enumerated. This is a materially different submission (different submission timestamp/hash/signature, re-researched, no mvdan/sh source used at all) on a story that never published, so it is not a duplicate review of merged content. Applied maximum scrutiny given that history. All 3 sources fetched successfully (status 200, no suspicious_patterns in manifest.json) and re-verified by decompressing each .html.gz and rehashing against manifest sha256 — all three matched exactly (source-0: db2798ac..., source-1: 802399e7..., source-2: 56af8556...). source-0.html.gz (eslint.org blog, 'ESLint now officially supports linting of shell scripts', published/updated 06 Nov 2026, byline Nicholas C. Zakas / ESLint Technical Steering Committee) — read in full as extracted plain text; confirms the July 2024 general-purpose-linter plan, prior JSON/Markdown/CSS support, the @eslint/shell introduction, Bash/POSIX/mksh dialect support, ESTree-style tree, mvdan-sh/shfmt parser lineage, inline-disable-comment example, and the byline/date. source-1.html.gz (github.com/eslint/shell README, full rule table) — read in full; confirms npm install command ('npm install --save-dev eslint @eslint/shell'), Node requirement '^20.19.0 || ^22.13.0 || >=24', 'Tested with ESLint v10', the three languages (shell/bash used by recommended config, shell/posix, shell/mksh), and critically the 10-row rule table: no-backticks/SC2006/fixable/error, no-expansions-in-single-quotes/SC2016/warn, no-ls-iteration/SC2045/error, no-unquoted-expansions/SC2086-46/fixable/error, no-unused-vars/SC2034/error, no-useless-cat/SC2002/error, no-useless-echo/SC2116/error, no-variables-in-printf-format/SC2059/error, require-cd-guard/SC2164/error, require-read-r/SC2162/fixable/error — exactly 10 rules, exactly as the article enumerates them, and no-expansions-in-single-quotes is indeed the only 'warn'-level rule as the article states. source-2.html.gz (github.com/eslint/shell/releases) — read in full; confirms v0.1.0 released 03 Nov 22:10 2026, v0.1.1 released 06 Nov 21:22 2026, v0.1.2 released 06 Nov 21:39 2026 (17 minutes apart, both same day as the blog post) — matches the article's claims of '0.1.0 on November 3... three days before the public announcement' and '0.1.1 and 0.1.2... tagged minutes apart on November 6... the same day as the blog post.' Minor observation (not a correction): the v0.1.0 release notes list all 10 rules as added in that initial release (0.1.1/0.1.2 are bug-fix-only releases), so the breakdown the article's 'What We Don't Know' section says the blog post doesn't specify is in fact determinable from the releases page the article itself cites elsewhere — the sentence is narrowly and accurately scoped to 'the blog post' specifically so it is not a false statement, but it slightly undersells information available from the Herald's own other cited source. Not corrections-worthy on its own. Anthropic disclosure: not required - the article's subject is ESLint's shell-linting plugin; Anthropic, Claude Code, and Bun are not the subject, headline, summary, or lead, and contributor_model (Claude Sonnet 5) is pipeline metadata, not an in-article credit line.
Factual Accuracy: All substantive claims (release date, dialect support, install/compatibility requirements, parser lineage, rule count and content, release-tag timeline, license/credit) trace to the cited sources and were independently re-derived from raw source text, not accepted from the writer's self-report. No hallucinated specifics found. The 'ten rules' claim and all ten rule descriptions were checked individually against the GitHub README's rule table and match exactly, including which single rule is 'warn' rather than 'error' and which rules are auto-fixable.
Overall Assessment: Clean, accurate News piece on a genuinely new topic for the Herald. All three sources read in full from verified-hash snapshots; every direct quote checked word-for-word against the raw source text and found verbatim; the specific quote-fidelity and rule-count/completeness failures that sank the prior submission on this same story are absent here and the writer's self-reported fixes independently verify. No corrections needed. Featured candidacy: 0 - a routine, incremental developer-tooling release (a new lint-rule plugin) of interest to a defined JS/shell-scripting audience but not a broad-impact or exceptional story.