github-labelslisted

# GitHub Labels — kookr-ai/kookr When creating or updating issues and PRs, apply labels from the categories below. Every issue/PR should have at least one **type** label and one **area** label. Add **priority** and **phase** labels when known. ## Label taxonomy ### Type (pick one — what kind of work is this?) | Label | When to use | |---|---| | `bug` | Something is broken or behaving incorrectly | | `type: feature` | New user-facing capability or behavior | | `enhancement` | Improvement to existing functionality | | `type: refactor` | Code restructuring with no behavior change | | `type: test` | Adding or improving tests (unit, integration, E2E) | | `type: chore` | Build system, CI, tooling, dependency updates | | `type: design` | ADR, RFC, or architecture proposal | | `type: spike` | Research, proof-of-concept, or exploration | | `type: security` | Security vulnerability, fix, or hardening | | `type: performance` | Performance regression or optimization | | `documentation` | Docs-only changes (README, feature specs, guides) | ### Priority (pick one — how urgent?) | Label | When to use | |---|---| | `priority: critical` | Blocks release or causes data loss — drop everything | | `priority: high` | Important, resolve in current work cycle | | `priority: medium` | Normal priority, scheduled for near-term | | `priority: low` | Nice to have, no time pressure | ### Status (pick one — current state) | Label | When to use | |---|---| | `status: needs triage` | New issue, not