Correct + reinforce version/issue/milestone/project tracking across harnesses (#153)

type:* label taxonomy (per gh-labels-milestones), schema-valid config (status_field_id; dropped ad-hoc keys), Status casing (In progress), and the rule reinforced in the orchestrator agents across .claude/.cursor/.opencode. Closes #152.

Author: kinncj

.claude/agents/orchestrator.md

@@ -262,7 +262,19 @@ If failure → return to Phase 5.
 On success: Create PR via gh pr create, post completion summary.
 
 ## GitHub Issue Management
-Every feature has a corresponding GitHub issue. Update issues at each phase transition:
+
+### Version & Issue Tracking (mandatory — every change)
+Classify the SemVer bump first: **major** (breaking) / **minor** (new backward-compatible
+feature) / **patch** (bug fix / no API change). Then:
+- **Milestone — major & minor only.** Ensure `vX.Y.0` exists (`gh-labels-milestones`);
+  patches attach to their minor's `vX.Y.0`, never get their own.
+- **Issue — every change.** Labelled the matching **`type:*`** label (`type:bug` fix · `type:feature` feature · `type:docs`/`type:refactor`/`type:chore`, per `gh-labels-milestones`), assigned to the target major/minor milestone (`gh-issues`).
+- **Project board.** Add the issue and set **Status** (`In progress` → `Done`); read the
+  board number from `github.project_number` in `project.config.yaml` (`gh-projects`),
+  never hard-code it.
+- PR `Closes #N`. **No Claude/Anthropic attribution** anywhere.
+
+Every change has a corresponding GitHub issue. Update issues at each phase transition:
 
 ```bash
 # Create issue (done by @product-owner, but you track)

.claude/schemas/project.config.schema.json

@@ -4,13 +4,17 @@
   "title": "MAPLE Project Configuration",
   "description": "Project-level configuration for the MAPLE platform (project.config.yaml).",
   "type": "object",
-  "required": ["project"],
+  "required": [
+    "project"
+  ],
   "additionalProperties": false,
   "properties": {
     "project": {
       "type": "object",
       "description": "Project identity and metadata.",
-      "required": ["name"],
+      "required": [
+        "name"
+      ],
       "additionalProperties": false,
       "properties": {
         "name": {
@@ -38,7 +42,10 @@
         "mode": {
           "type": "string",
           "description": "standard: full Spec-Kit + 8-phase pipeline. spike: skips Spec-Kit; used for time-boxed research tasks.",
-          "enum": ["standard", "spike"],
+          "enum": [
+            "standard",
+            "spike"
+          ],
           "default": "standard"
         },
         "require_adr_for": {
@@ -75,7 +82,11 @@
         "bdd": {
           "type": "string",
           "description": "BDD framework used for Gherkin scenario automation. cucumber = @cucumber/cucumber (JS/TS) or Cucumber-JVM (Java/.NET). behave = Python. none = disabled.",
-          "enum": ["cucumber", "behave", "none"],
+          "enum": [
+            "cucumber",
+            "behave",
+            "none"
+          ],
           "default": "cucumber"
         },
         "step_defs_dir": {
@@ -98,7 +109,12 @@
         "ui_library": {
           "type": "string",
           "description": "Component library used for mockup generation and component scaffolding.",
-          "enum": ["mantine", "tailwind", "shadcn", "none"],
+          "enum": [
+            "mantine",
+            "tailwind",
+            "shadcn",
+            "none"
+          ],
           "default": "none"
         },
         "tokens_file": {
@@ -109,13 +125,20 @@
         "wireframe_format": {
           "type": "string",
           "description": "Default format for wireframes generated by the wireframe-architect agent.",
-          "enum": ["ascii", "svg", "html"],
+          "enum": [
+            "ascii",
+            "svg",
+            "html"
+          ],
           "default": "ascii"
         },
         "target": {
           "type": "string",
           "description": "UI medium the design phase targets. web = HTML/React/CSS artifacts and browser a11y. tui = terminal ASCII wireframes, lipgloss mockups, and terminal a11y. Selects which artifacts the design agents emit; artifact paths are identical across targets.",
-          "enum": ["web", "tui"],
+          "enum": [
+            "web",
+            "tui"
+          ],
           "default": "web"
         }
       }
@@ -126,14 +149,28 @@
       "additionalProperties": false,
       "properties": {
         "project_number": {
-          "type": ["integer", "null"],
+          "type": [
+            "integer",
+            "null"
+          ],
           "description": "GitHub Project v2 number (numeric ID, not node ID). Set by `maple project bootstrap`.",
           "default": null
         },
         "project_node_id": {
-          "type": ["string", "null"],
+          "type": [
+            "string",
+            "null"
+          ],
           "description": "GitHub Project v2 GraphQL node ID. Set by `maple project bootstrap`.",
           "default": null
+        },
+        "status_field_id": {
+          "type": [
+            "string",
+            "null"
+          ],
+          "description": "GitHub Project v2 Status single-select field node ID (used to set a card's Status). Set by `maple project bootstrap`.",
+          "default": null
         }
       }
     },

.claude/skills/gh-projects/SKILL.md

@@ -18,7 +18,7 @@ Manage GitHub Projects v2 board operations: add issues as cards, update field va
 | `issue_node_id` | `gh-issues` skill output | `"I_kwDO..."` |
 | `issue_number` | `gh-issues` skill output | `42` |
 | `field_name` | project field name | `"Status"` |
-| `field_value` | target option name | `"In Progress"` |
+| `field_value` | target option name | `"In progress"` |
 
 ## Read project config
 
@@ -153,8 +153,8 @@ gh api graphql -f query='
 | Phase | Field | Value |
 |---|---|---|
 | Discover | Status | `Todo` |
-| Architect | Status | `In Progress` |
-| Implement | Status | `In Progress` |
+| Architect | Status | `In progress` |
+| Implement | Status | `In progress` |
 | Validate | Status | `In Review` |
 | Done | Status | `Done` |
 
@@ -182,6 +182,6 @@ gh project item-list "$PROJECT_NUMBER" \
 
 ```
 [gh-projects] ADD    #42  → project #{project_number}  item_id={id}
-[gh-projects] UPDATE #42  field=Status  value="In Progress"
+[gh-projects] UPDATE #42  field=Status  value="In progress"
 [gh-projects] SKIP   #42  already on board
 ```

.cursor/agents/orchestrator.md

@@ -262,7 +262,19 @@ If failure → return to Phase 5.
 On success: Create PR via gh pr create, post completion summary.
 
 ## GitHub Issue Management
-Every feature has a corresponding GitHub issue. Update issues at each phase transition:
+
+### Version & Issue Tracking (mandatory — every change)
+Classify the SemVer bump first: **major** (breaking) / **minor** (new backward-compatible
+feature) / **patch** (bug fix / no API change). Then:
+- **Milestone — major & minor only.** Ensure `vX.Y.0` exists (`gh-labels-milestones`);
+  patches attach to their minor's `vX.Y.0`, never get their own.
+- **Issue — every change.** Labelled the matching **`type:*`** label (`type:bug` fix · `type:feature` feature · `type:docs`/`type:refactor`/`type:chore`, per `gh-labels-milestones`), assigned to the target major/minor milestone (`gh-issues`).
+- **Project board.** Add the issue and set **Status** (`In progress` → `Done`); read the
+  board number from `github.project_number` in `project.config.yaml` (`gh-projects`),
+  never hard-code it.
+- PR `Closes #N`. **No Claude/Anthropic attribution** anywhere.
+
+Every change has a corresponding GitHub issue. Update issues at each phase transition:
 
 ```bash
 # Create issue (done by @product-owner, but you track)

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

@@ -1,5 +1,5 @@
 ---
-description: Version & issue tracking — every change gets a SemVer class, an issue with bug|enhancement label, a major/minor milestone, and a card on the configured project board (project.config.yaml)
+description: Version & issue tracking — every change gets a SemVer class, an issue with the matching type:* label, a major/minor milestone, and a card on the configured project board (project.config.yaml)
 alwaysApply: true
 ---
 
@@ -14,7 +14,7 @@ finish it):
    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
+   the matching **`type:*`** label (`type:bug` fix · `type:feature` feature · `type:docs`/`type:refactor`/`type:chore`, per `gh-labels-milestones`), assigned
    to the target major/minor milestone.
 4. **Project board.** Add the issue to the project board — read its number from
    `github.project_number` in `project.config.yaml` (never hard-code it) — and set

.cursor/skills/gh-projects/SKILL.md

@@ -18,7 +18,7 @@ Manage GitHub Projects v2 board operations: add issues as cards, update field va
 | `issue_node_id` | `gh-issues` skill output | `"I_kwDO..."` |
 | `issue_number` | `gh-issues` skill output | `42` |
 | `field_name` | project field name | `"Status"` |
-| `field_value` | target option name | `"In Progress"` |
+| `field_value` | target option name | `"In progress"` |
 
 ## Read project config
 
@@ -153,8 +153,8 @@ gh api graphql -f query='
 | Phase | Field | Value |
 |---|---|---|
 | Discover | Status | `Todo` |
-| Architect | Status | `In Progress` |
-| Implement | Status | `In Progress` |
+| Architect | Status | `In progress` |
+| Implement | Status | `In progress` |
 | Validate | Status | `In Review` |
 | Done | Status | `Done` |
 
@@ -182,6 +182,6 @@ gh project item-list "$PROJECT_NUMBER" \
 
 ```
 [gh-projects] ADD    #42  → project #{project_number}  item_id={id}
-[gh-projects] UPDATE #42  field=Status  value="In Progress"
+[gh-projects] UPDATE #42  field=Status  value="In progress"
 [gh-projects] SKIP   #42  already on board
 ```

.github/copilot-instructions.md

@@ -210,7 +210,7 @@ Every change is tracked automatically. When you start a piece of work (and befor
 
 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.
+3. **Issue — every change, patches included.** Labelled the matching **`type:*`** label (`type:bug` fix · `type:feature` feature · `type:docs`/`type:refactor`/`type:chore`, per `gh-labels-milestones`), assigned to the target major/minor milestone.
 4. **Project board** — add the issue and set **Status** (`In progress` → `Done`). Read the board number from `github.project_number` in `project.config.yaml` (never hard-code it).
 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.

.opencode/agents/orchestrator.md

@@ -266,7 +266,19 @@ If failure → return to Phase 5.
 On success: Create PR via gh pr create, post completion summary.
 
 ## GitHub Issue Management
-Every feature has a corresponding GitHub issue. Update issues at each phase transition:
+
+### Version & Issue Tracking (mandatory — every change)
+Classify the SemVer bump first: **major** (breaking) / **minor** (new backward-compatible
+feature) / **patch** (bug fix / no API change). Then:
+- **Milestone — major & minor only.** Ensure `vX.Y.0` exists (`gh-labels-milestones`);
+  patches attach to their minor's `vX.Y.0`, never get their own.
+- **Issue — every change.** Labelled the matching **`type:*`** label (`type:bug` fix · `type:feature` feature · `type:docs`/`type:refactor`/`type:chore`, per `gh-labels-milestones`), assigned to the target major/minor milestone (`gh-issues`).
+- **Project board.** Add the issue and set **Status** (`In progress` → `Done`); read the
+  board number from `github.project_number` in `project.config.yaml` (`gh-projects`),
+  never hard-code it.
+- PR `Closes #N`. **No Claude/Anthropic attribution** anywhere.
+
+Every change has a corresponding GitHub issue. Update issues at each phase transition:
 
 ```bash
 # Create issue (done by @product-owner, but you track)

.opencode/skills/gh-projects/SKILL.md

@@ -18,7 +18,7 @@ Manage GitHub Projects v2 board operations: add issues as cards, update field va
 | `issue_node_id` | `gh-issues` skill output | `"I_kwDO..."` |
 | `issue_number` | `gh-issues` skill output | `42` |
 | `field_name` | project field name | `"Status"` |
-| `field_value` | target option name | `"In Progress"` |
+| `field_value` | target option name | `"In progress"` |
 
 ## Read project config
 
@@ -153,8 +153,8 @@ gh api graphql -f query='
 | Phase | Field | Value |
 |---|---|---|
 | Discover | Status | `Todo` |
-| Architect | Status | `In Progress` |
-| Implement | Status | `In Progress` |
+| Architect | Status | `In progress` |
+| Implement | Status | `In progress` |
 | Validate | Status | `In Review` |
 | Done | Status | `Done` |
 
@@ -182,6 +182,6 @@ gh project item-list "$PROJECT_NUMBER" \
 
 ```
 [gh-projects] ADD    #42  → project #{project_number}  item_id={id}
-[gh-projects] UPDATE #42  field=Status  value="In Progress"
+[gh-projects] UPDATE #42  field=Status  value="In progress"
 [gh-projects] SKIP   #42  already on board
 ```

AGENTS.md

@@ -82,8 +82,7 @@ finish it):
    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.
+3. **Issue — every change, patches included.** Labelled the matching **`type:*`** label (`type:bug` fix · `type:feature` feature · `type:docs`/`type:refactor`/`type:chore`, per `gh-labels-milestones`), assigned to the target major/minor milestone.
 4. **Project board** — add the issue and set **Status** (`In progress` → `Done`).
    Read the board number from `github.project_number` in `project.config.yaml`
    (never hard-code it).