[robertodr]

🤖 AI text below 🤖

Summary

In the release notes of AEGISS v0.1.0, the PR numbers ((#46), …) are not clickable on the release page, and GitHub never autolinks #N in files such as CHANGELOG.md. This PR makes cliff.toml write each entry's PR number as an absolute link:

- **io:** Crash on NaN input ([#13](https://github.com/Algorithmiq/AEGISS/pull/13))

• Which repository: it comes from GITHUB_REPOSITORY, which GitHub Actions sets to the calling repository, including inside the reusable release workflow and the release-notes action. Consumers change nothing.
• What becomes a link: only the (#N) that squash-merging appends to the title. A #3 elsewhere in a title stays as written, and commits without a PR number are unchanged.
• Without GITHUB_REPOSITORY: the number stays plain. The just changelog recipes (the stubs, both variants, and this repository's own) set the variable from the origin remote, so local previews match the release PR.
• Tests:
  • two new tests in tests/test_cliff.py: with the variable set, and without it;
  • an autouse fixture in conftest.py unsets the variable, because Actions also sets it while running the tests. Three existing tests compare notes and failed when I ran the suite with it set.
• README: one paragraph about the links.

This changes the changelog format and needs no action from consumers, which the README's versioning rules class as a minor release (v1.1.0). After the release, AEGISS's existing 0.1.0 section in CHANGELOG.md and its release notes can be regenerated with links. The bot only prepends new sections.

Checklist

• just lint and just test pass (also with GITHUB_REPOSITORY set, as in CI)
• README.md updated if the stubs, inputs or setup changed
• Breaking change or deprecation: the Migration section says what consumers must change (not applicable)