feat: implement repository governance standards

.github/CODEOWNERS

@@ -0,0 +1,15 @@
+# Default owners for everything in the repo
+* @MandarapuMadhulatha @sandeepkunkunuru @vinod-dega
+
+# Frontend code ownership
+/frontend/ @MandarapuMadhulatha @sandeepkunkunuru
+
+# Python implementation ownership
+*.py @MandarapuMadhulatha @sandeepkunkunuru
+
+# Documentation ownership
+/docs/ @MandarapuMadhulatha @sandeepkunkunuru
+*.md @MandarapuMadhulatha @sandeepkunkunuru
+
+# GitHub specific files
+.github/ @vinod-dega

.github/ISSUE_TEMPLATE/bug_report.md

@@ -0,0 +1,30 @@
+---
+name: Bug Report
+about: Create a report to help us improve
+title: '[BUG] '
+labels: bug
+assignees: ''
+---
+
+**Describe the bug**
+A clear and concise description of what the bug is.
+
+**To Reproduce**
+Steps to reproduce the behavior:
+1. Go to '...'
+2. Click on '....'
+3. See error
+
+**Expected behavior**
+A clear and concise description of what you expected to happen.
+
+**Screenshots**
+If applicable, add screenshots to help explain your problem.
+
+**Environment:**
+ - OS: [e.g. Windows, Linux]
+ - Python Version: [e.g. 3.8]
+ - Browser (if applicable): [e.g. chrome, safari]
+
+**Additional context**
+Add any other context about the problem here.

.github/ISSUE_TEMPLATE/feature_request.md

@@ -0,0 +1,19 @@
+---
+name: Feature Request
+about: Suggest an idea for this project
+title: '[FEATURE] '
+labels: enhancement
+assignees: ''
+---
+
+**Is your feature request related to a problem? Please describe.**
+A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
+
+**Describe the solution you'd like**
+A clear and concise description of what you want to happen.
+
+**Describe alternatives you've considered**
+A clear and concise description of any alternative solutions or features you've considered.
+
+**Additional context**
+Add any other context or screenshots about the feature request here.

.github/ISSUE_TEMPLATE/repository_enhancement.md

@@ -0,0 +1,41 @@
+---
+name: Repository Enhancement
+about: Suggest improvements to repository structure, workflow, or infrastructure
+title: '[REPO] '
+labels: infrastructure, enhancement
+assignees: '@vinod-dega'
+---
+
+**Area of Enhancement**
+- [ ] Repository Configuration
+- [ ] CI/CD Pipeline
+- [ ] Documentation
+- [ ] Security
+- [ ] Developer Experience
+- [ ] Other
+
+**Current State**
+Describe the current state of the area you want to enhance.
+
+**Proposed Changes**
+List the specific changes or improvements you're proposing:
+1. 
+2. 
+3. 
+
+**Benefits**
+Explain how these changes will benefit:
+- [ ] Code Quality
+- [ ] Development Speed
+- [ ] Security
+- [ ] Contributor Experience
+- [ ] Other: _____
+
+**Implementation Checklist**
+- [ ] Configuration changes required
+- [ ] Documentation updates needed
+- [ ] Team training/communication needed
+- [ ] Security implications considered
+
+**Additional Context**
+Add any other context, references, or screenshots about the enhancement here.

.github/workflows/test.yml

@@ -23,6 +23,7 @@ jobs:
         python -m pip install --upgrade pip
         pip install -r requirements.txt
         pip install pytest
+        pip install -e .
 
     - name: Run tests
       run: |

CODE_OF_CONDUCT.md

@@ -0,0 +1,47 @@
+# Contributor Covenant Code of Conduct
+
+## Our Pledge
+
+We as members, contributors, and leaders pledge to make participation in our
+community a harassment-free experience for everyone, regardless of age, body
+size, visible or invisible disability, ethnicity, sex characteristics, gender
+identity and expression, level of experience, education, socio-economic status,
+nationality, personal appearance, race, religion, or sexual identity
+and orientation.
+
+## Our Standards
+
+Examples of behavior that contributes to a positive environment:
+
+* Using welcoming and inclusive language
+* Being respectful of differing viewpoints and experiences
+* Gracefully accepting constructive criticism
+* Focusing on what is best for the community
+* Showing empathy towards other community members
+
+Examples of unacceptable behavior:
+
+* The use of sexualized language or imagery, and sexual attention or advances
+* Trolling, insulting or derogatory comments, and personal or political attacks
+* Public or private harassment
+* Publishing others' private information without explicit permission
+* Other conduct which could reasonably be considered inappropriate
+
+## Enforcement Responsibilities
+
+Project maintainers are responsible for clarifying and enforcing standards of
+acceptable behavior and will take appropriate and fair corrective action in
+response to any behavior that they deem inappropriate, threatening, offensive,
+or harmful.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be
+reported to the project team at support@vaidhyamegha.com. All
+complaints will be reviewed and investigated promptly and fairly.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant](https://www.contributor-covenant.org),
+version 2.0, available at
+https://www.contributor-covenant.org/version/2/0/code_of_conduct.html.

CONTRIBUTING.md

@@ -0,0 +1,40 @@
+# Contributing Guidelines
+
+## Pull Request Process
+
+1. Fork the repository
+2. Create your feature branch (`git checkout -b feature/amazing-feature`)
+3. Commit your changes (`git commit -m 'Add some amazing feature'`)
+4. Push to the branch (`git push origin feature/amazing-feature`)
+5. Open a Pull Request
+
+## Pull Request Requirements
+
+- Keep changes focused and atomic
+- Update documentation as needed
+- Include tests for new features
+- Ensure all checks pass
+- Get approval from code owners
+
+## Branch Naming
+
+- Features: `feature/description`
+- Bug fixes: `fix/description`
+- Documentation: `docs/description`
+
+## Commit Messages
+
+Format:
+```
+type: description
+
+[optional body]
+```
+
+Types: `feat`, `fix`, `docs`, `test`, `refactor`
+
+## Getting Help
+
+- Open an issue with a clear description
+- Check existing documentation
+- Contact maintainers if needed

SECURITY.md

@@ -0,0 +1,15 @@
+# Security Policy
+
+## Reporting a Vulnerability
+
+If you believe you have found a security vulnerability in this project, please report it to us by emailing support@vaidhyamegha.com.
+
+**Please do not report security vulnerabilities through public GitHub issues.**
+
+Please include:
+- Description of the vulnerability
+- Steps to reproduce
+- Potential impact
+- Any possible solutions you've considered
+
+We will respond within 48 hours and work with you to address the issue.