@paigy/mcp 0.40.43 → 0.40.44

package/dist/{chunk-DMQHSNFJ.js → chunk-4US4OJR5.js}

@@ -7,7 +7,7 @@ import {
   saveToken,
   setIdentity,
   sleep
-} from "./chunk-ULCS3CYO.js";
+} from "./chunk-5OKHG3FO.js";
 
 // src/identity.ts
 var CLIENT_LABELS = {

package/dist/{chunk-ULCS3CYO.js → chunk-5OKHG3FO.js}

@@ -1653,11 +1653,11 @@ var CompleteChangeSchema = CompletionSchema.omit({ causedBy: true, shipped: true
 var ASKING_RULES = `HOW TO ASK:
 1. One question per object in \`questions\`, so each is answered on its own.
 2. \`goalId\` names the existing Goal it is about (create one with manage_goals first); the answer comes back there.
-3. \`workItBlocks\` only when you are truly blocked: it asks for a call.
+3. They asked you to call? \`userExplicitlyRequested:"call"\`; \`workItBlocks\` rings when blocked.
 4. No while-loops. While any Call is open, even one your question joined from their items, keep receiving through empty windows; otherwise stop at one: the answer reaches you on the Goal. Yield only with a listener or wakeup.
 5. One question, one row: never re-send one still waiting; take back one that no longer matters with \`withdrawQuestionIds\`.
 6. Read the Goal before asking; never re-ask what was answered or shipped. \`replied\` means they chose no option: it is still yours to settle.
-7. Give options when you have them. Each label names its choice in full (never "Option 2"); never add "Other". \`pickMode\`: one (default), many, rank.
+7. Give options when you have them. Each label names its choice in full (never "Option 2"); never add "Other".
 8. A diagnosis says when, why and how it happens, then proposes one fix.
 9. Give a report its \`reply\`: one line in THEIR voice for THAT report, so you learn whether they verified it or only received it. Required when it is delivered or its Goal is done.`;
 function draft2020(node) {
@@ -1699,7 +1699,7 @@ var reason = z5.string().trim().min(1).max(500).describe("Why, as an explanation
 var actionFits = (b) => b.blocked.type === "goal" === (b.action !== "answer");
 var ACTION_FITS = "a goal is blocked from start or complete; a question from answer";
 var userExplicitlyRequested = z5.enum(["any", "call"]).optional().describe(
-  `Only what the person said about THIS message, in so many words: "any" when they asked you to send it to them ("send it to my phone", "message me the result"), "call" when they asked to be called about it. It is then delivered (a call rings for the whole contact, and carries everything waiting on them); omitted, an update is only recorded as the Goal's progress unless the person needs it. Never set it to make a message louder.`
+  'What the person asked for about THIS message, in so many words: "any" when they asked you to send it to them ("send it to my phone", "message me the result"), "call" when they asked to be called about it. It is then delivered (a call rings for the whole contact, and carries everything waiting on them); omitted, an update is only recorded as the Goal\'s progress unless the person needs it. ALSO "any" whenever this message directly answers a question they asked you, wherever they asked it -- on a call, in a reply, in passing: their question is the request, so it is delivered every time, even with no pending question of theirs on file and even if they never said to send it. A correction of something you or another agent told them is such an answer. Never set it to make a message louder. This is the field that rings a phone: "call" here is how you call them when they asked you to, and `help` has the whole mechanism.'
 );
 var units = z5.array(UnitInputSchema).optional().describe(
   `The context this message needs, as up to ${UNITS_MAX} units in reading order, each {title, body}: a title of at most ${UNIT_TITLE_MAX} characters and a body of at most ${UNIT_BODY_MAX}. One idea per unit: context they may open, never something they must hear. Leave it out when the main text says it all. Over a cap is refused by name (ask_too_long, too_many_units, unit_title_too_long, unit_body_too_long) and nothing is sent.`
@@ -1919,13 +1919,13 @@ LENGTH: the question, message or answer is the one point, at most ${ASK_MAX} cha
 UPDATES ask nothing. One reaches the person only when they asked for it, it answers something they said, or its Goal is done; else it is kept as progress. One that reaches them joins an open report card or a live call.
 
 RECEIVING: contact({}) waits ~45 s; contact({wait:false}) returns \`events\` at once. Confirm the ones you handled with contact({ackEventIds}).`;
-var GUIDE = '# Paigy\n\nThe user is remote. Reach them only through Paigy\'s tools, never the terminal. The server\'s own instructions and each tool\'s description are the contract: read them. Every read ends in `next`, the one step to take.\n\nThis same guide is inside the MCP: the `help` tool (whole, or one `topic`) and the `/mcp__paigy__help` prompt. `/mcp__paigy__welcome` starts a session.\n\nHosted (no machine): skip Pairing and Listening; answers wake you.\n\n## Pairing\n\n- Call `configure` first. With a device credential on this machine it hatches you at once.\n- Otherwise print its `user_message` to the user, then do what the result says:\n  - `awaiting_approval`: call `configure` again with its `device_code` in the same turn. On `pending`, call again.\n  - `awaiting_confirmation`: end your turn with the code as your whole reply; call `configure` with the `device_code` next turn. Calling it in the same turn drops the code.\n- When it returns `enable_command`, print it for the user to run. Do not run it yourself.\n- `configure({ logOut: true })` logs out only this agent, and only when the user asks.\n\n## Listening\n\n- Call `listen` once per session.\n  - `listening`: done.\n  - `receiving`: a listener runs but cannot wake you. Do not start a second.\n  - `unpaired`: call `configure`.\n  - `start`: run its `command` exactly, now.\n- Claude Code: run it with the **Monitor** tool, never a background Bash command. Start it again whenever the monitor expires.\n- Codex: run its `command` as a long-running background process. It queues each answer into this thread (`CODEX_THREAD_ID`).\n- Grok: run it with the **monitor** tool, never a background shell command. Start it again whenever the monitor expires.\n- With no `listen` tool, run `npx -y -p @paigy/mcp@latest paigy-listen --brief` the same way.\n- One listener per session. A `paigy-listen` in `ps` belongs to another session; ask `listen`, never `ps`.\n- Each line it prints is work: receive, read the Goal, act.\n\n## Receiving\n\n- On startup and after every wake or listener line: `contact({ wait: false })`.\n- Events: `question` (you owe an answer: send `answers`), `update` (something new on your Goal: an answer, a reply, a review), `instruction` (work sent to you).\n- Read the Goal with `get_goals` before acting. An answer arrives as an `update` event and lands on the question\'s Goal. A question reading `replied` means they chose no option: settle it from their words.\n- Acknowledge each event you handled: `contact({ ackEventIds })`. Reading acknowledges nothing; events repeat until acknowledged. A `question` event is answered, never acknowledged away.\n- `contact({ wait: true })` waits about 45 s. On `expired`, wait again without re-sending, or stop. No while-loops: while any Call is open, keep receiving through empty windows; otherwise stop at one empty window.\n\n## Asking\n\n- One question per object in `questions`, at most 80 characters. Context goes in `units`: at most 12, title \u226450, body \u2264200, one idea each.\n- `goalId` names an existing Goal. Create it with `manage_goals` first.\n- Give options when you have them: up to 6, label \u226450 naming the choice in full, `hint` \u2264200 saying what it does. Never "Other" or "Option 2". `pickMode`: `one` (default), `many`, `rank`.\n- `workItBlocks` only when you are truly stopped: it asks for a call.\n- Read the Goal before asking. Never re-ask an open or answered question, or one whose work shipped.\n- Take back a question that no longer matters: `withdrawQuestionIds`.\n- An answer you give (`answers`) is at most 80 characters.\n\n## Updates and completions\n\n- An update (`updates`: `message` \u226480, `goalIds`) asks nothing. It reaches the user only when they asked for it, when it answers something they said, or when its Goal is done; otherwise it stays on the Goal as progress.\n- Updates never complete a Goal.\n- One load-bearing point per report: `message` is the point they must not miss, and a second point that would go wrong or stay unclear later if they missed it is its own update. `units` are context they may open, never something they must hear.\n- `reply` is the button in the user\'s voice instead of "Got it", \u226450 characters ("Sounds good, I\'ll test later"). Required (`reply_required`) when the update is delivered on request (`userExplicitlyRequested`) or any Goal it names is already done.\n- Set `userExplicitlyRequested` only to relay the user\'s own words: `"any"` for "send it to me", `"call"` for "call me". Never to make a message louder.\n- Finish with a completion (`contact.completions`, or `manage_goals` kind `complete`): `goalId`, `message` \u226450, `reply` \u226450, optional `units`, optional next-step `options` {label, hint}. It closes and reports in one step. Say only what your evidence supports.\n- Read `results`: each item applies on its own, and a failed one names why.\n\n## Goals\n\n- `manage_goals` `changes`, applied in order:\n  - `create`: `title` (1-5 words) and `outcome` (one paragraph, \u2264500). More work is child Goals: `parentGoalId`. New ids come back in `results[i].goalId`.\n  - `assign`: `ownerId`, a participant as `check_activity` shows it.\n  - `defer`: `until`. You are woken when it passes. This is how you follow up later.\n  - `dependency`: `add`/`remove`; `goalId` waits on `dependsOnGoalId` to `start` or `complete`.\n  - `edit`, `move`, `state` (open, completed, canceled).\n- Any open question on a Goal, anyone\'s, blocks its completion (`goal_blocked`). Before completing, withdraw yours, finish or move its required children, and clear its dependencies.\n- On `goal_revision_conflict`, read the Goal again and reconsider.\n- Before overlapping work, read `check_activity` and the Goal\'s other contributors. Every Goal of your person is open to you; your first write puts you on it.\n- `search` finds earlier words, Goals and answers. Nothing found is not proof of absence.\n\n## Calls\n\n- Call only when the user asked: `userExplicitlyRequested: "call"` on that item. A question with `workItBlocks` may ring too.\n- Any contact while the user is on a call joins that call (`joinedCall` in `results`). Several questions arrive as one call.\n- While any Call is open, keep receiving.\n- An open Call Delivery is not proof it rang. `get_delivery` reads a Call\'s state, and with `transcript: true` what was said.\n';
-var HELP_TOPICS = ["pairing", "listening", "receiving", "asking", "updates", "goals", "calls"];
+var GUIDE = '# Paigy\n\nThe user is remote. Reach them only through Paigy\'s tools, never the terminal. The server\'s own instructions and each tool\'s description are the contract: read them. Every read ends in `next`, the one step to take.\n\nThis same guide is inside the MCP: the `help` tool (whole, or one `topic`) and the `/mcp__paigy__help` prompt. `/mcp__paigy__welcome` starts a session; `/mcp__paigy__organize` sets up a person\'s work as a board.\n\nHosted (no machine): skip Pairing and Listening; answers wake you.\n\n## Pairing\n\n- Call `configure` first. With a device credential on this machine it hatches you at once.\n- Otherwise print its `user_message` to the user, then do what the result says:\n  - `awaiting_approval`: call `configure` again with its `device_code` in the same turn. On `pending`, call again.\n  - `awaiting_confirmation`: end your turn with the code as your whole reply; call `configure` with the `device_code` next turn. Calling it in the same turn drops the code.\n- When it returns `enable_command`, print it for the user to run. Do not run it yourself.\n- `configure({ logOut: true })` logs out only this agent, and only when the user asks.\n\n## Listening\n\n- Call `listen` once per session.\n  - `listening`: done.\n  - `receiving`: a listener runs but cannot wake you. Do not start a second.\n  - `unpaired`: call `configure`.\n  - `start`: run its `command` exactly, now.\n- Claude Code: run it with the **Monitor** tool, never a background Bash command. Start it again whenever the monitor expires.\n- Codex: run its `command` as a long-running background process. It queues each answer into this thread (`CODEX_THREAD_ID`).\n- Grok: run it with the **monitor** tool, never a background shell command. Start it again whenever the monitor expires.\n- With no `listen` tool, run `npx -y -p @paigy/mcp@latest paigy-listen --brief` the same way.\n- One listener per session. A `paigy-listen` in `ps` belongs to another session; ask `listen`, never `ps`.\n- Each line it prints is work: receive, read the Goal, act.\n\n## Receiving\n\n- On startup and after every wake or listener line: `contact({ wait: false })`.\n- Events: `question` (you owe an answer: send `answers`), `update` (something new on your Goal: an answer, a reply, a review), `instruction` (work sent to you).\n- Read the Goal with `get_goals` before acting. An answer arrives as an `update` event and lands on the question\'s Goal. A question reading `replied` means they chose no option: settle it from their words.\n- Acknowledge each event you handled: `contact({ ackEventIds })`. Reading acknowledges nothing; events repeat until acknowledged. A `question` event is answered, never acknowledged away.\n- `contact({ wait: true })` waits about 45 s. On `expired`, wait again without re-sending, or stop. No while-loops: while any Call is open, keep receiving through empty windows; otherwise stop at one empty window.\n\n## Asking\n\n- One question per object in `questions`, at most 80 characters. Context goes in `units`: at most 12, title \u226450, body \u2264200, one idea each.\n- `goalId` names an existing Goal. Create it with `manage_goals` first.\n- Give options when you have them: up to 6, label \u226450 naming the choice in full, `hint` \u2264200 saying what it does. Never "Other" or "Option 2". `pickMode`: `one` (default), `many`, `rank`.\n- `workItBlocks` only when you are truly stopped: it asks for a call.\n- Read the Goal before asking. Never re-ask an open or answered question, or one whose work shipped.\n- Take back a question that no longer matters: `withdrawQuestionIds`.\n- An answer you give (`answers`) is at most 80 characters.\n\n## Updates and completions\n\n- An update (`updates`: `message` \u226480, `goalIds`) asks nothing. It reaches the user only when they asked for it, when it answers something they said, or when its Goal is done; otherwise it stays on the Goal as progress.\n- Updates never complete a Goal.\n- One load-bearing point per report: `message` is the point they must not miss, and a second point that would go wrong or stay unclear later if they missed it is its own update. `units` are context they may open, never something they must hear.\n- `reply` is the button in the user\'s voice instead of "Got it", \u226450 characters ("Sounds good, I\'ll test later"). Required (`reply_required`) when the update is delivered on request (`userExplicitlyRequested`) or any Goal it names is already done.\n- Set `userExplicitlyRequested` only to relay the user\'s own words: `"any"` for "send it to me", `"call"` for "call me". Never to make a message louder.\n- Finish with a completion (`contact.completions`, or `manage_goals` kind `complete`): `goalId`, `message` \u226450, `reply` \u226450, optional `units`, optional next-step `options` {label, hint}. It closes and reports in one step. Say only what your evidence supports.\n- Read `results`: each item applies on its own, and a failed one names why.\n\n## Goals\n\n- `manage_goals` `changes`, applied in order:\n  - `create`: `title` (1-5 words) and `outcome` (one paragraph, \u2264500). More work is child Goals: `parentGoalId`. New ids come back in `results[i].goalId`.\n  - `assign`: `ownerId`, a participant as `check_activity` shows it.\n  - `defer`: `until`. You are woken when it passes. This is how you follow up later.\n  - `dependency`: `add`/`remove`; `goalId` waits on `dependsOnGoalId` to `start` or `complete`.\n  - `edit`, `move`, `state` (open, completed, canceled).\n- Shape your work as projects with steps. Create a project under its area (`create` with `parentGoalId` = the area), then one child Goal per step; complete each step as it lands. A top-level Goal that has children is an area, not a project: never hang steps straight off a top-level Goal. The person\'s Work tab shows a project\'s progress as its steps, "3 of 5 steps done"; a project with no steps shows none. When you touch an older Goal of yours that sits flat or under a finished project, move it into that shape (`move`). A flat Goal is still valid; never reshape another agent\'s Goals.\n- Any open question on a Goal, anyone\'s, blocks its completion (`goal_blocked`). Before completing, withdraw yours, finish or move its required children, and clear its dependencies.\n- On `goal_revision_conflict`, read the Goal again and reconsider.\n- Before overlapping work, read `check_activity` and the Goal\'s other contributors. Every Goal of your person is open to you; your first write puts you on it.\n- `search` finds earlier words, Goals and answers. Nothing found is not proof of absence.\n\n## Organize\n\nWhen the person asks you to set up or organize their work ("set up my project", "help me manage all this", several products or parts to juggle), turn it into a board they can run like a team. Their Work tab shows it.\n\n- Learn the work first: read the repo and their Goals (`get_goals`, `search`). Ask only what you cannot read, at most three questions, each its own question.\n- The shape: an area per product or business (a top-level Goal); under it a project per part that moves on its own (landing page, graphics, web app, mobile app, launch); under each project its steps, three to seven, each an outcome someone can finish and check.\n- Propose before you build. Create one Goal for the setup itself, then ask one question on it: the tree in `units` (one unit per project: its title, then its steps), options "Build it" and "Change it: I\'ll say how". Create nothing else until they answer.\n- On "Build it", one `manage_goals` call per level, since a parent\'s id comes back in `results[i].goalId`: the areas, then their projects (`parentGoalId`), then every step; then a `dependency` where a project waits on another (web on the design). Never copy work that already has a Goal: yours move into the tree (`move`); another agent\'s stay where they are, named in the proposal. Then complete the setup Goal.\n- Report how to run it, and hand over one brief per project for the person to paste as that session\'s first message. Each brief names the project\'s Goal (title and id) and says: call `listen` and keep the listener running; receive with `contact({ wait: false })` at startup and after every wake; work the steps in order and complete each as it lands; report progress as updates on the project; ask anything you are blocked on through Paigy, as a question on that step\'s Goal (`workItBlocks` only when it truly stops you), never in the terminal.\n- One session per project, plus one lead session that keeps the board current. Any agent, Claude, Codex or another, can pick up any Goal; `check_activity` shows who is on what. A subagent inside a session shares that session\'s identity and listener: it may ask through Paigy, but never starts a listener of its own.\n- Keep it current as you work: complete each step as it lands and add a step when new work appears. Never reshape another agent\'s Goals.\n\n## Calls\n\n- Call only when the user asked: `userExplicitlyRequested: "call"` on that item. A question with `workItBlocks` may ring too.\n- Any contact while the user is on a call joins that call (`joinedCall` in `results`). Several questions arrive as one call.\n- While any Call is open, keep receiving.\n- An open Call Delivery is not proof it rang. `get_delivery` reads a Call\'s state, and with `transcript: true` what was said.\n';
+var HELP_TOPICS = ["pairing", "listening", "receiving", "asking", "updates", "goals", "organize", "calls"];
 var unknownTopic = (topic) => `unknown_topic: ${JSON.stringify(topic)} is not a section of the guide. Topics: ${HELP_TOPICS.join(", ")}; or omit topic for the whole guide.`;
 var HelpSchema = z6.object({
   topic: z6.enum(HELP_TOPICS, { errorMap: (_issue, ctx) => ({ message: unknownTopic(ctx.data) }) }).optional().describe("One section of the guide. Omit it for the whole guide.")
 }).strict();
-var HELP_DESCRIPTION = "Start here: how to use Paigy, in full \u2014 pairing, listening, receiving, asking, updates and completions, Goals and calls. Pass a topic for one section. Read-only; needs no setup.";
+var HELP_DESCRIPTION = "Start here: how to use Paigy, in full \u2014 pairing, listening, receiving, asking, updates and completions, Goals, organizing work, and calls. Pass a topic for one section. Read-only; needs no setup.";
 function section(topic) {
   const parts = GUIDE.split(/^(?=## )/m);
   const found = parts.find((p) => p.slice(3).toLowerCase().startsWith(topic));
@@ -1946,7 +1946,8 @@ var AGENT_PROMPTS = [
     description: "How to use Paigy: the whole guide, or one topic of it.",
     arguments: [{ name: "topic", description: `One section: ${HELP_TOPICS.join(", ")}. Omit it for the whole guide.`, required: false }]
   },
-  { name: "welcome", description: "Start here: who you are on Paigy, then listen and collect your open work." }
+  { name: "welcome", description: "Start here: who you are on Paigy, then listen and collect your open work." },
+  { name: "organize", description: "Set up the person's work as a board: areas, projects and steps, proposed on a card before anything is built." }
 ];
 var CreateGoalSchema = z7.object({
   outcome: z7.string().trim().min(1).max(1e4),
@@ -1995,7 +1996,7 @@ var CreateChange = z7.object({
   title: goalTitle,
   outcome: goalOutcome,
   ownerId: z7.string().trim().min(1).optional().describe("Who owns the work: an agent's participant (as check_activity shows it) or the person's. Omitted: you."),
-  parentGoalId: z7.string().uuid().optional().describe("The Goal it belongs under. Omitted: a root."),
+  parentGoalId: z7.string().uuid().optional().describe("The Goal it belongs under. Omitted: a root. A project with several parts: create it, then one child per step under it; the person's Work tab counts a project's progress in those steps."),
   sourceEntryIds: z7.array(z7.string().uuid()).max(20).optional().describe("The whole Entries the work came from, ones you can read.")
 }).strict();
 var EditChange = z7.object({ kind: z7.literal("edit"), goalId: changedGoal, title: goalTitle.optional(), outcome: goalOutcome.optional() }).strict();
@@ -2040,7 +2041,7 @@ var ManageGoalsSchema = z7.object({
 var ManageGoalsToolSchema = z7.object({
   changes: z7.array(z7.discriminatedUnion("kind", [CreateChange, CompleteChangeSchema, EditChange, StateChange, AssignChange, DeferChange, MoveChange, DependencyChange])).min(1).max(50).describe("The changes, applied in order, each on its own.")
 }).strict().superRefine((v, ctx) => editNames(v.changes, ctx));
-var MANAGE_GOALS_DESCRIPTION = "Create, edit, assign, organize or close work. Every change here changes Goals; answering, withdrawing or asking Questions stays in contact. Each change applies independently: a refused one names why (`results[i].error`, e.g. goal_revision_conflict, goal_children_open, goal_not_found) and the rest still apply, so read every result: a partial result is never a complete success. Kinds: complete (goalId, message capped at 50 characters, units, reply, optional next-step options {label, hint}) closes and reports atomically, exactly as contact.completions; create (title, outcome, ownerId, parentGoalId, sourceEntryIds) returns the new Goal's id in `results[i].goalId`, in the order requested, to use in later calls (an outcome is one paragraph, at most 500 characters: split more into child Goals with parentGoalId); edit (title and/or outcome); state (open, completed, canceled); assign (ownerId); defer (until: the Goal waits until then and its owner is woken when it passes; null takes it back); move (parentGoalId, or null for a root: only this Goal moves); dependency (add or remove: goalId waits on dependsOnGoalId to start or to complete). A Goal cannot be completed while its required children or dependencies remain open: finish or move them first. Finishing the children does not prove the parent's own work is done. An edit applies at the version you last read: if someone changed the Goal since, it is refused as goal_revision_conflict, so read it again (get_goals) and reconsider. You may change any Goal of your person; a change puts you on it. Returns `ok` (every change applied), `results` per change (applied or failed), and `goals`, each changed Goal's id, state, title, outcome and revision.";
+var MANAGE_GOALS_DESCRIPTION = "Create, edit, assign, organize or close work. SHAPE IT AS PROJECTS WITH STEPS: create a project under its area (parentGoalId; a top-level Goal with children is an area), then each part as its child Goal, so the person sees N of M steps. Move a flat or orphaned Goal of yours into that shape when you touch it; a flat Goal is valid. Every change here changes Goals; answering, withdrawing or asking Questions stays in contact. Each change applies independently: a refused one names why (`results[i].error`, e.g. goal_revision_conflict, goal_children_open, goal_not_found) and the rest still apply, so read every result: a partial result is never a complete success. Kinds: complete (goalId, message capped at 50 characters, units, reply, optional next-step options {label, hint}) closes and reports atomically, exactly as contact.completions; create (title, outcome, ownerId, parentGoalId, sourceEntryIds) returns the new Goal's id in `results[i].goalId`, in the order requested, to use in later calls (an outcome is one paragraph, at most 500 characters: split more into child Goals with parentGoalId); edit (title and/or outcome); state (open, completed, canceled); assign (ownerId); defer (until: the Goal waits until then and its owner is woken when it passes; null takes it back); move (parentGoalId, or null for a root: only this Goal moves); dependency (add or remove: goalId waits on dependsOnGoalId to start or to complete). A Goal cannot be completed while its required children or dependencies remain open: finish or move them first. Finishing the children does not prove the parent's own work is done. An edit applies at the version you last read: if someone changed the Goal since, it is refused as goal_revision_conflict, so read it again (get_goals) and reconsider. You may change any Goal of your person; a change puts you on it. Returns `ok` (every change applied), `results` per change (applied or failed), and `goals`, each changed Goal's id, state, title, outcome and revision.";
 var GetGoalsSchema = z7.object({
   goalIds: z7.array(z7.string().uuid()).min(1).max(10).describe("The Goals to read, in order; one to ten IDs."),
   /** Every entry in full. Without it the read carries the person's words, open questions and your
@@ -2188,6 +2189,10 @@ var BrainMessageSchema = z8.union([
     // WHAT IT ASKS THE AGENT, IN UNDER TEN WORDS (owner, 2026-10-15: "Yes, add the summary"): the talker's own, stored
     // as the sent Entry's summary, which the recap's "Sent to <agent>: …" row shows. Absent on results written before it.
     summary: z8.string().optional(),
+    // THE PERSON'S LINES IT CARRIES, IN THEIR WORDS (owner, 2026-11-05: "just deliver my exact words to the agent"): the
+    // `entries` keys of those lines, each relayed whole on the agent's Delivery (`context = false`), where the rest of
+    // `entryKeys` ride as context. Absent on results written before it, and on a message that carries none.
+    carries: z8.array(key).optional(),
     // THE PERSON ASKED TO BE CALLED BACK ONCE THIS AGENT'S WORK IS DONE (turns.md, step 0): the agent owes
     // the call, and its next contact about it rings them (`public.callbacks`).
     callback: z8.literal(true).optional()
@@ -2251,8 +2256,11 @@ var TalkerReplySchema = z9.object({
    *  "Yes, add the summary"), which the recap's "Sent to <agent>: …" row shows; `about` names
    *  handles; `blocks` is the item a question to an agent must be answered before ("" for none);
    *  `callback` is true on a message to the agent doing work the person asked to be called back about
-   *  once it is done (false otherwise): that agent then owes the call (turns.md, step 0). */
-  messages: z9.array(z9.object({ key: str3, to: str3, sentences: strs2, text: str3, summary: str3, about: strs2, blocks: str3, callback: z9.boolean() }).strict()),
+   *  once it is done (false otherwise): that agent then owes the call (turns.md, step 0). `lines` are the
+   *  person's line handles a message to an agent carries ([] for none): the agent receives those lines, in their
+   *  words, and `text` is then only what the talker adds beyond them (owner, 2026-11-05: "just deliver my exact
+   *  words to the agent, keeping the summary as a way for me to navigate them more easily"). */
+  messages: z9.array(z9.object({ key: str3, to: str3, sentences: strs2, text: str3, summary: str3, about: strs2, blocks: str3, callback: z9.boolean(), lines: strs2.optional() }).strict()),
   /** What the call does next: listen, hold (the person asked for a moment) or end (they asked to). */
   then: z9.enum(["listen", "hold", "end"]),
   /** The person's replies to items (replies, owner 2026-10-07): the item's handle, the chosen option
@@ -2270,9 +2278,14 @@ var TalkerReplySchema = z9.object({
   /** The handle of the item to explain ("" for none). */
   explain: str3
 }).strict();
-var TALKER_REPLY_JSON_SCHEMA = (({ $schema: _, ...rest }) => rest)(
+var TALKER_REPLY_JSON_SCHEMA = withEveryMessageField((({ $schema: _, ...rest }) => rest)(
   zodToJsonSchema(TalkerReplySchema, { $refStrategy: "none" })
-);
+));
+function withEveryMessageField(schema) {
+  const item = schema.properties?.messages?.items;
+  if (item?.properties) item.required = Object.keys(item.properties);
+  return schema;
+}
 var str4 = z10.string();
 var strs3 = z10.array(z10.string());
 var FilerReplySchema = z10.object({
@@ -3006,11 +3019,41 @@ var InboxItemSchema = z14.object({
   rev: z14.string().optional()
 });
 var APNS_TOKEN_RE = /^[0-9a-fA-F]{64}$/;
+var PushDeviceIdSchema = z14.string().regex(/^[A-Za-z0-9._:-]{1,200}$/, "not an install id");
+var PushDeviceSchema = z14.object({
+  deviceId: z14.string(),
+  platform: z14.enum(["ios", "android"]),
+  label: z14.string().nullable(),
+  model: z14.string().nullable(),
+  /** Calls and banners go here. */
+  rings: z14.boolean(),
+  /** It has a token a call can ring. */
+  ringable: z14.boolean(),
+  chosenAt: z14.string().nullable(),
+  updatedAt: z14.string()
+});
+var PushTokenDeviceSchema = z14.object({
+  deviceId: z14.string(),
+  rings: z14.boolean(),
+  ask: z14.boolean(),
+  ringsOn: z14.object({ deviceId: z14.string().nullable(), label: z14.string().nullable() }).nullable()
+});
+var PushRingsSchema = z14.object({ rings: z14.boolean() });
 var PushTokenSchema = z14.object({
   voipToken: z14.string().min(1).optional(),
   alertToken: z14.string().min(1).optional(),
   fcmToken: z14.string().min(1).optional(),
-  platform: z14.enum(["ios", "android"])
+  platform: z14.enum(["ios", "android"]),
+  /** WHICH INSTALL POSTED IT (owner, 2026-11-05: "Ask on each new device"). Absent from every
+   *  build before it, and then the post is exactly what it always was: the one row per account.
+   *  With it, the install has its own row and calls ring only where the person chose. */
+  deviceId: PushDeviceIdSchema.optional(),
+  /** The install's name as the person knows it ("iPhone", "iPad"), and its model. */
+  label: z14.string().trim().min(1).max(80).optional(),
+  model: z14.string().trim().min(1).max(80).optional(),
+  /** The person's choice, when the post carries it; absent, the install keeps what it has (and
+   *  its first ring token decides once: it rings unless another install already does). */
+  rings: z14.boolean().optional()
 }).superRefine((v, ctx) => {
   if (v.platform !== "ios") return;
   for (const field of ["voipToken", "alertToken"]) {
@@ -3120,7 +3163,11 @@ var GoalLatestSchema = z14.object({
   titles: z14.array(z14.string()).optional(),
   /** A PROGRESS NOTE'S ONE POINT ("An agent's progress note -> maybe let's cap it at 200 chars"): the
    *  update's own line, before its units; the row caps it at 200. Absent on anything else. */
-  line: z14.string().optional()
+  line: z14.string().optional(),
+  /** THE PERSON'S ENTRIES IT CARRIED TO AN AGENT, IN THEIR WORDS (owner, 2026-11-05: "paraphrasing shouldn't change
+   *  attribution in the UI"): on a message Paigy sent an agent, the person's Entries its Delivery relays whole. A row
+   *  draws it as theirs. Absent on anything else, and from a door older than it. */
+  carries: z14.array(z14.string()).optional()
 });
 var HistoryWorkSchema = z14.object({
   id: z14.string(),
@@ -3389,6 +3436,11 @@ var QueueItemSchema = z14.object({
    *  and a door older than 20261013045542 need not spell them. */
   yours: GoalLatestSchema.nullable().optional(),
   theirs: GoalLatestSchema.nullable().optional(),
+  /** ITS STEPS, COUNTED IN THE DATABASE (owner, 2026-11-04: "Count on the server, and agents make steps"): its
+   *  direct children that were not cancelled, and how many of them are done. The queue holds only a recent
+   *  slice of finished work, so counting `childGoalIds` read "0 of 1" for a project with five done. Absent
+   *  from a door older than this field, or when the count failed: the app then counts what it holds. */
+  steps: z14.object({ total: z14.number().int().nonnegative(), done: z14.number().int().nonnegative() }).nullable().optional(),
   /** WHAT THIS ROW IS, IN TWELVE CHARACTERS (#2928) — the hash of every other field on it, stamped
    *  by the one projection that builds the row (`apps/api/src/goal/queue.ts`). It is how the
    *  incremental read knows a row has not moved: the phone echoes back the revs it holds
@@ -3744,6 +3796,12 @@ var CallRecapSchema = z14.object({
      *  summary (Brain, 2026-10-14). Optional: absent from an API before it. */
     filedOn: z14.array(z14.object({ goalId: z14.string().uuid(), title: z14.string() })).optional(),
     recorded: z14.boolean().optional(),
+    /** On a `said` row: the agents the call SENT those words to, from the sending action's own
+     *  `about.agents` (20261106220220). The review's receipt is drawn from this and from the row's
+     *  own `requestId`, never from the asker of a question the words happened to sit under: on call
+     *  f9670f67 that asker was Interface while the send named Comms. `[]` or absent means nothing
+     *  was sent for that row, which is why the receipt is positive-only. */
+    sentTo: z14.array(z14.object({ id: z14.string().nullable(), name: z14.string() })).optional(),
     settled: z14.object({ requestId: z14.string(), answer: z14.string() }).nullable().optional(),
     acknowledged: z14.boolean().optional(),
     /** On a `put` row: still waiting for the person's answer (not settled, not answered, not put off).
@@ -4310,10 +4368,11 @@ function conversation(e) {
     const need = (e.decisionNeeds ?? []).find((n) => n.requestEntryId === entry.entryId);
     const answer = need ? answers.get(need.decisionNeedId) : void 0;
     const decision = answer ? decided(answer.result) : void 0;
-    const owed = need?.state === "open" && entry.authorParticipant.startsWith("human:");
+    const person = entry.authorParticipant.startsWith("human:");
+    const owed = need?.state === "open" && person;
     const re = thread(entry);
     return compact({
-      id: repliedTo.has(entry.entryId) || owed ? handle2(entry.entryId) : void 0,
+      id: repliedTo.has(entry.entryId) || owed || person ? handle2(entry.entryId) : void 0,
       from: who(entry.authorParticipant),
       at: at(entry.createdAt),
       said: sealed ? "[encrypted]" : entryWords(entry).trim(),

package/dist/{chunk-LGG4IKAW.js → chunk-CVQOJB2S.js}

@@ -3,17 +3,19 @@ import {
   ENABLE_LISTEN_COMMAND,
   READS,
   SENDS,
+  SKILL,
+  SKILL_MARK,
   mcpInputSchema,
   serverInstructions,
   sessionStartHook,
   withGrokPaigyHooks,
   withSessionStartHook
-} from "./chunk-ZCWFBY4B.js";
+} from "./chunk-LRROOCLY.js";
 import {
   CODEX_ENV,
   agentName,
   withCodexEnv
-} from "./chunk-ULCS3CYO.js";
+} from "./chunk-5OKHG3FO.js";
 
 // src/toolset.ts
 var CONFIGURE_DESCRIPTION = "Set this agent up with Paigy \u2014 call it FIRST, before contact, and any time you're unsure who you are. One call does whatever the situation needs: NOT SET UP \u2192 if this machine holds a device credential (the user ran the Paigy desktop app or harness) it hatches an identity INSTANTLY, no code and no approval; otherwise it starts the code ceremony. ALREADY SET UP \u2192 returns your current identity and the two things left to decide, renaming it or logging out. 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 (pick your own; voices: rachel, george, jessica, brian, lily). Safe to call any time: idempotent, and it never writes settings.\n\nTHE CODE CEREMONY does not open a browser; the user enters the code in the Paigy app (or scans `qr`). A result with { user_code, device_code, qr, user_message } has already started polling for approval in the background: you MUST immediately print the `user_message` (the bare code) to the user, AND in that same turn call configure again with that `device_code` to collect the result. It returns the moment the user approves; on { status:'pending' } call again to keep waiting; on { status:'awaiting_confirmation' } (E2EE) show the bare `user_message` verify code and call again to finish. Every result's first text block states the code plainly.\n\nOn { status:'paired' }, or whenever it returns `enable_command`, ALWAYS follow the `enable_prompt`: PRINT that command for the user to run, so Paigy's tools stop prompting each time. 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.\n\nLOG OUT with { logOut: true }: it logs out THIS agent only \u2014 its token is revoked server-side and its local entry removed. Other agents and this device's credential are untouched, and a later configure re-hatches instantly while the device credential exists. Disconnecting the device itself is not an agent tool.";
@@ -284,6 +286,41 @@ var HOOK_CONFIGS = [
   { harness: "Claude Code", path: () => join(homedir(), ".claude", "settings.json") },
   { harness: "Codex", path: () => join(homedir(), ".codex", "hooks.json") }
 ];
+var SKILL_DIRS = [
+  { harness: "Claude Code", present: () => join(homedir(), ".claude"), skills: () => join(homedir(), ".claude", "skills") },
+  { harness: "Codex", present: () => process.env["CODEX_HOME"] ?? join(homedir(), ".codex"), skills: () => join(homedir(), ".agents", "skills") },
+  { harness: "Grok", present: () => join(homedir(), ".grok"), skills: () => join(homedir(), ".grok", "skills") }
+];
+function installPaigySkill() {
+  const out = [];
+  for (const { harness, present, skills } of SKILL_DIRS) {
+    if (!existsSync(present())) continue;
+    const path = join(skills(), "paigy", "SKILL.md");
+    let existing = null;
+    try {
+      existing = existsSync(path) ? readFileSync(path, "utf8") : null;
+    } catch (e) {
+      out.push({ harness, path, ok: false, why: e.message });
+      continue;
+    }
+    if (existing !== null && !existing.includes(SKILL_MARK)) {
+      out.push({ harness, path, ok: false, why: "not Paigy's \u2014 left alone" });
+      continue;
+    }
+    if (existing === SKILL) {
+      out.push({ harness, path, ok: true, already: true });
+      continue;
+    }
+    try {
+      mkdirSync(dirname(path), { recursive: true });
+      writeFileSync(path, SKILL);
+      out.push({ harness, path, ok: true, already: false });
+    } catch (e) {
+      out.push({ harness, path, ok: false, why: e.message });
+    }
+  }
+  return out;
+}
 function installSessionListening() {
   const script = join(homedir(), ".paigy", "hooks", "session-start.sh");
   try {
@@ -356,5 +393,6 @@ export {
   PAIGY_TOOL_IDS,
   paigyToolsAllowlisted,
   enablePaigyTools,
+  installPaigySkill,
   installSessionListening
 };

package/dist/{chunk-ZCWFBY4B.js → chunk-LRROOCLY.js}

@@ -130,11 +130,11 @@ var CompleteChangeSchema = CompletionSchema.omit({ causedBy: true, shipped: true
 var ASKING_RULES = `HOW TO ASK:
 1. One question per object in \`questions\`, so each is answered on its own.
 2. \`goalId\` names the existing Goal it is about (create one with manage_goals first); the answer comes back there.
-3. \`workItBlocks\` only when you are truly blocked: it asks for a call.
+3. They asked you to call? \`userExplicitlyRequested:"call"\`; \`workItBlocks\` rings when blocked.
 4. No while-loops. While any Call is open, even one your question joined from their items, keep receiving through empty windows; otherwise stop at one: the answer reaches you on the Goal. Yield only with a listener or wakeup.
 5. One question, one row: never re-send one still waiting; take back one that no longer matters with \`withdrawQuestionIds\`.
 6. Read the Goal before asking; never re-ask what was answered or shipped. \`replied\` means they chose no option: it is still yours to settle.
-7. Give options when you have them. Each label names its choice in full (never "Option 2"); never add "Other". \`pickMode\`: one (default), many, rank.
+7. Give options when you have them. Each label names its choice in full (never "Option 2"); never add "Other".
 8. A diagnosis says when, why and how it happens, then proposes one fix.
 9. Give a report its \`reply\`: one line in THEIR voice for THAT report, so you learn whether they verified it or only received it. Required when it is delivered or its Goal is done.`;
 function draft2020(node) {
@@ -176,7 +176,7 @@ var reason = z5.string().trim().min(1).max(500).describe("Why, as an explanation
 var actionFits = (b) => b.blocked.type === "goal" === (b.action !== "answer");
 var ACTION_FITS = "a goal is blocked from start or complete; a question from answer";
 var userExplicitlyRequested = z5.enum(["any", "call"]).optional().describe(
-  `Only what the person said about THIS message, in so many words: "any" when they asked you to send it to them ("send it to my phone", "message me the result"), "call" when they asked to be called about it. It is then delivered (a call rings for the whole contact, and carries everything waiting on them); omitted, an update is only recorded as the Goal's progress unless the person needs it. Never set it to make a message louder.`
+  'What the person asked for about THIS message, in so many words: "any" when they asked you to send it to them ("send it to my phone", "message me the result"), "call" when they asked to be called about it. It is then delivered (a call rings for the whole contact, and carries everything waiting on them); omitted, an update is only recorded as the Goal\'s progress unless the person needs it. ALSO "any" whenever this message directly answers a question they asked you, wherever they asked it -- on a call, in a reply, in passing: their question is the request, so it is delivered every time, even with no pending question of theirs on file and even if they never said to send it. A correction of something you or another agent told them is such an answer. Never set it to make a message louder. This is the field that rings a phone: "call" here is how you call them when they asked you to, and `help` has the whole mechanism.'
 );
 var units = z5.array(UnitInputSchema).optional().describe(
   `The context this message needs, as up to ${UNITS_MAX} units in reading order, each {title, body}: a title of at most ${UNIT_TITLE_MAX} characters and a body of at most ${UNIT_BODY_MAX}. One idea per unit: context they may open, never something they must hear. Leave it out when the main text says it all. Over a cap is refused by name (ask_too_long, too_many_units, unit_title_too_long, unit_body_too_long) and nothing is sent.`
@@ -396,13 +396,14 @@ LENGTH: the question, message or answer is the one point, at most ${ASK_MAX} cha
 UPDATES ask nothing. One reaches the person only when they asked for it, it answers something they said, or its Goal is done; else it is kept as progress. One that reaches them joins an open report card or a live call.
 
 RECEIVING: contact({}) waits ~45 s; contact({wait:false}) returns \`events\` at once. Confirm the ones you handled with contact({ackEventIds}).`;
-var GUIDE = '# Paigy\n\nThe user is remote. Reach them only through Paigy\'s tools, never the terminal. The server\'s own instructions and each tool\'s description are the contract: read them. Every read ends in `next`, the one step to take.\n\nThis same guide is inside the MCP: the `help` tool (whole, or one `topic`) and the `/mcp__paigy__help` prompt. `/mcp__paigy__welcome` starts a session.\n\nHosted (no machine): skip Pairing and Listening; answers wake you.\n\n## Pairing\n\n- Call `configure` first. With a device credential on this machine it hatches you at once.\n- Otherwise print its `user_message` to the user, then do what the result says:\n  - `awaiting_approval`: call `configure` again with its `device_code` in the same turn. On `pending`, call again.\n  - `awaiting_confirmation`: end your turn with the code as your whole reply; call `configure` with the `device_code` next turn. Calling it in the same turn drops the code.\n- When it returns `enable_command`, print it for the user to run. Do not run it yourself.\n- `configure({ logOut: true })` logs out only this agent, and only when the user asks.\n\n## Listening\n\n- Call `listen` once per session.\n  - `listening`: done.\n  - `receiving`: a listener runs but cannot wake you. Do not start a second.\n  - `unpaired`: call `configure`.\n  - `start`: run its `command` exactly, now.\n- Claude Code: run it with the **Monitor** tool, never a background Bash command. Start it again whenever the monitor expires.\n- Codex: run its `command` as a long-running background process. It queues each answer into this thread (`CODEX_THREAD_ID`).\n- Grok: run it with the **monitor** tool, never a background shell command. Start it again whenever the monitor expires.\n- With no `listen` tool, run `npx -y -p @paigy/mcp@latest paigy-listen --brief` the same way.\n- One listener per session. A `paigy-listen` in `ps` belongs to another session; ask `listen`, never `ps`.\n- Each line it prints is work: receive, read the Goal, act.\n\n## Receiving\n\n- On startup and after every wake or listener line: `contact({ wait: false })`.\n- Events: `question` (you owe an answer: send `answers`), `update` (something new on your Goal: an answer, a reply, a review), `instruction` (work sent to you).\n- Read the Goal with `get_goals` before acting. An answer arrives as an `update` event and lands on the question\'s Goal. A question reading `replied` means they chose no option: settle it from their words.\n- Acknowledge each event you handled: `contact({ ackEventIds })`. Reading acknowledges nothing; events repeat until acknowledged. A `question` event is answered, never acknowledged away.\n- `contact({ wait: true })` waits about 45 s. On `expired`, wait again without re-sending, or stop. No while-loops: while any Call is open, keep receiving through empty windows; otherwise stop at one empty window.\n\n## Asking\n\n- One question per object in `questions`, at most 80 characters. Context goes in `units`: at most 12, title \u226450, body \u2264200, one idea each.\n- `goalId` names an existing Goal. Create it with `manage_goals` first.\n- Give options when you have them: up to 6, label \u226450 naming the choice in full, `hint` \u2264200 saying what it does. Never "Other" or "Option 2". `pickMode`: `one` (default), `many`, `rank`.\n- `workItBlocks` only when you are truly stopped: it asks for a call.\n- Read the Goal before asking. Never re-ask an open or answered question, or one whose work shipped.\n- Take back a question that no longer matters: `withdrawQuestionIds`.\n- An answer you give (`answers`) is at most 80 characters.\n\n## Updates and completions\n\n- An update (`updates`: `message` \u226480, `goalIds`) asks nothing. It reaches the user only when they asked for it, when it answers something they said, or when its Goal is done; otherwise it stays on the Goal as progress.\n- Updates never complete a Goal.\n- One load-bearing point per report: `message` is the point they must not miss, and a second point that would go wrong or stay unclear later if they missed it is its own update. `units` are context they may open, never something they must hear.\n- `reply` is the button in the user\'s voice instead of "Got it", \u226450 characters ("Sounds good, I\'ll test later"). Required (`reply_required`) when the update is delivered on request (`userExplicitlyRequested`) or any Goal it names is already done.\n- Set `userExplicitlyRequested` only to relay the user\'s own words: `"any"` for "send it to me", `"call"` for "call me". Never to make a message louder.\n- Finish with a completion (`contact.completions`, or `manage_goals` kind `complete`): `goalId`, `message` \u226450, `reply` \u226450, optional `units`, optional next-step `options` {label, hint}. It closes and reports in one step. Say only what your evidence supports.\n- Read `results`: each item applies on its own, and a failed one names why.\n\n## Goals\n\n- `manage_goals` `changes`, applied in order:\n  - `create`: `title` (1-5 words) and `outcome` (one paragraph, \u2264500). More work is child Goals: `parentGoalId`. New ids come back in `results[i].goalId`.\n  - `assign`: `ownerId`, a participant as `check_activity` shows it.\n  - `defer`: `until`. You are woken when it passes. This is how you follow up later.\n  - `dependency`: `add`/`remove`; `goalId` waits on `dependsOnGoalId` to `start` or `complete`.\n  - `edit`, `move`, `state` (open, completed, canceled).\n- Any open question on a Goal, anyone\'s, blocks its completion (`goal_blocked`). Before completing, withdraw yours, finish or move its required children, and clear its dependencies.\n- On `goal_revision_conflict`, read the Goal again and reconsider.\n- Before overlapping work, read `check_activity` and the Goal\'s other contributors. Every Goal of your person is open to you; your first write puts you on it.\n- `search` finds earlier words, Goals and answers. Nothing found is not proof of absence.\n\n## Calls\n\n- Call only when the user asked: `userExplicitlyRequested: "call"` on that item. A question with `workItBlocks` may ring too.\n- Any contact while the user is on a call joins that call (`joinedCall` in `results`). Several questions arrive as one call.\n- While any Call is open, keep receiving.\n- An open Call Delivery is not proof it rang. `get_delivery` reads a Call\'s state, and with `transcript: true` what was said.\n';
-var HELP_TOPICS = ["pairing", "listening", "receiving", "asking", "updates", "goals", "calls"];
+var GUIDE = '# Paigy\n\nThe user is remote. Reach them only through Paigy\'s tools, never the terminal. The server\'s own instructions and each tool\'s description are the contract: read them. Every read ends in `next`, the one step to take.\n\nThis same guide is inside the MCP: the `help` tool (whole, or one `topic`) and the `/mcp__paigy__help` prompt. `/mcp__paigy__welcome` starts a session; `/mcp__paigy__organize` sets up a person\'s work as a board.\n\nHosted (no machine): skip Pairing and Listening; answers wake you.\n\n## Pairing\n\n- Call `configure` first. With a device credential on this machine it hatches you at once.\n- Otherwise print its `user_message` to the user, then do what the result says:\n  - `awaiting_approval`: call `configure` again with its `device_code` in the same turn. On `pending`, call again.\n  - `awaiting_confirmation`: end your turn with the code as your whole reply; call `configure` with the `device_code` next turn. Calling it in the same turn drops the code.\n- When it returns `enable_command`, print it for the user to run. Do not run it yourself.\n- `configure({ logOut: true })` logs out only this agent, and only when the user asks.\n\n## Listening\n\n- Call `listen` once per session.\n  - `listening`: done.\n  - `receiving`: a listener runs but cannot wake you. Do not start a second.\n  - `unpaired`: call `configure`.\n  - `start`: run its `command` exactly, now.\n- Claude Code: run it with the **Monitor** tool, never a background Bash command. Start it again whenever the monitor expires.\n- Codex: run its `command` as a long-running background process. It queues each answer into this thread (`CODEX_THREAD_ID`).\n- Grok: run it with the **monitor** tool, never a background shell command. Start it again whenever the monitor expires.\n- With no `listen` tool, run `npx -y -p @paigy/mcp@latest paigy-listen --brief` the same way.\n- One listener per session. A `paigy-listen` in `ps` belongs to another session; ask `listen`, never `ps`.\n- Each line it prints is work: receive, read the Goal, act.\n\n## Receiving\n\n- On startup and after every wake or listener line: `contact({ wait: false })`.\n- Events: `question` (you owe an answer: send `answers`), `update` (something new on your Goal: an answer, a reply, a review), `instruction` (work sent to you).\n- Read the Goal with `get_goals` before acting. An answer arrives as an `update` event and lands on the question\'s Goal. A question reading `replied` means they chose no option: settle it from their words.\n- Acknowledge each event you handled: `contact({ ackEventIds })`. Reading acknowledges nothing; events repeat until acknowledged. A `question` event is answered, never acknowledged away.\n- `contact({ wait: true })` waits about 45 s. On `expired`, wait again without re-sending, or stop. No while-loops: while any Call is open, keep receiving through empty windows; otherwise stop at one empty window.\n\n## Asking\n\n- One question per object in `questions`, at most 80 characters. Context goes in `units`: at most 12, title \u226450, body \u2264200, one idea each.\n- `goalId` names an existing Goal. Create it with `manage_goals` first.\n- Give options when you have them: up to 6, label \u226450 naming the choice in full, `hint` \u2264200 saying what it does. Never "Other" or "Option 2". `pickMode`: `one` (default), `many`, `rank`.\n- `workItBlocks` only when you are truly stopped: it asks for a call.\n- Read the Goal before asking. Never re-ask an open or answered question, or one whose work shipped.\n- Take back a question that no longer matters: `withdrawQuestionIds`.\n- An answer you give (`answers`) is at most 80 characters.\n\n## Updates and completions\n\n- An update (`updates`: `message` \u226480, `goalIds`) asks nothing. It reaches the user only when they asked for it, when it answers something they said, or when its Goal is done; otherwise it stays on the Goal as progress.\n- Updates never complete a Goal.\n- One load-bearing point per report: `message` is the point they must not miss, and a second point that would go wrong or stay unclear later if they missed it is its own update. `units` are context they may open, never something they must hear.\n- `reply` is the button in the user\'s voice instead of "Got it", \u226450 characters ("Sounds good, I\'ll test later"). Required (`reply_required`) when the update is delivered on request (`userExplicitlyRequested`) or any Goal it names is already done.\n- Set `userExplicitlyRequested` only to relay the user\'s own words: `"any"` for "send it to me", `"call"` for "call me". Never to make a message louder.\n- Finish with a completion (`contact.completions`, or `manage_goals` kind `complete`): `goalId`, `message` \u226450, `reply` \u226450, optional `units`, optional next-step `options` {label, hint}. It closes and reports in one step. Say only what your evidence supports.\n- Read `results`: each item applies on its own, and a failed one names why.\n\n## Goals\n\n- `manage_goals` `changes`, applied in order:\n  - `create`: `title` (1-5 words) and `outcome` (one paragraph, \u2264500). More work is child Goals: `parentGoalId`. New ids come back in `results[i].goalId`.\n  - `assign`: `ownerId`, a participant as `check_activity` shows it.\n  - `defer`: `until`. You are woken when it passes. This is how you follow up later.\n  - `dependency`: `add`/`remove`; `goalId` waits on `dependsOnGoalId` to `start` or `complete`.\n  - `edit`, `move`, `state` (open, completed, canceled).\n- Shape your work as projects with steps. Create a project under its area (`create` with `parentGoalId` = the area), then one child Goal per step; complete each step as it lands. A top-level Goal that has children is an area, not a project: never hang steps straight off a top-level Goal. The person\'s Work tab shows a project\'s progress as its steps, "3 of 5 steps done"; a project with no steps shows none. When you touch an older Goal of yours that sits flat or under a finished project, move it into that shape (`move`). A flat Goal is still valid; never reshape another agent\'s Goals.\n- Any open question on a Goal, anyone\'s, blocks its completion (`goal_blocked`). Before completing, withdraw yours, finish or move its required children, and clear its dependencies.\n- On `goal_revision_conflict`, read the Goal again and reconsider.\n- Before overlapping work, read `check_activity` and the Goal\'s other contributors. Every Goal of your person is open to you; your first write puts you on it.\n- `search` finds earlier words, Goals and answers. Nothing found is not proof of absence.\n\n## Organize\n\nWhen the person asks you to set up or organize their work ("set up my project", "help me manage all this", several products or parts to juggle), turn it into a board they can run like a team. Their Work tab shows it.\n\n- Learn the work first: read the repo and their Goals (`get_goals`, `search`). Ask only what you cannot read, at most three questions, each its own question.\n- The shape: an area per product or business (a top-level Goal); under it a project per part that moves on its own (landing page, graphics, web app, mobile app, launch); under each project its steps, three to seven, each an outcome someone can finish and check.\n- Propose before you build. Create one Goal for the setup itself, then ask one question on it: the tree in `units` (one unit per project: its title, then its steps), options "Build it" and "Change it: I\'ll say how". Create nothing else until they answer.\n- On "Build it", one `manage_goals` call per level, since a parent\'s id comes back in `results[i].goalId`: the areas, then their projects (`parentGoalId`), then every step; then a `dependency` where a project waits on another (web on the design). Never copy work that already has a Goal: yours move into the tree (`move`); another agent\'s stay where they are, named in the proposal. Then complete the setup Goal.\n- Report how to run it, and hand over one brief per project for the person to paste as that session\'s first message. Each brief names the project\'s Goal (title and id) and says: call `listen` and keep the listener running; receive with `contact({ wait: false })` at startup and after every wake; work the steps in order and complete each as it lands; report progress as updates on the project; ask anything you are blocked on through Paigy, as a question on that step\'s Goal (`workItBlocks` only when it truly stops you), never in the terminal.\n- One session per project, plus one lead session that keeps the board current. Any agent, Claude, Codex or another, can pick up any Goal; `check_activity` shows who is on what. A subagent inside a session shares that session\'s identity and listener: it may ask through Paigy, but never starts a listener of its own.\n- Keep it current as you work: complete each step as it lands and add a step when new work appears. Never reshape another agent\'s Goals.\n\n## Calls\n\n- Call only when the user asked: `userExplicitlyRequested: "call"` on that item. A question with `workItBlocks` may ring too.\n- Any contact while the user is on a call joins that call (`joinedCall` in `results`). Several questions arrive as one call.\n- While any Call is open, keep receiving.\n- An open Call Delivery is not proof it rang. `get_delivery` reads a Call\'s state, and with `transcript: true` what was said.\n';
+var SKILL_MARK = "<!-- paigy-skill";
+var HELP_TOPICS = ["pairing", "listening", "receiving", "asking", "updates", "goals", "organize", "calls"];
 var unknownTopic = (topic) => `unknown_topic: ${JSON.stringify(topic)} is not a section of the guide. Topics: ${HELP_TOPICS.join(", ")}; or omit topic for the whole guide.`;
 var HelpSchema = z6.object({
   topic: z6.enum(HELP_TOPICS, { errorMap: (_issue, ctx) => ({ message: unknownTopic(ctx.data) }) }).optional().describe("One section of the guide. Omit it for the whole guide.")
 }).strict();
-var HELP_DESCRIPTION = "Start here: how to use Paigy, in full \u2014 pairing, listening, receiving, asking, updates and completions, Goals and calls. Pass a topic for one section. Read-only; needs no setup.";
+var HELP_DESCRIPTION = "Start here: how to use Paigy, in full \u2014 pairing, listening, receiving, asking, updates and completions, Goals, organizing work, and calls. Pass a topic for one section. Read-only; needs no setup.";
 function section(topic) {
   const parts = GUIDE.split(/^(?=## )/m);
   const found = parts.find((p) => p.slice(3).toLowerCase().startsWith(topic));
@@ -423,7 +424,8 @@ var AGENT_PROMPTS = [
     description: "How to use Paigy: the whole guide, or one topic of it.",
     arguments: [{ name: "topic", description: `One section: ${HELP_TOPICS.join(", ")}. Omit it for the whole guide.`, required: false }]
   },
-  { name: "welcome", description: "Start here: who you are on Paigy, then listen and collect your open work." }
+  { name: "welcome", description: "Start here: who you are on Paigy, then listen and collect your open work." },
+  { name: "organize", description: "Set up the person's work as a board: areas, projects and steps, proposed on a card before anything is built." }
 ];
 function promptText(name, facts) {
   if (name === "help") {
@@ -446,6 +448,11 @@ ${helpView(parsed.data).guide}`;
 ${steps.map((s, i) => `${i + 1}. ${s}`).join("\n")}
 
 The whole guide is the \`help\` tool (or /mcp__paigy__help).`;
+  }
+  if (name === "organize") {
+    return `Help me organize my work with Paigy: propose a board of areas, projects and steps, and build it once I approve. Follow this:
+
+${helpView({ topic: "organize" }).guide}`;
   }
   throw new Error(`unknown_prompt: ${JSON.stringify(name)}. Prompts: ${AGENT_PROMPTS.map((p) => p.name).join(", ")}.`);
 }
@@ -500,7 +507,7 @@ var CreateChange = z7.object({
   title: goalTitle,
   outcome: goalOutcome,
   ownerId: z7.string().trim().min(1).optional().describe("Who owns the work: an agent's participant (as check_activity shows it) or the person's. Omitted: you."),
-  parentGoalId: z7.string().uuid().optional().describe("The Goal it belongs under. Omitted: a root."),
+  parentGoalId: z7.string().uuid().optional().describe("The Goal it belongs under. Omitted: a root. A project with several parts: create it, then one child per step under it; the person's Work tab counts a project's progress in those steps."),
   sourceEntryIds: z7.array(z7.string().uuid()).max(20).optional().describe("The whole Entries the work came from, ones you can read.")
 }).strict();
 var EditChange = z7.object({ kind: z7.literal("edit"), goalId: changedGoal, title: goalTitle.optional(), outcome: goalOutcome.optional() }).strict();
@@ -545,7 +552,7 @@ var ManageGoalsSchema = z7.object({
 var ManageGoalsToolSchema = z7.object({
   changes: z7.array(z7.discriminatedUnion("kind", [CreateChange, CompleteChangeSchema, EditChange, StateChange, AssignChange, DeferChange, MoveChange, DependencyChange])).min(1).max(50).describe("The changes, applied in order, each on its own.")
 }).strict().superRefine((v, ctx) => editNames(v.changes, ctx));
-var MANAGE_GOALS_DESCRIPTION = "Create, edit, assign, organize or close work. Every change here changes Goals; answering, withdrawing or asking Questions stays in contact. Each change applies independently: a refused one names why (`results[i].error`, e.g. goal_revision_conflict, goal_children_open, goal_not_found) and the rest still apply, so read every result: a partial result is never a complete success. Kinds: complete (goalId, message capped at 50 characters, units, reply, optional next-step options {label, hint}) closes and reports atomically, exactly as contact.completions; create (title, outcome, ownerId, parentGoalId, sourceEntryIds) returns the new Goal's id in `results[i].goalId`, in the order requested, to use in later calls (an outcome is one paragraph, at most 500 characters: split more into child Goals with parentGoalId); edit (title and/or outcome); state (open, completed, canceled); assign (ownerId); defer (until: the Goal waits until then and its owner is woken when it passes; null takes it back); move (parentGoalId, or null for a root: only this Goal moves); dependency (add or remove: goalId waits on dependsOnGoalId to start or to complete). A Goal cannot be completed while its required children or dependencies remain open: finish or move them first. Finishing the children does not prove the parent's own work is done. An edit applies at the version you last read: if someone changed the Goal since, it is refused as goal_revision_conflict, so read it again (get_goals) and reconsider. You may change any Goal of your person; a change puts you on it. Returns `ok` (every change applied), `results` per change (applied or failed), and `goals`, each changed Goal's id, state, title, outcome and revision.";
+var MANAGE_GOALS_DESCRIPTION = "Create, edit, assign, organize or close work. SHAPE IT AS PROJECTS WITH STEPS: create a project under its area (parentGoalId; a top-level Goal with children is an area), then each part as its child Goal, so the person sees N of M steps. Move a flat or orphaned Goal of yours into that shape when you touch it; a flat Goal is valid. Every change here changes Goals; answering, withdrawing or asking Questions stays in contact. Each change applies independently: a refused one names why (`results[i].error`, e.g. goal_revision_conflict, goal_children_open, goal_not_found) and the rest still apply, so read every result: a partial result is never a complete success. Kinds: complete (goalId, message capped at 50 characters, units, reply, optional next-step options {label, hint}) closes and reports atomically, exactly as contact.completions; create (title, outcome, ownerId, parentGoalId, sourceEntryIds) returns the new Goal's id in `results[i].goalId`, in the order requested, to use in later calls (an outcome is one paragraph, at most 500 characters: split more into child Goals with parentGoalId); edit (title and/or outcome); state (open, completed, canceled); assign (ownerId); defer (until: the Goal waits until then and its owner is woken when it passes; null takes it back); move (parentGoalId, or null for a root: only this Goal moves); dependency (add or remove: goalId waits on dependsOnGoalId to start or to complete). A Goal cannot be completed while its required children or dependencies remain open: finish or move them first. Finishing the children does not prove the parent's own work is done. An edit applies at the version you last read: if someone changed the Goal since, it is refused as goal_revision_conflict, so read it again (get_goals) and reconsider. You may change any Goal of your person; a change puts you on it. Returns `ok` (every change applied), `results` per change (applied or failed), and `goals`, each changed Goal's id, state, title, outcome and revision.";
 var GetGoalsSchema = z7.object({
   goalIds: z7.array(z7.string().uuid()).min(1).max(10).describe("The Goals to read, in order; one to ten IDs."),
   /** Every entry in full. Without it the read carries the person's words, open questions and your
@@ -596,10 +603,11 @@ var LISTEN_COMMAND = "npx -y -p @paigy/mcp@latest paigy-listen --brief";
 var LISTEN_MONITOR = "your harness's MONITOR tool, the kind that wakes you on every line it prints (in Claude Code: Monitor, not a background Bash command, which only tells you when it exits; in Grok: the monitor tool, the same way)";
 function serverInstructions(opts) {
   const waits = opts.waits ? `contact({wait:true}) waits ~45 s for a reply to what you sent; contact({}) for anything addressed to you. Call \`listen\` once to wake at rest.` : "A contact here returns after one read; answers wake you, and contact({wait:false}) collects them.";
-  return `New here? Call help. On startup and after a wake, contact({wait:false}) returns your events. They repeat until acknowledged with contact({ackEventIds}); reading does not. get_goals reads a Goal's conversation; your first write puts you on it; every Goal of your person is open to you. manage_goals creates, assigns and organizes work; to follow up, defer the Goal (woken when due). Complete and report at once: contact.completions or manage_goals kind:complete. Every read ends in \`next\`: your next step. ${waits} Report progress as a contact update (what changed for them; causedBy, shipped); one they don't need yet stays on the Goal. An open Call is not proof it rang. Your user is remote: reach them only through Paigy, never the terminal.
+  return `New here? Call help. On startup and after a wake, contact({wait:false}) returns your events. They repeat until acknowledged with contact({ackEventIds}); reading doesn't. get_goals reads a Goal; your first write puts you on it; every Goal of your person is open to you. manage_goals creates, assigns and organizes work as projects with steps; to follow up, defer it (woken when due). Complete and report at once: contact.completions or manage_goals kind:complete. Every read ends in \`next\`: your next step. ${waits} Report progress as a contact update (what changed for them; causedBy, shipped); one they don't need yet stays on the Goal. An open Call isn't proof it rang. Your user is remote: reach them only through Paigy, never the terminal.
 
 ${ASKING_RULES}`;
 }
+var SKILL = '---\nname: paigy\ndescription: Reach the user through Paigy. Use whenever you need to tell the user something, ask them a question, get a decision or approval, call their phone, wait for or receive their answers, start or check the Paigy listener, or create, assign, defer or complete Paigy Goals.\n---\n<!-- paigy-skill \xB7 source: paigy monorepo packs/skill/paigy/SKILL.md; mirrored to paigy-ai/claude plugins/paigy/skills/paigy/SKILL.md and written by https://paigy.ai/install, which replaces only a file carrying this line. Edit the source, never a copy. -->\n\n# Paigy\n\nThe user is remote. Reach them only through Paigy\'s tools, never the terminal. The server\'s own instructions and each tool\'s description are the contract: read them. Every read ends in `next`, the one step to take.\n\nThis same guide is inside the MCP: the `help` tool (whole, or one `topic`) and the `/mcp__paigy__help` prompt. `/mcp__paigy__welcome` starts a session; `/mcp__paigy__organize` sets up a person\'s work as a board.\n\nHosted (no machine): skip Pairing and Listening; answers wake you.\n\n## Pairing\n\n- Call `configure` first. With a device credential on this machine it hatches you at once.\n- Otherwise print its `user_message` to the user, then do what the result says:\n  - `awaiting_approval`: call `configure` again with its `device_code` in the same turn. On `pending`, call again.\n  - `awaiting_confirmation`: end your turn with the code as your whole reply; call `configure` with the `device_code` next turn. Calling it in the same turn drops the code.\n- When it returns `enable_command`, print it for the user to run. Do not run it yourself.\n- `configure({ logOut: true })` logs out only this agent, and only when the user asks.\n\n## Listening\n\n- Call `listen` once per session.\n  - `listening`: done.\n  - `receiving`: a listener runs but cannot wake you. Do not start a second.\n  - `unpaired`: call `configure`.\n  - `start`: run its `command` exactly, now.\n- Claude Code: run it with the **Monitor** tool, never a background Bash command. Start it again whenever the monitor expires.\n- Codex: run its `command` as a long-running background process. It queues each answer into this thread (`CODEX_THREAD_ID`).\n- Grok: run it with the **monitor** tool, never a background shell command. Start it again whenever the monitor expires.\n- With no `listen` tool, run `npx -y -p @paigy/mcp@latest paigy-listen --brief` the same way.\n- One listener per session. A `paigy-listen` in `ps` belongs to another session; ask `listen`, never `ps`.\n- Each line it prints is work: receive, read the Goal, act.\n\n## Receiving\n\n- On startup and after every wake or listener line: `contact({ wait: false })`.\n- Events: `question` (you owe an answer: send `answers`), `update` (something new on your Goal: an answer, a reply, a review), `instruction` (work sent to you).\n- Read the Goal with `get_goals` before acting. An answer arrives as an `update` event and lands on the question\'s Goal. A question reading `replied` means they chose no option: settle it from their words.\n- Acknowledge each event you handled: `contact({ ackEventIds })`. Reading acknowledges nothing; events repeat until acknowledged. A `question` event is answered, never acknowledged away.\n- `contact({ wait: true })` waits about 45 s. On `expired`, wait again without re-sending, or stop. No while-loops: while any Call is open, keep receiving through empty windows; otherwise stop at one empty window.\n\n## Asking\n\n- One question per object in `questions`, at most 80 characters. Context goes in `units`: at most 12, title \u226450, body \u2264200, one idea each.\n- `goalId` names an existing Goal. Create it with `manage_goals` first.\n- Give options when you have them: up to 6, label \u226450 naming the choice in full, `hint` \u2264200 saying what it does. Never "Other" or "Option 2". `pickMode`: `one` (default), `many`, `rank`.\n- `workItBlocks` only when you are truly stopped: it asks for a call.\n- Read the Goal before asking. Never re-ask an open or answered question, or one whose work shipped.\n- Take back a question that no longer matters: `withdrawQuestionIds`.\n- An answer you give (`answers`) is at most 80 characters.\n\n## Updates and completions\n\n- An update (`updates`: `message` \u226480, `goalIds`) asks nothing. It reaches the user only when they asked for it, when it answers something they said, or when its Goal is done; otherwise it stays on the Goal as progress.\n- Updates never complete a Goal.\n- One load-bearing point per report: `message` is the point they must not miss, and a second point that would go wrong or stay unclear later if they missed it is its own update. `units` are context they may open, never something they must hear.\n- `reply` is the button in the user\'s voice instead of "Got it", \u226450 characters ("Sounds good, I\'ll test later"). Required (`reply_required`) when the update is delivered on request (`userExplicitlyRequested`) or any Goal it names is already done.\n- Set `userExplicitlyRequested` only to relay the user\'s own words: `"any"` for "send it to me", `"call"` for "call me". Never to make a message louder.\n- Finish with a completion (`contact.completions`, or `manage_goals` kind `complete`): `goalId`, `message` \u226450, `reply` \u226450, optional `units`, optional next-step `options` {label, hint}. It closes and reports in one step. Say only what your evidence supports.\n- Read `results`: each item applies on its own, and a failed one names why.\n\n## Goals\n\n- `manage_goals` `changes`, applied in order:\n  - `create`: `title` (1-5 words) and `outcome` (one paragraph, \u2264500). More work is child Goals: `parentGoalId`. New ids come back in `results[i].goalId`.\n  - `assign`: `ownerId`, a participant as `check_activity` shows it.\n  - `defer`: `until`. You are woken when it passes. This is how you follow up later.\n  - `dependency`: `add`/`remove`; `goalId` waits on `dependsOnGoalId` to `start` or `complete`.\n  - `edit`, `move`, `state` (open, completed, canceled).\n- Shape your work as projects with steps. Create a project under its area (`create` with `parentGoalId` = the area), then one child Goal per step; complete each step as it lands. A top-level Goal that has children is an area, not a project: never hang steps straight off a top-level Goal. The person\'s Work tab shows a project\'s progress as its steps, "3 of 5 steps done"; a project with no steps shows none. When you touch an older Goal of yours that sits flat or under a finished project, move it into that shape (`move`). A flat Goal is still valid; never reshape another agent\'s Goals.\n- Any open question on a Goal, anyone\'s, blocks its completion (`goal_blocked`). Before completing, withdraw yours, finish or move its required children, and clear its dependencies.\n- On `goal_revision_conflict`, read the Goal again and reconsider.\n- Before overlapping work, read `check_activity` and the Goal\'s other contributors. Every Goal of your person is open to you; your first write puts you on it.\n- `search` finds earlier words, Goals and answers. Nothing found is not proof of absence.\n\n## Organize\n\nWhen the person asks you to set up or organize their work ("set up my project", "help me manage all this", several products or parts to juggle), turn it into a board they can run like a team. Their Work tab shows it.\n\n- Learn the work first: read the repo and their Goals (`get_goals`, `search`). Ask only what you cannot read, at most three questions, each its own question.\n- The shape: an area per product or business (a top-level Goal); under it a project per part that moves on its own (landing page, graphics, web app, mobile app, launch); under each project its steps, three to seven, each an outcome someone can finish and check.\n- Propose before you build. Create one Goal for the setup itself, then ask one question on it: the tree in `units` (one unit per project: its title, then its steps), options "Build it" and "Change it: I\'ll say how". Create nothing else until they answer.\n- On "Build it", one `manage_goals` call per level, since a parent\'s id comes back in `results[i].goalId`: the areas, then their projects (`parentGoalId`), then every step; then a `dependency` where a project waits on another (web on the design). Never copy work that already has a Goal: yours move into the tree (`move`); another agent\'s stay where they are, named in the proposal. Then complete the setup Goal.\n- Report how to run it, and hand over one brief per project for the person to paste as that session\'s first message. Each brief names the project\'s Goal (title and id) and says: call `listen` and keep the listener running; receive with `contact({ wait: false })` at startup and after every wake; work the steps in order and complete each as it lands; report progress as updates on the project; ask anything you are blocked on through Paigy, as a question on that step\'s Goal (`workItBlocks` only when it truly stops you), never in the terminal.\n- One session per project, plus one lead session that keeps the board current. Any agent, Claude, Codex or another, can pick up any Goal; `check_activity` shows who is on what. A subagent inside a session shares that session\'s identity and listener: it may ask through Paigy, but never starts a listener of its own.\n- Keep it current as you work: complete each step as it lands and add a step when new work appears. Never reshape another agent\'s Goals.\n\n## Calls\n\n- Call only when the user asked: `userExplicitlyRequested: "call"` on that item. A question with `workItBlocks` may ring too.\n- Any contact while the user is on a call joins that call (`joinedCall` in `results`). Several questions arrive as one call.\n- While any Call is open, keep receiving.\n- An open Call Delivery is not proof it rang. `get_delivery` reads a Call\'s state, and with `transcript: true` what was said.\n';
 var id = z8.string().uuid();
 var key = z8.string().min(1).max(40);
 var participant = z8.string().regex(/^(human|agent):.+$/, "a participant ID such as agent:<uuid>");
@@ -701,6 +709,10 @@ var BrainMessageSchema = z8.union([
     // WHAT IT ASKS THE AGENT, IN UNDER TEN WORDS (owner, 2026-10-15: "Yes, add the summary"): the talker's own, stored
     // as the sent Entry's summary, which the recap's "Sent to <agent>: …" row shows. Absent on results written before it.
     summary: z8.string().optional(),
+    // THE PERSON'S LINES IT CARRIES, IN THEIR WORDS (owner, 2026-11-05: "just deliver my exact words to the agent"): the
+    // `entries` keys of those lines, each relayed whole on the agent's Delivery (`context = false`), where the rest of
+    // `entryKeys` ride as context. Absent on results written before it, and on a message that carries none.
+    carries: z8.array(key).optional(),
     // THE PERSON ASKED TO BE CALLED BACK ONCE THIS AGENT'S WORK IS DONE (turns.md, step 0): the agent owes
     // the call, and its next contact about it rings them (`public.callbacks`).
     callback: z8.literal(true).optional()
@@ -764,8 +776,11 @@ var TalkerReplySchema = z9.object({
    *  "Yes, add the summary"), which the recap's "Sent to <agent>: …" row shows; `about` names
    *  handles; `blocks` is the item a question to an agent must be answered before ("" for none);
    *  `callback` is true on a message to the agent doing work the person asked to be called back about
-   *  once it is done (false otherwise): that agent then owes the call (turns.md, step 0). */
-  messages: z9.array(z9.object({ key: str3, to: str3, sentences: strs2, text: str3, summary: str3, about: strs2, blocks: str3, callback: z9.boolean() }).strict()),
+   *  once it is done (false otherwise): that agent then owes the call (turns.md, step 0). `lines` are the
+   *  person's line handles a message to an agent carries ([] for none): the agent receives those lines, in their
+   *  words, and `text` is then only what the talker adds beyond them (owner, 2026-11-05: "just deliver my exact
+   *  words to the agent, keeping the summary as a way for me to navigate them more easily"). */
+  messages: z9.array(z9.object({ key: str3, to: str3, sentences: strs2, text: str3, summary: str3, about: strs2, blocks: str3, callback: z9.boolean(), lines: strs2.optional() }).strict()),
   /** What the call does next: listen, hold (the person asked for a moment) or end (they asked to). */
   then: z9.enum(["listen", "hold", "end"]),
   /** The person's replies to items (replies, owner 2026-10-07): the item's handle, the chosen option
@@ -783,9 +798,14 @@ var TalkerReplySchema = z9.object({
   /** The handle of the item to explain ("" for none). */
   explain: str3
 }).strict();
-var TALKER_REPLY_JSON_SCHEMA = (({ $schema: _, ...rest }) => rest)(
+var TALKER_REPLY_JSON_SCHEMA = withEveryMessageField((({ $schema: _, ...rest }) => rest)(
   zodToJsonSchema3(TalkerReplySchema, { $refStrategy: "none" })
-);
+));
+function withEveryMessageField(schema) {
+  const item = schema.properties?.messages?.items;
+  if (item?.properties) item.required = Object.keys(item.properties);
+  return schema;
+}
 var str4 = z10.string();
 var strs3 = z10.array(z10.string());
 var FilerReplySchema = z10.object({
@@ -1505,11 +1525,41 @@ var InboxItemSchema = z14.object({
   rev: z14.string().optional()
 });
 var APNS_TOKEN_RE = /^[0-9a-fA-F]{64}$/;
+var PushDeviceIdSchema = z14.string().regex(/^[A-Za-z0-9._:-]{1,200}$/, "not an install id");
+var PushDeviceSchema = z14.object({
+  deviceId: z14.string(),
+  platform: z14.enum(["ios", "android"]),
+  label: z14.string().nullable(),
+  model: z14.string().nullable(),
+  /** Calls and banners go here. */
+  rings: z14.boolean(),
+  /** It has a token a call can ring. */
+  ringable: z14.boolean(),
+  chosenAt: z14.string().nullable(),
+  updatedAt: z14.string()
+});
+var PushTokenDeviceSchema = z14.object({
+  deviceId: z14.string(),
+  rings: z14.boolean(),
+  ask: z14.boolean(),
+  ringsOn: z14.object({ deviceId: z14.string().nullable(), label: z14.string().nullable() }).nullable()
+});
+var PushRingsSchema = z14.object({ rings: z14.boolean() });
 var PushTokenSchema = z14.object({
   voipToken: z14.string().min(1).optional(),
   alertToken: z14.string().min(1).optional(),
   fcmToken: z14.string().min(1).optional(),
-  platform: z14.enum(["ios", "android"])
+  platform: z14.enum(["ios", "android"]),
+  /** WHICH INSTALL POSTED IT (owner, 2026-11-05: "Ask on each new device"). Absent from every
+   *  build before it, and then the post is exactly what it always was: the one row per account.
+   *  With it, the install has its own row and calls ring only where the person chose. */
+  deviceId: PushDeviceIdSchema.optional(),
+  /** The install's name as the person knows it ("iPhone", "iPad"), and its model. */
+  label: z14.string().trim().min(1).max(80).optional(),
+  model: z14.string().trim().min(1).max(80).optional(),
+  /** The person's choice, when the post carries it; absent, the install keeps what it has (and
+   *  its first ring token decides once: it rings unless another install already does). */
+  rings: z14.boolean().optional()
 }).superRefine((v, ctx) => {
   if (v.platform !== "ios") return;
   for (const field of ["voipToken", "alertToken"]) {
@@ -1619,7 +1669,11 @@ var GoalLatestSchema = z14.object({
   titles: z14.array(z14.string()).optional(),
   /** A PROGRESS NOTE'S ONE POINT ("An agent's progress note -> maybe let's cap it at 200 chars"): the
    *  update's own line, before its units; the row caps it at 200. Absent on anything else. */
-  line: z14.string().optional()
+  line: z14.string().optional(),
+  /** THE PERSON'S ENTRIES IT CARRIED TO AN AGENT, IN THEIR WORDS (owner, 2026-11-05: "paraphrasing shouldn't change
+   *  attribution in the UI"): on a message Paigy sent an agent, the person's Entries its Delivery relays whole. A row
+   *  draws it as theirs. Absent on anything else, and from a door older than it. */
+  carries: z14.array(z14.string()).optional()
 });
 var HistoryWorkSchema = z14.object({
   id: z14.string(),
@@ -1888,6 +1942,11 @@ var QueueItemSchema = z14.object({
    *  and a door older than 20261013045542 need not spell them. */
   yours: GoalLatestSchema.nullable().optional(),
   theirs: GoalLatestSchema.nullable().optional(),
+  /** ITS STEPS, COUNTED IN THE DATABASE (owner, 2026-11-04: "Count on the server, and agents make steps"): its
+   *  direct children that were not cancelled, and how many of them are done. The queue holds only a recent
+   *  slice of finished work, so counting `childGoalIds` read "0 of 1" for a project with five done. Absent
+   *  from a door older than this field, or when the count failed: the app then counts what it holds. */
+  steps: z14.object({ total: z14.number().int().nonnegative(), done: z14.number().int().nonnegative() }).nullable().optional(),
   /** WHAT THIS ROW IS, IN TWELVE CHARACTERS (#2928) — the hash of every other field on it, stamped
    *  by the one projection that builds the row (`apps/api/src/goal/queue.ts`). It is how the
    *  incremental read knows a row has not moved: the phone echoes back the revs it holds
@@ -2241,6 +2300,12 @@ var CallRecapSchema = z14.object({
      *  summary (Brain, 2026-10-14). Optional: absent from an API before it. */
     filedOn: z14.array(z14.object({ goalId: z14.string().uuid(), title: z14.string() })).optional(),
     recorded: z14.boolean().optional(),
+    /** On a `said` row: the agents the call SENT those words to, from the sending action's own
+     *  `about.agents` (20261106220220). The review's receipt is drawn from this and from the row's
+     *  own `requestId`, never from the asker of a question the words happened to sit under: on call
+     *  f9670f67 that asker was Interface while the send named Comms. `[]` or absent means nothing
+     *  was sent for that row, which is why the receipt is positive-only. */
+    sentTo: z14.array(z14.object({ id: z14.string().nullable(), name: z14.string() })).optional(),
     settled: z14.object({ requestId: z14.string(), answer: z14.string() }).nullable().optional(),
     acknowledged: z14.boolean().optional(),
     /** On a `put` row: still waiting for the person's answer (not settled, not answered, not put off).
@@ -2544,6 +2609,7 @@ function waitingSummary(received) {
 
 export {
   mcpInputSchema,
+  SKILL_MARK,
   AGENT_PROMPTS,
   promptResult,
   READS,
@@ -2551,6 +2617,7 @@ export {
   AGENT_TOOLS,
   LISTEN_COMMAND,
   serverInstructions,
+  SKILL,
   entryWords,
   entryUnit,
   harnessDriven,

package/dist/{dist-6D3WD3H6.js → dist-TJFO3UCZ.js}

@@ -65,7 +65,7 @@ import {
   viaLine,
   whoAmI,
   withCodexEnv
-} from "./chunk-ULCS3CYO.js";
+} from "./chunk-5OKHG3FO.js";
 export {
   AGENT_TOOLS,
   AGENT_TOOL_NAMES,

package/dist/enable.js

@@ -2,12 +2,13 @@
 import {
   PAIGY_TOOL_IDS,
   enablePaigyTools,
+  installPaigySkill,
   installSessionListening
-} from "./chunk-LGG4IKAW.js";
+} from "./chunk-CVQOJB2S.js";
 import {
   LISTEN_COMMAND
-} from "./chunk-ZCWFBY4B.js";
-import "./chunk-ULCS3CYO.js";
+} from "./chunk-LRROOCLY.js";
+import "./chunk-5OKHG3FO.js";
 
 // src/enable.ts
 function main() {
@@ -59,6 +60,12 @@ function main() {
     console.log(`  (${result.already.length} already present)`);
   }
   const hooks = installSessionListening();
+  const skills = installPaigySkill();
+  for (const s of skills) {
+    if (s.ok && !s.already) console.log(`\u2713 Paigy skill for ${s.harness} (${s.path})`);
+    else if (s.ok) console.log(`\u2713 Paigy skill for ${s.harness} already current`);
+    else console.log(`\u26A0 ${s.path}: ${s.why}`);
+  }
   for (const hook of hooks) {
     if (!hook.ok) console.log(`  ! ${hook.harness}: ${hook.why}`);
     else console.log(`\u2713 ${hook.harness} sessions will be told to listen (${hook.path})${hook.already ? " \u2014 already set" : ""}`);

package/dist/index.js

@@ -10,7 +10,7 @@ import {
   resolvePairing,
   startPairing,
   suggestedAgentName
-} from "./chunk-DMQHSNFJ.js";
+} from "./chunk-4US4OJR5.js";
 import {
   ConfigureSchema,
   ENABLE_COMMAND,
@@ -18,7 +18,7 @@ import {
   SERVER_INSTRUCTIONS,
   TOOLS,
   paigyToolsAllowlisted
-} from "./chunk-LGG4IKAW.js";
+} from "./chunk-CVQOJB2S.js";
 import {
   AGENT_PROMPTS,
   ReachTeller,
@@ -32,7 +32,7 @@ import {
   refreshSessionHook,
   wakeStatusPath,
   withReach
-} from "./chunk-ZCWFBY4B.js";
+} from "./chunk-LRROOCLY.js";
 import {
   clearSurface,
   writeSurface
@@ -53,7 +53,7 @@ import {
   setClient,
   slotName,
   whoAmI
-} from "./chunk-ULCS3CYO.js";
+} from "./chunk-5OKHG3FO.js";
 
 // src/index.ts
 import { Server } from "@modelcontextprotocol/sdk/server/index.js";

package/dist/listen.js

@@ -11,7 +11,7 @@ import {
   removeListenMark,
   wakeStatusPath,
   writeListenMark
-} from "./chunk-ZCWFBY4B.js";
+} from "./chunk-LRROOCLY.js";
 import {
   agentName,
   decided,
@@ -22,7 +22,7 @@ import {
   slotName,
   subscribeWake,
   viaLine
-} from "./chunk-ULCS3CYO.js";
+} from "./chunk-5OKHG3FO.js";
 
 // src/listen.ts
 import { createHash } from "crypto";

package/dist/onboard.js

@@ -3,14 +3,14 @@ import {
   resolvePairing,
   startPairing,
   suggestedAgentName
-} from "./chunk-DMQHSNFJ.js";
+} from "./chunk-4US4OJR5.js";
 import {
   autoConfigureClients,
   claudeInstallHint,
   openBrowser,
   removeOldGeminiHooks
-} from "./chunk-LGG4IKAW.js";
-import "./chunk-ZCWFBY4B.js";
+} from "./chunk-CVQOJB2S.js";
+import "./chunk-LRROOCLY.js";
 import {
   TOKEN_PATH,
   agentName,
@@ -21,7 +21,7 @@ import {
   saveToken,
   setIdentity,
   whoAmI
-} from "./chunk-ULCS3CYO.js";
+} from "./chunk-5OKHG3FO.js";
 
 // src/onboard.ts
 function reportRegistered() {

package/dist/slot.js

@@ -1,7 +1,7 @@
 #!/usr/bin/env node
 import {
   agentName
-} from "./chunk-ULCS3CYO.js";
+} from "./chunk-5OKHG3FO.js";
 
 // src/slot.ts
 process.stdout.write(agentName());

package/dist/stalled.js

@@ -33,7 +33,7 @@ async function main() {
   const dir = join(homedir(), ".paigy", "stalled-reminded");
   const mark = join(dir, `${session || "session"}-${day}`);
   if (existsSync(mark)) return;
-  const { receive } = await import("./dist-6D3WD3H6.js");
+  const { receive } = await import("./dist-TJFO3UCZ.js");
   const reply = stopReply((await receive()).stalled ?? []);
   if (!reply) return;
   mkdirSync(dir, { recursive: true });

package/dist/statusline.js

@@ -7,7 +7,7 @@ import {
   readToken,
   sessionSlot,
   slotName
-} from "./chunk-ULCS3CYO.js";
+} from "./chunk-5OKHG3FO.js";
 
 // src/statusline.ts
 import { realpathSync } from "fs";

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "@paigy/mcp",
   "mcpName": "io.github.paigy-ai/mcp",
-  "version": "0.40.43",
+  "version": "0.40.44",
   "description": "Paigy MCP server — the AI agent harness that calls you. Lets an agent notify a user and await their reply.",
   "license": "MIT",
   "type": "module",