chore: sync main back into staging (drift after bf9a4c0c)

[github-actions]

1 commit(s) in main are not in staging's ancestry after push to main at bf9a4c0.

This drift will cause conflicts on the next staging → main promotion.

Required action

1. Create a chore/sync-main-to-staging branch from origin/staging
2. git merge origin/main -X ours --no-edit (prefer staging for any conflicts)
3. PR the branch into staging, merge, redeploy staging
4. Close this issue

Auto-opened by the detect-staging-drift workflow.

[wilhel1812]

Main has been synced back into staging via PR #777. Automatic staging deploy completed for commit 7522b54 with build info 0.18.0+7522b546.

[wilhel1812]

Reopening briefly: PR #777 was squash-merged, so the deployed tree is synced but git ancestry still leaves origin/main visible in git cherry. Opening a no-tree-diff ancestry sync PR to prevent drift detection from recurring.

[wilhel1812]

Closing again. PR #777 synced the release content into staging and the automatic staging deploy completed at 7522b54 / build info 0.18.0+7522b546. A follow-up ancestry-only PR #778 could not be merged because repository settings disallow merge commits; current origin/staging has no tree diff from origin/main.