refactor: rename label workflows and add generic uniqueness enforcement

- Rename sync-squad-labels.yml → issue-labels-sync.yml
- Delete squad-label-enforce.yml (hardcoded per-category logic)
- Add issue-labels-enforce-unique.yml: generic enforcement for any
  category:value labels, reads sync file for priority ordering,
  exempts squad:* labels
- Update doc references in 3 files

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

Author: EMaher

.copilot/skills/init-mode/SKILL.md

@@ -58,7 +58,7 @@ No team exists yet. Propose one — but **DO NOT create any files until the user
 
 **Seeding:** Each agent's `history.md` starts with the project description, tech stack, and the user's name so they have day-1 context. Agent folder names are the cast name in lowercase (e.g., `.squad/agents/ripley/`). The Scribe's charter includes maintaining `decisions.md` and cross-agent context sharing.
 
-**Team.md structure:** `team.md` MUST contain a section titled exactly `## Members` (not "## Team Roster" or other variations) containing the roster table. This header is hard-coded in GitHub workflows (`squad-heartbeat.yml`, `squad-issue-assign.yml`, `squad-triage.yml`, `sync-squad-labels.yml`) for label automation. If the header is missing or titled differently, label routing breaks.
+**Team.md structure:** `team.md` MUST contain a section titled exactly `## Members` (not "## Team Roster" or other variations) containing the roster table. This header is hard-coded in GitHub workflows (`squad-heartbeat.yml`, `squad-issue-assign.yml`, `squad-triage.yml`, `issue-labels-sync.yml`) for label automation. If the header is missing or titled differently, label routing breaks.
 
 **Merge driver for append-only files:** Create or update `.gitattributes` at the repo root to enable conflict-free merging of `.squad/` state across branches:
 ```

.github/workflows/issue-labels-enforce-unique.yml

@@ -0,0 +1,98 @@
+name: Enforce Unique Category Labels
+
+on:
+  issues:
+    types: [labeled]
+
+permissions:
+  issues: write
+  contents: read
+
+jobs:
+  enforce:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+
+      - name: Enforce one label per category
+        uses: actions/github-script@v7
+        with:
+          script: |
+            const fs = require('fs');
+            const issue = context.payload.issue;
+            const appliedLabel = context.payload.label.name;
+
+            // Only handle "category:value" labels
+            const match = appliedLabel.match(/^([^:]+):/);
+            if (!match) {
+              core.info(`Label "${appliedLabel}" has no category prefix — skipping`);
+              return;
+            }
+
+            const category = match[1];
+
+            // squad: labels are exempt from uniqueness enforcement
+            if (category === 'squad') {
+              core.info(`squad: labels are exempt — skipping`);
+              return;
+            }
+
+            // Collect all labels in the same category currently on the issue
+            const allLabels = issue.labels.map(l => l.name);
+            const sameCategory = allLabels.filter(l => l.startsWith(category + ':'));
+
+            if (sameCategory.length <= 1) {
+              core.info(`Only one "${category}:" label present — nothing to enforce`);
+              return;
+            }
+
+            // Read the sync workflow to determine canonical label ordering.
+            // Labels listed earlier in issue-labels-sync.yml have higher priority.
+            const syncPath = '.github/workflows/issue-labels-sync.yml';
+            let labelOrder = [];
+            if (fs.existsSync(syncPath)) {
+              const syncContent = fs.readFileSync(syncPath, 'utf8');
+              const nameRegex = /name:\s*'([^']+)'/g;
+              let m;
+              while ((m = nameRegex.exec(syncContent)) !== null) {
+                if (m[1].startsWith(category + ':')) {
+                  labelOrder.push(m[1]);
+                }
+              }
+            }
+
+            // Determine winner: first label (by sync-file order) that is on the issue.
+            // If the category isn't in the sync file, fall back to keeping whichever
+            // label appeared first in the issue's current label list.
+            let winner = null;
+            if (labelOrder.length > 0) {
+              for (const ordered of labelOrder) {
+                if (sameCategory.includes(ordered)) {
+                  winner = ordered;
+                  break;
+                }
+              }
+            }
+            if (!winner) {
+              winner = sameCategory[0];
+            }
+
+            const toRemove = sameCategory.filter(l => l !== winner);
+            core.info(`Conflict in "${category}:" — keeping "${winner}", removing ${toRemove.join(', ')}`);
+
+            for (const label of toRemove) {
+              await github.rest.issues.removeLabel({
+                owner: context.repo.owner,
+                repo: context.repo.repo,
+                issue_number: issue.number,
+                name: label
+              });
+              core.info(`Removed: ${label}`);
+            }
+
+            await github.rest.issues.createComment({
+              owner: context.repo.owner,
+              repo: context.repo.repo,
+              issue_number: issue.number,
+              body: `🏷️ Label conflict resolved in \`${category}:\` — kept \`${winner}\`, removed ${toRemove.map(l => '`' + l + '`').join(', ')}.`
+            });

