Merge pull request #7 from iruvan/community-standards

docs: add GitHub community standard files

Author: iruvan

.github/ISSUE_TEMPLATE/bug_report.md

@@ -0,0 +1,23 @@
+---
+name: Bug report
+about: Report a problem with context-debug
+title: ""
+labels: bug
+---
+
+**Describe the bug**
+A clear description of what's wrong.
+
+**To Reproduce**
+Minimal code or steps to reproduce the behavior.
+
+**Expected behavior**
+What you expected to happen instead.
+
+**Environment**
+- context-debug version / commit:
+- Go version:
+- OS:
+
+**Additional context**
+Anything else relevant (logs, stack traces, etc).

.github/ISSUE_TEMPLATE/feature_request.md

@@ -0,0 +1,18 @@
+---
+name: Feature request
+about: Suggest an idea for context-debug
+title: ""
+labels: enhancement
+---
+
+**What problem does this solve?**
+A clear description of the problem or use case.
+
+**Proposed solution**
+What you'd like to see added or changed.
+
+**Alternatives considered**
+Any alternative approaches you've thought about.
+
+**Additional context**
+Anything else relevant.

.github/PULL_REQUEST_TEMPLATE.md

@@ -0,0 +1,13 @@
+## Motivation
+
+Why is this change needed?
+
+## Summary
+
+What changed.
+
+## Test plan
+
+- [ ] `go test ./...` passes
+- [ ] `go vet ./...` and `gofmt -l .` are clean
+- [ ] Manually verified (if applicable): describe how

CODE_OF_CONDUCT.md

@@ -0,0 +1,34 @@
+# Code of Conduct
+
+## Our Pledge
+
+We as contributors and maintainers pledge to make participation in this
+project a harassment-free experience for everyone, regardless of age, body
+size, disability, ethnicity, gender identity and expression, level of
+experience, nationality, personal appearance, race, religion, or sexual
+identity and orientation.
+
+## Our Standards
+
+Examples of behavior that contributes to a positive environment:
+
+- Being respectful of differing viewpoints and experiences
+- Gracefully accepting constructive criticism
+- Focusing on what is best for the community
+
+Examples of unacceptable behavior:
+
+- Trolling, insulting or derogatory comments, and personal or political attacks
+- Public or private harassment
+- Publishing others' private information without explicit permission
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be
+reported by opening a private security advisory or contacting the repository
+maintainer directly. 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.

CONTRIBUTING.md

@@ -0,0 +1,30 @@
+# Contributing
+
+Thanks for considering a contribution to context-debug.
+
+## Reporting bugs / requesting features
+
+Open an issue using the appropriate template. Include a minimal reproduction
+where possible.
+
+## Development
+
+```
+go test ./...              # run the package tests (root module)
+cd example && go run .     # run the example HTTP service (needs POSTGRES_DSN)
+```
+
+There is no separate lint config; rely on `go vet` and standard `gofmt`
+(`gofmt -l .` should report nothing before you open a PR).
+
+## Submitting changes
+
+1. Fork the repo and create a branch off `main`.
+2. Make your change, keeping it focused — unrelated cleanups belong in a
+   separate PR.
+3. Ensure `go vet ./...`, `gofmt -l .`, and `go test ./...` are clean.
+4. Open a pull request using the PR template, describing the motivation and
+   what changed.
+
+By contributing, you agree your contributions will be licensed under this
+project's [license](LICENSE).

SECURITY.md

@@ -0,0 +1,17 @@
+# Security Policy
+
+## Supported Versions
+
+This project is pre-1.0 and tracks a single moving `main` branch. Security
+fixes are made against the latest commit; there are no maintained older
+release lines.
+
+## Reporting a Vulnerability
+
+Please do not open a public issue for security vulnerabilities. Instead,
+report them privately via [GitHub Security Advisories](../../security/advisories/new)
+for this repository.
+
+Include as much detail as you can: affected code path, reproduction steps,
+and potential impact. We'll acknowledge reports as soon as possible and
+follow up with a fix or mitigation timeline.