Labels

• phase:architecture

  Structural system changes and boundary clarification.
• phase:governance

  Governance rollouts, standards enforcement, process updates.
• phase:hardening

  Security/safety/robustness improvements and guardrails.
• phase:mvp

  Minimum viable functionality to establish baseline.
• phase:observability

  Metrics/logging/tracing improvements.
• phase:operations

  Runtime, deployment, healthchecks, and operability.
• phase:optimization

  Performance/cost improvements after correctness is stable.
• phase:release

  Release preparation, packaging, and deploy readiness.
• phase:research

  Feasibility exploration and unknown reduction.
• phase:stabilization

  Correctness, CI confidence, and reliability improvements.
• priority:critical

  Must be addressed immediately.
• priority:high

  High priority; should be scheduled soon.
• priority:low

  Low priority; do last.
• priority:medium

  Normal priority.
• risk:critical

  High risk to security, correctness, or stability.
• risk:high

  Significant technical or operational risk.
• risk:low

  Low risk.
• risk:medium

  Moderate risk.
• status:blocked

  Blocked by unresolved issues listed under `blocked-by` in the issue body.
• status:needs-adr

  Requires an ADR before implementation.
• status:needs-clarification

  Cannot proceed until missing info is provided.
• status:needs-tests

  Requires test coverage (TDD enforcement).
• status:ready

  No unresolved `blocked-by` dependencies; eligible to start.
• type:architecture

  Structural design or boundary change affecting system architecture.
• type:bug

  A defect: something is not working as intended.
• type:documentation

  Documentation improvements or additions.
• type:feature

  New capability or user-facing functionality.
• type:governance

  Process, standards, templates, or engineering governance changes.
• type:infra

  Infrastructure, CI/CD, build, or environment-related work.
• type:performance

  Performance/cost/latency optimization work.