Repository Hygiene

[charlieroth]

Summary

Implements comprehensive repository hygiene to establish professional standards and improve contributor experience. This PR addresses all requirements from issue #18 to create a clean, well-organized repository surface.

Changes Made

• Documentation updates
• Infrastructure/CI changes

Detailed Changes

• CODEOWNERS: Added code ownership rules assigning @charlieroth as owner for all Rust code, documentation, database migrations, and CI/CD files
• LICENSE: Added MIT license with 2024 copyright for open source compliance
• CONTRIBUTING.md: Created comprehensive contributor guide with development setup, workflow, code style guidelines, and security best practices
• SECURITY.md: Established security policy with responsible disclosure process and vulnerability reporting procedures
• Issue Templates: Added structured GitHub issue forms for bug reports, feature requests, and tasks with validation and required fields
• Pull Request Template: Created comprehensive PR checklist covering testing, code quality, database changes, and deployment considerations

Testing

• All existing tests pass (make test)
• New tests added for new functionality (N/A - documentation only)
• Manual testing completed
• Edge cases considered and tested

Test Commands Run

# Verified no build issues introduced
make check

Code Quality

• Code follows project style guidelines (make fmt)
• No linting errors (make lint)
• Full check passes (make check)
• Code is well-documented where necessary
• No security vulnerabilities introduced

Database Changes

• No database changes

Breaking Changes

• No breaking changes

Deployment Notes

• No special deployment considerations

Documentation

• README updated (not needed - existing README remains relevant)
• API documentation updated (N/A)
• Contributing guidelines updated (new CONTRIBUTING.md created)
• Other documentation updated: Added LICENSE, SECURITY.md, CODEOWNERS, and GitHub templates

Additional Notes

This PR establishes the foundation for professional repository management by:

1. Improving Contributor Experience: Clear contributing guidelines, issue templates, and PR checklists help new contributors understand expectations
2. Establishing Ownership: CODEOWNERS ensures proper review assignment for different parts of the codebase
3. Security Best Practices: SECURITY.md provides clear vulnerability reporting process
4. Legal Compliance: MIT license clarifies usage terms for the open source project

All templates follow GitHub's recommended practices and include validation to ensure high-quality submissions. The contributing guide aligns with the existing Rust/Axum tech stack and development commands documented in AGENTS.md.

Closes #18

Co-authored-by: Amp amp@ampcode.com
Amp-Thread-ID: https://ampcode.com/threads/T-67d5d6d9-ed95-45c4-ad58-c3146da224e4