Where: CITATION.cff's version/date-released fields vs pyproject.toml and CHANGELOG.md.
The gap: CITATION.cff still says version: "2.0.0" / date-released: "2026-07-23", three shipped releases behind.
Repro:
$ grep -n "^version:\|^date-released:" CITATION.cff
27:version: "2.0.0"
28:date-released: "2026-07-23"
$ grep -n "^version" pyproject.toml
7:version = "2.2.0"
$ grep -n "^## \[" CHANGELOG.md | head -3
20:## [2.2.0] - 02 Sep 2026
45:## [2.1.1] - 02 Sep 2026
83:## [2.1.0] - 30 Aug 2026
Why it matters: CITATION.cff is what GitHub surfaces via its "Cite this repository" button - it exists specifically to identify what a citer is actually citing. Stuck at 2.0.0 despite three real releases since (2.1.0, 2.1.1, 2.2.0), including the entire MCP server and Phase 2 tool set that shipped after that version.
Suggested fix: bump version to 2.2.0 and date-released to 2026-09-02 (the 2.2.0 release date per CHANGELOG.md), and consider a CI check (in the spirit of scripts/check_explainer_count.py) asserting CITATION.cff's version matches pyproject.toml so this can't silently drift again.
Where:
CITATION.cff'sversion/date-releasedfields vspyproject.tomlandCHANGELOG.md.The gap:
CITATION.cffstill saysversion: "2.0.0"/date-released: "2026-07-23", three shipped releases behind.Repro:
Why it matters:
CITATION.cffis what GitHub surfaces via its "Cite this repository" button - it exists specifically to identify what a citer is actually citing. Stuck at 2.0.0 despite three real releases since (2.1.0, 2.1.1, 2.2.0), including the entire MCP server and Phase 2 tool set that shipped after that version.Suggested fix: bump
versionto2.2.0anddate-releasedto2026-09-02(the 2.2.0 release date per CHANGELOG.md), and consider a CI check (in the spirit ofscripts/check_explainer_count.py) assertingCITATION.cff's version matchespyproject.tomlso this can't silently drift again.