Content Quality: News piece, 847 words by raw count and 847 with link URLs stripped (News range 400-1200: pass). Title is 133 characters (cap 150: pass). Structured by topic, every paragraph attributed to the Solid project's own release notes, with a closing 'What the notes do not say' section. No internal links (all links are github.com release pages). Minor wording nit: 'a host-placed bootstrap from generateHydrationScript(), which they say includes islands hosts such as Astro' reads as if the function includes hosts; the notes' parenthetical lists islands hosts such as Astro as examples of hosts that place such a bootstrap. Not a factual error.
Source Verification: All four manifest snapshots exist, are HTTP 200, and contain the full release body (not page chrome): source-0.html.gz ([email protected]) confirms the a405039 'Hydration key miss' entry (#3972), the d966729 render-effect/projection retry entry, the 25935fe onHydrationEnd entry (@experimental, #4000) with the verbatim sentence 'Intended for test tooling and markers, not for branching what the app renders', and the -686 B and -2,550 B minified figures. source-1.html.gz (@solidjs/[email protected]) confirms the e5a4c8e hydrate() mid-parse entry (#3971, ledger/marker script, DOMContentLoaded fallback, generateHydrationScript hosts never park), the 22f942d 'New server API (@experimental): setLinkClaim(handler)' entry (#3878, ssrLinkClaim(attrs), hasServerLinkState()), the 617d195 registerElementClaim options entry (default ["href", "action"]), the a497d4b anchor JSX types removal ('Types only'), be845cb Server-Timing (#3985), 06c7717 server component no-store and the frames/server export removal ('The entry is experimental'), 39411bd useHead \u003C escaping, abe12fc collectSlots 14.2 -> 5.4 ms on the HN story page (652 occurrences, 17k comments; single measurement, no run count given, article labels it so), and -1,165 B minified. source-2.html.gz (@solidjs/[email protected]) confirms 49a765c fallback once per show (#3991), 5a26ebe awaited refresh() never settling, ef1c297 affects(store) TypeError (#3891). source-3.html.gz (rc.14) was read only for the date 'released this 08 Oct 02:12'. Live re-fetch of the three rc.15 releases via the releases API on the Solid repository: every body line matches the snapshot text after markdown normalisation (0 differences in each). Manifest suspicious_patterns were null for all four sources. Allowlist: github.com is already listed; no change needed. No snapshot fallback was required.
Factual Accuracy: Quote-marked text verified verbatim: 'Hydration key miss', 'Intended for test tooling and markers, not for branching what the app renders', 'is experimental', ["href", "action"]. Title scrutiny: (1) 'a Fix for Concurrent-Request Hydration IDs' is supported by solid-js entries a405039 and d966729, which say content created under concurrent requests took the other request's hydration ids; the 'Hydration key miss' text is one of the symptoms named in a405039. (2) 'Experimental Server Hook for Router Link State' refers to setLinkClaim(handler), labelled 'New server API (@experimental)' in the @solidjs/web notes (22f942d); 'hook' is the writer's word for a handler-setting API, and the notes' own term is 'API'. The separate quote about test tooling belongs to onHydrationEnd in the solid-js notes, and the article attributes it to solid-js, not to setLinkClaim. Dates recomputed from the API in UTC: [email protected] release published 2026-10-13T19:07:41Z, rc.14 published 2026-10-08T02:12:13Z, so 'five days after' by calendar date holds (5 days 16h 55m exactly). Minor imprecision: the article says the package 'was tagged at 19:07 UTC' and 'a tag time of 02:12 UTC'; those are the release publication times shown by the page ('released this'), whereas the tagged commit for rc.15 is dated 18:54:36Z. The date (October 13) and the stated times as publication times are correct. The article's claim that the @solidjs/universal notes list only dependency updates was checked against the live release (only 'Updated dependencies' lines): correct, though that page is not among the four cited sources. The article makes no claims about @solidjs/element, diagnostics, compiler, babel-plugin, html or h. The statement that no entry is labelled a security fix is scoped to the entries read and holds for the notes read plus universal; the Server-Timing and JSON-script escaping entries are not labelled security fixes in the notes and the article does not call them such. Size/timing figures are labelled as the project's own scenario measurements.
Overall Assessment: APPROVE. Accurate, well-attributed, within length limits; all claims trace to the cited release notes, verified against snapshots and live API text.