docs: remove unresolved merge conflict markers from README

[xiakong130]

What changed

Removed three unresolved git merge conflict markers (<<<<<<< HEAD, =======, >>>>>>> f3b7ebe...) from README.md that were accidentally committed and rendered as literal text on the GitHub README page.

Why

The conflict markers appeared between the badge section and the "Built With" section, making them visible to anyone viewing the repository README. This is a documentation quality issue.

How I checked

• Verified the diff only removes the three conflict marker lines
• Confirmed no remaining conflict markers via grep
• Checked that the <div> open/close structure is still correct after the fix

[vercel]

@xiakong130 is attempting to deploy a commit to the magic-peach1's projects Team on Vercel.

A member of the Team first needs to authorize it.

[github-actions]

⚠️ PR Format Issues — @xiakong130

Please fix the following before your PR can be reviewed:

• ⚠️ No linked issue found. Add Closes #<issue-number> to your PR description.

Push new commits after fixing — this comment will update automatically.

📖 CONTRIBUTING.md

[github-actions]

👋 Thanks for your PR, @xiakong130!

Welcome to Reframe — a browser-based video editor built for everyone 🎬

What happens next

1. 🤖 Automated checks — build & TypeScript typecheck will run automatically
2. ✅ Vercel preview — a preview deployment will be created (requires maintainer authorization for fork PRs)
3. 👀 Code review — a maintainer will review your changes
4. 🚀 Merge — once approved, your PR will be merged!

Quick checklist

• PR title follows Conventional Commits (e.g. feat: add dark mode)
• Linked the issue this PR closes (e.g. Closes #123)
• Tested the changes locally (bun run dev)
• Build passes (bun run build)

Useful links

• 📖 CONTRIBUTING.md
• 🐛 Open Issues
• ⭐ Star the repo to support the project!

Happy coding! 🎉