feat: integrate Memento MCP for shared memory across agents

- Add MEMENTO_MCP_SSE_URL/ACCESS_KEY/REMOTE_PATH to readEnvFile
- Merge .env vars into cleanEnv for runner process inheritance
- Claude Code runner: add memento-mcp via mcp-remote in mcpServers
- Codex runner: inject memento-mcp section into config.toml
- Various improvements: CI watch, task scheduler, DB, IPC auth

runners/agent-runner/src/index.ts

@@ -531,6 +531,18 @@ async function runQuery(
             NANOCLAW_IS_MAIN: containerInput.isMain ? '1' : '0',
           },
         },
+        ...(process.env.MEMENTO_MCP_SSE_URL
+          ? {
+              'memento-mcp': {
+                command: process.env.MEMENTO_MCP_REMOTE_PATH || 'mcp-remote',
+                args: [
+                  process.env.MEMENTO_MCP_SSE_URL,
+                  '--header',
+                  `Authorization:Bearer ${process.env.MEMENTO_ACCESS_KEY || ''}`,
+                ],
+              },
+            }
+          : {}),
       },
       hooks: {
         PreCompact: [{ hooks: [createPreCompactHook(containerInput.assistantName)] }],

runners/agent-runner/src/ipc-mcp-stdio.ts

@@ -12,6 +12,7 @@ import path from 'path';
 import { CronExpressionParser } from 'cron-parser';
 import {
   buildCiWatchPrompt,
+  DEFAULT_WATCH_CI_CONTEXT_MODE,
   normalizeWatchCiIntervalSeconds,
 } from './watch-ci.js';
 
@@ -174,8 +175,8 @@ server.tool(
       .describe('How often to poll in seconds. Default 60, minimum 30.'),
     context_mode: z
       .enum(['group', 'isolated'])
-      .default('group')
-      .describe('group=runs with chat history and memory, isolated=fresh session (include all context in check_instructions)'),
+      .default(DEFAULT_WATCH_CI_CONTEXT_MODE)
+      .describe('group=runs with chat history and memory, isolated=fresh session (include all context in check_instructions). Default: isolated.'),
     target_group_jid: z
       .string()
       .optional()
@@ -211,7 +212,7 @@ server.tool(
       prompt,
       schedule_type: 'interval' as const,
       schedule_value: String(pollSeconds * 1000),
-      context_mode: args.context_mode || 'group',
+      context_mode: args.context_mode || DEFAULT_WATCH_CI_CONTEXT_MODE,
       targetJid,
       createdBy: groupFolder,
       timestamp: new Date().toISOString(),

runners/agent-runner/src/watch-ci.ts

@@ -1,6 +1,7 @@
 export const DEFAULT_WATCH_CI_INTERVAL_SECONDS = 60;
 export const MIN_WATCH_CI_INTERVAL_SECONDS = 30;
 export const MAX_WATCH_CI_INTERVAL_SECONDS = 3600;
+export const DEFAULT_WATCH_CI_CONTEXT_MODE = 'isolated';
 
 export interface BuildCiWatchPromptArgs {
   taskId: string;
@@ -49,12 +50,21 @@ Check instructions:
 ${checkInstructions}
 
 Rules:
+- Use the watch target and check instructions in this prompt as the source of truth for what to inspect.
 - On each run, check whether the target is still queued, pending, running, in progress, or otherwise non-terminal.
 - If it is still not finished, send no visible message and end this run quietly.
 - If it reached a terminal state such as success, failure, cancelled, timed out, neutral, skipped, or action required:
   1. Send exactly one concise completion message with \`send_message\`.
-  2. Include the final status and only the most important details.
-  3. Call \`cancel_task\` with task_id "${taskId}" so this watcher stops itself.
+  2. Format it as a short multiline summary when possible, not one long paragraph.
+  3. Preferred shape:
+     - First line: \`CI 완료: <target>\`
+     - Second line: \`판정: <one-line conclusion>\`
+     - Then 2-4 flat bullet points with only the most important metrics, errors, or comparisons.
+     - Optional final line: \`다음: <next action>\` if a concrete follow-up is needed.
+  4. Adapt the content to the specific CI. Do not invent fixed fields when they do not fit.
+  5. Avoid tables unless they are clearly the shortest readable format.
+  6. Keep the message compact and easy for other agents to parse.
+  7. Call \`cancel_task\` with task_id "${taskId}" so this watcher stops itself.
 - If you hit a transient problem such as a rate limit, network issue, or temporary auth failure, send no visible message and leave the task active for the next retry.
 - Prefer no normal final response. Use \`send_message\` for the completion message, and keep any non-user-facing notes inside \`<internal>\` tags if needed.
 - Do not claim continued monitoring after you cancel the task.