mulmoclaude 0.1.0

package/src/composables/useViewLayout.ts

@@ -0,0 +1,55 @@
+// View-layout state: tracks whether the app is in a "stack" layout
+// (full-width canvas) or "single" (sidebar + canvas), remembers the
+// last chat-oriented view mode, and derives displayedCurrentSessionId
+// (blank in plugin views so no tab appears "current").
+
+import { computed, ref, watch, type ComputedRef, type Ref } from "vue";
+import { CANVAS_VIEW, type CanvasViewMode } from "../utils/canvas/viewMode";
+
+const CHAT_VIEWS = [CANVAS_VIEW.single, CANVAS_VIEW.stack] as const;
+type ChatViewMode = (typeof CHAT_VIEWS)[number];
+
+function isChatView(m: string): m is ChatViewMode {
+  return (CHAT_VIEWS as readonly string[]).includes(m);
+}
+
+export function useViewLayout(opts: {
+  canvasViewMode: Ref<CanvasViewMode> | ComputedRef<CanvasViewMode>;
+  setCanvasViewMode: (mode: CanvasViewMode) => void;
+  currentSessionId: Ref<string>;
+  activePane: Ref<"sidebar" | "main">;
+}) {
+  const { canvasViewMode, setCanvasViewMode, currentSessionId, activePane } = opts;
+
+  const isStackLayout = computed(() => canvasViewMode.value !== CANVAS_VIEW.single);
+
+  const lastChatViewMode = ref<ChatViewMode>(isChatView(canvasViewMode.value) ? canvasViewMode.value : CANVAS_VIEW.stack);
+
+  watch(canvasViewMode, (mode) => {
+    if (isChatView(mode)) lastChatViewMode.value = mode;
+  });
+
+  function restoreChatViewForSession(): void {
+    if (!isChatView(canvasViewMode.value)) {
+      setCanvasViewMode(lastChatViewMode.value);
+    }
+  }
+
+  const displayedCurrentSessionId = computed(() => (isChatView(canvasViewMode.value) ? currentSessionId.value : ""));
+
+  // Keep arrow-key navigation tied to the canvas when the sidebar
+  // list doesn't exist (Stack layout has no ToolResultsPanel).
+  watch(
+    isStackLayout,
+    (stack) => {
+      activePane.value = stack ? "main" : "sidebar";
+    },
+    { immediate: true },
+  );
+
+  return {
+    isStackLayout,
+    restoreChatViewForSession,
+    displayedCurrentSessionId,
+  };
+}

package/src/config/apiRoutes.ts

