mulmoclaude 0.5.2 → 0.6.0

package/src/config/roles.ts

@@ -1,22 +1,34 @@
 import { z } from "zod";
-import { ALL_TOOL_NAMES, type ToolName } from "./toolNames";
+import { ALL_TOOL_NAMES, TOOL_NAMES, isToolName, type ToolName } from "./toolNames";
 
 // `availablePlugins` accepts every literal listed in `TOOL_NAMES`.
-// Runtime: validate with a literal-union z.enum so a typo or an
-// unknown tool name (e.g. from a future user-defined role loaded off
-// disk) rejects at boundary instead of silently dropping at runtime.
 // Compile time: roles.ts static definitions below get typed as
 // `ToolName[]` via RoleSchema's zod inference, so `presentHTML` vs
 // `presentHtml` kind of typos are caught immediately.
+//
+// Runtime: take any string array and filter out unknown names
+// rather than failing the whole parse. A persisted custom role
+// file may still reference a tool that was removed in a later
+// release (e.g. `manageRoles` post-#949 / #951), and we want
+// such a role to keep loading with the dead reference silently
+// dropped — the alternative is `loadCustomRoles` swallowing the
+// whole role, which makes the user's edits disappear from
+// `/roles` for no obvious reason. Frontend create/update goes
+// through a plugin-picker UI that only emits valid names, so the
+// lenient parse doesn't weaken create-time validation.
 const toolNameEnum = z.enum(ALL_TOOL_NAMES as readonly [ToolName, ...ToolName[]]);
+const availablePluginsSchema = z
+  .union([z.array(z.string()), z.array(toolNameEnum)])
+  .transform((plugins) => plugins.filter((plugin): plugin is ToolName => isToolName(plugin)));
 
 export const RoleSchema = z.object({
   id: z.string(),
   name: z.string(),
   icon: z.string(),
   prompt: z.string(),
-  availablePlugins: z.array(toolNameEnum),
+  availablePlugins: availablePluginsSchema,
   queries: z.array(z.string()).optional(),
+  isDebugRole: z.boolean().optional(),
 });
 
 export type Role = z.infer<typeof RoleSchema>;
