@mutmutco/kilo-plugin 3.92.0 → 3.94.0

package/package.json

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

package/skills/bootstrap/SKILL.md

@@ -355,8 +355,11 @@ collaborator list + the per-branch allowlist are the record — no separate rost
   `--var` or `org project set <repo> --var gate={"maxSeconds":N}`); `ci audit` and the release train
   both enforce the step, so do not remove it. After apply,
   master-admin must **activate** that JSON as a repository ruleset (GitHub → Settings → Rules → Rulesets →
-  Import/create from the committed reference) so the `gate` context is required on train branches. MMI-Hub
-  keeps its own three-job gate (`cli`/`infra`/`docs`) — never apply the product ruleset there.
+  Import/create from the committed reference) so the `gate` context is required on train branches. Once the
+  gate is green on `development`, `mmi-cli ci reconcile --apply --repo $OWNER/$REPO` should flip enforcement
+  to **Active**; if it does not, use the Step 5 PUT fallback and confirm with `bootstrap verify` before
+  reporting bootstrap complete. MMI-Hub keeps its own three-job gate (`cli`/`infra`/`docs`) — never apply the
+  product ruleset there.
 - **A brand-new repo cannot pass the gate you just installed — its first commit must carry a real project
   (#2928).** The seeded `gate.yml` runs `GATE_INSTALL_CMD` + `GATE_CMD` (`npm ci` + `npm run check` by
   default) **unconditionally**. An empty repo has no `package.json`, so the gate **fails on the seed PR
@@ -423,8 +426,10 @@ collaborator list + the per-branch allowlist are the record — no separate rost
   `mmi-product-required-checks`, set **Enforcement** to **Disabled**, push/merge the filled `README.md` +
   `architecture.md`, then set **Enforcement** back to **Active**. Programmatic equivalent: PUT the ruleset
   with `enforcement: disabled` (a PATCH is rejected, #917/#922), push the fill, then PUT it back to
-  `active` (or re-run `bootstrap apply`, which re-activates the ruleset idempotently). Never leave enforcement
-  disabled.
+  `active` (or re-run `mmi-cli ci reconcile --apply --repo $OWNER/$REPO` once the gate is green, which
+  should activate idempotently). Before reporting bootstrap complete, run `mmi-cli bootstrap verify` and
+  confirm `product required-check ruleset enforcement active` is OK — a parked ruleset is not done. Never
+  leave enforcement disabled.
 - `.claude/settings.local.json` is local-only and gitignored; bootstrap seeds no committed `.claude/settings.json`.
 - **No agent guide is committed — none, anywhere (#2921).** `mmi-no-agent-files-org` is active with no bypass
   and restricts `AGENTS.md`, `CLAUDE.md`, `GEMINI.md`, `.claude/**`, `.codex/**`, `.agents/**` **and