chore: make version/issue/milestone/project tracking a standing rule across harnesses

Author: kinncj

.cursor/rules/version-and-issues.mdc

@@ -0,0 +1,29 @@
+---
+description: Version & issue tracking — every change gets a SemVer class, an issue with bug|enhancement label, a major/minor milestone, and a card on project 124
+alwaysApply: true
+---
+
+## Version & Issue Tracking (mandatory)
+
+Every change we work on is tracked. When you start a piece of work (and before you
+finish it):
+
+1. **Classify the SemVer bump** — **major** (breaking), **minor** (new
+   backward-compatible feature), or **patch** (bug fix / no API change).
+2. **Milestone — major & minor only.** Ensure a milestone `vX.Y.0` exists for the
+   target minor/major; create it if missing. **Patches never get their own
+   milestone** — attach them to their minor's milestone (`vX.Y.0`).
+3. **Issue — every change, patches included.** Create a GitHub issue, labelled
+   **`bug`** (patch / fix) or **`enhancement`** (feature / minor / major), assigned
+   to the target major/minor milestone.
+4. **Project board.** Add the issue to project **124**
+   (`github.project_number` in `project.config.yaml`) and set **Status**
+   (`In progress` while working, `Done` when shipped).
+5. **Link & close.** The PR references the issue (`Closes #N`); merging closes it.
+   On release the milestone version equals the release tag.
+6. **No Claude/Anthropic attribution** anywhere — commits, PR bodies, issues,
+   releases.
+
+Mechanics live in the maple skills — use them, don't hand-roll:
+`gh-labels-milestones` (milestone/label upsert), `gh-issues` (create/label/
+milestone), `gh-projects` (board add + Status). Config: `project.config.yaml → github`.

.github/copilot-instructions.md

@@ -203,3 +203,16 @@ Insert design sub-pipeline before IMPLEMENT:
 | Design system | `docs/design/system/components/` |
 
 Never write design artifacts to `docs/wireframes/`, `docs/identity/`, `docs/mockups/`, or any location outside `docs/design/`.
+
+## Version & Issue Tracking (mandatory)
+
+Every change is tracked automatically. When you start a piece of work (and before you finish it):
+
+1. **Classify the SemVer bump** — major (breaking) / minor (new backward-compatible feature) / patch (bug fix, no API change).
+2. **Milestone — major & minor only.** Ensure `vX.Y.0` exists (create if missing). **Patches never get their own milestone** — attach to their minor's `vX.Y.0`.
+3. **Issue — every change, patches included.** Labelled **`bug`** (patch/fix) or **`enhancement`** (feature), assigned to the target major/minor milestone.
+4. **Project 124** — add the issue and set **Status** (`In progress` → `Done`). Board id in `project.config.yaml → github`.
+5. **Link & close** — the PR says `Closes #N`; on release the milestone version equals the release tag.
+6. **No Claude/Anthropic attribution** anywhere — commits, PR bodies, issues, releases.
+
+Mechanics via the maple skills: `gh-labels-milestones`, `gh-issues`, `gh-projects`.

AGENTS.md

@@ -73,3 +73,19 @@ All agents use: `make build`, `make test`, `make test-integration`, `make test-e
 - Branch naming: `feat/{slug}`, `fix/{slug}`
 - Squash merge to main
 - Humanized commit messages; **no `Co-Authored-By` lines**.
+- **No Claude/Anthropic attribution** anywhere — commits, PR bodies, issues, releases.
+
+## Version & Issue Tracking (mandatory)
+Every change is tracked automatically. When you start a piece of work (and before you
+finish it):
+1. **Classify the SemVer bump** — major (breaking) / minor (new backward-compatible
+   feature) / patch (bug fix, no API change).
+2. **Milestone — major & minor only.** Ensure `vX.Y.0` exists (create if missing).
+   **Patches never get their own milestone** — attach to their minor's `vX.Y.0`.
+3. **Issue — every change, patches included.** Labelled **`bug`** (patch/fix) or
+   **`enhancement`** (feature), assigned to the target major/minor milestone.
+4. **Project 124** — add the issue and set **Status** (`In progress` → `Done`).
+   Board id in `project.config.yaml → github`.
+5. **Link & close** — PR says `Closes #N`; on release the milestone == the tag.
+
+Mechanics via the maple skills: `gh-labels-milestones`, `gh-issues`, `gh-projects`.

CLAUDE.md

@@ -50,7 +50,7 @@ Pipeline rules:
 4. QA writes failing tests. Implementation agents make them pass.
 5. 3 consecutive failures on any task → escalate to human.
 6. `make test-all` must pass before Phase 8 gate.
-7. Every feature gets a GitHub issue. Agents update it via `gh` CLI.
+7. Every change gets a GitHub issue, milestone, and project card — see **Version & Issue Tracking** below.
 8. Conventional Commits: `feat:`, `fix:`, `test:`, `docs:`, `infra:`, `refactor:`.
 
 **Gate enforcement:**
@@ -68,6 +68,32 @@ Pipeline rules:
 
 ---
 
+## Version & Issue Tracking (mandatory)
+
+Every change we work on is tracked — this is automatic, not optional. When you start
+a piece of work (and before you finish it):
+
+1. **Classify the SemVer bump** — **major** (breaking), **minor** (new
+   backward-compatible feature), or **patch** (bug fix / no API change).
+2. **Milestone — major & minor only.** Ensure a milestone `vX.Y.0` exists for the
+   target minor/major; create it if missing. **Patches never get their own
+   milestone** — attach them to their minor's milestone (`vX.Y.0`).
+3. **Issue — every change, patches included.** Create a GitHub issue, labelled
+   **`bug`** (patch / fix) or **`enhancement`** (feature / minor / major), assigned to
+   the target major/minor milestone.
+4. **Project board.** Add the issue to project **124**
+   (`github.project_number` in `project.config.yaml`) and set **Status**
+   (`In progress` while working, `Done` when shipped).
+5. **Link & close.** The PR references the issue (`Closes #N`); merging closes it. On
+   release the milestone version equals the release tag.
+6. **No Claude/Anthropic attribution** anywhere — commits, PR bodies, issues, releases.
+
+Use the maple skills for the mechanics, don't hand-roll: `gh-labels-milestones`
+(milestone/label upsert), `gh-issues` (create/label/milestone), `gh-projects` (board
+add + Status). Board and label config live in `project.config.yaml → github`.
+
+---
+
 ## Communication Style
 
 - Short sentences. Structured formatting (bullets, tables, sections).

project.config.yaml

@@ -25,5 +25,14 @@ design:
   token_format: dtcg      # W3C DTCG
 
 github:
-  project_number: null
-  project_node_id: null
+  project_number: 124
+  project_node_id: "PVT_kwHOAAR2vs4BcZgS"
+  status_field_id: "PVTSSF_lAHOAAR2vs4BcZgSzhXCpSM"
+  # Versioning & tracking (mandatory — see the "Version & Issue Tracking" section in
+  # CLAUDE.md / AGENTS.md). Every change = a GitHub issue, labelled bug|enhancement,
+  # on project 124 with a Status. Milestones exist only for major/minor versions
+  # (vX.Y.0); patches attach to their minor's milestone, never their own.
+  labels:
+    fix: "bug"           # patch / bugfix
+    feature: "enhancement" # minor / major
+  milestone_granularity: "minor"  # major & minor only — never per-patch