Fix GitHub Release creation in the publish workflow

.github/workflows/publish.yml

@@ -71,6 +71,10 @@ jobs:
     if: startsWith(github.ref, 'refs/tags/v')
     runs-on: ubuntu-latest
     steps:
+      # Needed for the GitHub Release step, which extracts the release notes
+      # from CHANGELOG.md.
+      - uses: actions/checkout@v7
+
       - name: Download dist
         uses: actions/download-artifact@v8
         with:

tasks/detailed_plan.md

@@ -146,3 +146,19 @@ pre-release validation (a tag always points at a merged PR's head).
 **Code:** `.github/workflows/publish.yml`
 **Tests:** skip — workflow-only; the build step is the check itself
 **Docs:** `docs/release.rst` (Package publishing section), `CHANGELOG.md`
+
+### S9: Check out the repo in the publish-pypi job
+
+Added 2026-09-16 at the publish gate. The real tag push published to PyPI
+successfully, but "Create GitHub Release" failed with
+`awk: fatal: cannot open file 'CHANGELOG.md'`: the `publish-pypi` job never
+checked out the repository (it only downloads the dist artifact), so the
+changelog was absent from its working directory. Latent bug — the step had
+never run before because every earlier attempt died upstream. The v5.0.0
+GitHub Release was created manually (same notes + the exact PyPI artifacts as
+assets) while this fix lands via PR for future releases.
+
+**Code:** `.github/workflows/publish.yml` (`actions/checkout@v7` in
+`publish-pypi`)
+**Tests:** skip — workflow-only
+**Docs:** none

tasks/tasks.md

@@ -34,4 +34,4 @@
 - [done] Task 32: Cool. Yes, fix Babel warnings. Analyze rest warnings. E.g. why you suppress aernings refs.citations and ref.footnote? Can we fix it and other warnings? I want to set warings as errors and go to 'no warnings policy'. Without suppresuins if possible. **[USER GUIDANCE]**: "Well. Try to find solution that does not require workarounds or checkers modification. If site o code refactoring required for this way, propose it to me. It may be easier to do smoll refactoring, rather than add workaround. If refactoring improve and simplify site and code, it is better that wotkaround or tooling patching." / "9 approved. Go."
 - [done] Task 33: Check developer documantation. Check that all parts of issue https://github.com/FormalLanguageConstrainedPathQuerying/CFPQ_Data/issues/76 well-documented, necessary parts added to README. **[USER GUIDANCE]**: "Let use docs as the source of truth, skills as thin pointers. Add this to main pronciples for future skills design and update."
 - [done] Task 34: Prepare v5.0.0 release (1/2): analyze the code with respect to the issues https://github.com/FormalLanguageConstrainedPathQuerying/CFPQ_Data/issues/122 https://github.com/FormalLanguageConstrainedPathQuerying/CFPQ_Data/issues/76 https://github.com/FormalLanguageConstrainedPathQuerying/CFPQ_Data/issues/75 https://github.com/FormalLanguageConstrainedPathQuerying/CFPQ_Data/issues/74 https://github.com/FormalLanguageConstrainedPathQuerying/CFPQ_Data/issues/28 https://github.com/FormalLanguageConstrainedPathQuerying/CFPQ_Data/issues/26 https://github.com/FormalLanguageConstrainedPathQuerying/CFPQ_Data/issues/16 https://github.com/FormalLanguageConstrainedPathQuerying/CFPQ_Data/issues/2 and add respective references to the Changelog for the resolved ones. **[USER GUIDANCE]**: "Reference partial, no close claim" (issue #2: only the Zheng & Rugina C alias analysis data is in; the Vedurada 'Batch Alias Analysis' data is missing) / "Reference resolved sub-items only" (umbrella issue #28: cite the resolved sub-issues #27, #32, #20, #30, #33, #26 individually; do not claim #28 done).
-- [ ] Task 35: Prepare v5.0.0 release (2/2): cut the v5.0.0 release per the release skill (bump_version, PR dev->master, tag on origin/master, push, verify PyPI + GitHub Release). **[USER GUIDANCE]**: "Yes, both tasks. But do not forget to ask me to assist with access to PyPI. Guide me step-by-step. And do not forget that I must review and merge requext to master manually, so, tag + push and PyPI/GitHub release only after I confirm that requies merged. Moreover you should pull master irst to create tag on respective commit." / "Trusted publisher added. Go."
+- [done] Task 35: Prepare v5.0.0 release (2/2): cut the v5.0.0 release per the release skill (bump_version, PR dev->master, tag on origin/master, push, verify PyPI + GitHub Release). **[USER GUIDANCE]**: "Yes, both tasks. But do not forget to ask me to assist with access to PyPI. Guide me step-by-step. And do not forget that I must review and merge requext to master manually, so, tag + push and PyPI/GitHub release only after I confirm that requies merged. Moreover you should pull master irst to create tag on respective commit." / "Trusted publisher added. Go."