Add GitHub community and maintenance files

Author: msLoginoff

.github/ISSUE_TEMPLATE/bug_report.md

@@ -0,0 +1,37 @@
+---
+name: Bug report
+about: Report a reproducible problem in the runner, examples, reports, or dashboards.
+title: "Bug: "
+labels: bug
+assignees: ""
+---
+
+## Summary
+
+What happened?
+
+## Steps To Reproduce
+
+1.
+2.
+3.
+
+## Expected Behavior
+
+What did you expect to happen?
+
+## Actual Behavior
+
+What happened instead?
+
+## Environment
+
+- OS:
+- .NET SDK:
+- Docker runtime:
+- ScenarioBench commit:
+
+## Logs Or Artifacts
+
+Paste relevant CLI output, `comparison.md`, or Grafana/InfluxDB details.
+

.github/ISSUE_TEMPLATE/feature_request.md

@@ -0,0 +1,24 @@
+---
+name: Feature request
+about: Suggest an improvement or new capability.
+title: "Feature: "
+labels: enhancement
+assignees: ""
+---
+
+## Summary
+
+What should ScenarioBench support?
+
+## Use Case
+
+Why is this useful?
+
+## Proposed Shape
+
+Describe the config, command, report, dashboard, or workflow you expect.
+
+## Alternatives Considered
+
+What other approaches did you consider?
+

.github/ISSUE_TEMPLATE/scenario_request.md

@@ -0,0 +1,29 @@
+---
+name: Scenario request
+about: Propose a benchmark scenario or workload profile.
+title: "Scenario: "
+labels: scenario
+assignees: ""
+---
+
+## Scenario Goal
+
+What behavior should this benchmark exercise?
+
+## Target Shape
+
+- Target type: local / Docker / stage / other
+- Endpoint or workflow:
+- Expected success criteria:
+
+## Load Profile
+
+- Rate:
+- Duration:
+- Warmup:
+- Ramp/stress/spike/soak needs:
+
+## Validation
+
+What should be checked after the run?
+

.github/pull_request_template.md

@@ -0,0 +1,20 @@
+## Summary
+
+Describe the change.
+
+## Changes
+
+- 
+
+## Verification
+
+Commands run:
+
+```bash
+
+```
+
+## Notes / Limitations
+
+Anything reviewers should know?
+

.github/workflows/ci.yml

@@ -0,0 +1,30 @@
+name: CI
+
+on:
+  push:
+    branches:
+      - main
+  pull_request:
+    branches:
+      - main
+
+jobs:
+  build:
+    name: Build
+    runs-on: ubuntu-latest
+
+    steps:
+      - name: Checkout
+        uses: actions/checkout@v4
+
+      - name: Setup .NET
+        uses: actions/setup-dotnet@v4
+        with:
+          dotnet-version: "10.0.x"
+
+      - name: Restore
+        run: dotnet restore ScenarioBench.sln
+
+      - name: Build
+        run: dotnet build ScenarioBench.sln --no-restore -m:1 -v:minimal
+

.gitignore

@@ -70,4 +70,8 @@ nunit-*.xml
 !.env.example
 
 # Rider/ReSharper user settings
-*.DotSettings.user
+*.DotSettings.user
+
+# Local AI handoff/context files
+AI_CONTEXT.md
+AI_*_CONTEXT.md

CONTRIBUTING.md

@@ -0,0 +1,56 @@
+# Contributing
+
+Thanks for considering a contribution to ScenarioBench.
+
+This project is early, so small focused pull requests are easier to review than
+large redesigns.
+
+## Development Setup
+
+Requirements:
+
+- .NET 10 SDK
+- Docker-compatible runtime, for example OrbStack or Docker Desktop
+
+Build:
+
+```bash
+dotnet restore ScenarioBench.sln
+dotnet build ScenarioBench.sln --no-restore -m:1 -v:minimal
+```
+
+Run the demo:
+
+```bash
+docker compose -f examples/docker-compose.observability.yml up -d
+docker compose -f examples/docker-compose.demo.yml up -d --build
+
+dotnet run --project src/ScenarioBench.Cli -- \
+  --config examples/http-smoke.json \
+  --infra-config examples/infra/influxdb.json
+```
+
+## Pull Requests
+
+Before opening a PR:
+
+- keep the change focused;
+- update docs when workflow/config changes;
+- include verification commands in the PR description;
+- avoid committing local artifacts, secrets, IDE files, or private target details.
+
+## Public Repo Boundary
+
+This repository must stay generic and public-safe.
+
+Do not add:
+
+- private endpoints;
+- auth secrets or tokens;
+- private database schemas;
+- real production payloads;
+- company-specific infrastructure details.
+
+Project-specific adapters and sensitive benchmark scenarios should live in a
+private repository.
+

README.md

@@ -331,3 +331,11 @@ details, or real Unicorn payloads.
 
 Unicorn-specific scenarios, auth, seed data, Docker overrides, and audit
 validation belong in a future private scenario adapter repository.
+
+## Contributing
+
+See [CONTRIBUTING.md](CONTRIBUTING.md) for local setup and pull request
+guidelines.
+
+For repository labels, issue style, and maintainer workflow, see
+[docs/MAINTAINER_GUIDE.md](docs/MAINTAINER_GUIDE.md).

SECURITY.md

@@ -0,0 +1,20 @@
+# Security Policy
+
+## Supported Versions
+
+ScenarioBench is pre-1.0. Security fixes are handled on the `main` branch.
+
+## Reporting A Vulnerability
+
+Please do not open a public issue for secrets, credential leaks, or exploitable
+security problems.
+
+Open a private security advisory on GitHub if available, or contact the
+maintainer directly.
+
+## Public Repo Boundary
+
+Do not include secrets, private endpoints, auth flows, real payloads, database
+schemas, or operational details in public issues, pull requests, examples, or
+documentation.
+

docs/MAINTAINER_GUIDE.md

@@ -0,0 +1,70 @@
+# Maintainer Guide
+
+This guide is for maintaining the public GitHub repository.
+
+## Suggested Labels
+
+Create these labels in GitHub:
+
+| Label | Purpose |
+| --- | --- |
+| `bug` | Something is broken. |
+| `enhancement` | New feature or improvement. |
+| `docs` | Documentation work. |
+| `scenario` | Benchmark scenario or workload work. |
+| `observability` | Grafana, InfluxDB, metrics, dashboards. |
+| `runner` | CLI, config parsing, NBomber execution. |
+| `docker` | Docker/Compose target or stack changes. |
+| `good first issue` | Small scoped issue for new contributors. |
+| `help wanted` | Maintainer wants outside input. |
+| `question` | Needs clarification or discussion. |
+
+## Suggested Milestones
+
+Initial milestones:
+
+- `MVP`
+- `Serious Benchmarking`
+- `Observability`
+- `Scenario Packs`
+- `Docs`
+
+## Issue Style
+
+Good issues should include:
+
+- what is needed;
+- why it matters;
+- expected behavior;
+- rough implementation notes if known;
+- verification criteria.
+
+Example:
+
+```md
+## Goal
+
+Add ramping load profile support to benchmark config.
+
+## Why
+
+Baseline runs need constant load, but stress tests need increasing load.
+
+## Acceptance Criteria
+
+- Config supports constant and ramping profiles.
+- README includes an example.
+- Existing http-smoke config still works.
+- `dotnet build ScenarioBench.sln --no-restore -m:1 -v:minimal` passes.
+```
+
+## Pull Request Review
+
+Review priority:
+
+1. Correctness and reproducibility.
+2. Public repo safety.
+3. Clear config/report behavior.
+4. Docs and examples.
+5. Code style.
+