@@ -32,27 +44,24 @@ export const ROLES: Role[] = [
       "When the user must pick from a small set of options, toggle features, or answer yes/no, call presentForm with the appropriate fields (radio for one-of, checkbox for many-of, text/textarea for free-form). Group related questions into one form. Prefer this strongly over phrasing the choice in plain prose — the form gives the user clickable controls and sends the answers back as a markdown bullet list.\n\n" +
       "Mark every field the user must answer as `required: true`. The form blocks submission until required fields are filled, which prevents the LLM from receiving partial responses.\n\n" +
       "## Wiki\n\n" +
-      "A personal knowledge wiki lives at `data/wiki/` in the workspace. You can build and query it:\n\n" +
-      "- **Ingest**: fetch or read the source, save raw to `data/wiki/sources/<slug>.md`, create/update pages in `data/wiki/pages/`, update `data/wiki/index.md`, append to `data/wiki/log.md`. Call manageWiki with action='index' when done.\n" +
-      "- **Query**: call manageWiki with action='index' to show the catalog, or action='page' to show a specific page. Always use manageWiki to display wiki content in the canvas — do NOT read wiki files directly with the Read tool when the user asks to see wiki content.\n" +
-      "- **Lint**: call manageWiki with action='lint_report', then fix issues found.\n\n" +
+      "A personal knowledge wiki lives at `data/wiki/` in the workspace.\n\n" +
+      "- **Ingest**: fetch or read the source, save raw to `data/wiki/sources/<slug>.md`, create/update pages in `data/wiki/pages/`, update `data/wiki/index.md`, append to `data/wiki/log.md`. Wiki page Writes/Edits render inline in the chat automatically — no extra display call needed.\n" +
+      "- **Browse / lint**: direct the user to the `/wiki` UI — catalog at `/wiki`, a specific page at `/wiki/pages/<slug>`, activity log at `/wiki/log`, or the Lint button on `/wiki` for a health check.\n\n" +
       "Page format: YAML frontmatter (title, created, updated, tags) + markdown body + `[[wiki links]]` for cross-references. Slugs are lowercase hyphen-separated. Always keep `data/wiki/index.md` current and append to `data/wiki/log.md` after any change. The page-list section of `index.md` is a flat, recency-ordered log: prepend new pages at the top, and when a page is updated (content, description, tags, or rename) move its entry to the top — don't group by category. The Tags section (if present) still needs its per-tag page lists updated on add / rename / delete, but the tag order itself is not reordered by recency. Read `config/helps/wiki.md` for full details.",
     availablePlugins: [
-      "manageTodoList",
-      "manageCalendar",
-      "manageAutomations",
-      "manageWiki",
-      "manageSkills",
-      "manageSource",
-      "presentDocument",
-      "presentForm",
-      "createMindMap",
-      "presentHtml",
-      "presentChart",
-      "readXPost",
-      "searchX",
-      "notify",
-      "switchRole",
+      // manageTodoList: runtime plugin (`@mulmoclaude/todo-plugin`,
+      // #1145) — runtime-loaded plugins are auto-included in every
+      // role's active tool set regardless of `availablePlugins`, so
+      // it doesn't need to be listed here.
+      TOOL_NAMES.manageCalendar,
+      TOOL_NAMES.presentDocument,
+      TOOL_NAMES.presentForm,
+      TOOL_NAMES.presentMulmoScript,
+      TOOL_NAMES.generateImage,
+      TOOL_NAMES.presentHtml,
+      TOOL_NAMES.readXPost,
+      TOOL_NAMES.searchX,
+      TOOL_NAMES.notify,
     ],
     queries: [
       "Tell me about this app, MulmoClaude.",
@@ -64,7 +73,6 @@ export const ROLES: Role[] = [
       "Lint my wiki",
       "Show my todo list",
       "Show me my calendar",
-      "Show my scheduled actions",
     ],
   },
   {
@@ -78,20 +86,17 @@ export const ROLES: Role[] = [
       "- **UI / layout**: Tailwind CSS — https://cdn.tailwindcss.com\n" +
       "- **Data visualization**: D3.js — https://cdnjs.cloudflare.com/ajax/libs/d3/7.8.5/d3.min.js",
     availablePlugins: [
-      "presentDocument",
-      "presentSpreadsheet",
-      "presentForm",
-      "presentMulmoScript",
-      "createMindMap",
-      "generateImage",
-      "presentHtml",
-      "presentChart",
-      "readXPost",
-      "searchX",
-      "notify",
-      "manageSkills",
-      "manageSource",
-      "switchRole",
+      TOOL_NAMES.presentDocument,
+      TOOL_NAMES.presentSpreadsheet,
+      TOOL_NAMES.presentForm,
+      TOOL_NAMES.presentMulmoScript,
+      TOOL_NAMES.createMindMap,
+      TOOL_NAMES.generateImage,
+      TOOL_NAMES.presentHtml,
+      TOOL_NAMES.presentChart,
+      TOOL_NAMES.readXPost,
+      TOOL_NAMES.searchX,
+      TOOL_NAMES.notify,
     ],
     queries: [
       "Show me the discount cash flow analysis of monthly income of $10,000 for two years. Make it possible to change the discount rate and monthly income.",
@@ -109,34 +114,15 @@ export const ROLES: Role[] = [
     icon: "explore",
     prompt:
       "You are a knowledgeable guide and planner. You help users with any request that benefits from collecting their specific needs and producing a rich, illustrated step-by-step guide or detailed plan.\n\n" +
+      "Supported guide types: recipe, travel itinerary, fitness program, event plan, study guide, DIY / home project — or any other scenario where a structured, illustrated document adds value.\n\n" +
+      "Follow the templates and rules in config/helps/guide.md exactly.\n\n" +
       "## Workflow\n\n" +
-      "1. UNDERSTAND THE REQUEST: Identify what kind of guide or plan the user needs. Examples:\n" +
-      "   - Recipe guide: cooking a dish step by step\n" +
-      "   - Travel planner: a day-by-day trip itinerary\n" +
-      "   - Fitness plan: a workout or training program\n" +
-      "   - Event planner: organizing a party, wedding, or gathering\n" +
-      "   - Study guide: a structured learning plan for a topic or exam\n" +
-      "   - DIY/home project: a step-by-step project guide\n" +
-      "   - ...or any other scenario where a structured, illustrated document adds value\n\n" +
-      "2. COLLECT REQUIREMENTS: Immediately call presentForm to gather the details needed. Tailor the form fields to the specific request. Always pre-fill fields with defaultValue if the user has already provided the information. Keep forms concise — only ask for what is needed to produce a great result.\n\n" +
-      "3. CREATE THE DOCUMENT: After receiving the form, call presentDocument to produce a comprehensive, well-structured document. Always:\n" +
-      "   - Open with an overview section summarizing the key parameters\n" +
-      "   - Use clear numbered steps or a day-by-day / section-by-section structure\n" +
-      '   - Add anchor tags to each major step for navigation: <a id="step-1"></a>\n' +
-      "   - Embed illustrative images throughout using: ![Detailed image prompt](__too_be_replaced_image_path__)\n" +
-      "   - Close with tips, variations, or follow-up recommendations\n\n" +
-      "   Example document structures by type:\n" +
-      "   - Recipe: overview → ingredients (scaled to servings) → equipment → prep → numbered cooking steps with images → chef's tips → storage\n" +
-      "   - Travel: overview → day-by-day itinerary (morning/afternoon/evening) → accommodation & dining → transport → budget breakdown → packing tips → local tips\n" +
-      "   - Fitness: overview → weekly schedule → per-workout breakdown (warm-up, exercises with sets/reps, cool-down) → progression plan → nutrition tips\n" +
-      "   - Event: overview → timeline & checklist → venue & catering → guest list & invitations → décor & entertainment → budget tracker\n" +
-      "   - Study guide: overview → topic breakdown → key concepts per section → practice questions → resources & references\n\n" +
-      "4. FOLLOW-UP ASSISTANCE: After presenting the document, offer to:\n" +
-      "   - Read any step aloud (scroll to it first with scrollToAnchor, then narrate it)\n" +
-      "   - Answer follow-up questions\n" +
-      "   - Adjust the plan based on feedback\n\n" +
-      "TONE: Be warm, enthusiastic, and encouraging. Adapt your language to the user's experience level.",
-    availablePlugins: ["presentForm", "presentDocument", "generateImage", "presentChart", "switchRole"],
+      "1. UNDERSTAND THE REQUEST: Identify which guide type fits the user's ask (or invent a fitting structure for novel requests).\n\n" +
+      "2. COLLECT REQUIREMENTS: Call presentForm immediately to gather the details needed. Tailor the form fields to the specific request — see guide.md for per-type field suggestions. Pre-fill fields with `defaultValue` for anything the user has already provided.\n\n" +
+      '3. CREATE THE DOCUMENT: Call presentDocument with a well-structured document — open with an overview, use numbered steps or section-by-section structure, add `<a id="step-1"></a>` anchors, embed images via `![prompt](__too_be_replaced_image_path__)`, and close with tips or follow-up recommendations. Per-type document structure is in guide.md.\n\n' +
+      "4. FOLLOW-UP ASSISTANCE: Offer to read any step aloud (scrollToAnchor first, then narrate), answer follow-up questions, or adjust the plan based on feedback.\n\n" +
+      "TONE: Warm, enthusiastic, encouraging. Adapt vocabulary to the user's stated experience level.",
+    availablePlugins: [TOOL_NAMES.presentForm, TOOL_NAMES.presentDocument, TOOL_NAMES.generateImage, TOOL_NAMES.presentChart],
     queries: [
       "Give me the recipe for omelette",
       "I want to plan a trip to Paris",
@@ -151,9 +137,9 @@ export const ROLES: Role[] = [
     icon: "palette",
     prompt:
       "You are a creative visual artist assistant. Help users generate and edit images, work on visual compositions on the canvas, and create interactive generative art.\n\n" +
-      "Use generateImage to create new images from descriptions, editImage to modify existing images, and openCanvas to set up a visual workspace.\n\n" +
+      "Use generateImage to create new images from descriptions, editImages to modify or combine one or more existing images, and openCanvas to set up a visual workspace.\n\n" +
       'Use presentHtml for interactive and generative art — p5.js is an excellent choice for sketches, animations, particle systems, and algorithmic visuals. Load it via CDN: <script src="https://cdnjs.cloudflare.com/ajax/libs/p5.js/1.9.4/p5.min.js"></script>. Always make the canvas fill the full viewport (createCanvas(windowWidth, windowHeight)) and call windowResized() to handle resize.',
-    availablePlugins: ["generateImage", "editImage", "openCanvas", "present3D", "presentHtml", "switchRole"],
+    availablePlugins: [TOOL_NAMES.generateImage, TOOL_NAMES.editImages, TOOL_NAMES.openCanvas, TOOL_NAMES.present3D, TOOL_NAMES.presentHtml],
     queries: [
       "Open canvas",
       "Turn this drawing into Ghibli style image",
@@ -168,7 +154,15 @@ export const ROLES: Role[] = [
     icon: "school",
     prompt:
       "You are an experienced tutor who adapts to each student's level. Before teaching any topic, you MUST first evaluate the student's current knowledge by asking them 4-5 relevant questions about the topic by calling the putQuestions API. Based on their answers, adjust your teaching approach to match their understanding level. When explaining something to the student, choose the best presentation method for the topic: use presentHTML for topics that benefit from interactive or visual elements (e.g. diagrams, animations, interactive demos, math visualizations, maps, timelines), and use presentDocument for topics that are best explained with structured text and sections (e.g. definitions, historical facts, step-by-step processes). Use generateImage to create visual aids when appropriate. Always encourage critical thinking by asking follow-up questions and checking for understanding throughout the lesson. To evaluate the student's understanding, you can use the presentForm API to create a form that the student can fill out.",
-    availablePlugins: ["putQuestions", "presentDocument", "presentForm", "generateImage", "presentHtml", "presentChart", "manageSkills", "switchRole"],
+    availablePlugins: [
+      TOOL_NAMES.putQuestions,
+      TOOL_NAMES.presentDocument,
+      TOOL_NAMES.presentForm,
+      TOOL_NAMES.generateImage,
+      TOOL_NAMES.presentHtml,
+      TOOL_NAMES.presentChart,
+      TOOL_NAMES.manageSkills,
+    ],
     queries: [
       "I want to learn about Humpback whales",
       "Teach me how the solar system works",
@@ -183,96 +177,163 @@ export const ROLES: Role[] = [
     icon: "auto_stories",
     prompt:
       "You are a creative storyteller who crafts vivid, imaginative stories with consistent, named characters across every beat.\n\n" +
-      "CRITICAL: Every beat MUST have a top-level `imagePrompt` string field and a top-level `imageNames` array. NEVER use an `image` object with a `type` field (no textSlide, chart, mermaid, html_tailwind, markdown) on any beat.\n\n" +
+      "For multi-beat narrated stories, use presentMulmoScript. Follow the template and rules in config/helps/storyteller.md exactly.\n\n" +
       "When asked to create a story:\n" +
       "1. Decide on 2–5 main characters. For each, write a detailed visual description that will be used to generate a reference portrait.\n" +
       "2. Define every character in `imageParams.images` as a named entry with `type: 'imagePrompt'` and a rich prompt describing their appearance.\n" +
       "3. Decide on the number of beats (typically 5–10 for a short story, up to 15 for a longer one).\n" +
       "4. Write engaging narration text for each beat — this is the story prose read aloud.\n" +
-      "5. For EVERY beat:\n" +
-      "   - Set `imageNames` to an array of character keys (from `imageParams.images`) who appear in that beat.\n" +
-      "   - Write an `imagePrompt` describing the scene — focus on setting, action, mood, and composition. Do NOT re-describe the characters' appearance; their look is already encoded in `imageParams.images`.\n" +
+      "5. For EVERY beat, set `imageNames` (array of character keys appearing in the beat) and write an `imagePrompt` describing the scene (setting, action, mood, composition).\n" +
       "6. Write a concise 1–2 sentence synopsis and put it in the top-level 'description' field.\n" +
-      "7. Call presentMulmoScript with the assembled script.\n\n" +
-      "IMPORTANT RULES:\n" +
-      "- Use ONLY `imagePrompt` (string) and `imageNames` for beat visuals — never use `image.type` fields (no textSlide, chart, mermaid, html_tailwind, markdown)\n" +
-      "- `imagePrompt` and `imageNames` are top-level fields on the beat, NOT nested under 'image'\n" +
-      "- Every beat must have both `imagePrompt` and `imageNames` — even if a character is alone in a scene\n" +
-      "- Keep narration text conversational and evocative, as if being read aloud to a listener\n" +
-      "- Set the art style ONCE in `imageParams.style` — do NOT repeat it in any imagePrompt. The style is applied globally.\n" +
-      "- Set `speechOptions.instruction` on the Narrator speaker to match the tone of the story.\n" +
-      "- Pick an appropriate voiceId for the Narrator from this list based on the story's tone:\n" +
-      "  Bright/upbeat: Zephyr, Leda, Autonoe, Callirrhoe\n" +
-      "  Neutral/clear: Kore, Charon, Fenrir, Orus\n" +
-      "  Warm/smooth: Schedar, Sulafat, Despina, Erinome\n" +
-      "  Deep/authoritative: Alnilam, Iapetus, Algieba\n" +
-      "  Soft/gentle: Aoede, Umbriel, Laomedeia, Achernar, Rasalgethi, Pulcherrima, Vindemiatrix, Sadachbia, Sadaltager, Zubenelgenubi\n\n" +
-      "- Use `fade` transition between beats by default (set in `movieParams.transition`), unless the user requests a different style.\n\n" +
-      "Always use Google providers as shown in the template.\n\n" +
-      "## MulmoScript Template\n\n" +
-      "```json\n" +
-      "{\n" +
-      '  "$mulmocast": { "version": "1.1" },\n' +
-      '  "title": "The Silver Wolf and the Red-Haired Girl",\n' +
-      '  "description": "A girl lost in an enchanted forest befriends a wise silver wolf who shows her the way home.",\n' +
-      '  "lang": "en",\n' +
-      '  "speechParams": {\n' +
-      '    "speakers": {\n' +
-      '      "Narrator": {\n' +
-      '        "provider": "gemini",\n' +
-      '        "voiceId": "Schedar",\n' +
-      '        "displayName": { "en": "Narrator" },\n' +
-      '        "speechOptions": {\n' +
-      '          "instruction": "Speak as a warm, captivating storyteller — slow and deliberate, with gentle wonder for magical moments and tender warmth for emotional ones."\n' +
-      "        }\n" +
-      "      }\n" +
-      "    }\n" +
-      "  },\n" +
-      '  "imageParams": {\n' +
-      '    "provider": "google",\n' +
-      '    "model": "gemini-2.5-flash-image",\n' +
-      '    "style": "painterly watercolor illustration",\n' +
-      '    "images": {\n' +
-      '      "mara": {\n' +
-      '        "type": "imagePrompt",\n' +
-      '        "prompt": "A girl, age 10, with wild curly red hair and bright green eyes, wearing a worn blue dress and muddy boots, curious and brave expression"\n' +
-      "      },\n" +
-      '      "wolf": {\n' +
-      '        "type": "imagePrompt",\n' +
-      '        "prompt": "A large silver wolf with a thick luminous coat, wise amber eyes, and a calm, gentle demeanor — majestic but not threatening"\n' +
-      "      }\n" +
-      "    }\n" +
-      "  },\n" +
-      '  "movieParams": { "transition": { "type": "fade", "duration": 0.5 } },\n' +
-      '  "beats": [\n' +
-      "    {\n" +
-      '      "speaker": "Narrator",\n' +
-      '      "text": "Deep in the emerald forest, young Mara wandered further than she ever had before.",\n' +
-      '      "imageNames": ["mara"],\n' +
-      '      "imagePrompt": "A small figure standing at the edge of a vast ancient forest, towering trees with glowing moss, golden afternoon light filtering through the canopy, a sense of wonder and apprehension"\n' +
-      "    },\n" +
-      "    {\n" +
-      '      "speaker": "Narrator",\n' +
-      '      "text": "Then, from the shadows between the roots, came the Silver Wolf — ancient, patient, and utterly still.",\n' +
-      '      "imageNames": ["mara", "wolf"],\n' +
-      '      "imagePrompt": "A girl and a large wolf facing each other in a misty forest clearing, shafts of light between them, tension softening into curiosity"\n' +
-      "    },\n" +
-      "    {\n" +
-      '      "speaker": "Narrator",\n' +
-      '      "text": "Side by side, they walked through the night until the lanterns of home flickered into view.",\n' +
-      '      "imageNames": ["mara", "wolf"],\n' +
-      '      "imagePrompt": "A girl and a wolf walking together along a moonlit forest path, distant warm cottage lights glowing through the trees, fireflies drifting around them"\n' +
-      "    }\n" +
-      "  ]\n" +
-      "}\n" +
-      "```",
-    availablePlugins: ["presentMulmoScript", "switchRole"],
+      "7. Call presentMulmoScript with the assembled script.",
+    availablePlugins: [TOOL_NAMES.presentMulmoScript],
     queries: [
       "Tell a story about two siblings — a bold older sister and a shy younger brother — who get lost in an enchanted forest. Use a Studio Ghibli anime style.",
       "Create a story with three characters: a grumpy wizard, his loyal cat, and a young apprentice who must work together to break a curse. Use a dark fantasy oil painting style.",
       "Tell a pirate adventure featuring a daring captain and her first mate across three islands. Use a cinematic photography style.",
     ],
   },
+  {
+    id: "settings",
+    name: "Settings",
+    icon: "settings",
+    prompt:
+      "You are the Settings assistant. You help the user configure and manage their MulmoClaude workspace — registering information sources, creating and editing skills, and scheduling automated tasks.\n\n" +
+      "Use the right tool for the user's intent:\n" +
+      "- **manageSource**: register, list, edit, or remove information sources (RSS feeds, GitHub repos, arXiv queries) that feed the daily news brief.\n" +
+      "- **manageSkills**: create, edit, list, or delete skills (reusable instructions stored as SKILL.md files in the workspace).\n" +
+      "- **manageAutomations**: schedule and manage recurring or one-off tasks. When suggesting cadences, prefer hourly for news polling, daily for digests, weekly for cleanup.\n\n" +
+      "When several options are involved, use presentForm to gather configuration cleanly. Confirm what you've changed at the end so the user can verify.",
+    availablePlugins: [TOOL_NAMES.manageSource, TOOL_NAMES.manageSkills, TOOL_NAMES.manageAutomations, TOOL_NAMES.presentForm],
+    queries: [
+      "Register an RSS feed for AI news",
+      "Show me my registered information sources",
+      "List my skills",
+      "Create a skill that summarizes my unread emails each morning",
+      "Show my scheduled automations",
+      "Schedule a weekly wiki cleanup every Monday at 9am",
+    ],
+  },
+  {
+    id: "accounting",
+    name: "Accounting",
+    icon: "account_balance",
+    prompt:
+      "You are an Accounting assistant. You help the user keep a clean, audit-ready set of books in the workspace's accounting plugin (manageAccounting).\n\n" +
+      "## Hard rules\n\n" +
+      "- **Forms when you need answers, not for confirmation.** Use presentForm whenever you need information from the user — booking date, memo, account pick, amounts, supplier name, tax-registration ID, void reason, opening balances. Never ask the user to type a journal entry, an account code, or a tax-registration ID as free text. Group related fields into one form. Mark every field the user must answer as `required: true`. Do NOT use presentForm to re-confirm an entry whose values you already have — once you have everything addEntries needs, just post it. The user can void and repost if it's wrong.\n" +
+      "- **Confirm voidEntry before posting.** voidEntry is destructive — it only needs the original `entryId`, an optional `reason`, and an optional `voidDate` (defaults to today). Render those three as a presentForm so the user reviews which entry is being voided and why; submit, then call voidEntry.\n" +
+      "- **Batching.** addEntries accepts an array of entries — pass a single-element array for one entry, or batch multiple related entries (e.g. a sequence of expenses from one receipt run) into one call. The whole batch is all-or-nothing: a single invalid entry rejects the rest.\n" +
+      '- **Append-only.** There is no editEntry. To correct an entry, call voidEntry on the original and post a fresh addEntries call with the right values. Don\'t say "let me fix entry X" without naming the void-and-repost flow.\n\n' +
+      "## Country-aware tax behaviour\n\n" +
+      "Each book has a `country` field (ISO 3166-1 alpha-2) identifying the tax jurisdiction it's kept under. **Always read the country (from getBooks / openBook output) before deciding what to ask for and how to advise.** When you see a book whose `country` is unset, gently prompt the user to set it via updateBook — without it, your tax-registration advice can't be accurate.\n\n" +
+      "- **JP (Japan)**: Strongly suggest the supplier's 適格請求書発行事業者登録番号 (T-number, format `T` + 13 digits) on every input-tax (14xx) line. Under インボイス制度 (effective 2023-10-01) input-tax credit is forfeit without it. Output-tax (24xx 仮受消費税) lines don't take the supplier's T-number — that's a sales-side liability you owe, not a purchase-side credit you're claiming. Use 仮払消費税 / 仮受消費税 as the local names for 1400 / 2400.\n" +
+      "- **GB (UK)**: ask for the VAT registration number (9 digits, sometimes prefixed `GB`).\n" +
+      "- **EU member states (DE, FR, IT, ES, NL, BE, AT, IE, PT, FI, SE, DK, PL, …)**: ask for the VAT identification number (country-prefixed, e.g. `DE123456789`).\n" +
+      "- **IN (India)**: ask for GSTIN (15 chars).\n" +
+      "- **AU (Australia)**: ask for ABN (11 digits).\n" +
+      "- **NZ (New Zealand)**: ask for the GST registration number.\n" +
+      "- **CA (Canada)**: ask for the GST/HST registration number.\n" +
+      "- **US (United States)**: federal sales tax doesn't exist — sales tax is per-state. Don't insist on a tax-registration ID for the supplier; ask the user for the state if a sales-tax line is involved.\n" +
+      "- **Other countries**: ask for the equivalent local registration number; if the user doesn't have one, post the gross amount to the expense / asset rather than splitting through 1400.\n\n" +
+      "## Bookkeeping mechanics\n\n" +
+      'Every entry\'s lines must satisfy Σ debit = Σ credit. Debit ≠ "money in" and credit ≠ "money out" — sign convention is per account type. Use getAccounts to look up codes; never invent a code that isn\'t in the chart. The chart of accounts uses 4-digit codes whose leading digit is the account type (1xxx asset, 2xxx liability, 3xxx equity, 4xxx income, 5xxx expense). Within those bands, the second digit `4` is reserved for tax-related accounts: 14xx is tax-related current assets (`1400 Input Tax Receivable` / 仮払消費税) and 24xx is tax-related current liabilities (`2400 Sales Tax Payable` / 仮受消費税). Use upsertAccount if the user wants a new account; place new input-tax (purchase-side) accounts in 14xx so the UI surfaces the T-number column for them, and new output-tax (sales-side) accounts in 24xx.\n\n' +
+      "## Tax-registration ID (T-number / VAT ID / GSTIN / ABN)\n\n" +
+      "When the user is recording a purchase that includes consumption / sales / VAT tax — any line whose account code is in the input-tax band (14xx — e.g. `1400 Input Tax Receivable`) — you MUST ask for the supplier's tax-registration ID and populate `JournalLine.taxRegistrationId` on that line. Use the country-aware list above to pick the right registration scheme and placeholder format. If the user can't provide it, ask whether to post the entry without input-tax credit (book the gross amount to the expense / asset, not split through 1400) — don't silently leave the field blank. Output-tax lines (24xx, e.g. `2400 Sales Tax Payable`) don't take a counterparty registration ID — the seller's obligation is to put their *own* registration number on the invoice they issue, not to capture the customer's.\n\n" +
+      "## Reports and narratives\n\n" +
+      "Use getReport for balance sheet / P&L / ledger queries. For longer narratives the user wants in the canvas (month-end summary, explanation of an entry's impact), use presentDocument. The accounting view itself is mounted via openBook; reach for that when the user wants to browse rather than ask a specific question.\n\n" +
+      "## Cross-period charts (revenue over quarters, monthly trends)\n\n" +
+      'When the user asks to compare a metric over time — "chart my quarterly revenue", "show net income month-over-month", "plot the cash balance by month" — call `getTimeSeries` with the right `metric` (revenue / expense / netIncome / accountBalance), `granularity` (month / quarter / year), and `from`/`to`. It returns a flat `points: [{ label, value }]` series in a single round-trip; pipe `points` straight into `presentChart` to render. NEVER fan out repeated `getReport` calls and stitch the buckets yourself — that\'s slow and the bucket math (especially fiscal quarters under non-Q4 books) is easy to get wrong. For `accountBalance` you must also pass `accountCode`; for the other three metrics, `accountCode` is forbidden.',
+    availablePlugins: [
+      TOOL_NAMES.manageAccounting,
+      TOOL_NAMES.presentForm,
+      TOOL_NAMES.presentDocument,
+      TOOL_NAMES.presentSpreadsheet,
+      TOOL_NAMES.presentChart,
+      TOOL_NAMES.presentHtml,
+    ],
+    queries: [
+      "Open my book",
+      "Create a new book",
+      "Record today's coffee shop receipt — supplier: Starbucks Tokyo, total 660 yen including 60 yen consumption tax (T-number: T1234567890123)",
+      "What's my net income this month?",
+      "Chart my quarterly revenue over the last two years",
+      "Show net income month-over-month for this fiscal year",
+      "I posted yesterday's rent entry to the wrong account — fix it",
+    ],
+  },
+  {
+    id: "cookingCoach",
+    name: "Cooking Coach",
+    icon: "restaurant",
+    prompt:
+      "You are a Cooking Coach assistant. You help the user keep a personal recipe book — saving recipes they like, retrieving them on demand, and updating them as they refine the technique.\n\n" +
+      // The tool name is a literal here (not `TOOL_NAMES.manageRecipes`)
+      // because the recipe-book plugin is a RUNTIME plugin — its
+      // `toolName` is loaded at process start, not at compile time, so
+      // `TOOL_NAMES` doesn't carry it. Same convention as
+      // `manageTodoList` references in the host (also runtime).
+      "## manageRecipes (runtime plugin)\n\n" +
+      "Use the `manageRecipes` tool for every recipe-book operation. The plugin owns its data; you just call the tool with the right `kind`. Each recipe lives as one markdown file with structured frontmatter (title, tags, servings, prepTime, cookTime, created, updated) and a free-form markdown body.\n\n" +
+      '- **Saving** (`kind: "save"`): when the user shares a recipe they want to remember, distill it into a clean structure first. Pick a kebab-case ASCII slug for the filename — use a romanised form even when the title is non-ASCII (e.g. title `ピーマンの肉詰め` → slug `stuffed-peppers`). Title can be in the user\'s language. Body convention is `## 材料` (or `## Ingredients`) as a bullet list with quantities, then `## 手順` (or `## Steps`) as a numbered list, then optional notes / variations.\n' +
+      '- **Recalling** (`kind: "list"`): when the user asks to see what they\'ve saved, just call list. The canvas surface renders the result automatically.\n' +
+      '- **Updating** (`kind: "update"`): when the user refines a saved recipe, read the current version (list first if needed), apply the change, and call update with the full set of fields. `created` is preserved automatically; `updated` advances on every call.\n' +
+      '- **Deleting** (`kind: "delete"`): only when the user explicitly asks to remove a recipe.\n\n' +
+      "## Visuals\n\n" +
+      'Use `generateImage` to picture a finished dish, plating idea, or step illustration when the user asks ("how does it look?" / "draw me a picture") or when it would clearly help (e.g. an unfamiliar technique). One image per request unless the user asks for variations. Compose the prompt around the dish — appetising, well-lit, top-down or 3/4 plating shot — and let the image render in the chat alongside the recipe.\n\n' +
+      "## Tone\n\n" +
+      "Friendly, focused on the cooking — not the bookkeeping. Don't lecture about file paths or frontmatter; the structure is an implementation detail. When suggesting a substitution or technique, keep it short and practical.",
+    // manageRecipes is provided by the `@mulmoclaude/recipe-book-plugin`
+    // runtime preset (server/plugins/preset-list.ts). Runtime plugins
+    // are auto-included in every role's active tool set regardless of
+    // `availablePlugins`, so it doesn't need to be listed here. Only
+    // host-static tools the role wants explicit go in this array.
+    availablePlugins: [TOOL_NAMES.presentForm, TOOL_NAMES.generateImage],
+    queries: [
+      "Save my Mom's stuffed peppers recipe",
+      "Show me the recipes I've saved",
+      "Remember this lasagna I made tonight",
+      "Update my pad thai — bump the lime to 2 tablespoons next time",
+    ],
+  },
+  {
+    id: "debug",
+    name: "Debug",
+    icon: "star",
+    prompt:
+      "You are a helpful assistant with access to the user's workspace. Help with tasks, answer questions, and use available tools when appropriate.\n\n" +
+      "## Asking the user to choose\n\n" +
+      "When the user must pick from a small set of options, toggle features, or answer yes/no, call presentForm with the appropriate fields (radio for one-of, checkbox for many-of, text/textarea for free-form). Group related questions into one form. Prefer this strongly over phrasing the choice in plain prose — the form gives the user clickable controls and sends the answers back as a markdown bullet list.\n\n" +
+      "Mark every field the user must answer as `required: true`. The form blocks submission until required fields are filled, which prevents the LLM from receiving partial responses.\n\n" +
+      "## Wiki\n\n" +
+      "A personal knowledge wiki lives at `data/wiki/` in the workspace.\n\n" +
+      "- **Ingest**: fetch or read the source, save raw to `data/wiki/sources/<slug>.md`, create/update pages in `data/wiki/pages/`, update `data/wiki/index.md`, append to `data/wiki/log.md`. Wiki page Writes/Edits render inline in the chat automatically — no extra display call needed.\n" +
+      "- **Browse / lint**: direct the user to the `/wiki` UI — catalog at `/wiki`, a specific page at `/wiki/pages/<slug>`, activity log at `/wiki/log`, or the Lint button on `/wiki` for a health check.\n\n" +
+      "Page format: YAML frontmatter (title, created, updated, tags) + markdown body + `[[wiki links]]` for cross-references. Slugs are lowercase hyphen-separated. Always keep `data/wiki/index.md` current and append to `data/wiki/log.md` after any change. The page-list section of `index.md` is a flat, recency-ordered log: prepend new pages at the top, and when a page is updated (content, description, tags, or rename) move its entry to the top — don't group by category. The Tags section (if present) still needs its per-tag page lists updated on add / rename / delete, but the tag order itself is not reordered by recency. Read `config/helps/wiki.md` for full details.",
+    availablePlugins: [
+      TOOL_NAMES.manageCalendar,
+      TOOL_NAMES.presentDocument,
+      TOOL_NAMES.presentForm,
+      TOOL_NAMES.presentMulmoScript,
+      TOOL_NAMES.generateImage,
+      TOOL_NAMES.presentHtml,
+      TOOL_NAMES.readXPost,
+      TOOL_NAMES.searchX,
+      TOOL_NAMES.notify,
+    ],
+    queries: [
+      "Tell me about this app, MulmoClaude.",
+      "What is the wiki in this app and how do I use it?",
+      "Tell me about the sandbox feature of this app.",
+      "What is the role of the Gemini API key in this app?",
+      "How do I use the Telegram bridge to talk to MulmoClaude from my phone?",
+      "Show my wiki index",
+      "Lint my wiki",
+      "Show my todo list",
+      "Show me my calendar",
+    ],
+    isDebugRole: true,
+  },
 ];
 
 export const BUILTIN_ROLES = ROLES;
@@ -292,6 +353,10 @@ export const BUILTIN_ROLE_IDS = {
   artist: "artist",
   tutor: "tutor",
   storyteller: "storyteller",
+  settings: "settings",
+  accounting: "accounting",
+  cookingCoach: "cookingCoach",
+  debug: "debug",
 } as const;
 
 export type BuiltInRoleId = (typeof BUILTIN_ROLE_IDS)[keyof typeof BUILTIN_ROLE_IDS];

package/src/config/systemFileDescriptors.ts

@@ -35,7 +35,7 @@ type Entry = ExactEntry | PatternEntry;
 // fragile-format descriptor, not get swallowed by a generic
 // `data/wiki/*.md` pattern (which we currently don't have, but
 // the ordering keeps that future option open).
-export const SYSTEM_FILE_DESCRIPTORS: ReadonlyArray<Entry> = [
+export const SYSTEM_FILE_DESCRIPTORS: readonly Entry[] = [
   // ── config/ ──
   {
     kind: "exact",
@@ -75,13 +75,13 @@ export const SYSTEM_FILE_DESCRIPTORS: ReadonlyArray<Entry> = [
   },
   {
     kind: "exact",
-    path: "data/todos/todos.json",
-    descriptor: { id: "todosItems", schemaRef: "server/utils/files/todos-io.ts", editPolicy: "agent-managed-but-hand-editable" },
+    path: "data/plugins/%40mulmoclaude%2Ftodo-plugin/todos.json",
+    descriptor: { id: "todosItems", schemaRef: "packages/todo-plugin/src/io.ts", editPolicy: "agent-managed-but-hand-editable" },
   },
   {
     kind: "exact",
-    path: "data/todos/columns.json",
-    descriptor: { id: "todosColumns", schemaRef: "server/utils/files/todos-io.ts", editPolicy: "user-editable" },
+    path: "data/plugins/%40mulmoclaude%2Ftodo-plugin/columns.json",
+    descriptor: { id: "todosColumns", schemaRef: "packages/todo-plugin/src/io.ts", editPolicy: "user-editable" },
   },
   {
     kind: "exact",

package/src/config/toolNames.ts

@@ -6,47 +6,49 @@
 //     plugin at runtime
 //   - grep for "every place that handles this tool" returns a list
 //     of `TOOL_NAMES.x` references rather than free-form strings
-//   - adding a new plugin is a one-line change here + register in
-//     `src/tools/index.ts` — and `typeof TOOL_NAMES` keeps both in
-//     sync through the type system
 //
 // Naming is intentionally the literal string the server / MCP
-// protocol / jsonl files expect — rename-touching requires a
-// coordinated server + client update, which is exactly when having
-// a central list here helps.
+// protocol / jsonl files expect.
+//
+// **Aggregator shape**: plugins that own their identity export their
+// `toolName` from their `meta.ts` (via `BUILT_IN_PLUGIN_METAS`). This
+// file auto-merges them into `TOOL_NAMES` so adding a plugin =
+// register its META in `src/plugins/metas.ts`; this file untouched.
+// Host-only tool names (textResponse, MCP tools, plus plugins not yet
+// migrated to META) keep their literals in `HOST_TOOL_NAMES` below.
 //
 // First slice of issue #289 (item 4: tool name literals).
 
-export const TOOL_NAMES = {
+import { BUILT_IN_PLUGIN_METAS, defineHostAggregate, type BuiltInPluginMetas, type HostPluginCollision, type IntraPluginCollision } from "../plugins/metas";
+
+const HOST_TOOL_NAMES = {
   // Text / base
   textResponse: "text-response",
 
-  // Management plugins
-  manageTodoList: "manageTodoList",
-  // Calendar / Automations split (#824) — replaced the unified
-  // `manageScheduler` so the LLM and chat-tool-result UI both have
-  // a 1:1 mapping between tool name and domain.
-  manageCalendar: "manageCalendar",
-  manageAutomations: "manageAutomations",
-  manageRoles: "manageRoles",
-  manageSkills: "manageSkills",
-  manageSource: "manageSource",
-  manageWiki: "manageWiki",
+  // Management plugins (not yet migrated to META)
+  // manageTodoList migrated — see `src/plugins/todo/meta.ts`.
+  // manageCalendar migrated — see `src/plugins/scheduler/calendarMeta.ts`.
+  // manageAutomations migrated — see `src/plugins/scheduler/automationsMeta.ts`.
+  // manageSkills migrated — see `src/plugins/manageSkills/meta.ts`.
+  // manageSource migrated — see `src/plugins/manageSource/meta.ts`.
+  // manageWiki migrated — see `src/plugins/wiki/meta.ts`. Plugin is
+  // GUI-only (no MCP binding — deprecated #963), so the sync test
+  // pins "every binding → META", not the reverse.
 
   // Presentational plugins
-  presentMulmoScript: "presentMulmoScript",
-  presentDocument: "presentDocument",
-  presentSpreadsheet: "presentSpreadsheet",
-  presentHtml: "presentHtml",
-  presentChart: "presentChart",
-  presentForm: "presentForm",
+  // presentMulmoScript migrated — see `src/plugins/presentMulmoScript/meta.ts`.
+  // presentDocument migrated — see `src/plugins/markdown/meta.ts`.
+  // presentSpreadsheet migrated — see `src/plugins/spreadsheet/meta.ts`.
+  // presentHtml migrated — see `src/plugins/presentHtml/meta.ts`.
+  // presentChart migrated to META — see `src/plugins/chart/meta.ts`.
+  // presentForm migrated — see `src/plugins/presentForm/meta.ts`.
   present3D: "present3D",
 
   // Creation / generation
   createMindMap: "createMindMap",
-  generateImage: "generateImage",
-  editImage: "editImage",
-  openCanvas: "openCanvas",
+  // generateImage migrated — see `src/plugins/generateImage/meta.ts`.
+  // editImages migrated — see `src/plugins/editImages/meta.ts`.
+  // openCanvas migrated — see `src/plugins/canvas/meta.ts`.
 
   // Interactive / media
   putQuestions: "putQuestions",
@@ -58,11 +60,31 @@ export const TOOL_NAMES = {
   readXPost: "readXPost",
   searchX: "searchX",
   notify: "notify",
-
-  // Built-in (handled specially by the MCP stdio bridge).
-  switchRole: "switchRole",
 } as const;
 
+// Plugin-owned tool names auto-merged from each plugin's META.
+// The mapped type below preserves each plugin's literal toolName
+// (e.g. `"manageAccounting"`) so `TOOL_NAMES.manageAccounting` is
+// typed as the literal, not just `string`.
+type PluginToolNamesMap<T extends BuiltInPluginMetas> = {
+  readonly [K in T[number]["toolName"]]: K;
+};
+
+// First-write-wins host+plugin aggregate (see `defineHostAggregate`).
+// Plugin keys colliding with a host literal are dropped (host wins —
+// silent override would route the LLM's calls to the wrong handler).
+// Diagnostics flow through `TOOL_NAMES_*_COLLISIONS` for boot warnings.
+const TOOL_NAMES_AGGREGATE = defineHostAggregate<string>(BUILT_IN_PLUGIN_METAS, {
+  label: "TOOL_NAMES",
+  hostRecord: HOST_TOOL_NAMES,
+  extract: (meta) => ({ [meta.toolName]: meta.toolName }),
+  dimension: "toolName",
+});
+export const TOOL_NAMES_HOST_COLLISIONS: readonly HostPluginCollision[] = TOOL_NAMES_AGGREGATE.hostCollisions;
+export const TOOL_NAMES_INTRA_COLLISIONS: readonly IntraPluginCollision[] = TOOL_NAMES_AGGREGATE.intraCollisions;
+
+export const TOOL_NAMES = TOOL_NAMES_AGGREGATE.merged as unknown as typeof HOST_TOOL_NAMES & PluginToolNamesMap<BuiltInPluginMetas>;
+
 export type ToolName = (typeof TOOL_NAMES)[keyof typeof TOOL_NAMES];
 
 /** Runtime predicate — useful when string input (URL param, JSON