mulmoterminal 8.3.0 → 8.5.0

package/README.md

@@ -1758,6 +1758,11 @@ narrow and tall for one record you are discussing — and each position keeps it
   each enabled plugin (skills shown as `plugin:skill`), and the `.claude/skills` of each folder a
   terminal has run in (folders with none are left out). A project skill with the same name as one
   of yours is marked as overriding it. The search (name, description or folder) narrows both lists.
+  Switch to **skills.sh** to search the public directory at [skills.sh](https://skills.sh) for
+  skills you do not have yet and read one before installing it: its `SKILL.md`, every file it would
+  bring, and a warning listing the files that can run code. Nothing is installed from the viewer —
+  it shows the `npx skills add …` line to copy and run yourself. Your search words go to skills.sh
+  only when you press **Search**.
 - **Grid of parallel sessions** — the ＋ Terminal / grid view runs many sessions at once,
   auto-sizing by count across pages. Cell borders signal state at a glance — **working**
   (pulsing blue), **blocked** (amber — needs a permission / answer), **done** (blue —

package/blueprints/adopt/hearing.json

@@ -27,7 +27,17 @@
         "プレスリリース・お知らせ",
         "契約書・利用規約",
         "規程・社内規則",
-        "論文"
+        "論文",
+        "ブログ（エッセイ・読み物）",
+        "メール・手紙",
+        "判決文",
+        "特許明細書",
+        "小説・物語",
+        "文学のエッセイ・随筆",
+        "詩",
+        "戯曲・脚本",
+        "演説・挨拶の原稿",
+        "書き起こし（会見・会議での発言の記録）"
       ]
     },
     {
@@ -36,7 +46,9 @@
       "why": "作ると、PR を出すたびに chaff が動き、新しい指摘がその行に出る",
       "kind": "select",
       "options": ["GitHub の PR に指摘を出すワークフローを作る", "作らない（手元で npx chaffjs を動かす）"],
-      "needsPath": { "GitHub の PR に指摘を出すワークフローを作る": ".git" }
+      "needsPath": {
+        "GitHub の PR に指摘を出すワークフローを作る": ".git"
+      }
     }
   ]
 }

package/blueprints/adopt/kinds.json

@@ -1,18 +1,100 @@
 {
   "kinds": [
-    { "option": "手順書・ヘルプ・マニュアル", "genre": "docs/manual" },
-    { "option": "README・開発者向けの説明", "genre": "technical/readme" },
-    { "option": "仕様書・設計書", "genre": "technical/spec" },
-    { "option": "よくある質問", "genre": "docs/faq" },
-    { "option": "用語集", "genre": "docs/glossary" },
-    { "option": "技術ブログ", "genre": "blog/tech" },
-    { "option": "会社のサイトの記事（オウンドメディア）", "genre": "blog/owned-media" },
-    { "option": "報告書・社内文書", "genre": "business/report" },
-    { "option": "提案書・企画書", "genre": "business/proposal" },
-    { "option": "議事録", "genre": "business/meeting-notes" },
-    { "option": "プレスリリース・お知らせ", "genre": "business/press-release" },
-    { "option": "契約書・利用規約", "genre": "legal/contract" },
-    { "option": "規程・社内規則", "genre": "legal/statute" },
-    { "option": "論文", "genre": "academic/paper" }
+    {
+      "option": "手順書・ヘルプ・マニュアル",
+      "genre": "docs/manual"
+    },
+    {
+      "option": "README・開発者向けの説明",
+      "genre": "technical/readme"
+    },
+    {
+      "option": "仕様書・設計書",
+      "genre": "technical/spec"
+    },
+    {
+      "option": "よくある質問",
+      "genre": "docs/faq"
+    },
+    {
+      "option": "用語集",
+      "genre": "docs/glossary"
+    },
+    {
+      "option": "技術ブログ",
+      "genre": "blog/tech"
+    },
+    {
+      "option": "会社のサイトの記事（オウンドメディア）",
+      "genre": "blog/owned-media"
+    },
+    {
+      "option": "報告書・社内文書",
+      "genre": "business/report"
+    },
+    {
+      "option": "提案書・企画書",
+      "genre": "business/proposal"
+    },
+    {
+      "option": "議事録",
+      "genre": "business/meeting-notes"
+    },
+    {
+      "option": "プレスリリース・お知らせ",
+      "genre": "business/press-release"
+    },
+    {
+      "option": "契約書・利用規約",
+      "genre": "legal/contract"
+    },
+    {
+      "option": "規程・社内規則",
+      "genre": "legal/statute"
+    },
+    {
+      "option": "論文",
+      "genre": "academic/paper"
+    },
+    {
+      "option": "ブログ（エッセイ・読み物）",
+      "genre": "blog/essay"
+    },
+    {
+      "option": "メール・手紙",
+      "genre": "business/email"
+    },
+    {
+      "option": "判決文",
+      "genre": "legal/judgment"
+    },
+    {
+      "option": "特許明細書",
+      "genre": "legal/patent"
+    },
+    {
+      "option": "小説・物語",
+      "genre": "literature/fiction"
+    },
+    {
+      "option": "文学のエッセイ・随筆",
+      "genre": "literature/essay"
+    },
+    {
+      "option": "詩",
+      "genre": "literature/poetry"
+    },
+    {
+      "option": "戯曲・脚本",
+      "genre": "literature/play"
+    },
+    {
+      "option": "演説・挨拶の原稿",
+      "genre": "speech/address"
+    },
+    {
+      "option": "書き起こし（会見・会議での発言の記録）",
+      "genre": "speech/transcript"
+    }
   ]
 }

