@mutmutco/kilo-plugin 3.90.0 → 3.92.0

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@mutmutco/kilo-plugin",
-  "version": "3.90.0",
+  "version": "3.92.0",
   "description": "MMI workflow skills and org gates delivery.",
   "author": {
     "name": "MMI Future",

package/skills/bootstrap/SKILL.md

@@ -250,12 +250,20 @@ gh project list --owner "$PROJECT_OWNER" --format json   # existing boards to ch
   ```bash
   gh project link "$PROJECT_NUMBER" --owner "$PROJECT_OWNER" --repo "$OWNER/$REPO"
   ```
-- **Create** the chosen board if it doesn't exist yet — clone an existing board so the 4-lane `Status` field
-  (`Todo · In Progress · In Review · Done`) **and its built-in workflows carry over**:
+- **Create** the chosen board if it doesn't exist yet — clone the **named template board**, never an
+  arbitrary existing one, so the 4-lane `Status` field (`Todo · In Progress · In Review · Done`), the
+  built-in workflows, **and** the org's view/card-field shape (#4093) all carry over instead of whatever
+  the previous copy-of-a-copy happened to drift to:
   ```bash
-  gh project copy <existing-project#> --source-owner "$PROJECT_OWNER" \
+  gh project copy 4 --source-owner "$PROJECT_OWNER" \
     --target-owner "$PROJECT_OWNER" --title "<Project>"
   ```
+  **Project 4 (MMI-Hub's own board) is the template** (#4093) — it already carries the org-standard view
+  triple (`List`/`Board`/`Roadmap`), Board grouping (columns=Status, swimlanes=Repository), and the
+  canonical Board card-field set (`Title, Assignees, Status, Labels, Linked pull requests, Parent issue,
+  Sub-issues progress, Priority`). `bootstrap verify` asserts all three against every board (next note); a
+  freshly copied project starts green on them instead of inheriting a stale source's drift. Copying from
+  anything else re-introduces the "5 card-field variants across 16 boards" problem #4093 was filed to end.
   Then **interview the master** for the seed short description + README (what it tracks, member repos, links
   to the repos' `README.md`/`architecture.md`); set them via the `updateProjectV2` mutation
   (`shortDescription`, `readme`). If cloning, verify the built-in workflows survived (next note).
@@ -265,6 +273,14 @@ gh project list --owner "$PROJECT_OWNER" --format json   # existing boards to ch
   on merge. GitHub's public GraphQL schema exposes delete/read surfaces for Project workflows but no
   create/update/enable mutation; if any required workflow is missing or disabled, repair it in the project's
   **Workflows** settings before calling the repo ready for developers.
+- **Board shape (#4093):** `mmi-cli bootstrap verify` also checks the view triple (`List`/`Board`/`Roadmap`
+  by name **and** layout), the Board view's grouping, and its card fields against the standard the template
+  board (project 4) carries. Grouping (columns=`Status`, swimlanes=`Repository`) has **no** GraphQL create/
+  update mutation (`ProjectV2ViewConfigurationInput` carries only `visibleFieldIds`) — a drifted swimlane or
+  column can only be fixed in the UI: Board view → ⚙ (top-right) → Group by / Swimlanes → Save view. The
+  view triple and the card fields (`Title, Assignees, Status, Labels, Linked pull requests, Parent issue,
+  Sub-issues progress, Priority`) ARE API-writable (`createProjectV2View`/`updateProjectV2View`), so a
+  drifted one can be fixed live instead of only reported.
 
 Record the chosen `projectNumber`/`projectId` plus Status/Priority field ids in the Hub registry META
 (`PROJECT#<slug>`) by re-running `mmi-cli bootstrap apply --execute` **after** `gh project link`. Apply reads
@@ -362,10 +378,12 @@ collaborator list + the per-branch allowlist are the record — no separate rost
   gh label create feature --color a2eeef --description "New capability or enhancement"        -R $OWNER/$REPO
   gh label create task    --color 0052cc --description "Task, chore, or improvement"           -R $OWNER/$REPO
   ```
-- **Board view (Priority chip)** — the Project's board view must **show the Priority field on cards**, not
-  the Labels field (GitHub's API can't set view columns): Board view → **Fields** → remove **Labels**, add
-  **Priority**. Otherwise cards show label soup and no priority chip. Strip any legacy `priority:*` /
-  taxonomy labels with `mmi-cli board doctor --fix`.
+- **Board view (card fields, #4093)** — the Project's Board view must show the org-standard card set:
+  `Title, Assignees, Status, Labels, Linked pull requests, Parent issue, Sub-issues progress, Priority`.
+  Cloning from the template board (project 4, Step 3) already produces this; `bootstrap verify` asserts it
+  (`Board view card fields match the org standard`) on every subsequent run, so drift shows up there rather
+  than only at bootstrap time. Fix via Board view → **Fields**, or `updateProjectV2View(configuration:
+  {visibleFieldIds:[...]})`. Strip any legacy `priority:*` / taxonomy labels with `mmi-cli board doctor --fix`.
 - **Org App credentials** — nothing to register per repo (#494). Board moves are central (the Hub webhook
   moves Todo/In Progress/In Review for every repo) and the org App token is minted inside the Hub's own
   central workflows, so `MMI_APP_ID` / `MMI_APP_PRIVATE_KEY` live only on the Hub — a product repo seeds no