[JarryShaw]

• Searched for similar pull requests
• Followed the coding style
• make test passes, and a test case covers the change
• Changelog entry: N/A — centralised in docs(changelog): shared 1.5.0 changelog — long-lived, merges last (#610, #616, #617, #618, #620) #657

What is the purpose of your pull request?

• docs — documentation only

---

Description

Closes #2163, per the owner's option D: CITATION.cff's date-released is the date of the version-bump commit, not the date the release is distributed.

• Prose: util/bump_version.py's module docstring, its RELEASED_KEY comment and plan_citation's released argument now state that meaning. The "eventually anchoring both fields to create-release.yml" aspiration is removed, along with the residual-risk paragraph that treated the bump date as an approximation. CITATION.cff's header comment and the releasing.rst bullet say the same, the latter citing :issue:2163. With docstrings stripped, bump_version.py's AST is unchanged.
• Test: CitationDateTests.test_a_bump_dates_the_release_by_the_bump_itself in tests/project/test_bump_version.py runs main() and asserts that version, __version__ and today's UTC date-released move together. It guards the ruled contract, so it passes on main too. Making main date the bump '2000-01-01' makes it fail.
• Tests run: test_bump_version.py (33) and the project tests that read these files (349) pass.
• Overlap: docs(repo): fifth whole-repo pass over the repository files (#1103) #2158 rewrites two of the bump_version.py paragraphs this PR removes, so they conflict. Whichever lands second takes this PR's wording.

[JarryShaw]

Review: NEEDS CHANGES at dd6f8ac64 (Sonnet): one paragraph in the module docstring, "So in this repository a bump is not a preparatory step…", still says the release follows "minutes later and with no human in between". That contradicts the new paragraph. The fix copies #2158's wording for that paragraph, so both PRs make the same change there. Everything else checked out: the AST is unchanged, the test passes, the mutation check fails as expected, and no text pins break.

[JarryShaw]

Review: GOOD TO GO at b59f77c98 (Sonnet delta): range-diff shows only the copied #2158 paragraph changed, the docstring no longer contradicts itself, and test_bump_version.py plus the docstring contract pass.

[JarryShaw]

Rebased onto main after #2158 merged: b59f77c98 → f9c96dda3.

• Conflict: util/bump_version.py, in the PyPI-upload measurement and "eventually anchoring" paragraphs, which docs(repo): fifth whole-repo pass over the repository files (#1103) #2158 had reworded. Following the fix(ci): CITATION.cff dates a release by its bump, not its approval #2163 ruling, both paragraphs stay removed.
• Kept from docs(repo): fifth whole-repo pass over the repository files (#1103) #2158: its one new fact, that 1.5.0b9's release was approved three days after its bump (fix(ci): Create Release tags main's tip at approval time, not the commit it was created for #1634). It is now the example in the ruling paragraph.
• Dropped: the "So in this repository…" hunk. main already has that text from docs(repo): fifth whole-repo pass over the repository files (#1103) #2158.
• Checks: with docstrings stripped, the AST matches main. test_bump_version.py plus the docstring contract pass (40).
• Old head: Sonnet GOOD TO GO.

The patch changed in that docstring, so CI runs again and a delta check follows.

[JarryShaw]

Review: GOOD TO GO at f9c96dda3 (Sonnet delta): the docstring agrees with itself after the rebase, the corrections #2158 made all survive, and test_bump_version.py plus the docstring contract pass.

[JarryShaw]

Ready to merge at f9c96dda3. Merging closes #2163.

• Review: Sonnet GOOD TO GO.
• CI: all checks complete, Required checks passed SUCCESS, 0 failed.
• KTLO: 12 legs, no warnings.
• Ordering: project leg merged into main: 2290 tests, 0 failures.
• Overlap: docs(repo): fifth whole-repo pass over the repository files (#1103) #2158 is merged, and this branch is rebased on top of it.