chore(repo): add standardized issue and PR templates

[AgentSmid]

🚀 Pull Request – ClipSelect

📋 Summary

This PR introduces a standardized and structured set of GitHub templates to improve contribution quality, review efficiency, and release consistency.

It establishes a solid foundation for issue tracking, pull request validation, and overall repository governance.

---

🔧 Type of Change

• Bug fix
• New feature
• Enhancement (non-breaking improvement)
• Code refactor (no behavior change)
• Documentation update
• Build/CI/Repo tooling
• Other (please describe):

---

🧪 Related Issues

N/A

---

🎯 Scope & Impact

• User-facing change?

  • Yes
  • No

• Affected modules/features:
  Repository structure (.github/ISSUE_TEMPLATE/, PULL_REQUEST_TEMPLATE.md)

• Expected behavior change:
  Improved developer experience, standardized contribution workflow, and stronger QA process.

• Out of scope changes:
  None

---

⚠️ Risk Assessment

• Risk level:

  • Low
  • Medium
  • High

• Potential blast radius:
  Minimal — only affects repository contribution workflow.

• Rollback plan:
  Revert PR to restore previous templates or empty state.

---

✅ Testing Performed

Browsers tested:

• Edge (Chromium): N/A
• Chrome: N/A
• Brave: N/A
• Other Chromium: N/A

Steps verified:

1. Verified templates render correctly in GitHub UI
2. Validated issue creation flow with new templates
3. Verified PR template loads correctly on new PR creation

• Async flows validated (not applicable)
• Hotkeys tested (not applicable)

---

📸 Screenshots / Recordings (if applicable)

N/A

---

🧾 Documentation & Changelog

• Documentation updated (README / docs/)
• CHANGELOG.md updated
• No documentation/changelog needed (repo tooling only)

---

✅ Checklist

• The code follows the project’s style guide
• I’ve tested this functionality locally in a supported browser (GitHub UI)
• I’ve reviewed and updated documentation where applicable
• I’ve added or adjusted relevant logging/debug output (no sensitive data)
• I’ve confirmed that no sensitive information is exposed in this PR
• MV3-friendly: no leaking listeners/timers; resources cleaned up appropriately (not applicable)
• User-facing errors tested (not applicable)

---

🎯 Notes for Reviewers

• This PR standardizes all issue templates for consistency and clarity
• PR template now enforces stronger validation on testing, scope, and risk
• Designed to support scalable development and cleaner release cycles

---

✅ Final Status

✔️ Ready for review and approval
✔️ No runtime impact
✔️ Clean and isolated change