@@ -0,0 +1,173 @@
+// Single source of truth for every HTTP endpoint the server exposes
+// under `/api/*`. Issue #289 (part 1) — consolidate the 77+ route
+// registrations and ~57 frontend `fetch("/api/...")` call sites so
+// that typos fail typecheck instead of producing runtime 404s.
+//
+// **Shape**: nested `as const` object grouped by owning route file /
+// resource family. Every value is the literal, full path including
+// the `/api` prefix. Routers in `server/routes/*.ts` register them
+// verbatim — the `app.use("/api", ...)` mount prefix was removed so
+// the constants are the unambiguous source.
+//
+// **Express params**: patterns like `:id` / `:filename` are kept as
+// Express-compatible strings. Client-side URL builders (e.g. a
+// `todoItem(id)` helper) are deliberately NOT added here until the
+// frontend migration lands — see plans/refactor-api-routes-constants.md.
+//
+// **Adding a new endpoint**: add it here first, then reference the
+// constant from the router file. Keep the nesting shallow and the
+// key names matched to the last URL segment where possible.
+
+import { CHAT_SERVICE_ROUTES } from "@mulmobridge/protocol";
+
+export const API_ROUTES = {
+  health: "/api/health",
+  sandbox: "/api/sandbox",
+
+  agent: {
+    run: "/api/agent",
+    cancel: "/api/agent/cancel",
+    internal: {
+      toolResult: "/api/internal/tool-result",
+      switchRole: "/api/internal/switch-role",
+    },
+  },
+
+  chart: {
+    present: "/api/present-chart",
+  },
+
+  chatIndex: {
+    rebuild: "/api/chat-index/rebuild",
+  },
+
+  // Single source of truth: @mulmobridge/protocol. See plans/messaging_transports.md.
+  chatService: CHAT_SERVICE_ROUTES,
+
+  config: {
+    base: "/api/config",
+    settings: "/api/config/settings",
+    mcp: "/api/config/mcp",
+    workspaceDirs: "/api/config/workspace-dirs",
+    referenceDirs: "/api/config/reference-dirs",
+    schedulerOverrides: "/api/config/scheduler-overrides",
+  },
+
+  files: {
+    tree: "/api/files/tree",
+    dir: "/api/files/dir",
+    content: "/api/files/content",
+    raw: "/api/files/raw",
+    refRoots: "/api/files/ref-roots",
+  },
+
+  html: {
+    generate: "/api/generate-html",
+    edit: "/api/edit-html",
+    present: "/api/present-html",
+  },
+
+  image: {
+    generate: "/api/generate-image",
+    edit: "/api/edit-image",
+    upload: "/api/images",
+    update: "/api/images/:filename",
+  },
+
+  mcpTools: {
+    list: "/api/mcp-tools",
+    invoke: "/api/mcp-tools/:tool",
+  },
+
+  notifications: {
+    // PoC endpoint for scheduled push fan-out (Web pub-sub + bridge).
+    // Scaffolding for #144 / #142 — see plans/feat-notification-push-scaffold.md.
+    test: "/api/notifications/test",
+  },
+
+  mulmoScript: {
+    save: "/api/mulmo-script",
+    updateBeat: "/api/mulmo-script/update-beat",
+    updateScript: "/api/mulmo-script/update-script",
+    beatImage: "/api/mulmo-script/beat-image",
+    beatAudio: "/api/mulmo-script/beat-audio",
+    generateBeatAudio: "/api/mulmo-script/generate-beat-audio",
+    renderBeat: "/api/mulmo-script/render-beat",
+    uploadBeatImage: "/api/mulmo-script/upload-beat-image",
+    characterImage: "/api/mulmo-script/character-image",
+    renderCharacter: "/api/mulmo-script/render-character",
+    uploadCharacterImage: "/api/mulmo-script/upload-character-image",
+    movieStatus: "/api/mulmo-script/movie-status",
+    generateMovie: "/api/mulmo-script/generate-movie",
+    downloadMovie: "/api/mulmo-script/download-movie",
+  },
+
+  pdf: {
+    markdown: "/api/pdf/markdown",
+  },
+
+  // Plugin-owned endpoints that don't follow a single naming pattern.
+  // Names match the plugin tool name or the short verb the plugin uses.
+  plugins: {
+    presentDocument: "/api/present-document",
+    updateMarkdown: "/api/markdowns/:filename",
+    presentSpreadsheet: "/api/present-spreadsheet",
+    updateSpreadsheet: "/api/spreadsheets/:filename",
+    mindmap: "/api/mindmap",
+    quiz: "/api/quiz",
+    form: "/api/form",
+    canvas: "/api/canvas",
+    present3d: "/api/present3d",
+  },
+
+  roles: {
+    list: "/api/roles",
+    manage: "/api/roles/manage",
+  },
+
+  scheduler: {
+    base: "/api/scheduler",
+    tasks: "/api/scheduler/tasks",
+    task: "/api/scheduler/tasks/:id",
+    taskRun: "/api/scheduler/tasks/:id/run",
+    logs: "/api/scheduler/logs",
+  },
+
+  sessions: {
+    list: "/api/sessions",
+    // GET /api/sessions/:id + POST /api/sessions/:id/mark-read
+    detail: "/api/sessions/:id",
+    markRead: "/api/sessions/:id/mark-read",
+  },
+
+  skills: {
+    list: "/api/skills",
+    detail: "/api/skills/:name",
+    create: "/api/skills",
+    update: "/api/skills/:name",
+    remove: "/api/skills/:name",
+  },
+
+  sources: {
+    list: "/api/sources",
+    create: "/api/sources",
+    remove: "/api/sources/:slug",
+    rebuild: "/api/sources/rebuild",
+    manage: "/api/sources/manage",
+  },
+
+  todos: {
+    list: "/api/todos",
+    dispatch: "/api/todos",
+    items: "/api/todos/items",
+    item: "/api/todos/items/:id",
+    itemMove: "/api/todos/items/:id/move",
+    columns: "/api/todos/columns",
+    column: "/api/todos/columns/:id",
+    columnsOrder: "/api/todos/columns/order",
+  },
+
+  wiki: {
+    base: "/api/wiki",
+  },
+} as const;

