Content Quality: Well-structured News piece (628 words, within 400-1200). Overview, What We Know (three lead features plus a bulleted secondary list) and What We Don't Know. Neutral tone, no AI self-reference, no promotional language.
Source Verification: Read both snapshots from disk (gunzip) and verified against the article. manifest.json: both sources status 200, no archive fallback, suspicious_patterns null for both (no injection text to evaluate). source-0.html.gz (clickhouse.com/blog/clickhouse-release-26-09): confirms 'The ClickHouse 26.9 release contains 56 new features, 135 performance optimizations and 464 bug fixes'; APPEND INCREMENTAL for refreshable MVs, 'Instead of scanning the entire source table on every refresh, ClickHouse processes only the rows committed since the previous refresh', copy append-only data to another ClickHouse table or replicate a MergeTree event stream into Iceberg, contributed by Smita Kulkarni; block-number and block-offset columns 'provide the cursor'; 'For an Iceberg target, ClickHouse stores the incremental cursor in the snapshot summary'; 'If ClickHouse restarts, the next refresh resumes from that position instead of replaying the same events'. CREATE TOKEN (Alexey Milovidov): 'time-limited credential for applications, scripts, CI jobs, and agents without exposing or replacing their main password'; 'A token never grants more privileges than the user already has, and it stops working when it expires or if the user is removed'; 'If you don't provide a VALID UNTIL or VALID FOR, the default lifetime is 30 minutes'; 'ClickHouse displays the token only once'. LIMIT boundary conditions (Zakhar Kravchuk and Nihal Miaji): 'a capability that, to our knowledge, is not currently available in any other database' - the article quotes this verbatim and explicitly attributes it to ClickHouse ('That is ClickHouse's own claim and was not independently verified'); AFTER inclusive, UNTIL exclusive, ALL reapplies; the LIMIT 5 AFTER status >= 500 example 'starts at the first 5xx response and returns five requests'. Also confirmed: min/max/count from part statistics and use_statistics_for_min_max_aggregation; max_bytes_before_external_distinct and max_bytes_ratio_before_external_distinct = 0.5 ('half of the memory available'); JSON bracket syntax; Time offsets on DateTime; PromQL expansion with PromQL and TimeSeries engine in private preview on ClickHouse Cloud. source-1.html.gz (presentations.clickhouse.com/2026-release-26.9/): confirms 56/135/464 counts and the exact syntax 'CREATE TOKEN VALID FOR INTERVAL 7 DAY GRANTS (SELECT ON default.sales);'. Its LIMIT AFTER/UNTIL, APPEND INCREMENTAL and Iceberg slides are consistent with the blog and add nothing the article relies on. The 'any other database' claim does not appear in the slides. No unique factual claim rests solely on the slide deck: the counts are duplicated in the blog, and the only slide-only element is the CREATE TOKEN syntax example, which the article correctly attributes to the slides. The internal link to the ClickHouse 26.5 article resolves to an existing published article (src/content/articles/2026-05/22-clickhouse-265-ships-38-new-features-and-51-performance-optimizations-in-its-spring-release.md).
Factual Accuracy: Every specific (counts, setting names, default 30 min lifetime, 0.5 ratio, contributor names, private-preview status) traces to the cited sources. The only direct quotes (release counts and the 'not currently available in any other database' claim) are verbatim. Headline, summary and lead are each backed by the blog. Both sources are vendor-owned; the article discloses this in What We Don't Know and flags the uniqueness claim as unverified vendor assertion. Minor observation: the summary line lists 'APPEND INCREMENTAL refreshable views for Iceberg' while the blog also presents ClickHouse-to-ClickHouse copying; this is a compression, not an error.
Overall Assessment: Accurate, well-attributed release coverage with appropriate vendor-source caveats. APPROVE, no corrections needed.