This repo's labels predate QEP-2 — the standard's home repo is unmigrated

[mmcky]

Observation from the QEP-6 field-test session (2026-08-27), noticed while tidying #19/#20: this repository's own label set is the pre-QEP-2 legacy set, not the standard its own qeps/qep-0002-labels.yml defines. The standard's home repo is itself unmigrated.

Current labels against the core set in the appendix:

Current label	QEP-2 disposition
bug, question, duplicate, wontfix, good first issue, help wanted, maintenance, discuss	In the core set — colors and descriptions need syncing to the appendix (e.g. discuss here is d876e3, the appendix says f904a0)
high priority	Rename variant of high-priority
in-work, ready, testing, blocked	Retired status labels — QEP-2's one behavioural change moves lifecycle state onto native features, and blocked was explicitly rejected in favour of native issue dependencies
editor	Lecture-extension label on a non-lecture repo
qep	Repo-local, not in the standard — needs a human mapping decision: keep as a deliberate repo-local extra, or retire
(absent)	Missing core labels: enhancement, documentation, infrastructure, low-priority, security, do-not-merge, automated, broken-links, build-failure, dependencies

Labelling practice is also thin: #15, #18, #19, and #20 all carry no labels; of the recent QEP threads only #11 is labelled (discuss).

The migration itself belongs to the QEP-2 rollout programme (QuantEcon/meta#358), whose delivery project QuantEcon/cli#20 ships qe gh labels sync — a tool that reads the yml appendix from this very repository. This issue records the instance so the rollout picks this repo up rather than proposing a hand-migration ahead of the tool; if anything, the repo whose file defines the schema is the natural first fixture for the sync tool's rollout phase.

The one decision that is this repo's rather than the tool's: what to do with qep, the only genuinely repo-local label here.