@chatpanel/events 0.114.0 → 0.114.1

package/find-tool.js

@@ -1 +1 @@
-import{makeDispatchProvider as a}from"./tool-dispatch.js";const n="find",r='Search and read the user\'s own saved data (past chats, notes, meetings) and the web. Pass an `action` and put that action\'s own arguments inside `args`, e.g. {"action":"history_search","args":{"query":"pricing"}}. Unsure of an action\'s arguments? {"action":"describe","args":{"tool":"<action>"}} returns its full schema. Use this when the answer plausibly depends on something the user already has; do not call it for greetings or general knowledge.',o="You HAVE access to the user's own ChatPanel data — past chats, notes, meeting transcripts and summaries — through `find`, plus the web. For anything they discussed or wrote, call `find` FIRST and answer from it; never say you cannot access their meetings, notes or history. For anything current — weather, prices, news — use `find` (actions `weather`, `web_search`), not a search tool of your own; the user sees `find` calls as steps. A [prefetch] block in the message IS that call, already made: answer from it, no call.";function c(e,{all:s=null,rank:t=void 0}={}){return a({name:n,description:r,resident:o,inner:e,remote:!1,all:s,rank:t})}export{r as FIND_DESCRIPTION,o as FIND_RESIDENT,n as FIND_TOOL_NAME,c as findDispatchProvider};
+import{makeDispatchProvider as a}from"./tool-dispatch.js";const n="find",r='Search and read the user\'s own saved data (past chats, notes, meetings) and the web. Pass an `action` and put that action\'s own arguments inside `args`, e.g. {"action":"history_search","args":{"query":"pricing"}}. Unsure of an action\'s arguments? {"action":"describe","args":{"tool":"<action>"}} returns its full schema. Use this when the answer plausibly depends on something the user already has; do not call it for greetings or general knowledge.',o="You HAVE access to the user's own ChatPanel data — past chats, notes, meeting transcripts and summaries — through `find`, plus the web. For anything they discussed or wrote, call `find` FIRST and answer from it; never say you cannot access their meetings, notes or history. For anything current — weather, prices, news — use `find` (actions `weather`, `web_search`), not a search tool of your own; the user sees `find` calls as steps. A [prefetch] block in the message IS that call, already made: answer from it, no call. A search returns excerpts, not the record: before reporting details (action items, decisions, who said what) read the full record by its id — each result names the action.";function c(e,{all:t=null,rank:s=void 0}={}){return a({name:n,description:r,resident:o,inner:e,remote:!1,all:t,rank:s})}export{r as FIND_DESCRIPTION,o as FIND_RESIDENT,n as FIND_TOOL_NAME,c as findDispatchProvider};

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@chatpanel/events",
-  "version": "0.114.0",
+  "version": "0.114.1",
   "description": "The canonical ChatPanel event-log and capability contracts — typed durable facts, clock-free deterministic linearization, schema upcasting, and the invariants the replay harness asserts. Pure, dependency-free ESM shared by the ChatPanel extension, gateway and bridge.",
   "type": "module",
   "main": "index.js",