QEP-2 §Scope: meta takes the org default, the core 19. Its local project and education labels are resolved by the migration like any other non-standard label, and are explicitly not held as a standing exception.
project is the harder of the two. The QuantEcon/status-projects collector contract records that the dashboard adds no labels and keys on nothing QEP-2 removes, so nothing machine-read depends on it — but it carries tags on live issues here, which makes it a re-tag or a recorded quarantine, never an unattended delete. The tracker structure project used to signal is now carried by the native Project issue type and by the projects registry.
Acceptance
QEP-2 §Scope:
metatakes the org default, the core 19. Its localprojectandeducationlabels are resolved by the migration like any other non-standard label, and are explicitly not held as a standing exception.projectis the harder of the two. The QuantEcon/status-projects collector contract records that the dashboard adds no labels and keys on nothing QEP-2 removes, so nothing machine-read depends on it — but it carries tags on live issues here, which makes it a re-tag or a recorded quarantine, never an unattended delete. The tracker structureprojectused to signal is now carried by the nativeProjectissue type and by the projects registry.Acceptance
metacarries the core 19 and nothing elseprojectandeducationeach have a recorded disposition, with their issues re-tagged before removal if they are removed