chore: sync develop with main's release merge commits

[Jaro-c]

Summary

No code change. Tree-identical to develop. Fast-forward sync of develop's HEAD to main's HEAD so the release merge commits from #31, #33, #36, #38 reach develop too.

Why

Every release PR (develop → main, merge commit) leaves a commit node on main that develop never learns about. Over several releases develop's graph falls "behind" main even though their trees are identical. This PR closes that gap.

Ongoing convention

Every release PR to main should be followed by this sync PR to develop, so develop's HEAD always reflects the latest main state.

Merge method

Fast-forward is fine — no content difference.

[github-advanced-security]

You are seeing this message because GitHub Code Scanning has recently been set up for this repository, or this pull request contains the workflow file for the Code Scanning tool.

What Enabling Code Scanning Means:

• The 'Security' tab will display more code scanning analysis results (e.g., for the default branch).
• Depending on your configuration and choice of analysis tool, future pull requests will be annotated with code scanning analysis results.
• You will be able to see the analysis results for the pull request's branch on this overview once the scans have completed and the checks have passed.

For more information about GitHub Code Scanning, check out the documentation.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!