Labels

• area:api

  area:api

  HTTP APIs, OpenAPI, request/response models, route design.

• area:docs

  area:docs

  Documentation, README, runbooks, API docs, architecture notes.

• area:eventing

  area:eventing

  Kafka, outbox, consumers, producers, replay, idempotency, schemas.

• area:frontend

  area:frontend

  UI, routes, forms, frontend state, browser app integration.

• area:infra

  area:infra

  Docker, Kubernetes, Terraform, CI/CD, hosting, gateway infrastructure.

• area:observability

  area:observability

  Logging, metrics, traces, dashboards, diagnostics.

• area:persistence

  area:persistence

  Database schema, EF mappings, migrations, repositories, transactions.

• area:security

  area:security

  Auth, authorization, secrets, permissions, data protection.

• area:testing

  area:testing

  Unit, integration, contract, E2E, smoke, load, regression tests.

• blocked

  blocked

  Cannot progress without a decision, dependency, access, or external input.

• breaking-change

  breaking-change

  Introduces a breaking API, event, schema, behaviour, or migration change.

• data-risk

  data-risk

  Could affect data integrity, migration safety, replay, deletion, or recovery.

• good-first-issue

  good-first-issue

  Safe, well-scoped issue suitable for a first contribution.

• help-wanted

  help-wanted

  External or wider-team help would be welcome.

• needs:decision

  needs:decision

  Requires an architectural, product, or technical decision.

• needs:discussion

  needs:discussion

  Needs discussion before implementation or closure.

• needs:review

  needs:review

  Needs human review, design review, or technical review.

• needs:triage

  needs:triage

  Captured but not yet reviewed or classified.

• security-risk

  security-risk

  Has security implications or needs extra security care.

• tech-debt

  tech-debt

  Known design, implementation, or operational debt.