@animalabs/agent-framework 0.5.7 → 0.6.0

package/src/types/agent.ts

@@ -138,4 +138,14 @@ export interface InferenceRequest {
   reason: string;
   source: string;
   timestamp: number;
+  /**
+   * The MCPL channel whose message triggered this inference, if any (composite
+   * id, e.g. `discord:guild:channel` / `discord:dm:id`). The framework routes
+   * the turn's auto-published plain-text speech here so a single TRUNK agent
+   * replies in the channel it is answering — not the process-global most-recent-
+   * inbound locus, which a concurrent message elsewhere can hijack (item-3
+   * redux). Undefined for non-channel wakes (heartbeat, timers, module events),
+   * which correctly fall back to the global default channel.
+   */
+  channelId?: string;
 }

package/src/types/framework.ts

@@ -68,6 +68,21 @@ export interface FrameworkConfig {
   /** EventGate config. If omitted, all events trigger inference (unchanged default). */
   gate?: GateOptions;
 
+  /**
+   * Liveness watchdog: fail hard (and let the supervisor restart) if the main
+   * thread wedges — a synchronous infinite loop or microtask flood that would
+   * otherwise leave the agent silently deaf. Off unless `enabled` is set.
+   */
+  watchdog?: {
+    enabled?: boolean;
+    /** Kill if no heartbeat for this long (ms). Default 30000. */
+    thresholdMs?: number;
+    /** 'abort' → SIGABRT (core dump for debugging); 'exit' → SIGKILL. Default 'abort'. */
+    action?: 'abort' | 'exit';
+    /** Optional path for a JSON wedge report written before the kill. */
+    reportPath?: string;
+  };
+
   /**
    * Per-channel conversation routing. When set, incoming MCPL channel
    * messages route to per-channel fork agents spawned from the template

package/src/types/module.ts

@@ -186,6 +186,19 @@ export interface ModuleContext {
    */
   unregisterSpeechHandler(): void;
 
+  /**
+   * Execute a tool call autonomously, without agent mediation.
+   *
+   * Routes through the framework's normal tool dispatch — MCPL-prefixed names
+   * (e.g. `mcpl--discord--unsubscribe_channel`) hit the MCPL subsystem; module
+   * names hit the owning module. Unlike pushing a `tool-call` event, this does
+   * NOT record tool_use/tool_result into any agent's context — it's a pure
+   * side-effecting call whose result is returned to the caller. Used by modules
+   * that need to act on their own (e.g. subscription GC unsubscribing a noisy
+   * channel) rather than asking the agent to call the tool.
+   */
+  callTool(call: ToolCall): Promise<ToolResult>;
+
   /**
    * Subscribe to the framework's trace event stream for observability.
    *