* docs(contributing): formalize issue assignment and duplicate-PR triage workflow
Comments are no longer required before an issue can be assigned - maintainers
may assign directly based on recent activity. Also documents the duplicate-PR
priority order for triage (contributor PR, claimed issue, activity tiebreak,
late duplicates, overlapping scope).
* docs(contributing): clarify assignment precedence and define activity tiebreak
Addresses Qodo review feedback on PR #1030: the duplicate-PR priority list
now states these rules apply on top of the assignment workflow (opening a PR
pre-assignment doesn't grant priority), and the "most active" tiebreak now
specifies a concrete 60-day window and signals instead of being subjective.
- Simplified CI to just build validation (no more failing tests/lints)
- Combined release.yml and pypi.yml into single workflow
- Simplified security.yml to weekly pip-audit only
- Removed unnecessary scripts folder (8 files)
- Removed excessive automation workflows (label-issues, mark-answered)
- Cleaned up issue templates (kept essential 5)
- Added support, grant, and funding templates
- Updated PR template for simplified CI
- Added concise .github/README.md
Mohd Kaif