package/blueprints/adopt/locales/en.json

@@ -0,0 +1,66 @@
+{
+  "manifest": {
+    "title": "Bring chaff into a document folder (shelve today's findings)",
+    "description": "Brings chaff into a folder of documents you already have. It places a chaff.yaml that fits the kind of documents, shelves today's findings with chaff baseline, and from then on only new findings appear. If you want, it also makes a workflow that shows findings on the lines of a GitHub PR. The originals do not change."
+  },
+  "hearing": {
+    "places": {
+      "label": "The documents for chaff to watch (one folder or file in this folder per line)",
+      "why": "Today's findings in these documents are shelved, and from then on only new findings here appear"
+    },
+    "kind": {
+      "label": "What kind of documents are they?",
+      "why": "chaff measures them with the yardstick for that kind of document (how long a sentence may be, which checks to run)",
+      "options": {
+        "手順書・ヘルプ・マニュアル": "Procedure, help or manual",
+        "README・開発者向けの説明": "README or explanation for developers",
+        "仕様書・設計書": "Specification or design document",
+        "よくある質問": "FAQ",
+        "用語集": "Glossary",
+        "技術ブログ": "Technical blog",
+        "会社のサイトの記事（オウンドメディア）": "An article on a company site",
+        "報告書・社内文書": "Report or internal document",
+        "提案書・企画書": "Proposal",
+        "議事録": "Minutes",
+        "プレスリリース・お知らせ": "Press release or notice",
+        "契約書・利用規約": "Contract or terms of service",
+        "規程・社内規則": "Regulation or company rules",
+        "論文": "Academic paper",
+        "ブログ（エッセイ・読み物）": "Blog (essay, feature)",
+        "メール・手紙": "Email or letter",
+        "判決文": "Court judgment",
+        "特許明細書": "Patent specification",
+        "小説・物語": "Novel or story",
+        "文学のエッセイ・随筆": "Literary essay",
+        "詩": "Poetry",
+        "戯曲・脚本": "Play or script",
+        "演説・挨拶の原稿": "Speech or address (to be read aloud)",
+        "書き起こし（会見・会議での発言の記録）": "Transcript (what was said at a press conference or meeting)"
+      }
+    },
+    "ci": {
+      "label": "Show findings on GitHub PRs?",
+      "why": "If made, chaff runs every time a PR is opened, and new findings appear on their lines",
+      "options": {
+        "GitHub の PR に指摘を出すワークフローを作る": "Make a workflow that shows findings on GitHub PRs",
+        "作らない（手元で npx chaffjs を動かす）": "Don't make one (run npx chaffjs on your own machine)"
+      }
+    }
+  },
+  "steps": {
+    "survey": {
+      "title": "Measure today's findings",
+      "description": "Measures how many findings the documents have now, for the chosen kind, and drafts the settings to put in. Nothing changes yet."
+    },
+    "apply": {
+      "title": "Bring chaff in",
+      "description": "Places chaff.yaml, shelves today's findings in .chaff-baseline.json, and, if you want, adds a workflow that shows findings on PRs. Checks by machine that from then on only new findings appear."
+    }
+  },
+  "presets": {
+    "help-pages": {
+      "title": "Bring chaff into help pages",
+      "description": "Measures the sample help pages (login.md and export.md) as \"Procedure, help or manual\", shelves today's findings of sentences that are too long, and from then on only new findings appear. It also makes a workflow that shows findings on GitHub PRs. The originals do not change."
+    }
+  }
+}

