Phase 14: Add cross-platform packaging, releases and contributor workflow

[ashishsinghbora]

Goal

Make the project easy to install, test, contribute to and release.

Scope

• Define supported OS/architecture matrix.
• Add reproducible Go builds.
• Add Tauri packaging for supported desktop targets.
• Add GitHub Actions for tests, linting, race detection, security checks and release builds.
• Add release versioning and changelog automation.
• Add issue templates for bug reports, feature requests and good-first issues.
• Add PR template with tests, architecture impact and performance considerations.
• Add CONTRIBUTING.md, CODE_OF_CONDUCT.md, and SECURITY.md.
• Add labels for phase, good first issue, help wanted, bug, performance, security, frontend, backend, documentation, and testing.

Acceptance criteria

• A contributor can clone the repo and follow one documented setup path.
• CI validates every PR.
• Release artifacts are generated automatically for supported targets.
• Security reports have a private disclosure path.

[ashishsinghbora]

Hi @chicagobearsirf-cmd , thanks for offering to help out.

I've assigned this issue to you. To make sure we're fully aligned, here is the scope outlined for this task:

Define the supported OS/architecture matrix.
Implement reproducible Go builds.
Configure Tauri packaging across the supported desktop targets.
Set up the necessary CI/CD and release automation workflows.

Feel free to share the approach or setup you’ve used previously, and let me know if you run into any questions or need access to anything before opening a draft PR. Looking forward to your contribution!