@paigy/mcp 0.40.25 → 0.40.26

package/README.md

@@ -118,13 +118,20 @@ Then pair: `PAIGY_AGENT=gemini npx -p @paigy/mcp@latest paigy-mcp-onboard`.
 
 One catalog, on every transport (2026-09-11): the agent tools are `AGENT_TOOLS` in
 `packages/schema/src/tools.ts` — who_is_working, contact, manage_goals, claim_goal,
-get_goal, update_goal — and both this server and the hosted MCP
+get_goal, search, send_feedback — and both this server and the hosted MCP
 (`apps/api/src/mcp`) publish that list and dispatch it through the SDK's one `runTool`.
 This server adds only onboard, pair and unpair, the tools that mint and delete the token
-file this machine holds. See the [SDK contract](../../packages/sdk/README.md) for the
-single-Goal start shape. Notification returns immediately. Call holds one cancellable
-~45-second window here (the hosted transport returns after one read); continue with
-contact({deliveryId}) without sending another ask. Durable Entries and accepted answers can
+file this machine holds, and listen. See the [SDK contract](../../packages/sdk/README.md) for the
+contact shape. Sending returns immediately unless it asks to `wait`: `wait: true` holds one
+cancellable ~45-second window here for a response to what was sent (the hosted transport
+returns after one read), and `contact({})` holds one for anything addressed to you; after an
+`expired` window, wait again without sending again. Every Goal a contact names must already
+exist (create it with manage_goals); a question with `workItBlocks` asks for a call; a
+question, an update or an answer is at most 250 characters with its context in `units`; and
+`withdrawQuestionIds` takes back a question of yours. `update_goal` is gone (2026-10-07): progress
+is a contact update (one the person does not need yet is kept as the Goal's progress), a review is
+acknowledged with `ackEventIds`, and a Goal is postponed with manage_goals `defer` (you are woken
+when its time comes). Durable Entries and accepted answers can
 repeat on reads; contact with nothing to send receives what is addressed to you (a request the
 user started toward you, an answer relayed to something you asked, a handoff, a question you owe) without
 consuming any of it until you acknowledge it (`ackEventIds`), and claim_goal is the catch-up for
@@ -171,7 +178,7 @@ To launch an agent — any agent, not just Claude — when work arrives, set
 | `PAIGY_WORK` | everything the wake found, as JSON (`deliveries`, `goal`) |
 | `PAIGY_EVENT` | the wake that caused this run — `boot`, `wake:reply`, `wake:request`… |
 | `PAIGY_PARENT_ID` | the thread to continue on (`PAIGY_THREAD_ID` is the same value, for existing scripts) |
-| `PAIGY_DELIVERY_ID` | the Delivery being acted on — `contact({deliveryId})` rereads it |
+| `PAIGY_DELIVERY_ID` | the Delivery being acted on (`get_goal` on `PAIGY_GOAL_ID` reads its conversation) |
 | `PAIGY_GOAL_ID` | the Goal it belongs to — `claim_goal` it **first** |
 | `PAIGY_TEXT` | what the person said, in prose |
 

package/dist/{chunk-UAVXYNLV.js → chunk-5MQ3J6S3.js}

@@ -4,12 +4,12 @@ import {
   serverInstructions,
   sessionStartHook,
   withSessionStartHook
-} from "./chunk-GHSB2VP6.js";
+} from "./chunk-7LQKX73K.js";
 import {
   CODEX_ENV,
   agentName,
   withCodexEnv
-} from "./chunk-EJYXBEWN.js";
+} from "./chunk-OVSAQW3K.js";
 
 // src/toolset.ts
 var ONBOARD_DESCRIPTION = "Get this agent talking to Paigy \u2014 call it FIRST, before contact, and any time you're unsure who you are. One call, and it does whatever the situation needs: NOT SET UP \u2192 hatches an identity instantly if this machine holds a device credential (the user ran the Paigy desktop app or harness), otherwise starts the code ceremony; ALREADY SET UP \u2192 returns your current identity and offers the two things left to decide, renaming it or unpairing; TOKEN NO LONGER VALID \u2192 says so, then re-pairs. Pass { name, voice } to choose who you are when hatching, or to RENAME yourself when already set up (voices: rachel, george, jessica, brian, lily). Safe to call any time: idempotent, and it never writes settings \u2014 the tool-allowlist state it reports is read-only. If it returns a `user_code`, print it to the user immediately and call onboard again with the `device_code`. If it returns `enable_command`, PRINT that command for the user to run \u2014 you cannot apply it yourself (it writes your own permission allowlist, which hosts block as privilege escalation), so print it, don't wait for it, and carry on.";