package/blueprints/adopt/steps.json

@@ -14,7 +14,8 @@
       "skill": "skills/apply",
       "check": "node \"$BLUEPRINT_USECASE/checks/adopt.mjs\" apply && node \"$BLUEPRINT_USECASE/checks/report.mjs\"",
       "gates": ["review"],
-      "reads": [".blueprint/adopt.txt"]
+      "reads": [".blueprint/adopt.txt"],
+      "revises": [".blueprint/adopt.json"]
     }
   ]
 }

package/blueprints/ask/locales/en.json

@@ -0,0 +1,44 @@
+{
+  "manifest": {
+    "title": "Ask your documents (with where each answer is written)",
+    "description": "Ask a question of a complicated manual, regulation or contract, and the answer shows where in the documents it is written, quoting the original text. Something that is not written is answered \"not written\". chaff cite checks that each quote is in the original. After a person reads the answers, they can be kept in FAQ.md."
+  },
+  "hearing": {
+    "documents": {
+      "label": "The documents to ask (one file in this folder per line)",
+      "why": "Answers come only from these documents, with where each is written"
+    },
+    "questions": {
+      "label": "Questions (one per line)",
+      "why": "One answer for each question"
+    },
+    "keep": {
+      "label": "Keep the answers?",
+      "why": "Whether to add the checked answers to FAQ.md in this folder",
+      "options": {
+        "このフォルダの FAQ.md に書き足す": "Add them to FAQ.md in this folder",
+        "残さない（.blueprint の中だけ）": "Don't keep them (only inside .blueprint)"
+      }
+    }
+  },
+  "steps": {
+    "answer": {
+      "title": "Answer from the documents",
+      "description": "Answers each question, quoting where in the documents it is written. If it is not written, says so and records what was searched."
+    },
+    "keep": {
+      "title": "Keep the answers",
+      "description": "If you chose to keep them, adds the checked answers to FAQ.md."
+    }
+  },
+  "presets": {
+    "keihi": {
+      "title": "Ask the expense claim guide",
+      "description": "Asks the sample guide (keihi.md) 3 questions, and each answer shows where it is written, quoting the original. Something that is not written (the daily allowance for trips abroad) is answered \"not written\"."
+    },
+    "kyuka": {
+      "title": "Ask the leave regulation and guide",
+      "description": "Asks the sample leave regulation (kitei.md) and guide (tebiki.md) 3 questions. The deadline for applying differs between the regulation and the guide, so both are quoted to show the mismatch. Half-day leave is answered with a quote from the guide, and summer leave, which neither mentions, is answered \"not written\". The answers are not kept in the folder."
+    }
+  }
+}

package/blueprints/ask/steps.json

@@ -14,7 +14,8 @@
       "skill": "skills/keep",
       "check": "node \"$BLUEPRINT_USECASE/checks/replies.mjs\" keep",
       "gates": ["review"],