.github/workflows/sync-squad-labels.yml .github/workflows/issue-labels-sync.yml.github/workflows/sync-squad-labels.yml renamed to .github/workflows/issue-labels-sync.yml

@@ -58,7 +58,7 @@ No team exists yet. Propose one — but **DO NOT create any files until the user
 
 **Seeding:** Each agent's `history.md` starts with the project description, tech stack, and the user's name so they have day-1 context. Agent folder names are the cast name in lowercase (e.g., `.squad/agents/ripley/`). The Scribe's charter includes maintaining `decisions.md` and cross-agent context sharing.
 
-**Team.md structure:** `team.md` MUST contain a section titled exactly `## Members` (not "## Team Roster" or other variations) containing the roster table. This header is hard-coded in GitHub workflows (`squad-heartbeat.yml`, `squad-issue-assign.yml`, `squad-triage.yml`, `sync-squad-labels.yml`) for label automation. If the header is missing or titled differently, label routing breaks.
+**Team.md structure:** `team.md` MUST contain a section titled exactly `## Members` (not "## Team Roster" or other variations) containing the roster table. This header is hard-coded in GitHub workflows (`squad-heartbeat.yml`, `squad-issue-assign.yml`, `squad-triage.yml`, `issue-labels-sync.yml`) for label automation. If the header is missing or titled differently, label routing breaks.
 
 **Merge driver for append-only files:** Create or update `.gitattributes` at the repo root to enable conflict-free merging of `.squad/` state across branches:
 ```

.github/workflows/squad-label-enforce.yml

@@ -92,7 +92,7 @@ No team exists yet. Propose one — but **DO NOT create any files until the user
 
 **Seeding:** Each agent's `history.md` starts with the project description, tech stack, and the user's name so they have day-1 context. Agent folder names are the cast name in lowercase (e.g., `.squad/agents/ripley/`). The Scribe's charter includes maintaining `decisions.md` and cross-agent context sharing. Rai's charter is seeded from the `Rai-charter.md` template, and `.squad/rai/policy.md` is seeded from `rai-policy.md`.
 
-**Team.md structure:** `team.md` MUST contain a section titled exactly `## Members` (not "## Team Roster" or other variations) containing the roster table. This header is hard-coded in GitHub workflows (`squad-heartbeat.yml`, `squad-issue-assign.yml`, `squad-triage.yml`, `sync-squad-labels.yml`) for label automation. If the header is missing or titled differently, label routing breaks.
+**Team.md structure:** `team.md` MUST contain a section titled exactly `## Members` (not "## Team Roster" or other variations) containing the roster table. This header is hard-coded in GitHub workflows (`squad-heartbeat.yml`, `squad-issue-assign.yml`, `squad-triage.yml`, `issue-labels-sync.yml`) for label automation. If the header is missing or titled differently, label routing breaks.
 
 **Merge driver for append-only files:** Create or update `.gitattributes` at the repo root to enable conflict-free merging of `.squad/` state across branches:
 ```
@@ -186,7 +186,7 @@ For each squad member with assigned issues, note them in the session context. Wh
 
 **Proactive issue pickup:** If a user starts a session and there are open `squad:{member}` issues, mention them: *"Hey {user}, {AgentName} has an open issue — #42: Fix auth endpoint timeout. Want them to pick it up?"*
 
-**Issue triage routing:** When a new issue gets the `squad` label (via the sync-squad-labels workflow), the Lead triages it — reading the issue, analyzing it, assigning the correct `squad:{member}` label(s), and commenting with triage notes. The Lead can also reassign by swapping labels.
+**Issue triage routing:** When a new issue gets the `squad` label (via the issue-labels-sync workflow), the Lead triages it — reading the issue, analyzing it, assigning the correct `squad:{member}` label(s), and commenting with triage notes. The Lead can also reassign by swapping labels.
 
 **⚡ Read `.squad/team.md` (roster), `.squad/routing.md` (routing), and `.squad/casting/registry.json` (persistent names) as parallel tool calls in a single turn. Do NOT read these sequentially.**