chore: back-merge main → develop after v0.8.0 promote

[saadqbal]

Back-merge main into develop after the v0.8.0 promote (#219).

main accrues promote merge/snapshot commits (#219, #194, #164) that are never in develop's ancestry, so develop diverges and every future develop→main promote PR eventually goes CONFLICTING. main carries no unique code — only these promote snapshots — so this back-merge is content-only-neutral for develop; it just realigns ancestry so the next promote stays clean.

No code changes vs develop; merging this keeps develop == main content-wise going forward.

🤖 Generated with Claude Code

---

Note

Low Risk
Merge-only with an empty diff relative to develop; no runtime or security impact.

Overview
No application code changes — this PR only merges main into develop so branch histories match after the v0.8.0 promote.

main had accumulated promote/snapshot merge commits that were not in develop's ancestry, which causes future develop→main promote PRs to conflict. The back-merge realigns ancestry while keeping develop content-equivalent to what it already had; main adds no unique code beyond those promote commits.

^{Reviewed by Cursor Bugbot for commit b7fbdcc. Bugbot is set up for automated code reviews on this repo. Configure here.}