-      "reads": [".blueprint/replies.md"]
+      "reads": [".blueprint/replies.md"],
+      "revises": [".blueprint/replies.json"]
     }
   ]
 }

package/blueprints/cloudflare/locales/en.json

@@ -0,0 +1,52 @@
+{
+  "manifest": {
+    "title": "Cloudflare (Workers + D1 + Vue)",
+    "description": "Runs on Cloudflare: a Worker for the API, D1 (SQLite) for data, and a Vue screen served as static assets from the same Worker. Developed and checked on this computer with wrangler dev, then published with wrangler deploy after approval. A free Cloudflare account is enough to start."
+  },
+  "steps": {
+    "spec": {
+      "title": "Write the spec",
+      "description": "Fills in the spec templates for the base and the use case from the answers to the questions. Anything not yet decided goes on a list."
+    },
+    "prerequisites": {
+      "title": "Check the tools",
+      "description": "Checks Node (22 or later) and yarn. wrangler is installed in the project, so it is not needed here."
+    },
+    "scaffold": {
+      "title": "App skeleton",
+      "description": "Creates the Worker API, D1, the Vue screens and the starting point for tests that run on Workers, all in one folder."
+    },
+    "data": {
+      "title": "Data shape",
+      "description": "Turns the \"things it handles\" in the spec into D1 tables, and writes migrations and tests."
+    },
+    "api": {
+      "title": "API",
+      "description": "Turns the operations in the spec into a Worker API, checks what comes in, and writes tests."
+    },
+    "ui": {
+      "title": "Screens",
+      "description": "Builds the screens in the spec with Vue and connects them to the API."
+    },
+    "auth": {
+      "title": "Sign-in",
+      "description": "Adds the sign-in method in the spec. Anyone can open the published app, so without sign-in, what may be shown is limited as the spec says."
+    },
+    "run-check": {
+      "title": "Start it and check",
+      "description": "Builds it, starts it on this computer with wrangler dev, and checks that the screens and the API respond."
+    },
+    "security": {
+      "title": "Security check",
+      "description": "Reads what was built the way an attacker would, following OWASP Top 10:2025, fixes the holes that can be exploited, confirms the fixes with tests, and writes a report. The result is checked by sending the Worker running on this computer requests shaped like real attacks (changes from another site, broken JSON)."
+    },
+    "deploy": {
+      "title": "Publish to Cloudflare",
+      "description": "Creates the D1 database, applies the migrations, and publishes with wrangler deploy. Checks that the published URL serves this build."
+    },
+    "handover": {
+      "title": "How to use it, and handover",
+      "description": "Writes in the README and the getting-started page the published URL, how to run it on this computer, the steps for the next change, and how to back up the data."
+    }
+  }
+}

package/blueprints/compare/locales/en.json

@@ -0,0 +1,40 @@
+{
+  "manifest": {
+    "title": "Compare versions (a side-by-side table)",
+    "description": "Matches the old and new versions of a contract or regulation article by article, and makes a side-by-side table of what changed, what was added and what was removed. Whether an article changed is decided by comparing its text by machine, so saying an unchanged article \"changed\", or the reverse, does not pass. The originals do not change."
+  },
+  "hearing": {
+    "old": {
+      "label": "The old version (one file in this folder)",
+      "why": "What to compare from. Each article is matched to the new version"
+    },
+    "new": {
+      "label": "The new version (one file in this folder)",
+      "why": "What to compare to"
+    },
+    "focus": {
+      "label": "Anything to look at especially",
+      "why": "Changes about that point are written first and in more detail"
+    }
+  },
+  "steps": {
+    "pair": {
+      "title": "Match the articles of the old and new versions",
+      "description": "Writes, pair by pair, which article of the old version became which article of the new one, and marks each changed, added or removed. Whether an article changed is checked by comparing its text by machine."
+    },
+    "report": {
+      "title": "Make the side-by-side table",
+      "description": "After checking the matching, makes a side-by-side table of the articles that changed, were added and were removed."
+    }
+  },
+  "presets": {
+    "itaku-kaitei": {
+      "title": "Compare a revised service contract",
+      "description": "Matches the old version (kyu.txt) and the revised version (shin.txt) of the sample service contract article by article, and makes a side-by-side table showing that the fee and the number of reports changed, that an article on reporting was added, and that the article on deliverables was removed so the article on the contract period moved up. The originals do not change."
+    },
+    "ryohi-kaitei": {
+      "title": "Compare a revised travel expense regulation",
+      "description": "Matches the old version (kyu.txt) and the revised version (shin.txt) of the sample travel expense regulation article by article, and makes a side-by-side table showing that the caps on the daily allowance and lodging went up, that a proviso added the cases where no trip is ordered, that the article on ticket books was removed so the article on settling expenses moved up and its deadline got shorter, and that an article on when the regulation takes effect was added. The originals do not change."
+    }
+  }
+}

