chore: standardize agent guidance

Author: jonathanperis

.agents/memory/MEMORY.md

@@ -0,0 +1,5 @@
+- [Architecture](architecture.md) — Native AOT, source-generated JSON, conditional OpenTelemetry, Npgsql multiplexing, build flag matrix.
+- [Workflow](workflow.md) — Branch+PR strategy required; PRs are rebase-only.
+- [GitHub Conventions](github.md) — Repo-wide community health files live in `jonathanperis/.github`; use `gh` CLI.
+- [User Profile](user_profile.md) — Maintainer context for sibling Rinha implementations and shared infrastructure patterns.
+- [GitHub Pages & Docs](github_pages.md) — Astro docs site, documentation source, deploy workflow, GHCR image, stress-test reports.

.agents/memory/architecture.md

@@ -0,0 +1,36 @@
+---
+name: .NET Rinha Architecture
+description: Native AOT Minimal APIs, source-generated JSON, conditional OpenTelemetry compilation, Npgsql multiplexing
+type: project
+---
+
+## Design Decisions
+
+**Single Program.cs with Minimal APIs:**
+- No controllers or MVC layers; route handlers are direct and compact.
+- The minimal shape is intentional for challenge performance.
+
+**Why:** Challenge constraints (1.5 CPU, 550MB RAM) favor zero-JIT startup and minimal allocations.
+
+**How to apply:** Keep all challenge routes in `Program.cs`. Do not add controllers or service layers unless a measured change justifies the extra overhead.
+
+## Key Technical Choices
+
+- **Native AOT** (`AOT=true`): eliminates JIT warmup in release images.
+- **Source generators**: `SourceGenerationContext` and `[JsonSerializable(...)]` metadata keep JSON compatible with AOT.
+- **Conditional compilation**: `#if !EXTRAOPTIMIZE` wraps OpenTelemetry code. Release builds set `EXTRA_OPTIMIZE=true` so observability support is compiled out.
+- **Npgsql multiplexing**: `Multiplexing=true` with a bounded pool in the compose connection string.
+- **Snake_case JSON**: `JsonNamingPolicy.SnakeCaseLower` matches the challenge API shape.
+
+## Build Flag Matrix
+
+| Flag | Development compose | Release workflow |
+|------|---------------------|------------------|
+| `AOT` | `true` | `true` |
+| `TRIM` | `false` | `false` |
+| `EXTRA_OPTIMIZE` | `false` | `true` |
+| `BUILD_CONFIGURATION` | `Release` | `Release` |
+
+## Shared Infrastructure
+
+This implementation follows the same broad Rinha2 infrastructure pattern as the sibling Rust, Go, and Python implementations: PostgreSQL stored procedures, NGINX on `9999`, and the shared `rinha2-back-end-k6` load-test image.

.agents/memory/github.md

@@ -0,0 +1,14 @@
+---
+name: GitHub Conventions & Shared .github Repo
+description: Repo-wide community health files live in jonathanperis/.github; use gh CLI for GitHub operations
+type: feedback
+---
+
+Repo-wide community health files (`CODE_OF_CONDUCT.md`, `CONTRIBUTING.md`, `SECURITY.md`, `FUNDING.yml`, issue/PR templates, and related files) are managed centrally in the `jonathanperis/.github` repository. Do not create these files in individual project repos.
+
+**Why:** GitHub automatically inherits community health files from the owner's `.github` repository. Duplicating them causes maintenance drift.
+
+**How to apply:**
+- Do not create community health files in this repo.
+- Use `gh` for repository, PR, issue, check, release, and merge operations.
+- If a community health file is needed, add it to `jonathanperis/.github` instead.

.agents/memory/github_pages.md

@@ -0,0 +1,12 @@
+---
+name: GitHub Pages & Documentation
+description: Astro docs site at jonathanperis.github.io/rinha2-back-end-dotnet served from docs/ and sourced from docs/wiki/
+type: reference
+---
+
+- **GitHub Pages:** https://jonathanperis.github.io/rinha2-back-end-dotnet/ — deployed by `.github/workflows/deploy.yml`.
+- **Documentation source:** Markdown files under `docs/wiki/` render into the Astro docs routes.
+- **Docs package:** `docs/package.json`; use Bun for install/build/lint.
+- **Deploy workflow:** `.github/workflows/deploy.yml` delegates to the shared Pages workflow and passes `package-manager: bun`.
+- **Stress-test reports:** k6 HTML reports are published under `docs/reports/` when release/report artifacts are present.
+- **Docker image:** `ghcr.io/jonathanperis/rinha2-back-end-dotnet:latest` — multi-platform manifest after the main release workflow completes.

.agents/memory/user_profile.md

@@ -0,0 +1,11 @@
+---
+name: Jonathan Peris - Developer Profile
+description: Maintainer context for multiple backend challenge implementations across .NET, Rust, Go, and Python
+type: user
+---
+
+- Maintains multiple implementations of the Rinha de Backend challenge, including .NET, Rust, Go, and Python variants.
+- Uses a shared infrastructure pattern across sibling Rinha2 implementations: PostgreSQL stored procedures, NGINX, and shared k6 test image.
+- Values clean linear git history, PR-based changes, CI/CD, and GitHub best practices.
+- Uses a centralized `jonathanperis/.github` repository for community health files across repos.
+- Prefers `gh` CLI over raw HTTP API calls for GitHub operations.

.agents/memory/workflow.md

@@ -0,0 +1,15 @@
+---
+name: Branch + PR Workflow & Rebase Strategy
+description: All changes must use branch+PR strategy; PRs are rebase-only
+type: feedback
+---
+
+All changes to this repository must follow a branch + PR workflow. Do not commit directly to `main`.
+
+**Why:** The repository keeps linear history on `main`.
+
+**How to apply:**
+- Create a feature/fix/docs/chore branch before making changes.
+- Create a PR with `gh pr create` targeting `main`.
+- Merge using rebase strategy only; do not use merge commits or squash merges.
+- Use conventional branch prefixes such as `docs/`, `fix/`, `feat/`, `chore/`, `refactor/`, and `ci/`.