Labels

• area: admin-ui

  WordPress admin screens, settings UI, notices, onboarding, or admin bar UX.
• area: assets-manager

  Asset Manager behavior, compatibility, UI, persistence, or per-page controls.
• area: build-ci

  Composer, npm, linting, static analysis, GitHub Actions, or release automation.
• area: cache

  Page cache, menu cache, preload, invalidation, observability, or cache settings.
• area: compatibility

  WordPress, PHP, multisite, WooCommerce, theme, or plugin compatibility.
• area: docs

  Documentation URLs, help links, readme copy, changelog, or support guidance.
• area: frontend

  Public-facing frontend output, assets, feeds, headers, or visitor behavior.
• area: integrations

  External scripts, analytics, CDN providers, APIs, or third-party services.
• area: performance

  Performance-sensitive behavior, page weight, caching, preloading, or resource hints.
• area: settings

  Settings schema, storage contracts, migration, import/export, and validation.
• bug

  Confirmed or likely defect affecting runtime behavior, UX, compatibility, or data handling.
• dependencies

  Pull requests that update a dependency file
• duplicate

  This issue or pull request already exists
• enhancement

  Feature or improvement request that changes product behavior or user experience.
• good first issue

  Scoped, low-risk issue suitable for a first contribution.
• help wanted

  Maintainer-reviewed issue where outside contribution is welcome.
• invalid

  This doesn't seem right
• javascript

  Pull requests that update javascript code
• priority: high

  Important for the next planned release or high user impact.
• priority: low

  Nice-to-have, low urgency, or small polish item.
• priority: medium

  Useful or user-impacting work that should be planned but is not blocking now.
• question

  Further information is requested
• risk: backward-compatibility

  Touches public data, options, hooks, migrations, or established behavior.
• risk: release-blocker

  Should be resolved or explicitly deferred before the target release ships.
• status: in-progress

  Work has a branch, PR, or active release branch implementation path.
• status: needs-repro

  Needs a current reproduction, environment details, or validation before implementation.
• status: needs-spec

  Needs acceptance criteria, scope, UX, or technical design before implementation.
• status: needs-verification

  Likely implemented or partially handled; needs validation before closure.
• status: ready

  Scoped enough for implementation without major open questions.
• type: maintenance

  Engineering maintenance, CI, dependency, refactor, tooling, or release hygiene.