package/blueprints/compare/steps.json

@@ -14,7 +14,8 @@
       "skill": "skills/report",
       "check": "node \"$BLUEPRINT_USECASE/checks/report.mjs\"",
       "gates": ["review"],
-      "reads": [".blueprint/comparison.txt"]
+      "reads": [".blueprint/comparison.txt"],
+      "revises": [".blueprint/comparison.json"]
     }
   ]
 }

package/blueprints/docs/locales/en.json

@@ -0,0 +1,12 @@
+{
+  "manifest": {
+    "title": "A folder of documents",
+    "description": "All you need is one folder that holds your documents. No GitHub or git is needed. chaff checks the writing, run with npx."
+  },
+  "steps": {
+    "workspace": {
+      "title": "Check the folder and chaff",
+      "description": "Checks that chaff (the writing checker) runs in the document folder, and sets up .blueprint/, where the record of the work is kept."
+    }
+  }
+}

package/blueprints/firebase/locales/en.json

@@ -0,0 +1,48 @@
+{
+  "manifest": {
+    "title": "Firebase",
+    "description": "Firebase Hosting + Authentication + Firestore + Cloud Functions, with separate dev and production projects."
+  },
+  "steps": {
+    "spec": {
+      "title": "Write the spec",
+      "description": "Fills in the spec templates for the base and the use case from the answers to the questions. Anything not yet decided goes on a list."
+    },
+    "prerequisites": {
+      "title": "Tools and sign-in",
+      "description": "Installs the CLIs and signs in to Firebase and Google Cloud."
+    },
+    "projects": {
+      "title": "Development and production projects",
+      "description": "Sets up two Firebase projects and puts them on the pay-as-you-go (Blaze) plan."
+    },
+    "scaffold": {
+      "title": "App skeleton",
+      "description": "Creates the screens, Cloud Functions, the emulator settings and the starting point for testing the rules."
+    },
+    "auth": {
+      "title": "Sign-in",
+      "description": "Adds sign-in with Google and checks it with the Auth emulator."
+    },
+    "data-rules": {
+      "title": "Data shape and security rules",
+      "description": "Creates the collections in the spec and opens them one at a time in firestore.rules. Everything else is refused."
+    },
+    "deploy-dev": {
+      "title": "Publish for development",
+      "description": "Publishes the rules, functions and screens to the development project."
+    },
+    "protect": {
+      "title": "App Check and a budget alert",
+      "description": "Turns on App Check and sets a budget alert on the production project."
+    },
+    "security": {
+      "title": "Security check",
+      "description": "Before publishing to production, reads what was built the way an attacker would, following OWASP Top 10:2025, fixes the holes that can be exploited, confirms the fixes with emulator tests, and writes a report. The fixes are published to development again, to check that the screens still work."
+    },
+    "deploy-production": {
+      "title": "Publish to production",
+      "description": "Publishes to production the same build that was checked in development."
+    }
+  }
+}

package/blueprints/from-collection/locales/en.json

