Improve release process for squash merge workflow

[waynebrantley]

Summary

Updates the release process to properly handle squash merges, ensuring tags always point to the same commit as main.

Problem

Previously, the release script would:

1. Create a tag on the release branch commit
2. Push the tag
3. PR gets squash-merged, creating a NEW commit
4. Tag points to old commit, main points to new commit ❌

Solution

Split the release process into two steps:

Step 1: release.sh

• Creates release branch with version bump
• Creates PR for review
• Waits for tests and merge
• Does NOT create tag yet

Step 2: finalize-release.sh (after PR merge)

• Runs on main after PR is merged
• Creates tag on the merged (squashed) commit ✅
• Creates GitHub release
• Triggers npm publish workflow

Benefits

• Tags and main always aligned
• Works seamlessly with branch protection
• Works with squash merge strategy
• Automated tag creation on correct commit

Testing

• Scripts have correct permissions
• .gitignore updated for .release-temp/
• Line endings preserved (LF)

Workflow Example

# Start release
./scripts/release.sh patch

# Wait for PR to merge...

# Finalize release (creates tag + GitHub release)
./scripts/finalize-release.sh