docs: add CONTRIBUTING.md and CODE_OF_CONDUCT.md

Add community guidelines for the public repository:
- CONTRIBUTING.md with dev setup, testing, and PR guidelines
- CODE_OF_CONDUCT.md based on Contributor Covenant 2.1

Author: tbartel74

CODE_OF_CONDUCT.md

@@ -0,0 +1,53 @@
+# 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, caste, color, 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 of any kind
+- Trolling, insulting or derogatory comments, and personal or political attacks
+- Public or private harassment
+- Publishing others' private information without their explicit permission
+- Other conduct which could reasonably be considered inappropriate in a professional setting
+
+## Enforcement Responsibilities
+
+Project maintainers are responsible for clarifying and enforcing our 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.
+
+## Scope
+
+This Code of Conduct applies within all community spaces, and also applies when
+an individual is officially representing the community in public spaces.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be
+reported to the project team at **[email protected]**.
+
+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.1, available at
+[https://www.contributor-covenant.org/version/2/1/code_of_conduct.html](https://www.contributor-covenant.org/version/2/1/code_of_conduct.html).

CONTRIBUTING.md

@@ -0,0 +1,67 @@
+# Contributing to Vigil Guard Python SDK
+
+Thank you for your interest in contributing to the Vigil Guard Python SDK.
+
+## Getting Started
+
+### Development Setup
+
+```bash
+git clone https://github.com/Vigil-Guard/python-SDK-vge.git
+cd python-SDK-vge
+python -m venv .venv
+source .venv/bin/activate
+pip install -e ".[dev]"
+```
+
+### Running Tests
+
+```bash
+pytest -m "not integration and not performance" -v
+```
+
+### Linting and Type Checking
+
+```bash
+ruff check src/vigil/ tests/
+mypy --strict src/vigil/
+```
+
+## How to Contribute
+
+### Reporting Bugs
+
+Open a [GitHub issue](https://github.com/Vigil-Guard/python-SDK-vge/issues) with:
+
+- Python version and OS
+- SDK version (`pip show vigil-guard`)
+- Minimal reproduction steps
+- Expected vs actual behavior
+
+For security vulnerabilities, see [SECURITY.md](SECURITY.md).
+
+### Submitting Changes
+
+1. Fork the repository
+2. Create a feature branch (`git checkout -b feature/your-feature`)
+3. Write tests for your changes
+4. Ensure all tests pass and linters are clean
+5. Submit a pull request against `main`
+
+### Pull Request Guidelines
+
+- Keep changes focused — one feature or fix per PR
+- Add or update tests (target 80%+ coverage for new code)
+- Follow existing code style (enforced by ruff and mypy)
+- Update CHANGELOG.md under `[Unreleased]`
+
+## Code Style
+
+- Python 3.9+ compatible syntax
+- Type hints on all public APIs (mypy strict mode)
+- ruff for linting and formatting
+- 100 character line length
+
+## License
+
+By contributing, you agree that your contributions will be licensed under the [MIT License](LICENSE).