package/src/config/pubsubChannels.ts

@@ -0,0 +1,45 @@
+// Single source of truth for every WebSocket pub/sub channel name
+// the app publishes to or subscribes to. Keeping these in one file
+// means:
+//
+//   - a rename is one edit instead of a grep-and-edit across
+//     server + client
+//   - typo-wise, publisher and subscriber can't drift (both import
+//     the same const / factory)
+//   - a new channel gets declared here first, then wired — the
+//     declaration serves as a lightweight registry / audit list
+//
+// First slice of issue #289 (item 6: pub-sub channels).
+
+/**
+ * Channel for the per-session event stream. One per chat session.
+ * Publishers: `server/session-store/index.ts` (tool results, status,
+ * text chunks, switch-role, session_finished, …).
+ * Subscribers: `src/App.vue` (one subscription per actively-viewed
+ * session).
+ */
+export function sessionChannel(chatSessionId: string): string {
+  return `session.${chatSessionId}`;
+}
+
+/** Static pub/sub channel names. Factories for parameterised channels
+ *  (e.g. `sessionChannel(id)`) live alongside as named helpers. */
+export const PUBSUB_CHANNELS = {
+  /** Sidebar "a session updated, please refetch" notification.
+   *  Publisher: `server/session-store/index.ts#notifySessionsChanged`.
+   *  Subscriber: `src/App.vue`. */
+  sessions: "sessions",
+  /** Server-side debug heartbeat — wired through the task-manager
+   *  demo counter. Useful for sanity-checking that the WS pipe is
+   *  alive end-to-end. */
+  debugBeat: "debug.beat",
+  /** Broadcast push notifications to every open Web tab (scaffold for
+   *  the in-app notification center #144). The test endpoint
+   *  `POST /api/notifications/test` publishes here; the production
+   *  triggers (scheduler / todo reminders / journal) will follow
+   *  the same channel. Subscriber list starts empty — the UI lands
+   *  in a separate PR. Payload: `{ message: string, firedAt: ISO8601 }`. */
+  notifications: "notifications",
+} as const;
+
+export type StaticPubSubChannel = (typeof PUBSUB_CHANNELS)[keyof typeof PUBSUB_CHANNELS];

package/src/config/roles.ts

