chore: sync main ancestry before 0.9.4

[progresshans]

Summary

• merge the current main history back into develop without rebasing
• preserve the already-validated develop tree unchanged
• make develop up to date with the strict main branch before the 0.9.4 release PR

Why

PR #34 is content-correct but main requires the head branch to contain the latest main commit. The previous develop-to-main merge commit had not been merged back into develop, so GitHub reported the release PR as behind.

Validation

• the resulting tree is byte-for-byte identical to origin/develop
• origin/main is an ancestor of this branch
• no source or release metadata files changed

After this ancestry-only PR merges, PR #34 will rerun on the updated develop head.

[chatgpt-codex-connector]

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review	Status	Commit	Review trigger
📝 Code Review	✅ Completed 2026-08-29T07:48:18.080444Z	6914c2f	PR opened

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.