Changelog fixes

CHANGELOG_AUTOMATION_CONTRACT.md

@@ -49,7 +49,7 @@ If `--current-tag` is omitted, the generator must resolve the exact tag at
 
 Each consumer repo provides `scripts/changelog.json` with:
 
-- `repo_url`: canonical web URL for pull request links
+- `repo_url`: canonical web URL for pull request and commit links
 - `categories[]`
 - `categories[].title`
 - `categories[].sections[]`
@@ -60,8 +60,12 @@ Paths are repo-relative path filters passed through to `git log`.
 
 ## Author Contract
 
-Rendered changelog entries must resolve pull request author names from the
-Gitea pull request API rather than trusting the merge commit author field.
+Rendered changelog entries must support both first-parent pull-request-style
+pushes and direct first-parent pushes between the selected tags.
+
+For pull-request-style commits that include a `(#123)` suffix, the generator
+must resolve author names from the Gitea pull request API rather than trusting
+the merge commit author field.
 
 Expected endpoint shape:
 
@@ -82,6 +86,10 @@ The changelog is a staged build artifact, not a committed source-controlled file
 This avoids detached-tag push complexity while preserving a stable artifact for
 later aggregation.
 
+For direct pushes without a pull number suffix, the generator must render the
+commit using its commit hash link and commit author without calling the pull
+request API.
+
 ## Output Contract
 
 The Markdown output must remain simple and merge-friendly:
@@ -90,10 +98,11 @@ The Markdown output must remain simple and merge-friendly:
 - comparison line naming the previous tag when one exists
 - category headings
 - section headings
-- bullet entries in the form:
+- bullet entries in one of these forms:
 
 ```text
 - Title ([#123](.../pulls/123)) - From Author Name
+- Title ([abc1234](.../commit/<sha>)) - From Author Name
 ```
 
 ## Deferred Work