@mutmutco/kilo-plugin 3.100.0 → 3.102.0

package/package.json

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

package/skills/bootstrap/seeds/gate.template.yml

@@ -83,20 +83,3 @@ jobs:
           command: {{GATE_CMD}}
           max-seconds: {{GATE_MAX_SECONDS}}
           working-directory: {{GATE_WORKDIR}}
-      # MMI-Hub#3329: the deterministic doc ref-gate — every file:line ref, command name,
-      # relative link, and pin comment in docs/** + README.md + architecture.md must resolve.
-      # Routing-index + ref integrity only — not a living-docs keeper (topology D retired, Hub#4119/#4164).
-      # Fleet-portable via the released CLI; runs from the repo root.
-      # MMI-Hub#3406: check the GENERATED index before resolving refs. docs/index.md is produced by
-      # `mmi-cli docs index --write`, and a stale one silently re-hosts child docs' relative links and
-      # backticked paths at the index's own depth — where they no longer resolve. Every finding it
-      # causes points at docs/index.md, so the ref-gate blames the artifact while the real fault is
-      # that nobody regenerated it. Worse, a copied `../../x.md` can escape the repo root, which used
-      # to crash the ref-gate outright rather than report (fixed in 3.44.0). Checking staleness first
-      # names the actual cause and the one-command fix.
-      - name: Doc index freshness
-        run: npx -y @mutmutco/cli@latest docs index --check
-        working-directory: '.'
-      - name: Doc ref-gate
-        run: npx -y @mutmutco/cli@latest docs refs
-        working-directory: '.'

package/skills/bootstrap/seeds/manifest.json

@@ -7,7 +7,7 @@
     { "target": ".github/ISSUE_TEMPLATE/task.yml", "source": "self", "ownership": "org", "classes": ["deployable", "content"] },
     { "target": ".github/ISSUE_TEMPLATE/config.yml", "source": "self", "ownership": "repo", "classes": ["deployable", "content"] },
     { "target": "scripts/next-version.mjs", "source": "self", "ownership": "org", "classes": ["deployable"] },
-    { "target": ".github/workflows/gate.yml", "source": "seed:gate.template.yml", "ownership": "org", "classes": ["deployable"] },
+    { "target": ".github/workflows/gate.yml", "source": "seed:gate.template.yml", "ownership": "repo", "classes": ["deployable"] },
     { "target": ".github/workflows/agent-pr.yml", "source": "self", "ownership": "org", "classes": ["deployable"], "waivers": { "jerv-jervcode": "pins this workflow's EXACT step shapes in its own scripts/workflow-boundary-core.mjs — a literal repositories: Jerv-JervCode token scope, and whole-step equality for the surface and verdict legs. #4040 widened the org seed to the same hardened boundary (pull_request_target off the trusted base, an immutable BASE..HEAD compare with a file-count equality wall, a per-repo App token scope, and a certified-head merge), so the two now agree on substance. They cannot agree on bytes: a seed serving 16 repos resolves its token scope and its required contexts at run time, which exact-step equality rejects by construction. The waiver is permanent by design, not a deferral — lifting it would mean weakening the strictest repo to match a fleet file." } },
     { "target": ".github/rulesets/mmi-product-required-checks.json", "source": "seed:mmi-product-required-checks.template.json", "ownership": "org", "classes": ["deployable"] },
     { "target": ".gitignore", "source": "managed-block", "ownership": "org", "classes": ["deployable", "content"] },