fix(labels): make lib/labels.yml the only canonical label file

.github/README.md

@@ -97,7 +97,7 @@ Starter workflows available in every org repository under **Actions > New workfl
 | Zsh CI        | Starter Zsh CI workflow     |
 | Rclone Action | File sync with rclone       |
 
-Label definitions live in [`./lib/labels.yml`](lib/labels.yml) and should be applied through org maintenance scripts or API-driven automation, not via a generic starter workflow template.
+Label definitions live in [`lib/labels.yml`](../lib/labels.yml) and should be applied through org maintenance scripts or API-driven automation, not via a generic starter workflow template.
 
 Task tracking is documented in [`../runbooks/project-tracker.md`](../runbooks/project-tracker.md).
 
@@ -133,7 +133,7 @@ This repository is the right place for any **organization-level** configuration:
 - **Defining weekly review, ADR, or release coordination workflows** — add or update the relevant file under `runbooks/`
 - **Recording cross-agent progress** — follow `.github/AGENT_MEMORY.md` and keep active state in issues, pull requests, and Linear
 - **Managing organization task tracking** — follow `../runbooks/project-tracker.md`
-- **Updating the shared label set** — edit `.github/lib/labels.yml` and roll it out via the org's maintenance automation
+- **Updating the shared label set** — edit `lib/labels.yml` and roll it out via the org's maintenance automation
 - **Cleaning legacy labels** — follow `../runbooks/labels.md` before deleting labels from live repositories
 - **Creating a reusable CI action** — add a composite action under `actions/<name>/action.yml`
 - **Providing a starter workflow** — add `.yml` + `.properties.json` to `workflow-templates/`

AGENTS.md

@@ -86,7 +86,7 @@ Use `runbooks/triage.md` for the full process.
 Short version:
 
 - Classify issues by work type, area, and severity.
-- Use the canonical labels from `.github/lib/labels.yml`.
+- Use the canonical labels from `lib/labels.yml`.
 - Search for prior art across the org before responding.
 - Put cross-repo, release-blocking, security, or strategic work on Linear.
 

runbooks/labels.md

@@ -4,7 +4,7 @@ Use this runbook when cleaning or syncing labels across z-shell repositories.
 
 ## Source of truth
 
-`.github/lib/labels.yml` is the canonical organization label set.
+`lib/labels.yml` is the canonical organization label set.
 
 Use compact namespace names:
 
@@ -108,11 +108,11 @@ Also retire spaced namespace variants such as `type: bug`, `area: docs`, `priori
    scripts/labels-sync.rb --all-repos > /tmp/z-shell-labels-dry-run.md
    ```
 
-3. Create or update every canonical label from `.github/lib/labels.yml`.
+3. Create or update every canonical label from `lib/labels.yml`.
 4. For each legacy label, find open issues and pull requests using it.
 5. Add the canonical replacement to each item before removing the legacy label.
 6. Delete legacy labels only after they are no longer used.
-7. Re-run the dry-run audit and compare it with `.github/lib/labels.yml`.
+7. Re-run the dry-run audit and compare it with `lib/labels.yml`.
 
 Do not delete unknown labels in bulk. If a repository has a local label that is not obviously legacy, open or update an issue before removing it.
 
@@ -180,6 +180,6 @@ scripts/labels-sync.rb \
 
 ## See also
 
-- `.github/lib/labels.yml`
+- `lib/labels.yml`
 - `runbooks/triage.md`
 - `runbooks/org-review.md`

runbooks/triage.md

@@ -23,7 +23,7 @@ If classification takes more than a few minutes, mark it for investigation and m
 
 ## Step 2 — Apply the canonical labels
 
-The organization label set in `.github/lib/labels.yml` is the source of truth. Apply at least one work-type label and one area label when the area is known.
+The organization label set in `lib/labels.yml` is the source of truth. Apply at least one work-type label and one area label when the area is known.
 
 ### Work type