@mutmutco/pi-plugin 4.5.150 → 4.5.151

package/package.json

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

package/skills/bootstrap/seeds/suite-guide.template.md

@@ -8,4 +8,4 @@ Before the first CI/deploy, an org admin must grant this repo **Read** on `@mutm
 
 The server exposes `/health` and `/module.js`. Register the module's bundle URL, id, name and capabilities with MM-Work following the GUIDE. The seed deliberately exposes no authenticated product API yet.
 
-`gate` installs and checks the backend and module. `screens / screens` follows MM-PM's non-blocking PR/push/tag shape, using MM-Work's reusable runner with `run: false` (browser audits are not merge gates). Configure scheduled/on-demand screen audits separately when the product has screens to audit.
+`gate` installs and checks the backend and module. Product repos carry no screenshot or browser tests (owner ruling 2026-10-15, MM-Work#5388).

package/skills/bootstrap/seeds/suite-module-package.template.json

@@ -3,7 +3,7 @@
   "version": "0.1.0",
   "private": true,
   "type": "module",
-  "description": "MM-Work module screens",
+  "description": "MM-Work module",
   "scripts": {
     "lint": "mmwork-check-ui src",
     "build": "vite build",

package/skills/bootstrap/seeds/suite-files.template.json

@@ -1 +0,0 @@
-{ "result": { "items": [{ "id": "sample", "name": "Sample brief" }] } }

package/skills/bootstrap/seeds/suite-screens.template.json

@@ -1,170 +0,0 @@
-{
-  "module": {
-    "id": "{{REPO_SLUG}}",
-    "name": "{{REPO_NAME}}",
-    "glyph": "grid",
-    "tone": "blue",
-    "description": "Offline module screen check",
-    "sections": [
-      {
-        "label": "Home",
-        "path": "/"
-      },
-      {
-        "label": "Details",
-        "path": "/details"
-      }
-    ],
-    "help": {
-      "home": {
-        "name": "Example home",
-        "howTos": [
-          {
-            "id": "recent",
-            "title": "See recent files",
-            "intro": "The module counts the files you opened lately in Google Drive.",
-            "steps": [
-              {
-                "title": "Connect Drive",
-                "text": "Connect your Google account in Files to see your recent files.",
-                "scene": "connect"
-              },
-              {
-                "title": "Come back here",
-                "text": "The overview shows how many recent files MM-Work found."
-              }
-            ]
-          },
-          {
-            "id": "details",
-            "title": "Open the details page",
-            "steps": [
-              {
-                "title": "Press Open a page inside the module",
-                "text": "It is under the overview. Details is also in the section row.",
-                "scene": "screen"
-              },
-              {
-                "title": "Go back",
-                "text": "Press Home in the section row."
-              }
-            ]
-          }
-        ],
-        "faq": [
-          {
-            "id": "drive",
-            "question": "Where are my files?",
-            "answer": "Recent files come from your connected Google Drive."
-          },
-          {
-            "id": "job",
-            "question": "What is the Review files job?",
-            "answer": "A job your admin can give you. The overview says whether you hold it."
-          },
-          {
-            "id": "access",
-            "question": "Does this module get my Google password?",
-            "answer": "No. It asks MM-Work for your files, and MM-Work uses the access you granted it."
-          }
-        ],
-        "tour": [
-          {
-            "anchor": "example-intro",
-            "title": "What this is",
-            "text": "A module's own screen, drawn with MM-Work's design system."
-          },
-          {
-            "anchor": "example-overview",
-            "title": "Your overview",
-            "text": "See your workspace and recent Drive files here."
-          },
-          {
-            "anchor": "example-actions",
-            "title": "Where to go next",
-            "text": "Open the details page, or go to Files."
-          }
-        ]
-      }
-    },
-    "privacy": [
-      {
-        "class": "company-visible",
-        "what": {
-          "en": "The example reads recent Google Drive file metadata through MM-Work after the person connects Files.",
-          "tr": "Örnek modül, kişi Files bağlantısını kurduktan sonra MM-Work üzerinden son Google Drive dosyalarının meta verilerini okur."
-        },
-        "who": {
-          "en": "The signed-in person sees the count on this example screen; no file content is saved by the example.",
-          "tr": "Oturum açmış kişi örnek ekranda sayıyı görür; örnek modül dosya içeriğini kaydetmez."
-        },
-        "evidence": [
-          "repo:MM-Work:examples/example-module/src/module.jsx"
-        ]
-      }
-    ]
-  },
-  "screens": [
-    {
-      "name": "home",
-      "path": "/m/example",
-      "jobs": [
-        "files.review"
-      ],
-      "routes": {
-        "POST /api/actions/files.list": "files.json"
-      }
-    },
-    {
-      "name": "open details journey",
-      "path": "/m/example",
-      "steps": [
-        {
-          "assert": {
-            "selector": "[data-tour=example-actions] button",
-            "count": 2
-          }
-        },
-        {
-          "click": "[data-tour=example-actions] button:first-child"
-        },
-        {
-          "assert": {
-            "url": "/m/example/details"
-          }
-        }
-      ],
-      "routes": {
-        "POST /api/actions/files.list": "files.json"
-      }
-    },
-    {
-      "name": "details",
-      "path": "/m/example/details",
-      "routes": {
-        "POST /api/actions/files.list": "files.json"
-      }
-    },
-    {
-      "name": "loading",
-      "path": "/m/example",
-      "query": "state=loading",
-      "routes": {
-        "POST /api/actions/files.list": "pending"
-      }
-    },
-    {
-      "name": "error",
-      "path": "/m/example",
-      "query": "state=error",
-      "routes": {
-        "POST /api/actions/files.list": {
-          "status": 500,
-          "body": {
-            "error": "offline failure"
-          }
-        }
-      }
-    }
-  ]
-}

package/skills/bootstrap/seeds/suite-screens.template.yml

@@ -1,63 +0,0 @@
-name: screens
-# A required check (#250): it runs wherever gate runs, so no PR into development, rc or main and no train tag
-# waits on a context that never reports.
-on:
-  pull_request:
-  merge_group:
-    types: [checks_requested]
-  push:
-    branches: {{GATE_PUSH_BRANCHES_YAML}}
-    tags: ['v*']
-# Cancel superseded runs per PR, or per branch for pushes (MMI-Hub#7515, #3001; as MM-Strategy#415).
-concurrency:
-  group: screens-${{ github.event.pull_request.number || (github.event_name == 'push' && github.sha) || github.ref }}
-  cancel-in-progress: true
-permissions:
-  contents: read
-  packages: read
-  pull-requests: read
-jobs:
-  # Owner ruling (#474, 6 Oct 2026): browser checks block nothing, releases included. Every PR, push and tag
-  # reports this required context without a browser audit (run: false); screens-sweep.yml audits nightly and
-  # on demand (issue-on-red). A development push still reports
-  # the required "screens / screens" on the SHA, which the dev deploy needs (MMI-Hub dev-auto-deploy).
-  changes:
-    runs-on: [self-hosted, linux, x64, mmi-live]
-    outputs:
-      run: ${{ steps.pick.outputs.run }}
-      full: ${{ steps.pick.outputs.full }}
-    steps:
-      - id: pick
-        env:
-          GH_TOKEN: ${{ github.token }}
-          EVENT: ${{ github.event_name }}
-          BASE: ${{ github.base_ref }}
-          REF: ${{ github.ref_name }}
-          REF_TYPE: ${{ github.ref_type }}
-          PR: ${{ github.event.pull_request.number }}
-          REPO: ${{ github.repository }}
-        run: |
-          set -euo pipefail
-          # #474: no browser audit on any PR, push or tag; screens-sweep.yml runs it nightly.
-          run=false; full=false
-          echo "run=$run full=$full"
-          { echo "run=$run"; echo "full=$full"; } >> "$GITHUB_OUTPUT"
-  screens:
-    needs: changes
-    # Fail closed (MMI-Hub, 6 Oct): a SKIPPED required check counts as passing, so this job runs even when
-    # `changes` failed, and a missing answer means the full audit, never a skip.
-    if: ${{ !cancelled() }}
-    uses: mutmutco/MM-Work/.github/workflows/module-screens.yml@development
-    with:
-      run: ${{ needs.changes.outputs.run != 'false' }}
-      audit-sizes: ${{ needs.changes.outputs.full != 'false' && '["phone","768","1024","1280"]' || '["phone"]' }}
-      # Pinned to the shell built from the kit this module ships (ds-v0.71.42): the runner MM-Work
-      # published with that kit; bump with the kit.
-      # 0.1.55+ checks MM-Work #1575: selectedStyle, pageBackground, noJump (#418).
-      screens-version: '0.1.113'
-      working-directory: 'module'
-      build-command: 'npm run build'
-      bundle-path: 'dist/module.js'
-      fixtures-path: 'screens/screens.json'
-      # Every screen in English and Turkish (#369): Turkish words run longer, so they get their own audit.
-      languages: 'en,tr'