Comparison: review competitor facts before each release, starting with the stale ones #121

Problem

docs/comparison.md states competitors' features at named versions and dates, and each one rests on a design/knowledge/ entry pinned external {name} {version}. Nothing checks those entries against newer releases ("no check compares it, so it is as fresh as its date", design/knowledge/README.md). A page that persuades by being exact goes on persuading after it stops being exact. Two outside reviews of the page (#120) asked for its maintenance to be visible.

It is already out of date in places, as of 2026-10-29 (KB-045):

• Thinktecture.Runtime.Extensions is at 10.6.0 (2026-10-19). The tables name 10.5.0 and 10.5.1.
• LanguageExt 5.0 is at beta-78. The table names beta-77.
• TypeKit's own columns say 2.1.0, and so does the root README's Status section. Done in Comparison: add SuperStrong.Types to the value-object table #120's branch: both name 2.3.0, and every TypeKit cell was checked again on release/2.3.0.

Change

• A review step before each release, in CONTRIBUTING's "Releasing" and AGENTS.md's "Releasing": list the external facts whose verified: date is more than six months old, or whose pinned version is no longer the latest on NuGet, and re-read them. Update or re-date each one, and correct the page with it.
• A listing to drive it, with no model involved: docs-query list kind=fact already shows each fact's date. Add a filter for external pins older than a given number of days, or a command that compares each pinned package with NuGet's latest version, run by hand. It's never a CI check, because a build mustn't fail just because time passed.
• The page's date list ("Every fact here was read ... at the release named") moves with each re-read.
• Do the first pass now: re-read Thinktecture.Runtime.Extensions 10.6.0 and LanguageExt beta-78. TypeKit's own columns are done (2.3.0).
• TypeKit's columns move with each release as part of the review: re-check each cell against the release branch, rather than only changing the header.

Done when

• The release steps include the review, and running the listing shows which facts are due.
• The tables name the current release of each library, or a date that says when it was last read, and TypeKit's columns and the README name the version being released.