@@ -0,0 +1,154 @@
+{
+  "manifest": {
+    "title": "Turn a collection into an app",
+    "description": "Start from a collection in the workspace: its schema, screens and actions are copied into the build's folder and become the spec of an app you own as code, on this computer, on Firebase, on Cloudflare or on Supabase. With its records, they are moved into the new app too. The collection itself is not touched."
+  },
+  "hearing": {
+    "source": {
+      "label": "The collection (or shared app) to start from",
+      "why": "Its fields, screens and actions (for a shared app, also its members and roles, its sign-up requests and its email declarations) are copied from here into the spec. The original is not changed"
+    },
+    "copyRecords": {
+      "label": "Copy the records (the data inside) too?",
+      "why": "If yes, the records it has now, and the images and files they point to, are moved into the new app. Any personal information in them is copied into the new folder too. A shared app's records are read with your sign-in (you need a role that can read all of them). If no, only the shape is copied and you get an empty app"
+    },
+    "appName": {
+      "label": "The app's name (empty: the collection's name)",
+      "why": "Shown on the screens and in the instructions"
+    },
+    "whyApp": {
+      "label": "Why make it an app? (What does the collection not do?)",
+      "why": "This is how the must-haves are chosen. If you only want to copy what the collection has, say so"
+    },
+    "audience": {
+      "label": "Who will use it?",
+      "why": "This decides sign-in and who can see it",
+      "options": {
+        "自分だけ": "Only me",
+        "家族・友人など少人数": "A few people, such as family or friends",
+        "社内・チーム": "My company or team",
+        "不特定の人（公開）": "Anyone (public)"
+      }
+    },
+    "mustHaves": {
+      "label": "Features it must have from the start (empty: everything the collection can do)",
+      "why": "At the end, each one is proved to work by a test"
+    },
+    "later": {
+      "label": "Features that can wait",
+      "why": "They are left out of the first version"
+    },
+    "signIn": {
+      "label": "How should people sign in?",
+      "why": "This decides how it is protected",
+      "options": {
+        "なし（このパソコンからだけ使う）": "No sign-in (used only from this computer)",
+        "共有のパスワード一つ": "One shared password",
+        "一人ずつのアカウント": "An account for each person"
+      }
+    },
+    "roles": {
+      "label": "Should there be roles? (for example, admin and regular user)",
+      "why": "These become the rules for who can do what"
+    },
+    "dataSensitivity": {
+      "label": "The most sensitive information it handles",
+      "why": "This decides how it is stored and how strict the backups are",
+      "options": {
+        "公開してよい情報のみ": "Only information that can be public",
+        "身内だけの情報": "Information for close people only",
+        "個人情報を含む": "Includes personal information",
+        "お金や健康など特に機微な情報": "Especially sensitive information, such as money or health"
+      }
+    },
+    "uiLanguage": {
+      "label": "The language of the screens",
+      "why": "The language the app is shown in",
+      "options": {
+        "日本語": "Japanese",
+        "English": "English",
+        "両方": "Both"
+      }
+    },
+    "design": {
+      "label": "Look",
+      "why": "\"The same as MulmoTerminal\" builds it with the same parts, colors and icons as the collection's screens you saw in MulmoTerminal. The others are templates that keep those parts' shapes and swap the colors and the roundness of the corners",
+      "options": {
+        "MulmoTerminal と同じ": "The same as MulmoTerminal",
+        "やわらかい（暖かい紙の色・丸い角）": "Soft (warm paper colors, round corners)",
+        "くっきり（白と黒・小さな角）": "Crisp (black and white, small corners)",
+        "落ち着いた（深い緑・やさしい灰色）": "Calm (deep green, gentle gray)"
+      }
+    }
+  },
+  "steps": {
+    "import@local": {
+      "title": "Move the records",
+      "description": "Moves the copied collection's records, and the images and files they point to, into the app's database and data/files/. Running it again gives the same result. A build that copied only the shape does nothing here."
+    },
+    "import@firebase": {
+      "title": "Move the records (emulators)",
+      "description": "Builds the way to move the copied collection's records into Firestore, and the images and files they point to into Cloud Storage, and checks it on the emulators. A build that copied only the shape does nothing here."
+    },
+    "import@cloudflare": {
+      "title": "Move the records",
+      "description": "Builds the way to move the copied collection's records into D1, and the images and files they point to into R2, and checks it by moving them twice into an empty local setup. A build that copied only the shape does nothing here."
+    },
+    "import@supabase": {
+      "title": "Move the records",
+      "description": "Builds the way to move the copied collection's records into Postgres, and the images and files they point to into Storage, and checks it by rebuilding the local database and moving them twice. A build that copied only the shape does nothing here."
+    },
+    "acceptance@local": {
+      "title": "Prove the must-haves by tests",
+      "description": "Each must-have in the spec gets a test that shows it working end to end through the API."
+    },
+    "acceptance@firebase": {
+      "title": "Prove the must-haves by tests",
+      "description": "Each must-have gets a test against the emulators that walks it end to end as a signed-in user, and is refused for everyone it should be refused for."
+    },
+    "acceptance@cloudflare": {
+      "title": "Prove the must-haves by tests",
+      "description": "Each must-have in the spec gets a test that shows it working end to end through the Worker, inside the Workers runtime."
+    },
+    "acceptance@supabase": {
+      "title": "Prove the must-haves by tests",
+      "description": "Each must-have in the spec gets a test against the local Supabase stack that walks it end to end as the user the spec names, and is refused for everyone it should be refused for."
+    },
+    "actions@local": {
+      "title": "Make the actions features",
+      "description": "Of the original actions and automatic imports, builds the ones the spec decided to \"make a feature\", and writes the steps for the ones \"a person does by hand\" in the README."
+    },
+    "actions@firebase": {
+      "title": "Make the actions features",
+      "description": "Of the original actions and automatic imports, builds the ones the spec decided to \"make a feature\" as screen actions, functions and scheduled functions, and writes the steps for the ones \"a person does by hand\" in the README."
+    },
+    "actions@cloudflare": {
+      "title": "Make the actions features",
+      "description": "Of the original actions and automatic imports, builds the ones the spec decided to \"make a feature\" as Worker operations and scheduled runs (Cron Triggers), and writes the steps for the ones \"a person does by hand\" in the README."
+    },
+    "actions@supabase": {
+      "title": "Make the actions features",
+      "description": "Of the original actions and automatic imports, builds the ones the spec decided to \"make a feature\" as Postgres functions, Edge Functions and scheduled runs, and writes the steps for the ones \"a person does by hand\" in the README."
+    },
+    "features": {
+      "title": "Features and screens",
+      "description": "Builds the spec's must-haves as screens and client-side code, and checks on the emulators that they work inside the Firestore rules."
+    },
+    "design": {
+      "title": "Match the look",
+      "description": "Makes the screens match the chosen look (the same as MulmoTerminal, or a template). Uses the same parts and classes as MulmoTerminal's collection screens, with Tailwind, and carries the original collection's icon over to the headings. Writes the rules down in DESIGN.md."
+    },
+    "import-production@firebase": {
+      "title": "Move the records to production",
+      "description": "With the way checked on the emulators, moves the copied records, images and files into the production Firestore and Cloud Storage, then reads production back and compares it with the original. A build that copied only the shape does nothing here."
+    },
+    "import-production@cloudflare": {
+      "title": "Move the records to production",
+      "description": "With the way checked locally, moves the copied records, images and files into the production D1 and R2, then reads them back with wrangler and compares them with the original. A build that copied only the shape does nothing here."
+    },
+    "import-production@supabase": {
+      "title": "Move the records to production",
+      "description": "With the way checked locally, moves the copied records, images and files into the production Postgres and Storage, then reads them back with the Supabase CLI and compares them with the original. A build that copied only the shape does nothing here."
+    }
+  }
+}