@@ -0,0 +1,335 @@
+import { z } from "zod";
+import { ALL_TOOL_NAMES, 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.
+const toolNameEnum = z.enum(ALL_TOOL_NAMES as readonly [ToolName, ...ToolName[]]);
+
+export const RoleSchema = z.object({
+  id: z.string(),
+  name: z.string(),
+  icon: z.string(),
+  prompt: z.string(),
+  availablePlugins: z.array(toolNameEnum),
+  queries: z.array(z.string()).optional(),
+});
+
+export type Role = z.infer<typeof RoleSchema>;
+
+export const ROLES: Role[] = [
+  {
+    id: "general",
+    name: "General",
+    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" +
+      "## 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" +
+      "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. Read `config/helps/wiki.md` for full details.",
+    availablePlugins: [
+      "manageTodoList",
+      "manageScheduler",
+      "manageWiki",
+      "manageSkills",
+      "manageSource",
+      "presentDocument",
+      "createMindMap",
+      "presentHtml",
+      "presentChart",
+      "readXPost",
+      "searchX",
+      "switchRole",
+    ],
+    queries: [
+      "Tell me about this app, MulmoClaude.",
+      "What is wiki in this app and how to use it?",
+      "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 the scheduler",
+    ],
+  },
+  {
+    id: "office",
+    name: "Office",
+    icon: "business_center",
+    prompt:
+      "You are a professional office assistant. Create and edit documents, spreadsheets, and presentations. Read existing files in the workspace for context.\n\n" +
+      "For multi-slide presentations, use presentMulmoScript. Follow the template and rules in config/helps/business.md exactly.\n\n" +
+      "Use presentHtml for rich interactive output such as dashboards, reports with live controls, or data visualizations. Recommended libraries (load via CDN):\n" +
+      "- **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",
+      "manageSkills",
+      "manageSource",
+      "switchRole",
+    ],
+    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.",
+      "Write a one-page business report on the pros and cons of remote work.",
+      "Create a 5-slide presentation on the current state of AI in business.",
+      "Fetch AAPL's revenue and net profit for the last several quarters and visualize the trends using D3.js.",
+      "Fetch NVDA's latest financial data and present it as a modern financial infographic with a left-to-right Sankey diagram using D3.js.",
+      "Perform relevant search on X about OpenAI and Anthropic, pick top ten interesting topics from them and show the list to me. Then, create a presentation about each article, one by one.",
+    ],
+  },
+  {
+    id: "guide",
+    name: "Guide & Planner",
+    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" +
+      "## 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"],
+    queries: [
+      "Give me the recipe for omelette",
+      "I want to plan a trip to Paris",
+      "Create a 4-week beginner running plan",
+      "Help me plan a birthday dinner party for 10 people",
+      "Make a study guide for learning JavaScript",
+    ],
+  },
+  {
+    id: "artist",
+    name: "Artist",
+    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 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"],
+    queries: [
+      "Open canvas",
+      "Turn this drawing into Ghibli style image",
+      "Generate an image of a big fat cat",
+      "Simulate 100 fish boids using p5.js — they should flock together but avoid the mouse cursor",
+    ],
+  },
+  {
+    id: "tutor",
+    name: "Tutor",
+    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"],
+    queries: [
+      "I want to learn about Humpback whales",
+      "Teach me how the solar system works",
+      "Explain how sorting algorithms compare visually",
+      "Help me understand fractions and decimals",
+      "Teach me about the water cycle",
+    ],
+  },
+  {
+    id: "storyteller",
+    name: "Storyteller",
+    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" +
+      "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" +
+      "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"],
+    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: "roleManager",
+    name: "Role Manager",
+    icon: "manage_accounts",
+    prompt:
+      "You are a role management assistant. Help the user create, update, and delete custom roles. " +
+      "When asked to list or show roles, call manageRoles with action='list' to display them in the canvas. " +
+      "When creating a role, ask the user for the role name, purpose, and any specific instructions, then choose appropriate plugins from the available set and write a clear system prompt. " +
+      "Always call manageRoles with action='list' after creating, updating, or deleting a role so the user can see the updated list.",
+    availablePlugins: ["manageRoles", "switchRole"],
+    queries: ["Show my custom roles", "Create a new role for me"],
+  },
+  {
+    id: "sourceManager",
+    name: "Source Manager",
+    icon: "rss_feed",
+    prompt:
+      "You are an information-source curator. Help the user register, review, and rebuild their information-source registry (RSS feeds, GitHub repos, arXiv queries).\n\n" +
+      "When asked to show or list sources, call manageSource with action='list' so the canvas displays them.\n\n" +
+      "When registering a source, ask for the canonical URL (RSS feed URL, GitHub repo URL, or arXiv listing URL), infer fetcherKind from it ('rss' for feeds, 'github-releases' or 'github-issues' depending on user intent, 'arxiv' for arxiv.org), and populate fetcherParams accordingly:\n" +
+      "- rss: { rss_url: <feed URL> }\n" +
+      "- github-releases / github-issues: { github_repo: '<owner>/<name>' }\n" +
+      "- arxiv: { arxiv_query: <search query, e.g. cat:cs.CL> }\n\n" +
+      "Let the auto-classifier pick categories by default (omit the categories field) unless the user explicitly specifies some.\n\n" +
+      "When asked to rebuild / refresh / aggregate today's brief, call manageSource with action='rebuild'.\n\n" +
+      "After any register / remove / rebuild, call manageSource with action='list' to render the updated registry — except when the action's own response already includes the refreshed list (the server returns it for every action, so you usually don't need a second call).\n\n" +
+      "## Data layout\n\n" +
+      "The pipeline reads and writes these files (all under the workspace root):\n" +
+      "- `sources/<slug>.md` — source config (YAML frontmatter: title, url, fetcherKind, fetcherParams, schedule, categories, maxItemsPerFetch, addedAt, notes)\n" +
+      "- `sources/_state/<slug>.json` — runtime state (lastFetchedAt, cursor, consecutiveFailures, nextAttemptAt)\n" +
+      "- `news/daily/YYYY/MM/DD.md` — the aggregated daily brief (markdown body + trailing fenced JSON block listing items)\n" +
+      "- `news/archive/<slug>/YYYY/MM.md` — per-source monthly archive; lossless (no cross-source dedup)\n\n" +
+      'When the user asks questions like "summarize last week\'s AI news", "what\'s new on HN today", or "show me articles about <topic>", **read the relevant daily / archive files directly with the Read tool** rather than re-running the pipeline — the data is already there. Use Glob to enumerate date ranges when needed.',
+    availablePlugins: ["manageSource", "switchRole"],
+    queries: [
+      "Show my information sources",
+      "Register the Hacker News RSS feed (https://news.ycombinator.com/rss)",
+      "Register the anthropics/claude-code GitHub releases",
+      "Register an arXiv query for cs.CL new submissions",
+      "Rebuild today's brief",
+    ],
+  },
+];
+
+export const BUILTIN_ROLES = ROLES;
+
+// String-literal constants for every built-in role id. Use these
+// instead of inline `"general"` / `"sourceManager"` etc. so that
+// renaming a role id is one place to change and `BuiltInRoleId`
+// catches typos at compile time.
+//
+// Test `test/config/test_roles.ts` asserts these keys/values stay in
+// sync with `ROLES[].id` — adding a new role to ROLES without
+// updating this map fails the test.
+export const BUILTIN_ROLE_IDS = {
+  general: "general",
+  office: "office",
+  guide: "guide",
+  artist: "artist",
+  tutor: "tutor",
+  storyteller: "storyteller",
+  roleManager: "roleManager",
+  sourceManager: "sourceManager",
+} as const;
+
+export type BuiltInRoleId = (typeof BUILTIN_ROLE_IDS)[keyof typeof BUILTIN_ROLE_IDS];
+
+export const DEFAULT_ROLE_ID: BuiltInRoleId = BUILTIN_ROLE_IDS.general;
+
+export function getRole(id: string): Role {
+  return ROLES.find((r) => r.id === id) ?? ROLES[0];
+}

package/src/config/schedulerActions.ts

@@ -0,0 +1,25 @@
+// Scheduler MCP tool action constants.
+// Used by both the tool definition (frontend) and the route handler (server).
+
+export const SCHEDULER_ACTIONS = {
+  // Calendar item actions (existing)
+  show: "show",
+  add: "add",
+  delete: "delete",
+  update: "update",
+  // Scheduled task actions (Phase 3)
+  createTask: "createTask",
+  listTasks: "listTasks",
+  deleteTask: "deleteTask",
+  runTask: "runTask",
+} as const;
+
+export type SchedulerAction = (typeof SCHEDULER_ACTIONS)[keyof typeof SCHEDULER_ACTIONS];
+
+/** Task-specific actions that route to user-task subsystem. */
+export const TASK_ACTIONS: ReadonlySet<string> = new Set([
+  SCHEDULER_ACTIONS.createTask,
+  SCHEDULER_ACTIONS.listTasks,
+  SCHEDULER_ACTIONS.deleteTask,
+  SCHEDULER_ACTIONS.runTask,
+]);