@paigy/mcp 0.40.25 → 0.40.27

package/README.md

@@ -84,7 +84,7 @@ args = ["-y", "@paigy/mcp@latest"]
 env = { PAIGY_AGENT = "codex" }
 ```
 
-Then pair: `PAIGY_AGENT=codex npx -p @paigy/mcp@latest paigy-mcp-onboard` (or have the agent call the `pair` tool — it pairs under its own name automatically).
+Then pair: `PAIGY_AGENT=codex npx -p @paigy/mcp@latest paigy-mcp-onboard` (or have the agent call the `configure` tool — it pairs under its own name automatically).
 
 ### Gemini CLI
 
@@ -117,18 +117,28 @@ Then pair: `PAIGY_AGENT=gemini npx -p @paigy/mcp@latest paigy-mcp-onboard`.
 ## Tools
 
 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
+`packages/schema/src/tools.ts` — contact, manage_goals, get_goal, search, check_activity,
+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
+This server adds only `configure`, the one identity tool, which pairs, reports who you are,
+renames and logs this agent out (`logOut: true`) over the token file this machine holds, and listen.
+`onboard` is now `configure`; `pair` and `unpair` are folded into it (2026-10-07). 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
-your own Goals. manage_goals creates, edits, assigns, organizes and closes work, a change at a
+consuming any of it until you acknowledge it (`ackEventIds`), and get_goal reads a Goal.
+`claim_goal` is gone (2026-10-07): you are on a Goal from your first write to it (a contact
+naming it, or a manage_goals change), never from a read, so there is nothing to claim or join;
+`who_is_working` is now `check_activity`. manage_goals creates, edits, assigns, organizes and closes work, a change at a
 time. Bookkeeping (`operationId`, the manage request id, the revision an edit was read at) is
 minted here, never asked of the model. Retired
 reply-lease/ACK/work/callback tools and hidden notification aliases are rejected.
@@ -158,10 +168,10 @@ with `paigy-listen --install` (launchd on macOS, systemd user unit on Linux;
 
 The read is `receive` (behind `contact({})`) — the open Deliveries addressed to this agent — and it
 **consumes nothing**: no lease, no acknowledgement, and the same read twice returns the
-same list. So the daemon hands the launcher what it found and stops there; claiming is
-the agent's own first act (`claim_goal`), because the daemon shares this machine's
-token with the agent it launches and a second claimer on one identity eats the first
-one's claim.
+same list. So the daemon hands the launcher what it found and stops there; it never
+writes, because an agent is on a Goal from its first write and the daemon shares this
+machine's token with the agent it launches: a write here would put that agent on work it
+never started.
 
 To launch an agent — any agent, not just Claude — when work arrives, set
 `PAIGY_ON_WAKE` to a command before `--install`:
@@ -171,8 +181,8 @@ 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_GOAL_ID` | the Goal it belongs to — `claim_goal` it **first** |
+| `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 — read it with `get_goal` **first** |
 | `PAIGY_TEXT` | what the person said, in prose |
 
 Hand `$PAIGY_WORK` to a harness that can read JSON and decide for itself; use the
@@ -183,7 +193,7 @@ Goal" from "an empty id".
 
 ```sh
 # Claude Code — hand it everything and let it plan:
-PAIGY_ON_WAKE='claude -p "Handle the Paigy work in $PAIGY_WORK — claim_goal first, and read a Goal you do not recognize with get_goal."' \
+PAIGY_ON_WAKE='claude -p "Handle the Paigy work in $PAIGY_WORK — read each Goal it names with get_goal first."' \
   npx -y -p @paigy/mcp paigy-listen --install
 
 # Codex terminal session: no custom script and no new conversation.
@@ -227,7 +237,7 @@ script and branch on `$PAIGY_EVENT` there:
 ```sh
 #!/bin/sh
 # ~/.paigy/on-wake.sh — chmod +x, then PAIGY_ON_WAKE=~/.paigy/on-wake.sh
-codex exec "Paigy goal $PAIGY_GOAL_ID. claim_goal it first. The user said: $PAIGY_TEXT. Reply with contact when done."
+codex exec "Paigy goal $PAIGY_GOAL_ID. Read it with get_goal first. The user said: $PAIGY_TEXT. Reply with contact when done."
 ```
 
 ## Stalled work (turn-end hook — Claude Code, Codex, Gemini CLI, Antigravity)