Migrate from legacy release branch to tag-based releases

[Copilot]

Release Branch Migration - Ready to Merge

This PR migrates the repository from using a legacy release branch to a modern tag-based release workflow.

Changes Made

• CI Workflow Update - Removed branches-ignore: release from .github/workflows/ci.yml
• Version Bump - Updated pyproject.toml from 1.0.1 to 1.0.2
• Automation Script - Created scripts/complete-release-migration.sh with safety checks

Next Steps (After Merge)

Run the automation script:

./scripts/complete-release-migration.sh

Or manually:

git checkout main && git pull origin main
git push origin --delete release
git tag -a v1.0.2 -m "Release v1.0.2"
git push origin v1.0.2

The tag push will trigger the existing release workflow to build and publish binaries for all platforms.

Future Releases

Simply push a tag to main:

git tag -a v1.0.3 -m "Release v1.0.3"
git push origin v1.0.3

Original prompt

help me delete the release branch to use the modern way to create a release binaries with tags on the master or main branch. do not edit the original master or main branch name. after deleting the lagacy release branch. help me bump a commit with tag to trogger the release action to publish the latest binaries.

---

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.

[scc-tw]

@copilot remove those redundant markdown trash. it is not relative and unessential to this repository.

[Copilot]

@copilot remove those redundant markdown trash. it is not relative and unessential to this repository.

Removed the markdown documentation files in commit 95739a3. The PR now only includes the essential changes: CI workflow update, version bump, and the automation script.