@mutmutco/pi-plugin 4.5.99 → 4.5.100

package/package.json

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

package/skills/bootstrap/SKILL.md

@@ -481,6 +481,9 @@ web tenants, `--project-type desktop-game --deploy-model none --clear-web-profil
 `--project-type mobile-app --deploy-model none --clear-web-profile` for a phone app distributed through the
 app stores, and
 `--class content --project-type content --deploy-model content --clear-web-profile` for a content/KB repo.
+An **MM-Work module** adds `--var SUITE=mm-work` (#7944): it registers `suite: mm-work` and derives its
+own `dev.<sub>.mutmut.work` + `<sub>.mutmut.work` hosts, with no rc host (the suite serves its rc from the
+live host). Without it, apply derives the `*.mutatismutandis.co` web-app hosts, which a module never uses.
 Run the apply path with the board variables discovered above, or register the same values with
 `mmi-cli oracle org project set` from the Hub or from the target project checkout:
 

package/skills/org-guide/references/domains-and-oauth.md

@@ -4,9 +4,13 @@ MMI owns the central project registry and provisioning workflows. Read
 `mmi-cli oracle org project get <owner/repo> --json` before changing hostnames or login settings.
 Use the declared edge domains for each stage; do not guess hostnames from a slug or create a
 second DNS/deployment control plane in a product repository. New project setup goes through
-[bootstrap](../../bootstrap/SKILL.md).
+[bootstrap](../../bootstrap/SKILL.md). An MM-Work suite module serves from its own
+`dev.<name>.mutmut.work` and `<name>.mutmut.work` hosts, with no rc host; bootstrap declares them
+with `--var SUITE=mm-work`.
 
 Cloudflare owns public DNS and edge TLS. Preserve unrelated records during an authorized change.
+The Hub creates each registered host's proxied record during bootstrap and never edits an existing
+one; check or re-run it with `mmi-cli devops runtime edge dns status|ensure <owner/repo> <stage>`.
 A dev stage is private only after its independent edge-block check succeeds. A configured record
 or successful deployment alone does not prove access control. Use [stage](../../stage/SKILL.md)
 for the supported private live workflow.