@imenam/mcp-organizer 1.0.1 → 1.0.3

package/dist/src/core/store.js

@@ -2,6 +2,7 @@ import { openDatabase } from "./db.js";
 import { ForbiddenError, InvariantError, NotFoundError, OrganizerError } from "./errors.js";
 import { positionBetween } from "../../shared/logic/positions.js";
 import { newId } from "./ids.js";
+import { WatcherRegistry } from "./watchers.js";
 import { MAX_TASK_DEPTH, } from "../../shared/schemas/enums.schema.js";
 import { AccessLinkSchema, AgentActionSchema, AgentTokenSchema, AgentRequestSchema, AttachmentSchema, ChangeSchema, ChecklistItemSchema, CommentSchema, EntityVersionSchema, IdeaSchema, IdeaSnapshotSchema, InvitationSchema, MembershipSchema, NotificationSchema, SessionSchema, SpaceSchema, TagSchema, TaskSchema, TaskSnapshotSchema, TestCheckpointSchema, TestResultSchema, TestReviewSchema, UserSchema, UserSettingsSchema, } from "../../shared/schemas/entities.schema.js";
 /** Valide `value` avec `schema` ; une donnée invalide est une erreur métier qui liste les champs fautifs. */
@@ -276,6 +277,9 @@ export class Store {
     db;
     activeMutation = null;
     emailListener = null;
+    pendingRequestListeners = new Set();
+    /** Présence des veilleurs de notifications, par jeton d'agent. */
+    watchers = new WatcherRegistry();
     constructor(db) {
         this.db = db;
     }
@@ -767,6 +771,15 @@ export class Store {
     setEmailListener(listener) {
         this.emailListener = listener;
     }
+    /**
+     * Abonne `listener` aux demandes qui passent en attente (créées, ou
+     * libérées par un membre) : il les reçoit après la validation de la
+     * mutation. La fonction rendue désabonne.
+     */
+    onPendingRequest(listener) {
+        this.pendingRequestListeners.add(listener);
+        return () => this.pendingRequestListeners.delete(listener);
+    }
     /**
      * Point unique d'écriture. `fn` reçoit une `Mutation` et s'exécute dans une
      * transaction exclusive ; à sa sortie, les invariants sont vérifiés sur l'état
@@ -777,6 +790,7 @@ export class Store {
         if (this.activeMutation)
             throw new Error("Store.mutate is not reentrant: use the Mutation passed to the running mutation.");
         let emails = [];
+        let pending = [];
         const run = this.db.transaction(() => {
             const tx = new Mutation(this, actor);
             this.activeMutation = tx;
@@ -784,6 +798,7 @@ export class Store {
                 const result = fn(tx);
                 tx.finish();
                 emails = tx.emailNotificationIds;
+                pending = tx.pendingRequestIds;
                 return result;
             }
             finally {
@@ -793,6 +808,13 @@ export class Store {
         const result = run.immediate();
         if (emails.length > 0 && this.emailListener)
             this.emailListener(emails);
+        if (pending.length > 0 && this.pendingRequestListeners.size > 0) {
+            for (const id of pending) {
+                const request = this.getAgentRequest(id);
+                for (const listener of [...this.pendingRequestListeners])
+                    listener(request);
+            }
+        }
         return result;
     }
 }
@@ -809,6 +831,8 @@ export class Mutation {
     touched = new Map();
     /** Notifications créées par la mutation dont le destinataire veut un e-mail. */
     emailNotificationIds = [];
+    /** Demandes passées en attente par la mutation : créées, ou libérées. */
+    pendingRequestIds = [];
     /** Demande pour laquelle agit l'agent, lue au début de la mutation. */
     request;
     /** Jeton avec lequel agit l'agent. */
@@ -1690,6 +1714,7 @@ export class Mutation {
          VALUES (?, ?, ?, ?, ?, ?, ?, ?, ?, ?)`)
             .run(request.id, request.authorId, request.targetSpaceId, request.kind, request.contextTaskId, request.contextIdeaId, request.text, request.status, request.createdAt, request.updatedAt);
         this.createdRequestIds.add(request.id);
+        this.pendingRequestIds.push(request.id);
         this.touchRequest(request);
         return request;
     }
@@ -1735,6 +1760,7 @@ export class Mutation {
             throw new InvariantError(`Request ${id} is ${current.status}: only a processing request can be released.`);
         this.db.prepare("UPDATE agent_requests SET status = 'pending', claimed_at = NULL, claimed_by_token_id = NULL, updated_at = ? WHERE id = ?").run(this.now, id);
         const released = this.store.getAgentRequest(id);
+        this.pendingRequestIds.push(id);
         this.touchRequest(released);
         return released;
     }

package/dist/src/core/watchers.d.ts

@@ -0,0 +1,30 @@
+/**
+ * Présence des veilleurs de notifications, par jeton d'agent.
+ *
+ * Un veilleur enchaîne des attentes longues sur `GET /api/agent/requests/wait`.
+ * Le registre rend sa présence observable : `enable_notifications` répond
+ * « déjà armé », la page Agent de la GUI affiche « à l'écoute ».
+ *
+ * État de connexion, donc volatile : il vit en mémoire du processus du site et
+ * disparaît avec lui.
+ */
+/**
+ * Délai de grâce entre deux attentes d'un même veilleur : le jeton reste
+ * « à l'écoute » pendant le court intervalle où aucune attente n'est ouverte.
+ */
+export declare const WATCHER_GRACE_MS: number;
+export interface WatcherStatus {
+    armed: boolean;
+    /** Début de la série d'attentes en cours, null sans veilleur. */
+    since: string | null;
+    /** Dernière activité connue d'un veilleur de ce jeton, null si aucune. */
+    lastSeen: string | null;
+}
+export declare class WatcherRegistry {
+    private readonly now;
+    private readonly presence;
+    constructor(now?: () => number);
+    /** Déclare une attente de veilleur du jeton `tokenId`. La fonction rendue la clôt ; elle doit toujours être appelée. */
+    begin(tokenId: string): () => void;
+    status(tokenId: string): WatcherStatus;
+}

package/dist/src/core/watchers.js

@@ -0,0 +1,50 @@
+/**
+ * Présence des veilleurs de notifications, par jeton d'agent.
+ *
+ * Un veilleur enchaîne des attentes longues sur `GET /api/agent/requests/wait`.
+ * Le registre rend sa présence observable : `enable_notifications` répond
+ * « déjà armé », la page Agent de la GUI affiche « à l'écoute ».
+ *
+ * État de connexion, donc volatile : il vit en mémoire du processus du site et
+ * disparaît avec lui.
+ */
+/**
+ * Délai de grâce entre deux attentes d'un même veilleur : le jeton reste
+ * « à l'écoute » pendant le court intervalle où aucune attente n'est ouverte.
+ */
+export const WATCHER_GRACE_MS = 2 * 60 * 1000;
+export class WatcherRegistry {
+    now;
+    presence = new Map();
+    constructor(now = Date.now) {
+        this.now = now;
+    }
+    /** Déclare une attente de veilleur du jeton `tokenId`. La fonction rendue la clôt ; elle doit toujours être appelée. */
+    begin(tokenId) {
+        const now = this.now();
+        const current = this.presence.get(tokenId);
+        const continuing = current !== undefined && (current.inflight > 0 || now - current.lastSeen <= WATCHER_GRACE_MS);
+        this.presence.set(tokenId, continuing ? { ...current, inflight: current.inflight + 1, lastSeen: now } : { inflight: 1, since: now, lastSeen: now });
+        let released = false;
+        return () => {
+            if (released)
+                return;
+            released = true;
+            const active = this.presence.get(tokenId);
+            if (!active)
+                return;
+            this.presence.set(tokenId, { ...active, inflight: Math.max(0, active.inflight - 1), lastSeen: this.now() });
+        };
+    }
+    status(tokenId) {
+        const entry = this.presence.get(tokenId);
+        if (!entry)
+            return { armed: false, since: null, lastSeen: null };
+        const armed = entry.inflight > 0 || this.now() - entry.lastSeen <= WATCHER_GRACE_MS;
+        if (!armed) {
+            this.presence.delete(tokenId);
+            return { armed: false, since: null, lastSeen: new Date(entry.lastSeen).toISOString() };
+        }
+        return { armed: true, since: new Date(entry.since).toISOString(), lastSeen: new Date(entry.lastSeen).toISOString() };
+    }
+}

package/dist/src/index.js

@@ -19,6 +19,10 @@ Usage :
                                     (dossier <fichier>.attachments).
   mcp-organizer --claude-setup-mcp [--force] --url=<URL du site> --token=<jeton>
                                     Écrit l'entrée du mode MCP dans ./.mcp.json.
+  mcp-organizer --watch <id du jeton>
+                                    Veilleur de notifications : une ligne par demande passée en attente.
+                                    Lancé par l'outil Monitor de l'agent, avec la commande que rend
+                                    l'outil enable_notifications.
   mcp-organizer --version           Affiche la version.
   mcp-organizer --help              Affiche cette aide.
 
@@ -50,6 +54,12 @@ async function main() {
         const { runSetupMcp } = await import("./cli/setup-mcp.js");
         process.exit(runSetupMcp(argv, process.cwd()));
     }
+    // Le veilleur lit l'URL du site et le jeton dans le relais déposé par enable_notifications.
+    const watchIndex = argv.indexOf("--watch");
+    if (watchIndex !== -1) {
+        const { runWatchMode } = await import("./cli/watch.js");
+        process.exit(await runWatchMode(argv[watchIndex + 1]));
+    }
     const rootDir = findProjectRoot(path.dirname(fileURLToPath(import.meta.url)));
     const siteCommand = SITE_COMMANDS.some((flag) => argv.includes(flag));
     // Les commandes du site ouvrent la base : better-sqlite3 doit avoir son module natif.

package/dist/src/mcp/client.d.ts

@@ -1,9 +1,11 @@
+import type { z } from "zod";
+import { type AgentEnvelope, type WaitRequestsData } from "../../shared/schemas/agent-tools.schema.js";
 import type { ToolHttpRequest } from "./tools.js";
 /**
  * Client HTTP de l'API agent du site : seul point de sortie réseau du mode
  * MCP. Chaque appel porte le jeton dans `Authorization: Bearer`.
  */
-/** Délai maximal d'un appel au site. */
+/** Délai maximal d'un appel au site, hors attente longue. */
 export declare const REQUEST_TIMEOUT_MS = 30000;
 /** Échec d'un appel : refus du site (avec son message) ou site injoignable. */
 export declare class SiteError extends Error {
@@ -20,4 +22,17 @@ export declare class OrganizerSiteClient {
     constructor(connection: SiteConnection);
     /** Exécute la requête d'un outil et renvoie le texte rédigé pour l'agent. */
     call(request: ToolHttpRequest): Promise<string>;
+    /**
+     * Attente longue des demandes qui passent en attente (`GET requests/wait`) ;
+     * le délai de l'appel couvre la durée de l'attente.
+     */
+    waitForRequests(query: {
+        timeout_seconds: number;
+        since?: string;
+        watcher?: boolean;
+    }): Promise<WaitRequestsData>;
+    /** Données structurées d'une réponse, validées par `schema`. */
+    parseData<S extends z.ZodType>(schema: S, data: unknown): z.infer<S>;
+    /** Exécute une requête de l'API agent et renvoie sa réponse : texte rédigé pour l'agent et données structurées. */
+    envelope(request: ToolHttpRequest, timeoutMs?: number): Promise<AgentEnvelope>;
 }

package/dist/src/mcp/client.js

@@ -1,9 +1,9 @@
-import { AgentEnvelopeSchema, AgentErrorSchema } from "../../shared/schemas/agent-tools.schema.js";
+import { AgentEnvelopeSchema, AgentErrorSchema, WaitRequestsDataSchema } from "../../shared/schemas/agent-tools.schema.js";
 /**
  * Client HTTP de l'API agent du site : seul point de sortie réseau du mode
  * MCP. Chaque appel porte le jeton dans `Authorization: Bearer`.
  */
-/** Délai maximal d'un appel au site. */
+/** Délai maximal d'un appel au site, hors attente longue. */
 export const REQUEST_TIMEOUT_MS = 30_000;
 /** Échec d'un appel : refus du site (avec son message) ou site injoignable. */
 export class SiteError extends Error {
@@ -33,6 +33,31 @@ export class OrganizerSiteClient {
     }
     /** Exécute la requête d'un outil et renvoie le texte rédigé pour l'agent. */
     async call(request) {
+        return (await this.envelope(request)).text;
+    }
+    /**
+     * Attente longue des demandes qui passent en attente (`GET requests/wait`) ;
+     * le délai de l'appel couvre la durée de l'attente.
+     */
+    async waitForRequests(query) {
+        const params = { timeout_seconds: String(query.timeout_seconds) };
+        if (query.since !== undefined)
+            params.since = query.since;
+        if (query.watcher)
+            params.watcher = "true";
+        const envelope = await this.envelope({ method: "GET", path: "requests/wait", query: params, body: undefined }, query.timeout_seconds * 1000 + REQUEST_TIMEOUT_MS);
+        return this.parseData(WaitRequestsDataSchema, envelope.data);
+    }
+    /** Données structurées d'une réponse, validées par `schema`. */
+    parseData(schema, data) {
+        const parsed = schema.safeParse(data);
+        if (!parsed.success) {
+            throw new SiteError(`The organizer site at ${this.connection.url} sent an unexpected answer. Check that the site runs the same version of @imenam/mcp-organizer.`);
+        }
+        return parsed.data;
+    }
+    /** Exécute une requête de l'API agent et renvoie sa réponse : texte rédigé pour l'agent et données structurées. */
+    async envelope(request, timeoutMs = REQUEST_TIMEOUT_MS) {
         const url = new URL(`${this.connection.url}/api/agent/${request.path}`);
         for (const [name, value] of Object.entries(request.query))
             url.searchParams.set(name, value);
@@ -48,7 +73,7 @@ export class OrganizerSiteClient {
                 body: request.body === undefined ? undefined : JSON.stringify(request.body),
                 // Une redirection n'est jamais suivie : le jeton ne part que vers ORGANIZER_URL.
                 redirect: "manual",
-                signal: AbortSignal.timeout(REQUEST_TIMEOUT_MS),
+                signal: AbortSignal.timeout(timeoutMs),
             });
         }
         catch (error) {
@@ -76,6 +101,6 @@ export class OrganizerSiteClient {
         if (!envelope.success) {
             throw new SiteError(`The organizer site at ${this.connection.url} sent an unexpected answer. Check ORGANIZER_URL and that the site runs the same version of @imenam/mcp-organizer.`);
         }
-        return envelope.data.text;
+        return envelope.data;
     }
 }

package/dist/src/mcp/notifications.d.ts

@@ -0,0 +1,30 @@
+import { type AgentRequestSummary } from "../../shared/schemas/agent-tools.schema.js";
+import type { OrganizerSiteClient, SiteConnection } from "./client.js";
+import { type ToolDefinition } from "./tools.js";
+/**
+ * Outils de notification, exécutés par le mode MCP lui-même.
+ *
+ * `enable_notifications` fonctionne de deux façons. En local, il dépose le
+ * relais du veilleur et rend l'appel `Monitor` qui lance `--watch`. Derrière
+ * le relais de mcp-http-gateway, qui remplit l'argument réservé
+ * `_gateway_watch`, il rend une spécification de veille
+ * (`_meta["gateway/watch"]`) : le relais lance alors son propre veilleur, qui
+ * appelle `wait_for_requests` en boucle à travers la gateway.
+ */
+/** Clés de la convention de veille de mcp-http-gateway (voir son gateway-watch.js). */
+export declare const WATCH_ARG = "_gateway_watch";
+/** Résultat d'un outil de notification : texte pour l'agent et métadonnées pour le relais. */
+export interface NotificationToolResult {
+    text: string;
+    meta?: Record<string, unknown>;
+}
+/** Ligne d'une demande : une seule ligne, lisible telle quelle dans la notification. */
+export declare function formatRequestEvent(request: AgentRequestSummary): string;
+/** Durée maximale d'un `Monitor` côté hôte. */
+export declare const MONITOR_TIMEOUT_MS = 1800000;
+export declare const ENABLE_NOTIFICATIONS_TOOL: ToolDefinition;
+export declare const WAIT_FOR_REQUESTS_TOOL: ToolDefinition;
+/** Commande du veilleur du jeton `tokenId`. */
+export declare function watchCommand(tokenId: string): string;
+export declare function enableNotifications(client: OrganizerSiteClient, connection: SiteConnection, args: Record<string, unknown>): Promise<NotificationToolResult>;
+export declare function waitForRequests(client: OrganizerSiteClient, args: Record<string, unknown>): Promise<NotificationToolResult>;

package/dist/src/mcp/notifications.js

@@ -0,0 +1,140 @@
+import { MAX_WAIT_SECONDS, NotificationsDataSchema } from "../../shared/schemas/agent-tools.schema.js";
+import { ToolArgumentError } from "./tools.js";
+import { writeHandoff } from "./watch-handoff.js";
+/**
+ * Outils de notification, exécutés par le mode MCP lui-même.
+ *
+ * `enable_notifications` fonctionne de deux façons. En local, il dépose le
+ * relais du veilleur et rend l'appel `Monitor` qui lance `--watch`. Derrière
+ * le relais de mcp-http-gateway, qui remplit l'argument réservé
+ * `_gateway_watch`, il rend une spécification de veille
+ * (`_meta["gateway/watch"]`) : le relais lance alors son propre veilleur, qui
+ * appelle `wait_for_requests` en boucle à travers la gateway.
+ */
+/** Clés de la convention de veille de mcp-http-gateway (voir son gateway-watch.js). */
+export const WATCH_ARG = "_gateway_watch";
+const WATCH_META = "gateway/watch";
+const EVENTS_META = "gateway/events";
+/** Longueur maximale de l'extrait du texte d'une demande dans sa ligne. */
+const EXCERPT_LENGTH = 120;
+/** Ligne d'une demande : une seule ligne, lisible telle quelle dans la notification. */
+export function formatRequestEvent(request) {
+    const text = request.text.replace(/\s+/g, " ").trim();
+    const excerpt = text.length > EXCERPT_LENGTH ? `${text.slice(0, EXCERPT_LENGTH - 1)}…` : text;
+    const context = request.contextTask ? ` · ${request.contextTask.key}` : "";
+    return `[organizer] ${request.kind} · ${request.author.name} — "${excerpt}"${context} (${request.id})`;
+}
+/** Durée maximale d'un `Monitor` côté hôte. */
+export const MONITOR_TIMEOUT_MS = 1_800_000;
+const PACKAGE_NAME = "@imenam/mcp-organizer";
+export const ENABLE_NOTIFICATIONS_TOOL = {
+    name: "enable_notifications",
+    description: "Get notified in real time of the requests the members of your space send to the AI, without polling the queue. Returns immediately: it blocks nothing and starts nothing on its own. It hands you the exact Monitor call to make right after — arming that watcher is what actually delivers notifications, and until you do it no request will reach you. Call this once at the start of a session; then keep working, each new pending request interrupts you on its own. The host stops the watcher after 30 minutes at most: re-arm it with the same Monitor call each time it expires.",
+    inputSchema: {
+        type: "object",
+        properties: {
+            [WATCH_ARG]: {
+                type: "object",
+                description: "Filled in by the mcp-http-gateway relay, never by the agent: the relay will run the watcher and needs a watch specification instead of a local command.",
+            },
+        },
+        additionalProperties: false,
+    },
+};
+export const WAIT_FOR_REQUESTS_TOOL = {
+    name: "wait_for_requests",
+    description: "Block until at least one request of your space becomes pending (created, or released by a member), or until the timeout. Returns the new pending requests (none on timeout) and a cursor: pass it to the next call to get exactly what became pending since. It is the waiting tool of the notification watcher; to stay reachable, prefer enable_notifications.",
+    inputSchema: {
+        type: "object",
+        properties: {
+            cursor: {
+                type: "string",
+                description: "Cursor returned by the previous call. Without it, only requests that become pending after the call starts are returned.",
+            },
+            timeout_seconds: { type: "integer", minimum: 1, maximum: MAX_WAIT_SECONDS, description: `Maximum wait, in seconds (1-${MAX_WAIT_SECONDS}, defaults to 30).` },
+            watcher: {
+                type: "boolean",
+                description: "Set by the notification watcher: the wait counts as the presence of this token's watcher, shown as listening in the web app.",
+            },
+        },
+        additionalProperties: false,
+    },
+};
+/** Commande du veilleur du jeton `tokenId`. */
+export function watchCommand(tokenId) {
+    return `npx -y ${PACKAGE_NAME} --watch ${tokenId}`;
+}
+export async function enableNotifications(client, connection, args) {
+    for (const name of Object.keys(args)) {
+        if (name !== WATCH_ARG)
+            throw new ToolArgumentError(`Invalid arguments — ${name}: enable_notifications takes no argument.`);
+    }
+    const envelope = await client.envelope({ method: "GET", path: "notifications", query: {}, body: undefined });
+    const { token, space, pendingCount, watcher, cursor } = client.parseData(NotificationsDataSchema, envelope.data);
+    if (args[WATCH_ARG] !== undefined) {
+        return {
+            text: `Watch specification for the mcp-http-gateway relay: requests of space "${space.name}" for token "${token.name}".`,
+            meta: {
+                [WATCH_META]: {
+                    tool: WAIT_FOR_REQUESTS_TOOL.name,
+                    arguments: { watcher: true },
+                    cursor,
+                    description: "New requests for the AI in the organizer",
+                },
+            },
+        };
+    }
+    writeHandoff({ tokenId: token.id, url: connection.url, token: connection.token });
+    const command = watchCommand(token.id);
+    if (watcher.armed) {
+        const text = [
+            `Notifications are already live for token "${token.name}" on space "${space.name}" (watcher armed since ${watcher.since}).`,
+            "Nothing to do: keep working, new requests will interrupt you on their own.",
+            "Do not arm a second watcher — you would get every request twice.",
+            "Only exception: if the host just told you your watcher expired or stopped, re-arm it",
+            `with the same Monitor call (command \`${command}\`, timeout_ms ${MONITOR_TIMEOUT_MS}).`,
+        ].join("\n");
+        return { text };
+    }
+    const lines = [
+        `Notifications enabled for token "${token.name}" on space "${space.name}".`,
+        "",
+        "Last step — call the Monitor tool now, with exactly these arguments:",
+        `  command:     ${command}`,
+        "  description: New requests for the AI in the organizer",
+        `  timeout_ms:  ${MONITOR_TIMEOUT_MS}`,
+        "",
+        "Until that watcher is armed, nothing will reach you: no request will be announced.",
+        "Once it is, keep working normally — each request that becomes pending shows up on its own,",
+        "even while you are idle. One line per request; process it with claim_request.",
+        "",
+        "The host stops every monitor after 30 minutes at most. Each time it tells you this",
+        "watcher expired, call Monitor again right away with the same arguments — do not call",
+        "enable_notifications again. Skip that and notifications stop for good.",
+    ];
+    if (pendingCount > 0) {
+        lines.push("", `${pendingCount} request(s) are already pending. Only requests that become pending AFTER the`, "watcher starts are announced — process the backlog with list_requests.");
+    }
+    return { text: lines.join("\n") };
+}
+export async function waitForRequests(client, args) {
+    for (const name of Object.keys(args)) {
+        if (!(name in WAIT_FOR_REQUESTS_TOOL.inputSchema.properties))
+            throw new ToolArgumentError(`Invalid arguments — ${name}: unknown argument. Check the tool's input schema.`);
+    }
+    const { cursor, timeout_seconds: timeout, watcher } = args;
+    if (cursor !== undefined && typeof cursor !== "string")
+        throw new ToolArgumentError("Invalid arguments — cursor: expected the string returned by the previous call.");
+    if (timeout !== undefined && (typeof timeout !== "number" || !Number.isInteger(timeout) || timeout < 1 || timeout > MAX_WAIT_SECONDS)) {
+        throw new ToolArgumentError(`Invalid arguments — timeout_seconds: expected an integer from 1 to ${MAX_WAIT_SECONDS}.`);
+    }
+    if (watcher !== undefined && typeof watcher !== "boolean")
+        throw new ToolArgumentError("Invalid arguments — watcher: expected a boolean.");
+    const seconds = timeout ?? 30;
+    const result = await client.waitForRequests({ timeout_seconds: seconds, since: cursor, watcher: watcher === true });
+    const lines = result.requests.map(formatRequestEvent);
+    const text = lines.length === 0
+        ? `No new pending request in "${result.space.name}" after ${seconds}s. Cursor: ${result.cursor}`
+        : `${lines.length} new pending request(s) in "${result.space.name}":\n${lines.join("\n")}\nCursor: ${result.cursor}\n\nNext: call claim_request with the id of the oldest request.`;
+    return { text, meta: { [EVENTS_META]: { cursor: result.cursor, lines } } };
+}

package/dist/src/mcp/start.d.ts

@@ -1,6 +1,6 @@
 import { type SiteConnection } from "./client.js";
 /** Présentation du serveur transmise au client MCP : concepts et déroulé. */
-export declare const INSTRUCTIONS = "mcp-organizer connects you to an organizer site: a multi-user task manager where people organize tasks in a web app and queue requests for the AI. You, the connected agent, process those requests when the user asks you to. The site never calls an LLM: you are the intelligence.\n\nYour token covers exactly one space, with the rights of the user who created the token. Every tool works on that space.\n\nConcepts:\n- A **space** holds tasks and an idea box. A user's **personal space** is private; a **shared space** has one owner and members.\n- A **task** has a title, a markdown description, a status (todo, doing, review, done), a priority (low, medium, high, critical), assignees and tags. Tasks nest on two levels: task > sub-task > sub-sub-task. A task is either standard (with a checklist) or a test (with checkpoints that each tester marks ok, ko, blocked or untested).\n- A **request** is something a member of your space asked the AI: an idea, a remark, a test review, a message or an idea promotion. It is pending, then processing once you claim it (only your token can then act for it), then done (with your reply) or failed (with the reason).\n- A **batch** is the set of actions you perform for one request. Every action is logged with its before and after state and with your token, and users can undo one action or the whole batch.\n- The **scope** of your work is the space of your token: you see and process the requests of all its members, and you never act outside it.\n\nWork loop, when the user asks you to process the queue:\n1. list_requests to see the pending requests of your space.\n2. claim_request on the oldest one: it becomes processing for you and you get its context (text, author, context task, task tree, members, recent ideas). get_context shows the space at any time.\n3. Read what you need with get_task and search_tasks.\n4. Act with create_task, update_task, set_assignees, set_tags, edit_checklist, add_comment, create_idea, update_idea, promote_idea \u2014 always passing the request_id. Each write is one undoable action of the batch.\n5. complete_request with a short reply in the author's language (or fail_request with the reason), then go back to step 1 until no request is pending.\nNothing arrives on its own: there is no waiting tool. When the queue is empty, tell the user.\n\nHow to handle each kind of request:\n- **idea**: classify it. If it belongs to an existing task or sub-task, attach it there (sub-task, checklist item or comment). If it is actionable and important enough, create a task (or sub-task) with a fitting priority. Otherwise, put it in the idea box with create_idea. Prefer existing tasks over duplicates.\n- **test_review**: feed the tester's findings back into the existing tasks (status, checklist, comments, priority of the affected tasks), or create a task for each problem that has none.\n- **remark** and **message**: do whatever is useful \u2014 answer, update or create tasks, comment \u2014 and say what you did in the reply.\n- **idea_promotion**: turn the context idea into a well-formed task with promote_idea.\n\nRules: write titles, descriptions and replies in the language of the users; keep the reply short and factual. Errors tell you what to do next; an error about the token (missing, revoked, expired, owner no longer a member) cannot be fixed by retrying: tell the user.";
+export declare const INSTRUCTIONS = "mcp-organizer connects you to an organizer site: a multi-user task manager where people organize tasks in a web app and queue requests for the AI. You, the connected agent, process those requests when the user asks you to. The site never calls an LLM: you are the intelligence.\n\nYour token covers exactly one space, with the rights of the user who created the token. Every tool works on that space.\n\nConcepts:\n- A **space** holds tasks and an idea box. A user's **personal space** is private; a **shared space** has one owner and members.\n- A **task** has a title, a markdown description, a status (todo, doing, review, done), a priority (low, medium, high, critical), assignees and tags. Tasks nest on two levels: task > sub-task > sub-sub-task. A task is either standard (with a checklist) or a test (with checkpoints that each tester marks ok, ko, blocked or untested).\n- A **request** is something a member of your space asked the AI: an idea, a remark, a test review, a message or an idea promotion. It is pending, then processing once you claim it (only your token can then act for it), then done (with your reply) or failed (with the reason).\n- A **batch** is the set of actions you perform for one request. Every action is logged with its before and after state and with your token, and users can undo one action or the whole batch.\n- The **scope** of your work is the space of your token: you see and process the requests of all its members, and you never act outside it.\n\nWork loop, when the user asks you to process the queue:\n1. list_requests to see the pending requests of your space.\n2. claim_request on the oldest one: it becomes processing for you and you get its context (text, author, context task, task tree, members, recent ideas). get_context shows the space at any time.\n3. Read what you need with get_task and search_tasks.\n4. Act with create_task, update_task, set_assignees, set_tags, edit_checklist, add_comment, create_idea, update_idea, promote_idea \u2014 always passing the request_id. Each write is one undoable action of the batch.\n5. complete_request with a short reply in the author's language (or fail_request with the reason), then go back to step 1 until no request is pending.\nWhen the queue is empty, tell the user.\n\nNotifications: call enable_notifications once at the start of the session and arm the watcher it hands you with Monitor, whatever the command (behind mcp-http-gateway, the gateway relay answers in place of this server and gives its own watcher command). Each request that becomes pending in your space then arrives on its own as one line (kind, author, excerpt, request id), even while you are idle: process it with the work loop above, starting with claim_request. The host stops that watcher after 30 minutes at most: each time it tells you the watcher expired, re-arm it at once with the same Monitor call; otherwise notifications stop for good. A line \"notifications stopped\" means the site refused the token, and a line \"[gateway-watch] \u2026 la veille \u00E9choue\" means the gateway watcher keeps failing: tell the user. wait_for_requests is the waiting tool of the watcher: you do not need to call it.\n\nHow to handle each kind of request:\n- **idea**: classify it. If it belongs to an existing task or sub-task, attach it there (sub-task, checklist item or comment). If it is actionable and important enough, create a task (or sub-task) with a fitting priority. Otherwise, put it in the idea box with create_idea. Prefer existing tasks over duplicates.\n- **test_review**: feed the tester's findings back into the existing tasks (status, checklist, comments, priority of the affected tasks), or create a task for each problem that has none.\n- **remark** and **message**: do whatever is useful \u2014 answer, update or create tasks, comment \u2014 and say what you did in the reply.\n- **idea_promotion**: turn the context idea into a well-formed task with promote_idea.\n\nRules: write titles, descriptions and replies in the language of the users; keep the reply short and factual. Errors tell you what to do next; an error about the token (missing, revoked, expired, owner no longer a member) cannot be fixed by retrying: tell the user.";
 /**
  * Connexion au site d'après `ORGANIZER_URL` et `ORGANIZER_TOKEN` ; une valeur
  * absente ou invalide, ou une URL http vers une autre machine, est une `ConfigError`.

package/dist/src/mcp/start.js

@@ -6,32 +6,36 @@ import { createLogger, setupLogging } from "../core/logger.js";
 import { ConfigError } from "../core/errors.js";
 import { OrganizerSiteClient, SiteError } from "./client.js";
 import { AGENT_TOOLS, ToolArgumentError, findAgentTool, toolHttpRequest } from "./tools.js";
+import { ENABLE_NOTIFICATIONS_TOOL, WAIT_FOR_REQUESTS_TOOL, enableNotifications, waitForRequests } from "./notifications.js";
+import { removeOwnHandoffs } from "./watch-handoff.js";
 /** Présentation du serveur transmise au client MCP : concepts et déroulé. */
-export const INSTRUCTIONS = `mcp-organizer connects you to an organizer site: a multi-user task manager where people organize tasks in a web app and queue requests for the AI. You, the connected agent, process those requests when the user asks you to. The site never calls an LLM: you are the intelligence.
-
-Your token covers exactly one space, with the rights of the user who created the token. Every tool works on that space.
-
-Concepts:
-- A **space** holds tasks and an idea box. A user's **personal space** is private; a **shared space** has one owner and members.
-- A **task** has a title, a markdown description, a status (todo, doing, review, done), a priority (low, medium, high, critical), assignees and tags. Tasks nest on two levels: task > sub-task > sub-sub-task. A task is either standard (with a checklist) or a test (with checkpoints that each tester marks ok, ko, blocked or untested).
-- A **request** is something a member of your space asked the AI: an idea, a remark, a test review, a message or an idea promotion. It is pending, then processing once you claim it (only your token can then act for it), then done (with your reply) or failed (with the reason).
-- A **batch** is the set of actions you perform for one request. Every action is logged with its before and after state and with your token, and users can undo one action or the whole batch.
-- The **scope** of your work is the space of your token: you see and process the requests of all its members, and you never act outside it.
-
-Work loop, when the user asks you to process the queue:
-1. list_requests to see the pending requests of your space.
-2. claim_request on the oldest one: it becomes processing for you and you get its context (text, author, context task, task tree, members, recent ideas). get_context shows the space at any time.
-3. Read what you need with get_task and search_tasks.
-4. Act with create_task, update_task, set_assignees, set_tags, edit_checklist, add_comment, create_idea, update_idea, promote_idea — always passing the request_id. Each write is one undoable action of the batch.
-5. complete_request with a short reply in the author's language (or fail_request with the reason), then go back to step 1 until no request is pending.
-Nothing arrives on its own: there is no waiting tool. When the queue is empty, tell the user.
-
-How to handle each kind of request:
-- **idea**: classify it. If it belongs to an existing task or sub-task, attach it there (sub-task, checklist item or comment). If it is actionable and important enough, create a task (or sub-task) with a fitting priority. Otherwise, put it in the idea box with create_idea. Prefer existing tasks over duplicates.
-- **test_review**: feed the tester's findings back into the existing tasks (status, checklist, comments, priority of the affected tasks), or create a task for each problem that has none.
-- **remark** and **message**: do whatever is useful — answer, update or create tasks, comment — and say what you did in the reply.
-- **idea_promotion**: turn the context idea into a well-formed task with promote_idea.
-
+export const INSTRUCTIONS = `mcp-organizer connects you to an organizer site: a multi-user task manager where people organize tasks in a web app and queue requests for the AI. You, the connected agent, process those requests when the user asks you to. The site never calls an LLM: you are the intelligence.
+
+Your token covers exactly one space, with the rights of the user who created the token. Every tool works on that space.
+
+Concepts:
+- A **space** holds tasks and an idea box. A user's **personal space** is private; a **shared space** has one owner and members.
+- A **task** has a title, a markdown description, a status (todo, doing, review, done), a priority (low, medium, high, critical), assignees and tags. Tasks nest on two levels: task > sub-task > sub-sub-task. A task is either standard (with a checklist) or a test (with checkpoints that each tester marks ok, ko, blocked or untested).
+- A **request** is something a member of your space asked the AI: an idea, a remark, a test review, a message or an idea promotion. It is pending, then processing once you claim it (only your token can then act for it), then done (with your reply) or failed (with the reason).
+- A **batch** is the set of actions you perform for one request. Every action is logged with its before and after state and with your token, and users can undo one action or the whole batch.
+- The **scope** of your work is the space of your token: you see and process the requests of all its members, and you never act outside it.
+
+Work loop, when the user asks you to process the queue:
+1. list_requests to see the pending requests of your space.
+2. claim_request on the oldest one: it becomes processing for you and you get its context (text, author, context task, task tree, members, recent ideas). get_context shows the space at any time.
+3. Read what you need with get_task and search_tasks.
+4. Act with create_task, update_task, set_assignees, set_tags, edit_checklist, add_comment, create_idea, update_idea, promote_idea — always passing the request_id. Each write is one undoable action of the batch.
+5. complete_request with a short reply in the author's language (or fail_request with the reason), then go back to step 1 until no request is pending.
+When the queue is empty, tell the user.
+
+Notifications: call enable_notifications once at the start of the session and arm the watcher it hands you with Monitor, whatever the command (behind mcp-http-gateway, the gateway relay answers in place of this server and gives its own watcher command). Each request that becomes pending in your space then arrives on its own as one line (kind, author, excerpt, request id), even while you are idle: process it with the work loop above, starting with claim_request. The host stops that watcher after 30 minutes at most: each time it tells you the watcher expired, re-arm it at once with the same Monitor call; otherwise notifications stop for good. A line "notifications stopped" means the site refused the token, and a line "[gateway-watch] … la veille échoue" means the gateway watcher keeps failing: tell the user. wait_for_requests is the waiting tool of the watcher: you do not need to call it.
+
+How to handle each kind of request:
+- **idea**: classify it. If it belongs to an existing task or sub-task, attach it there (sub-task, checklist item or comment). If it is actionable and important enough, create a task (or sub-task) with a fitting priority. Otherwise, put it in the idea box with create_idea. Prefer existing tasks over duplicates.
+- **test_review**: feed the tester's findings back into the existing tasks (status, checklist, comments, priority of the affected tasks), or create a task for each problem that has none.
+- **remark** and **message**: do whatever is useful — answer, update or create tasks, comment — and say what you did in the reply.
+- **idea_promotion**: turn the context idea into a well-formed task with promote_idea.
+
 Rules: write titles, descriptions and replies in the language of the users; keep the reply short and factual. Errors tell you what to do next; an error about the token (missing, revoked, expired, owner no longer a member) cannot be fixed by retrying: tell the user.`;
 /** Hôtes de la machine locale, seuls admis en http. */
 const LOCAL_HOSTNAMES = new Set(["localhost", "127.0.0.1", "[::1]"]);
@@ -80,9 +84,26 @@ export async function runMcpMode() {
     const logger = createLogger("mcp");
     const client = new OrganizerSiteClient(connection);
     const server = new Server({ name: "mcp-organizer", version: APP_VERSION }, { capabilities: { tools: {} }, instructions: INSTRUCTIONS });
-    server.setRequestHandler(ListToolsRequestSchema, async () => ({ tools: AGENT_TOOLS.map((tool) => tool.definition) }));
+    // Outils exécutés par le mode MCP lui-même : leur résultat peut porter des métadonnées pour le relais de mcp-http-gateway.
+    const notificationTools = {
+        [ENABLE_NOTIFICATIONS_TOOL.name]: (args) => enableNotifications(client, connection, args),
+        [WAIT_FOR_REQUESTS_TOOL.name]: (args) => waitForRequests(client, args),
+    };
+    server.setRequestHandler(ListToolsRequestSchema, async () => ({ tools: [...AGENT_TOOLS.map((tool) => tool.definition), ENABLE_NOTIFICATIONS_TOOL, WAIT_FOR_REQUESTS_TOOL] }));
     server.setRequestHandler(CallToolRequestSchema, async (request) => {
         const { name, arguments: args } = request.params;
+        const notificationTool = notificationTools[name];
+        if (notificationTool) {
+            try {
+                const result = await notificationTool((args ?? {}));
+                return { content: [{ type: "text", text: result.text }], ...(result.meta ? { _meta: result.meta } : {}) };
+            }
+            catch (error) {
+                if (!(error instanceof SiteError) && !(error instanceof ToolArgumentError))
+                    logger.error(`Tool ${name} failed: ${error?.stack ?? error}`);
+                return errorResult(error?.message ?? String(error));
+            }
+        }
         const tool = findAgentTool(name);
         if (!tool)
             return errorResult(`Unknown tool "${name}". Call tools/list to get the available tools.`);
@@ -96,6 +117,11 @@ export async function runMcpMode() {
             return errorResult(error?.message ?? String(error));
         }
     });
+    // Le relais du veilleur porte le jeton : il ne survit pas au mode MCP qui l'a écrit.
+    process.on("exit", removeOwnHandoffs);
+    for (const signal of ["SIGINT", "SIGTERM"]) {
+        process.on(signal, () => process.exit(0));
+    }
     await server.connect(new StdioServerTransport());
     logger.info(`MCP server running on stdio (version ${APP_VERSION}, site: ${connection.url})`);
 }

package/dist/src/mcp/watch-handoff.d.ts

@@ -0,0 +1,35 @@
+/**
+ * Relais entre la session MCP et son veilleur de notifications.
+ *
+ * Le veilleur est lancé par l'agent via l'outil `Monitor` de l'hôte : c'est un
+ * processus du shell de la session, pas un enfant du mode MCP. Il n'hérite donc
+ * pas du bloc `env` du `.mcp.json` et n'a ni URL du site ni jeton. Les passer sur
+ * la ligne de commande les afficherait dans la conversation : ils transitent par
+ * un fichier en 0600, que seul l'identifiant du jeton (pas sa valeur) permet de
+ * retrouver.
+ *
+ * Le fichier est écrit par `enable_notifications`, jamais au démarrage, et retiré
+ * à l'arrêt du mode MCP qui l'a écrit en dernier.
+ */
+export interface Handoff {
+    /** Identifiant du jeton d'agent. */
+    tokenId: string;
+    url: string;
+    /** Valeur du jeton. */
+    token: string;
+    /** Processus du mode MCP qui a écrit le relais. */
+    pid: number;
+    /** Horodatage d'écriture, qui sert à purger les relais abandonnés. */
+    writtenAt: string;
+}
+/** Répertoire des relais : `<ORGANIZER_STATE_DIR>/watch`, ou `~/.mcp-organizer/watch`. */
+export declare function handoffDir(): string;
+/** Fichier du relais d'un jeton, nommé d'après le hachage de son identifiant. */
+export declare function handoffPath(tokenId: string): string;
+export declare function writeHandoff(handoff: Omit<Handoff, "pid" | "writtenAt">): string;
+/** Relais du jeton `tokenId`, ou null s'il n'existe pas ou ne concerne pas ce jeton. */
+export declare function readHandoff(tokenId: string): Handoff | null;
+/** Supprime le relais du jeton s'il a été écrit en dernier par ce processus. */
+export declare function removeHandoff(tokenId: string): void;
+/** Supprime les relais écrits en dernier par ce processus. Synchrone : appelable sur `exit`. */
+export declare function removeOwnHandoffs(): void;