Clarify release merge strategy

[rmorse]

Summary

• Clarify that short-lived work branches targeting develop can be squash-merged.
• Clarify that release PRs and direct develop -> main promotion PRs should use a normal merge commit, not squash.
• Explain why preserving ancestry matters for keeping main and develop easy to sync.

Verification

• git diff --check