fix: regenerate release-notes.md, sync main with release

[moui72]

Summary

• The stable-release.yml dispatch on 2026-07-23 failed at the "Fast-forward main into the release branch" step: release has commits that are not on main — refusing a non-fast-forward merge.
• Root cause: the workflow's step 4 (regenerate docs/release-notes.md and commit+push it to release) landed commit db7f5e3 directly on release on 2026-07-22, and nothing folds that back into main. Once main advanced past their common ancestor, the branches diverged and the ff-only merge correctly refused rather than force-pushing.
• This PR regenerates docs/release-notes.md on main via scripts/release-notes.sh (pure generated content, deterministic from the real GitHub release history) so main becomes a superset of release again and the next stable-release dispatch's fast-forward succeeds.

Test plan

• scripts/release-notes.sh run locally, diff reviewed — purely additive release-history content, no hand-authored edits at risk
• scripts/lint-docs.sh passes
• After merge, re-dispatch stable-release.yml (bump: minor) and confirm the ff-merge step succeeds

🤖 Generated with Claude Code

https://claude.ai/code/session_01DPyUE4w2CWGbtyafYfhhxw

Summary by CodeRabbit

• Documentation
  • Expanded release notes into a complete chronological history covering versions v1.1.1-beta.5 through v0.9.0.
  • Added publication dates, change summaries, contributor lists, and full changelog links for each release.
  • Preserved the existing v0.9.0 release details and command mapping table.

[coderabbitai]

Walkthrough

The release notes document now has a top-level header and chronological entries from v1.1.1-beta.5 through v0.9.0, with dates, change lists, contributors, changelog links, and the retained v0.9.0 narrative.

Changes

Release notes

Layer / File(s)	Summary
Chronological release history docs/release-notes.md	Adds versioned release sections with publication dates, change and contributor lists, full changelog links, and preserves the existing v0.9.0 content and command mapping table.

Estimated code review effort: 1 (Trivial) | ~2 minutes

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title clearly summarizes the main change: regenerating release notes to synchronize main with release.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch fix/release-notes-sync

---

_{Comment @coderabbitai help to get the list of available commands.}

[coderabbitai]

Actionable comments posted: 2

🤖 Prompt for all review comments with AI agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@docs/release-notes.md`:
- Around line 340-344: Update the v0.9.0 release section so “ARDD v0.9.0 release
notes” is not a second H1 under the existing top-level “ArDD release notes”
heading; remove the redundant title or change it to an appropriate lower-level
heading while preserving the ## v0.9.0 section structure.
- Around line 216-262: Restore chronological ordering of the v0.10.1 beta
releases in the release-note generator/source: place beta.11 and beta.10 before
beta.9, beta.8, and beta.7 according to their publication dates, then regenerate
docs/release-notes.md so the generated entries reflect that order.

🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

• Push a commit to this branch (recommended)
• Create a new PR with the fixes

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro Plus

Run ID: 059bb2dd-806a-4c7c-98b2-140e78d1553b

📥 Commits

Reviewing files that changed from the base of the PR and between 4e652b7 and 9da4c02.

📒 Files selected for processing (1)

• docs/release-notes.md

[coderabbitai]

🎯 Functional Correctness | 🟡 Minor | ⚡ Quick win

Restore chronological ordering for the v0.10.1 beta releases.

The entries currently list beta.9, beta.8, and beta.7 before beta.11 and beta.10, despite their publication dates. Move beta.11 and beta.10 ahead of beta.9–beta.7 in the generator/source, then regenerate this file.

🤖 Prompt for AI Agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@docs/release-notes.md` around lines 216 - 262, Restore chronological ordering
of the v0.10.1 beta releases in the release-note generator/source: place beta.11
and beta.10 before beta.9, beta.8, and beta.7 according to their publication
dates, then regenerate docs/release-notes.md so the generated entries reflect
that order.

[coderabbitai]

📐 Maintainability & Code Quality | 🟡 Minor | ⚡ Quick win

Fix the heading hierarchy around v0.9.0.

The document already has a top-level # ArDD release notes heading, so # ARDD v0.9.0 release notes becomes a second H1 nested inside the ## v0.9.0 section. Make this heading a lower level or remove the redundant title.

🤖 Prompt for AI Agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@docs/release-notes.md` around lines 340 - 344, Update the v0.9.0 release
section so “ARDD v0.9.0 release notes” is not a second H1 under the existing
top-level “ArDD release notes” heading; remove the redundant title or change it
to an appropriate lower-level heading while preserving the ## v0.9.0 section
structure.