@tickernelz/paperclip-pro-server 2026.928.6 → 2026.928.8

package/dist/build-info.json

@@ -1,3 +1,3 @@
 {
-  "commit": "99be30a18b87fa9c2e95d8c361fa32b5f42067dc"
+  "commit": "2c3e4f494ba2c32b8e16820517695ee89ddee1d5"
 }

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@tickernelz/paperclip-pro-server",
-  "version": "2026.928.6",
+  "version": "2026.928.8",
   "license": "MIT",
   "homepage": "https://github.com/tickernelz/paperclip-pro",
   "bugs": {
@@ -45,25 +45,25 @@
     "@discordjs/ws": "1.2.3",
     "@grpc/grpc-js": "1.14.4",
     "@opentelemetry/api": "^1.9.0",
-    "@tickernelz/paperclip-pro-adapter-claude-local": "2026.928.6",
-    "@tickernelz/paperclip-pro-adapter-codex-local": "2026.928.6",
-    "@tickernelz/paperclip-pro-adapter-cursor-cloud": "2026.928.6",
-    "@tickernelz/paperclip-pro-adapter-cursor-local": "2026.928.6",
-    "@tickernelz/paperclip-pro-adapter-gemini-local": "2026.928.6",
-    "@tickernelz/paperclip-pro-adapter-grok-local": "2026.928.6",
-    "@tickernelz/paperclip-pro-adapter-kimi-local": "2026.928.6",
-    "@tickernelz/paperclip-pro-adapter-openclaw-gateway": "2026.928.6",
-    "@tickernelz/paperclip-pro-adapter-omp-local": "2026.928.6",
-    "@tickernelz/paperclip-pro-adapter-opencode-local": "2026.928.6",
-    "@tickernelz/paperclip-pro-adapter-pi-local": "2026.928.6",
-    "@tickernelz/paperclip-pro-adapter-utils": "2026.928.6",
-    "@tickernelz/paperclip-pro-db": "2026.928.6",
-    "@tickernelz/paperclip-pro-hermes-paperclip-adapter": "2026.928.6",
-    "@tickernelz/paperclip-pro-mcp-server": "2026.928.6",
-    "@tickernelz/paperclip-pro-plugin-sdk": "2026.928.6",
-    "@tickernelz/paperclip-pro-shared": "2026.928.6",
-    "@tickernelz/paperclip-pro-teams-catalog": "2026.928.6",
-    "@tickernelz/paperclip-pro-skills-catalog": "2026.928.6",
+    "@tickernelz/paperclip-pro-adapter-claude-local": "2026.928.8",
+    "@tickernelz/paperclip-pro-adapter-codex-local": "2026.928.8",
+    "@tickernelz/paperclip-pro-adapter-cursor-cloud": "2026.928.8",
+    "@tickernelz/paperclip-pro-adapter-cursor-local": "2026.928.8",
+    "@tickernelz/paperclip-pro-adapter-gemini-local": "2026.928.8",
+    "@tickernelz/paperclip-pro-adapter-grok-local": "2026.928.8",
+    "@tickernelz/paperclip-pro-adapter-kimi-local": "2026.928.8",
+    "@tickernelz/paperclip-pro-adapter-openclaw-gateway": "2026.928.8",
+    "@tickernelz/paperclip-pro-adapter-omp-local": "2026.928.8",
+    "@tickernelz/paperclip-pro-adapter-opencode-local": "2026.928.8",
+    "@tickernelz/paperclip-pro-adapter-pi-local": "2026.928.8",
+    "@tickernelz/paperclip-pro-adapter-utils": "2026.928.8",
+    "@tickernelz/paperclip-pro-db": "2026.928.8",
+    "@tickernelz/paperclip-pro-hermes-paperclip-adapter": "2026.928.8",
+    "@tickernelz/paperclip-pro-mcp-server": "2026.928.8",
+    "@tickernelz/paperclip-pro-plugin-sdk": "2026.928.8",
+    "@tickernelz/paperclip-pro-shared": "2026.928.8",
+    "@tickernelz/paperclip-pro-teams-catalog": "2026.928.8",
+    "@tickernelz/paperclip-pro-skills-catalog": "2026.928.8",
     "@photon-ai/advanced-imessage": "2.1.0",
     "@vercel/connect": "0.6.1",
     "acorn": "8.18.0",
@@ -113,7 +113,7 @@
     "acpx"
   ],
   "devDependencies": {
-    "@tickernelz/paperclip-pro-paperclip-runner": "2026.928.6",
+    "@tickernelz/paperclip-pro-paperclip-runner": "2026.928.8",
     "@types/express": "^5.0.0",
     "@types/express-serve-static-core": "^5.1.3",
     "@types/jsdom": "^30.0.0",

package/skills/paperclip/SKILL.md

@@ -32,7 +32,7 @@ Manual local CLI mode (outside heartbeat runs): use `paperclip-pro agent local-c
 The `paperclip*` tools are how you talk to Paperclip. They carry your credential, your company id, and the current run id for you, and they validate arguments before the request leaves.
 
 - Hot paths map one-to-one: `paperclipMe`, `paperclipInboxLite`, `paperclipCheckoutIssue`, `paperclipGetHeartbeatContext`, `paperclipListComments`, `paperclipAddComment`, `paperclipUpdateIssue`, `paperclipCreateChildIssue`, `paperclipUpsertIssueDocument`, `paperclipCreateIssueWorkProduct`, `paperclipReleaseIssue`. The table in **Key Endpoints (Hot Routes)** names the tool for each action.
-- The default toolset is `core` (about 60 tools). The rest of the agent-callable surface ships in the `extended` toolset, available when the operator enables `PAPERCLIP_MCP_TOOLSETS=core,extended`; until then reach those operations with `paperclipApiRequest`.
+- The default toolset is `core` (about 60 tools). The rest of the agent-callable surface ships in the `full` toolset, available when the operator enables `PAPERCLIP_MCP_TOOLSETS=full`; until then reach those operations with `paperclipApiRequest`.
 - `paperclipApiRequest` is the escape hatch for anything without a dedicated tool. Arguments: `method`, `path` relative to `/api`, and `jsonBody` as a JSON string.
 - Tools marked destructive (deletes, terminations, workspace stops) do what they say and are not undone by a follow-up comment. Read before you write.
 
@@ -119,14 +119,14 @@ they mention a chat provider.
 Follow these steps every time you wake up unless the server-verified external
 chat shortcut above applies:
 
-**Scoped-wake fast path.** If the user message includes a **"Paperclip Resume Delta"** or **"Paperclip Wake Payload"** section that names a specific issue, **skip Steps 1–4 entirely**. Go straight to **Step 5 (Checkout)** for that issue, then continue with Steps 6–9. The scoped wake already tells you which issue to work on — do NOT call `paperclipMe`, do NOT fetch your inbox, do NOT pick work. Just checkout, read the wake context, do the work, and update.
+**Scoped-wake fast path.** If the user message includes a **"Paperclip Resume Delta"** or **"Paperclip Wake Payload"** section that names a specific issue, **skip Steps 1–4 entirely**. Go straight to **Step 5 (Checkout)** for that issue, then continue with Steps 6–9. The scoped wake already tells you which issue to work on — do NOT call `paperclipMe`, do NOT fetch your inbox, do NOT pick work. When the payload says `checkout: already claimed by the harness for this run`, the issue is already yours: skip Step 5 and do not call `paperclipCheckoutIssue`. Otherwise checkout, then read the wake context, do the work, and update.
 
 **Step 1 — Identity.** If not already in context, call `paperclipMe` to get your id, companyId, role, chainOfCommand, and budget.
 
 **Step 2 — Approval follow-up (when triggered).** If `PAPERCLIP_APPROVAL_ID` is set (or wake reason indicates approval resolution), review the approval first:
 
-- `paperclipGetApproval` with `id` set to the approval id
-- `paperclipGetApprovalIssues` with the same `id`
+- `paperclipGetApproval` with `approvalId` set to the approval id
+- `paperclipGetApprovalIssues` with the same `approvalId`
 - For each linked issue:
   - close it with `paperclipUpdateIssue` (`status: "done"`) if the approval fully resolves requested work, or
   - add a markdown comment with `paperclipAddComment` explaining why it remains open and what happens next.
@@ -145,9 +145,9 @@ Overrides and special cases:
 - **Blocked-task dedup:** before touching a `blocked` task, check the thread. If your most recent comment was a blocked-status update and no one has replied since, skip entirely — do not checkout, do not re-comment. Only re-engage on new context (comment, status change, event wake).
 - Nothing assigned and no valid mention handoff → exit the heartbeat.
 
-**Step 5 — Checkout.** You MUST checkout before doing any work. Call `paperclipCheckoutIssue`:
+**Step 5 — Checkout.** You MUST checkout before doing any work, unless the wake payload says `checkout: already claimed by the harness for this run`. Call `paperclipCheckoutIssue`:
 
-- `id`: the issue id
+- `issueId`: the issue id or identifier
 - `agentId`: your agent id
 - `expectedStatuses`: `["todo", "backlog", "blocked", "in_review"]`
 
@@ -159,7 +159,7 @@ If the run prompt includes a Paperclip wake payload, inspect that section before
 
 Use comments incrementally:
 
-- if `PAPERCLIP_WAKE_COMMENT_ID` is set, fetch that exact comment first with `paperclipGetComment` (`id`, `commentId`)
+- if `PAPERCLIP_WAKE_COMMENT_ID` is set, fetch that exact comment first with `paperclipGetComment` (`issueId`, `commentId`)
 - if you already know the thread and only need updates, call `paperclipListComments` with `after` set to the last-seen comment id and `order: "asc"`
 - call `paperclipListComments` without a cursor only when cold-starting or when incremental isn't enough
 
@@ -174,6 +174,8 @@ If `currentParticipant` matches you, submit your decision with `paperclipUpdateI
 
 If `currentParticipant` does not match you, do not try to advance the stage — Paperclip will reject other actors with `422`.
 
+To put your own issue through a review or approval stage, send the policy in the `advanced` object of `paperclipUpdateIssue`, never as a top-level argument: `advanced: { "executionPolicy": { "stages": [{ "type": "review", "participants": [{ "type": "agent", "agentId": "<reviewer-agent-id>" }] }] } }`. Stage `type` is `review` or `approval`; a participant is either `{ "type": "agent", "agentId" }` or `{ "type": "user", "userId" }`.
+
 **Step 7 — Do the work.** Use your tools and capabilities. Execution contract:
 
 - If the issue is actionable, start concrete work in the same heartbeat. Do not stop at a plan unless the issue specifically asks for planning.
@@ -213,7 +215,7 @@ Before ending any heartbeat, apply this final-disposition checklist:
 
 When writing issue descriptions or comments, follow the ticket-linking rule in **Comment Style** below.
 
-Record the disposition and the explanation in one call: `paperclipUpdateIssue` with `id` set to the issue, `status: "done"`, and `comment: "What was done and why."`
+Record the disposition and the explanation in one call: `paperclipUpdateIssue` with `issueId` set to the issue, `status: "done"`, and `comment: "What was done and why."`
 
 Tool arguments take real multiline strings, so paste markdown comments exactly as you want them stored — paragraph breaks and bullet lists survive as written, and there is no JSON-encoding step to get wrong.
 
@@ -235,7 +237,7 @@ A "watcher" or "monitor" is not something that lives inside a run. A run/heartbe
 
 Because of that, follow these rules:
 
-- **Only claim a watcher/monitor exists after you have actually scheduled one.** Describing a watcher in a comment does not create it. Schedule it by setting `advanced.executionPolicy.monitor.nextCheckAt` (with `kind`/`serviceName`/`externalRef`/`timeoutAt`/`maxAttempts`) through `paperclipUpdateIssue`; `executionPolicy` is not a top-level tool argument, it travels in the `advanced` object. Read that tool result to confirm `monitorNextCheckAt` is non-null, `assigneeAgentId` is set, `assigneeUserId` is null, and `status` is `in_progress` or `in_review` — do not issue a confirming read. The stored timestamp only fires under those conditions. Run a check on demand with `paperclipCheckNowIssueMonitor`, available when the operator enables `PAPERCLIP_MCP_TOOLSETS=core,extended`; otherwise use `paperclipApiRequest` with `method: "POST"`, `path: "/issues/<issueId>/monitor/check-now"`.
+- **Only claim a watcher/monitor exists after you have actually scheduled one.** Describing a watcher in a comment does not create it. Schedule it by setting `advanced.executionPolicy.monitor.nextCheckAt` (with `kind`/`serviceName`/`externalRef`/`timeoutAt`/`maxAttempts`) through `paperclipUpdateIssue`; `executionPolicy` is not a top-level tool argument, it travels in the `advanced` object. Read that tool result to confirm `monitorNextCheckAt` is non-null, `assigneeAgentId` is set, `assigneeUserId` is null, and `status` is `in_progress` or `in_review` — do not issue a confirming read. The stored timestamp only fires under those conditions. Run a check on demand with `paperclipCheckNowIssueMonitor`, available when the operator enables `PAPERCLIP_MCP_TOOLSETS=full`; otherwise use `paperclipApiRequest` with `method: "POST"`, `path: "/issues/<issueId>/monitor/check-now"`.
 - **Describe it in checkable terms.** State the monitor's kind, next check time, and attempt/timeout bounds — not vague "a watcher will wake me" background magic. If you cannot name those, you have not scheduled one and must not imply that you have.
 - **Never imply a live watcher on a task you are marking `done`.** `done` means no follow-up on this issue, which contradicts an ongoing watcher. If real re-checking is still needed, keep the issue `in_progress`/`in_review` with a scheduled monitor instead of closing it.
 - This is enforced by state, not by narration: the disposition guard rejects an agent move to `in_review` (`invalid_issue_disposition`) unless a real review path exists — interaction, approval, human reviewer, typed participant, or an actually-scheduled monitor with a real `monitorNextCheckAt` — and the recovery classifier flags `in_review_without_action_path` for anything parked with no live wake path. Keep your comments consistent with that real state.
@@ -255,7 +257,7 @@ Run-scoped writes are subtree-scoped: the delegate's run can write to its own is
 
 ## Managing A User's Inbox
 
-Agents may archive an issue from a user's Mine inbox with `paperclipInboxArchiveIssue` and reverse it with `paperclipDeleteIssueInboxArchive`. Both are available when the operator enables `PAPERCLIP_MCP_TOOLSETS=core,extended`; otherwise use `paperclipApiRequest` with `method: "POST"` or `method: "DELETE"` and `path: "/issues/<issueId>/inbox-archive"`. Omit `userId` for the normal case: Paperclip resolves the responsible user from the agent's run context. An explicit `userId` targets another user and requires either that user's saved opt-in policy (`open` or an allowlist containing the agent) or a matching `inbox:manage` grant. The implicit default-open policy for a user who has never saved the control does not authorize explicit cross-user targeting.
+Agents may archive an issue from a user's Mine inbox with `paperclipInboxArchiveIssue` and reverse it with `paperclipDeleteIssueInboxArchive`. Both are available when the operator enables `PAPERCLIP_MCP_TOOLSETS=full`; otherwise use `paperclipApiRequest` with `method: "POST"` or `method: "DELETE"` and `path: "/issues/<issueId>/inbox-archive"`. Omit `userId` for the normal case: Paperclip resolves the responsible user from the agent's run context. An explicit `userId` targets another user and requires either that user's saved opt-in policy (`open` or an allowlist containing the agent) or a matching `inbox:manage` grant. The implicit default-open policy for a user who has never saved the control does not authorize explicit cross-user targeting.
 
 Archive only when the issue is truly resolved for that user, such as after a pull request is confirmed merged at its current head and the result is verified. Never archive an issue while the user is still expected to review, approve, answer, choose, or otherwise decide something. Archiving is reversible and audited, and later issue activity can resurface the item, but those safeguards do not make premature cleanup acceptable.
 
@@ -329,7 +331,7 @@ Key shared semantics:
 
 ### Standalone Decisions
 
-Create a decision from an issue-scoped agent run with `paperclipCreateDecision`, available when the operator enables `PAPERCLIP_MCP_TOOLSETS=core,extended`; otherwise use `paperclipApiRequest` with `method: "POST"`, `path: "/companies/<companyId>/decisions"`, and this `jsonBody`:
+Create a decision from an issue-scoped agent run with `paperclipCreateDecision`, available when the operator enables `PAPERCLIP_MCP_TOOLSETS=full`; otherwise use `paperclipApiRequest` with `method: "POST"`, `path: "/companies/<companyId>/decisions"`, and this `jsonBody`:
 
 ```json
 {
@@ -358,7 +360,7 @@ Create a decision from an issue-scoped agent run with `paperclipCreateDecision`,
 - `continuationPolicy` is `none` or `wake_origin_agent`. Use the latter only when resolution or expiry must resume the proposer.
 - Each origin agent may have at most 50 open decisions by default.
 
-Bundle related cross-issue decisions with `paperclipCreateDecisionBundle` (same `extended` toolset, or `paperclipApiRequest` with `method: "POST"`, `path: "/companies/<companyId>/decision-bundles"`):
+Bundle related cross-issue decisions with `paperclipCreateDecisionBundle` (same `full` toolset, or `paperclipApiRequest` with `method: "POST"`, `path: "/companies/<companyId>/decision-bundles"`):
 
 ```json
 {
@@ -391,7 +393,7 @@ Bundle related cross-issue decisions with `paperclipCreateDecisionBundle` (same
 
 Bundles accept 1–50 decisions and are created atomically. The nested decision payload uses the same fields and limits as the single-create endpoint.
 
-Create a `request_checkbox_confirmation` with `paperclipRequestCheckboxConfirmation` (the responder selects any subset, then confirms). The tool sets the interaction kind; pass `id` for the issue plus the fields below:
+Create a `request_checkbox_confirmation` with `paperclipRequestCheckboxConfirmation` (the responder selects any subset, then confirms). The tool sets the interaction kind; pass `issueId` for the issue plus the fields below:
 
 ```json
 {
@@ -468,7 +470,7 @@ There is no dedicated tool for `request_item_verdicts`. Create one with `papercl
 }
 ```
 
-The responder submits verdicts with `paperclipCreateIssueInteractionVerdict`, available when the operator enables `PAPERCLIP_MCP_TOOLSETS=core,extended`. Partial submissions keep the interaction `pending` and wake the assignee once with `newlyResolvedItemIds`; when every item has a verdict, the interaction becomes `answered`.
+The responder submits verdicts with `paperclipCreateIssueInteractionVerdict`, available when the operator enables `PAPERCLIP_MCP_TOOLSETS=full`. Partial submissions keep the interaction `pending` and wake the assignee once with `newlyResolvedItemIds`; when every item has a verdict, the interaction becomes `answered`.
 
 ## Niche Workflow Pointers
 
@@ -484,14 +486,14 @@ Load `references/workflows.md` when the task matches one of these:
 
 Load `references/cases.md` when creating, upserting, documenting, attaching to,
 or linking cases through the agent-facing `paperclip*` case tools, available when
-the operator enables `PAPERCLIP_MCP_TOOLSETS=core,extended`.
+the operator enables `PAPERCLIP_MCP_TOOLSETS=full`.
 
 ## Company Skills Workflow
 
 Authorized managers can install company skills independently of hiring, then assign or remove those skills on agents.
 
-- Inspect company skills with `paperclipListSkills`; install them with `paperclipCreateSkill`, `paperclipImportSkill`, or `paperclipInstallCatalogSkill`, available when the operator enables `PAPERCLIP_MCP_TOOLSETS=core,extended`.
-- Assign skills to existing agents with `paperclipSyncAgentSkill` (available when the operator enables `PAPERCLIP_MCP_TOOLSETS=core,extended`) and an explicit `add`, `remove`, or `replace` mode. Prefer `add`; `replace` overwrites the complete desired skill set.
+- Inspect company skills with `paperclipListSkills`; install them with `paperclipCreateSkill`, `paperclipImportSkill`, or `paperclipInstallCatalogSkill`, available when the operator enables `PAPERCLIP_MCP_TOOLSETS=full`.
+- Assign skills to existing agents with `paperclipSyncAgentSkill` (available when the operator enables `PAPERCLIP_MCP_TOOLSETS=full`) and an explicit `add`, `remove`, or `replace` mode. Prefer `add`; `replace` overwrites the complete desired skill set.
 - When hiring or creating an agent, include optional `desiredSkills` so the same assignment model is applied on day one.
 
 If you are asked to install a skill for the company or an agent you MUST read:
@@ -501,7 +503,7 @@ If you are asked to install a skill for the company or an agent you MUST read:
 
 Routines are recurring tasks. Each time a routine fires it creates an execution issue assigned to the routine's agent — the agent picks it up in the normal heartbeat flow.
 
-- Create and manage routines with `paperclipCreateRoutine`, `paperclipListRoutines`, `paperclipUpdateRoutine`, and `paperclipRunRoutine` (available when the operator enables `PAPERCLIP_MCP_TOOLSETS=core,extended`) — agents can only manage routines assigned to themselves.
+- Create and manage routines with `paperclipCreateRoutine`, `paperclipListRoutines`, `paperclipUpdateRoutine`, and `paperclipRunRoutine` (available when the operator enables `PAPERCLIP_MCP_TOOLSETS=full`) — agents can only manage routines assigned to themselves.
 - Add triggers per routine: `schedule` (cron), `webhook`, or `api` (manual).
 - Control concurrency and catch-up behaviour with `concurrencyPolicy` and `catchUpPolicy`.
 
@@ -623,7 +625,7 @@ Recommended flow — write the document with `paperclipUpsertIssueDocument`:
 
 ```json
 {
-  "id": "{issueId}",
+  "issueId": "{issueId}",
   "key": "plan",
   "title": "Plan",
   "format": "markdown",
@@ -632,7 +634,7 @@ Recommended flow — write the document with `paperclipUpsertIssueDocument`:
 }
 ```
 
-If `plan` already exists, first call `paperclipGetDocument` (`id`, `key: "plan"`) and read its current body and `latestRevisionId`. Then send the revised body with `baseRevisionId` set to that returned `latestRevisionId`. The read field is `latestRevisionId`; the write argument is `baseRevisionId`. Omitting it on an update returns `409`. If the revision changed concurrently, fetch and reconcile the latest plan before trying again; never blindly overwrite it.
+If `plan` already exists, first call `paperclipGetDocument` (`issueId`, `key: "plan"`) and read its current body and `latestRevisionId`. Then send the revised body with `baseRevisionId` set to that returned `latestRevisionId`. The read field is `latestRevisionId`; the write argument is `baseRevisionId`. Omitting it on an update returns `409`. If the revision changed concurrently, fetch and reconcile the latest plan before trying again; never blindly overwrite it.
 
 ## Key Endpoints (Hot Routes)
 
@@ -646,7 +648,7 @@ If `plan` already exists, first call `paperclipGetDocument` (`id`, `key: "plan"`
 | Compact heartbeat context             | `paperclipGetHeartbeatContext`                                                                                                                                    |
 | Update task                           | `paperclipUpdateIssue` (optional `comment` argument)                                                                                                              |
 | Get comments / delta / single         | `paperclipListComments` • `paperclipGetComment`                                                                                                                   |
-| Add comment                           | `paperclipAddComment`                                                                                                                                             |
+| Add comment                           | `paperclipAddComment` (`deliver: "queue"` or `"steer"`; steering a running turn is board-only, so an agent's steer is queued; read `deliveredAs` in the result)         |
 | Issue-thread interactions             | `paperclipListIssueInteractions` • `paperclipAskUserQuestions` • `paperclipRequestConfirmation` • `paperclipRequestCheckboxConfirmation` • `paperclipSuggestTasks` |
 | Create task / subtask                 | `paperclipCreateIssue` • `paperclipCreateChildIssue`                                                                                                              |
 | Release task                          | `paperclipReleaseIssue`                                                                                                                                           |
@@ -664,7 +666,7 @@ If `plan` already exists, first call `paperclipGetDocument` (`id`, `key: "plan"`
 | Credentials and secrets               | none — `paperclipApiRequest`                                                                                                                                      |
 | Anything else                         | `paperclipApiRequest`                                                                                                                                             |
 
-The rest of the agent-callable surface (company imports/exports, OpenClaw invites, company skills, routines, cases) ships in the `extended` toolset and is documented in `references/api-reference.md`.
+The rest of the agent-callable surface (company imports/exports, OpenClaw invites, company skills, routines, cases) ships in the `full` toolset and is documented in `references/api-reference.md`.
 
 ## Searching Issues
 

package/skills/paperclip/references/api-reference.md

@@ -2,7 +2,7 @@
 
 Detailed reference for the Paperclip control plane as agents reach it: the `paperclip*` MCP tools. For the core heartbeat procedure and critical rules, see the main `SKILL.md`.
 
-The tool list your client advertises is the contract. Tools marked extended load only when the operator enables `PAPERCLIP_MCP_TOOLSETS=core,extended`; everything else is in the default `core` toolset. Any operation without a dedicated tool goes through `paperclipApiRequest` (`method`, `path` relative to `/api`, `jsonBody` as a JSON string). Operations that require a board actor, manage credentials, or are runner-owned have no dedicated tool on purpose.
+The tool list your client advertises is the contract. Tools marked extended load only when the operator enables `PAPERCLIP_MCP_TOOLSETS=full`; everything else is in the default `core` toolset. Any operation without a dedicated tool goes through `paperclipApiRequest` (`method`, `path` relative to `/api`, `jsonBody` as a JSON string). Operations that require a board actor, manage credentials, or are runner-owned have no dedicated tool on purpose.
 
 ---
 
@@ -508,7 +508,7 @@ paperclipUpdateIssue { issueId: "issue-200", comment: "Your Mine inbox has 1 unr
 
 Archive only after the issue is genuinely finished from the responsible user's perspective. Do not archive issues awaiting review, approval, confirmation, answers, or another user decision.
 
-`paperclipInboxArchiveIssue` and `paperclipDeleteIssueInboxArchive` are extended: available when the operator enables `PAPERCLIP_MCP_TOOLSETS=core,extended`; otherwise use `paperclipApiRequest`.
+`paperclipInboxArchiveIssue` and `paperclipDeleteIssueInboxArchive` are extended: available when the operator enables `PAPERCLIP_MCP_TOOLSETS=full`; otherwise use `paperclipApiRequest`.
 
 ```
 # The responsible user's id is resolved from the authenticated agent run.
@@ -726,7 +726,7 @@ Access is intentionally constrained:
 
 ## Setting Agent Instructions Path
 
-Use `paperclipUpdateAgentInstructionsPath` when setting an adapter instructions markdown path (`AGENTS.md`-style files). It is extended: available when the operator enables `PAPERCLIP_MCP_TOOLSETS=core,extended`; otherwise use `paperclipApiRequest`.
+Use `paperclipUpdateAgentInstructionsPath` when setting an adapter instructions markdown path (`AGENTS.md`-style files). It is extended: available when the operator enables `PAPERCLIP_MCP_TOOLSETS=full`; otherwise use `paperclipApiRequest`.
 
 ```json
 {
@@ -814,11 +814,11 @@ below remain available when local workspace configuration is needed.
 }
 ```
 
-Then `paperclipCreateProjectWorkspace`, extended: available when the operator enables `PAPERCLIP_MCP_TOOLSETS=core,extended`; otherwise use `paperclipApiRequest`.
+Then `paperclipCreateProjectWorkspace`, extended: available when the operator enables `PAPERCLIP_MCP_TOOLSETS=full`; otherwise use `paperclipApiRequest`.
 
 ```json
 {
-  "id": "{projectId}",
+  "projectId": "{projectId}",
   "cwd": "/Users/me/paperclip-mobile",
   "repoUrl": "https://github.com/acme/paperclip-mobile",
   "repoRef": "main",
@@ -849,7 +849,7 @@ environment, and managed AI connection. The new agent receives its own
 instructions; caller secrets, workspace paths, sessions, and instructions are
 not copied. Existing hiring permissions and company approval policy still apply.
 
-The equivalent native tool is `paperclipCreateAgentHire`, extended: available when the operator enables `PAPERCLIP_MCP_TOOLSETS=core,extended`; otherwise use `paperclipApiRequest`.
+The equivalent native tool is `paperclipCreateAgentHire`, extended: available when the operator enables `PAPERCLIP_MCP_TOOLSETS=full`; otherwise use `paperclipApiRequest`.
 
 ```json
 {
@@ -1237,7 +1237,7 @@ Payload field reference (`RequestItemVerdictsPayload`):
 | `supersedeOnUserComment` | boolean                                                  | `true` (set server-side)   | A later board/user comment expires the still-pending remainder with `outcome: "superseded_by_comment"`.                      |
 | `target`                 | `RequestConfirmationTarget` \| `null`                    | `null`                     | Same target schema as confirmations. Stale issue-document targets expire the still-pending remainder with `stale_target`.     |
 
-Submit item verdicts with `paperclipCreateIssueInteractionVerdict`, extended: available when the operator enables `PAPERCLIP_MCP_TOOLSETS=core,extended`; otherwise use `paperclipApiRequest`. This is a board action; it requires a board/user role and agents creating the interaction cannot submit verdicts.
+Submit item verdicts with `paperclipCreateIssueInteractionVerdict`, extended: available when the operator enables `PAPERCLIP_MCP_TOOLSETS=full`; otherwise use `paperclipApiRequest`. This is a board action; it requires a board/user role and agents creating the interaction cannot submit verdicts.
 
 ```json
 {
@@ -1361,7 +1361,7 @@ The tool result reports the underlying failure.
 
 ## Full Tool Reference
 
-Tools marked extended load only when the operator enables `PAPERCLIP_MCP_TOOLSETS=core,extended`; otherwise use `paperclipApiRequest` for the same job.
+Tools marked extended load only when the operator enables `PAPERCLIP_MCP_TOOLSETS=full`; otherwise use `paperclipApiRequest` for the same job.
 
 ### Agents
 
@@ -1374,17 +1374,17 @@ Tools marked extended load only when the operator enables `PAPERCLIP_MCP_TOOLSET
 | Agent details + chain of command | `paperclipGetAgent` | `agentId`, `companyId` |
 | List all agents in company | `paperclipListAgents` | `companyId` |
 | Create agent directly (no approval) | `paperclipCreateAgent` (extended) | `companyId`, agent fields |
-| Update agent config or budget | `paperclipUpdateAgent` (extended) | `id`, changed fields |
+| Update agent config or budget | `paperclipUpdateAgent` (extended) | `agentId`, changed fields |
 | Temporarily stop heartbeats | `paperclipApiRequest` | `method: "POST"`, `path: "/agents/:agentId/pause"` |
-| Resume a paused agent | `paperclipResumeAgent` (extended) | `id` |
+| Resume a paused agent | `paperclipResumeAgent` (extended) | `agentId` |
 | Permanently deactivate agent (irreversible) | `paperclipApiRequest` | `method: "POST"`, `path: "/agents/:agentId/terminate"` |
 | Create long-lived API key (full value shown once) | `paperclipApiRequest` | `method: "POST"`, `path: "/agents/:agentId/keys"` |
-| Manually trigger a heartbeat | `paperclipInvokeAgentHeartbeat` (extended) | `id` |
+| Manually trigger a heartbeat | `paperclipInvokeAgentHeartbeat` (extended) | `agentId` |
 | Org chart tree | `paperclipGetOrg` (extended) | `companyId` |
 | List selectable models for an adapter type | `paperclipListAdapterModels` (extended) | `companyId`, `type` |
-| Set/clear instructions path (`AGENTS.md`) | `paperclipUpdateAgentInstructionsPath` (extended) | `id`, `path`, `adapterConfigKey` |
-| List config revisions | `paperclipListAgentConfigRevisions` (extended) | `id` |
-| Roll back config | `paperclipRollbackAgentConfigRevision` (extended) | `id`, `revisionId` |
+| Set/clear instructions path (`AGENTS.md`) | `paperclipUpdateAgentInstructionsPath` (extended) | `agentId`, `path`, `adapterConfigKey` |
+| List config revisions | `paperclipListAgentConfigRevisions` (extended) | `agentId` |
+| Roll back config | `paperclipRollbackAgentConfigRevision` (extended) | `agentId`, `revisionId` |
 
 ### Issues (Tasks)
 
@@ -1393,20 +1393,20 @@ Tools marked extended load only when the operator enables `PAPERCLIP_MCP_TOOLSET
 | List issues, sorted by priority | `paperclipListIssues` | `companyId`, `status`, `assigneeAgentId`, `assigneeUserId`, `projectId`, `labelId`, `q` (full-text across title, identifier, description, comments) |
 | Issue details + ancestors | `paperclipGetIssue` | `issueId` |
 | Compact heartbeat context: issue state, ancestor summaries, comment cursor | `paperclipGetHeartbeatContext` | `issueId`, `wakeCommentId` |
-| Blocker diagnostic with `diagnosis`, readiness, bounded anomaly flags | `paperclipListIssueDiagnosticBlockers` (extended) | `id` |
-| Wake-history diagnostic with `diagnosis`, bounded events, Case-B inference | `paperclipListIssueDiagnosticWakes` (extended) | `id` |
-| Subtree diagnostic combining visible child, blocker, and wake edges | `paperclipGetIssueDiagnosticSubtree` (extended) | `id` |
+| Blocker diagnostic with `diagnosis`, readiness, bounded anomaly flags | `paperclipListIssueDiagnosticBlockers` (extended) | `issueId` |
+| Wake-history diagnostic with `diagnosis`, bounded events, Case-B inference | `paperclipListIssueDiagnosticWakes` (extended) | `issueId` |
+| Subtree diagnostic combining visible child, blocker, and wake edges | `paperclipGetIssueDiagnosticSubtree` (extended) | `issueId` |
 | Create issue | `paperclipCreateIssue` | `companyId`, `title`, `parentId`, `assigneeAgentId`, `status`, `priority`, `goalId`, `blockedByIssueIds`, `advanced` |
-| Create a child issue under an existing issue | `paperclipCreateChildIssue` | `id`, `body` |
+| Create a child issue under an existing issue | `paperclipCreateChildIssue` | `issueId`, child issue fields |
 | Update issue | `paperclipUpdateIssue` | `issueId`, changed fields, optional `comment`, `advanced`; the result is authoritative and includes `changes` + `comment`; `blockedByIssueIds` replaces the blocker set |
 | Atomic checkout (claim + start), idempotent if you already own it | `paperclipCheckoutIssue` | `issueId`, `agentId`, `expectedStatuses` |
 | Release task ownership | `paperclipReleaseIssue` | `issueId` |
 | List comments | `paperclipListComments` | `issueId`, `after`, `order`, `limit` |
 | Get a specific comment by ID | `paperclipGetComment` | `issueId`, `commentId` |
 | Add comment (@-mentions trigger wakeups) | `paperclipAddComment` | `issueId`, `body`, `resume` |
-| Archive issue from responsible user's inbox | `paperclipInboxArchiveIssue` (extended) | `id`, optional `userId` (needs saved target-user opt-in or cross-user grant) |
-| Reverse inbox archive, same target and policy rules | `paperclipDeleteIssueInboxArchive` (extended) | `id`, optional `userId` |
-| List issue-thread interactions | `paperclipListIssueInteractions` | `id` |
+| Archive issue from responsible user's inbox | `paperclipInboxArchiveIssue` (extended) | `issueId`, optional `userId` (needs saved target-user opt-in or cross-user grant) |
+| Reverse inbox archive, same target and policy rules | `paperclipDeleteIssueInboxArchive` (extended) | `issueId`, optional `userId` |
+| List issue-thread interactions | `paperclipListIssueInteractions` | `issueId` |
 | Create a `suggest_tasks` interaction | `paperclipSuggestTasks` | `issueId`, `payload`, `idempotencyKey`, `title`, `summary`, `resolverPolicy`, `addresseeAgentId`, `continuationPolicy` |
 | Create an `ask_user_questions` interaction | `paperclipAskUserQuestions` | same envelope |
 | Create a `request_confirmation` interaction | `paperclipRequestConfirmation` | same envelope |
@@ -1415,7 +1415,7 @@ Tools marked extended load only when the operator enables `PAPERCLIP_MCP_TOOLSET
 | Accept suggested tasks or confirmation | `paperclipApiRequest` | `method: "POST"`, `path: "/issues/:issueId/interactions/:interactionId/accept"`, `jsonBody` with `selectedClientKeys` for `suggest_tasks` or `selectedOptionIds` for `request_checkbox_confirmation` |
 | Reject suggested tasks or confirmation | `paperclipApiRequest` | `method: "POST"`, `path: "/issues/:issueId/interactions/:interactionId/reject"` |
 | Respond to structured questions | `paperclipApiRequest` | `method: "POST"`, `path: "/issues/:issueId/interactions/:interactionId/respond"` |
-| Submit partial item verdicts for `request_item_verdicts` | `paperclipCreateIssueInteractionVerdict` (extended) | `id`, `interactionId`, `verdicts` |
+| Submit partial item verdicts for `request_item_verdicts` | `paperclipCreateIssueInteractionVerdict` (extended) | `issueId`, `interactionId`, `verdicts` |
 | Withdraw any pending interaction (creator agent, current assignee agent, or board user) | `paperclipApiRequest` | `method: "POST"`, `path: "/issues/:issueId/interactions/:interactionId/withdraw"`, optional `jsonBody` `{ "reason": string }` |
 | List issue documents | `paperclipListDocuments` | `issueId` |
 | Get issue document by key | `paperclipGetDocument` | `issueId`, `key` |
@@ -1426,15 +1426,15 @@ Tools marked extended load only when the operator enables `PAPERCLIP_MCP_TOOLSET
 | List approvals linked to issue | `paperclipListIssueApprovals` | `issueId` |
 | Link approval to issue | `paperclipLinkIssueApproval` | `issueId`, `approvalId` |
 | Unlink approval from issue | `paperclipUnlinkIssueApproval` | `issueId`, `approvalId` |
-| List files attached to an issue | `paperclipListIssueAttachments` | `id` |
+| List files attached to an issue | `paperclipListIssueAttachments` | `issueId` |
 | Delete an issue attachment | `paperclipDeleteAttachment` | `attachmentId` |
-| List recorded work products | `paperclipListIssueWorkProducts` | `id` |
-| Record an operator-facing work product | `paperclipCreateIssueWorkProduct` | `id`, work-product fields |
-| Update a recorded work product | `paperclipUpdateWorkProduct` | `id`, changed fields |
-| Read the issue monitor/watchdog configuration | `paperclipGetIssueWatchdog` | `id` |
-| Schedule or clear the issue monitor | `paperclipSetIssueWatchdog` | `id`, watchdog fields |
+| List recorded work products | `paperclipListIssueWorkProducts` | `issueId` |
+| Record an operator-facing work product | `paperclipCreateIssueWorkProduct` | `issueId`, work-product fields |
+| Update a recorded work product | `paperclipUpdateWorkProduct` | `workProductId`, changed fields |
+| Read the issue monitor/watchdog configuration | `paperclipGetIssueWatchdog` | `issueId` |
+| Schedule or clear the issue monitor | `paperclipSetIssueWatchdog` | `issueId`, watchdog fields |
 | Current execution workspace, runtime services and service URLs | `paperclipGetIssueWorkspaceRuntime` | `issueId` |
-| Execution workspace detail | `paperclipGetExecutionWorkspace` | `id` |
+| Execution workspace detail | `paperclipGetExecutionWorkspace` | `executionWorkspaceId` |
 | Start, stop, or restart workspace runtime services | `paperclipControlIssueWorkspaceServices` | `issueId`, `action` (`start`, `stop`, `restart`), `runtimeServiceId`, `serviceIndex`, `workspaceCommandId` |
 | Wait until a runtime service is running and has a URL | `paperclipWaitForIssueWorkspaceService` | `issueId`, `runtimeServiceId`, `serviceName`, `timeoutSeconds` |
 | List company issue labels | `paperclipListLabels` | `companyId` |
@@ -1451,16 +1451,16 @@ Tools marked extended load only when the operator enables `PAPERCLIP_MCP_TOOLSET
 | Archive company | `paperclipApiRequest` | `method: "POST"`, `path: "/companies/:companyId/archive"` |
 | List projects | `paperclipListProjects` | `companyId` |
 | Project details | `paperclipGetProject` | `projectId`, `companyId` |
-| Create project | `paperclipCreateProject` | `companyId`, `name`, `repositoryIds`/`repositoryUrls` arrays or inline `workspace`, optional `idempotencyKey` |
-| Update project | `paperclipUpdateProject` | `id`, changed fields |
-| List project workspaces | `paperclipListProjectWorkspaces` (extended) | `id` |
-| Create project workspace | `paperclipCreateProjectWorkspace` (extended) | `id`, `cwd`, `repoUrl`, `repoRef`, `isPrimary` |
-| Update project workspace | `paperclipUpdateProjectWorkspace` (extended) | `id`, `workspaceId`, changed fields |
-| Delete project workspace | `paperclipDeleteProjectWorkspace` (extended) | `id`, `workspaceId` |
+| Create project | `paperclipCreateProject` | `companyId`, `name`, `repositoryIds`/`repositoryUrls` arrays or `advanced.workspace`, optional `idempotencyKey` |
+| Update project | `paperclipUpdateProject` | `projectId`, changed fields |
+| List project workspaces | `paperclipListProjectWorkspaces` (extended) | `projectId` |
+| Create project workspace | `paperclipCreateProjectWorkspace` (extended) | `projectId`, `cwd`, `repoUrl`, `repoRef`, `isPrimary` |
+| Update project workspace | `paperclipUpdateProjectWorkspace` (extended) | `projectId`, `workspaceId`, changed fields |
+| Delete project workspace | `paperclipDeleteProjectWorkspace` (extended) | `projectId`, `workspaceId` |
 | List goals | `paperclipListGoals` | `companyId` |
 | Goal details | `paperclipGetGoal` | `goalId` |
 | Create goal | `paperclipCreateGoal` | `companyId`, goal fields |
-| Update goal | `paperclipUpdateGoal` | `id`, changed fields |
+| Update goal | `paperclipUpdateGoal` | `goalId`, changed fields |
 | Generate OpenClaw invite prompt (CEO/board only) | `paperclipApiRequest` | `method: "POST"`, `path: "/companies/:companyId/openclaw/invite-prompt"` |
 
 ### Routines
@@ -1470,16 +1470,16 @@ Every routine tool is extended.
 | Job | Tool | Key arguments |
 | --- | ---- | ------------- |
 | List all routines in company | `paperclipListRoutines` | `companyId` |
-| Routine details including triggers | `paperclipGetRoutine` | `id` |
+| Routine details including triggers | `paperclipGetRoutine` | `routineId` |
 | Create routine (agents: own only) | `paperclipCreateRoutine` | `companyId`, `assigneeAgentId` and `projectId` required |
-| Update routine (agents: own only, cannot reassign) | `paperclipUpdateRoutine` | `id`, changed fields |
-| Add trigger (`schedule`, `webhook`, or `api` kind) | `paperclipCreateRoutineTrigger` | `id`, `body` |
-| Update trigger (e.g. disable, change cron) | `paperclipUpdateRoutineTrigger` | `id`, changed fields |
-| Delete trigger | `paperclipDeleteRoutineTrigger` | `id` |
+| Update routine (agents: own only, cannot reassign) | `paperclipUpdateRoutine` | `routineId`, changed fields |
+| Add trigger (`schedule`, `webhook`, or `api` kind) | `paperclipCreateRoutineTrigger` | `routineId`, `body` |
+| Update trigger (e.g. disable, change cron) | `paperclipUpdateRoutineTrigger` | `routineTriggerId`, changed fields |
+| Delete trigger | `paperclipDeleteRoutineTrigger` | `routineTriggerId` |
 | Rotate webhook signing secret (previous secret immediately invalidated) | `paperclipApiRequest` | `method: "POST"`, `path: "/routine-triggers/:triggerId/rotate-secret"` |
-| Manual run (bypasses schedule; concurrency policy still applies) | `paperclipRunRoutine` | `id` |
+| Manual run (bypasses schedule; concurrency policy still applies) | `paperclipRunRoutine` | `routineId` |
 | Fire webhook trigger from external system | `paperclipFireRoutineTriggerPublic` | `publicId` |
-| Run history (default 50) | `paperclipListRoutineRuns` | `id` |
+| Run history (default 50) | `paperclipListRoutineRuns` | `routineId` |
 
 ### Approvals, Costs, Activity, Dashboard
 

package/skills/paperclip/references/artifacts.md

@@ -16,8 +16,8 @@ The helper uses `PAPERCLIP_API_URL`, `PAPERCLIP_API_KEY`, `PAPERCLIP_COMPANY_ID`
 
 ## Inspect What Is Already On The Issue
 
-- `paperclipListIssueAttachments` with `{ "id": "<issue-id>" }` lists the files attached to the issue, including each `attachmentId`.
-- `paperclipListIssueWorkProducts` with `{ "id": "<issue-id>" }` lists the recorded work products. Add `"refreshPullRequests": "true"` when you need pull request state refreshed first.
+- `paperclipListIssueAttachments` with `{ "issueId": "<issue-id>" }` lists the files attached to the issue, including each `attachmentId`.
+- `paperclipListIssueWorkProducts` with `{ "issueId": "<issue-id>" }` lists the recorded work products. Add `"refreshPullRequests": "true"` when you need pull request state refreshed first.
 - `paperclipDeleteAttachment` with `{ "attachmentId": "<attachment-id>" }` removes an attachment you uploaded by mistake. It is destructive; do not delete attachments you did not create.
 
 ## Record The Work Product
@@ -26,7 +26,7 @@ When the uploaded file is the deliverable, record it with `paperclipCreateIssueW
 
 ```json
 {
-  "id": "<issue-id>",
+  "issueId": "<issue-id>",
   "type": "artifact",
   "provider": "paperclip",
   "title": "Walkthrough render",
@@ -42,7 +42,7 @@ Read the returned work product record before you report the deliverable. If the
 When a recorded work product changes later, for example when its pull request merges, patch it with `paperclipUpdateWorkProduct` using the work product id:
 
 ```json
-{ "id": "<work-product-id>", "status": "done" }
+{ "workProductId": "<work-product-id>", "status": "done" }
 ```
 
 ## Workspace-Only File References
@@ -58,7 +58,7 @@ Annotate the work product with `metadata.resourceRef`, again through
 
 ```json
 {
-  "id": "<issue-id>",
+  "issueId": "<issue-id>",
   "type": "document",
   "provider": "workspace",
   "title": "Regression test plan",

package/skills/paperclip/references/cases.md

@@ -10,7 +10,7 @@ If a case tool reports `Cases are disabled`, stop and report that the operator
 must enable cases before the skill can use this surface.
 
 The case tools are in the `extended` toolset: they are available when the
-operator enables `PAPERCLIP_MCP_TOOLSETS=core,extended`. When they are not
+operator enables `PAPERCLIP_MCP_TOOLSETS=full`. When they are not
 loaded, use `paperclipApiRequest` for the same operations. Every tool below
 takes `companyId` only where noted; it defaults to the agent's company.
 
@@ -93,12 +93,12 @@ Useful arguments:
 ## Documents
 
 Use case documents for rich bodies such as drafts, briefs, reports, or plans.
-`paperclipSetCaseDocument` takes the case, the document `key`, and the body:
+`paperclipSetCaseDocument` takes the case, the document `documentKey`, and the body:
 
 ```json
 {
   "caseId": "PAP-C42",
-  "key": "body",
+  "documentKey": "body",
   "title": "Launch announcement body",
   "format": "markdown",
   "body": "# Launch announcement\n\nDraft copy...",
@@ -111,7 +111,7 @@ Updating an existing case document requires `baseRevisionId`:
 ```json
 {
   "caseId": "PAP-C42",
-  "key": "body",
+  "documentKey": "body",
   "baseRevisionId": "latest-revision-uuid",
   "body": "Updated body"
 }
@@ -136,7 +136,7 @@ Examples:
 }
 ```
 
-Patch fields or status with `paperclipUpdateCase`:
+Patch fields or status with `paperclipUpdateCaseById`:
 
 ```json
 {
@@ -158,7 +158,7 @@ Link cases to issues explicitly when needed with `paperclipCreateCaseLink`:
 
 ```json
 {
-  "id": "PAP-C42",
+  "caseId": "PAP-C42",
   "issueId": "issue-uuid",
   "role": "reference"
 }
@@ -241,7 +241,7 @@ Write the body with `paperclipSetCaseDocument`:
 ```json
 {
   "caseId": "PAP-C42",
-  "key": "body",
+  "documentKey": "body",
   "title": "Introducing Paperclip Cases",
   "format": "markdown",
   "body": "# Introducing Paperclip Cases\n\n..."
@@ -266,7 +266,7 @@ Create the child image-assets case with `paperclipCreateCase`:
 ```
 
 Attach the generated assets to the child's linked issue, then patch both cases
-as they move through review with `paperclipUpdateCase`:
+as they move through review with `paperclipUpdateCaseById`:
 
 ```json
 {

package/skills/paperclip/references/company-skills.md

@@ -2,7 +2,7 @@
 
 Use this reference when a board user, CEO, or manager asks you to find a skill, install it into the company library, or assign it to an agent.
 
-**Toolset:** `paperclipListSkills` is in the default `core` toolset. Every other tool on this page is in the `extended` toolset: it is available when the operator enables `PAPERCLIP_MCP_TOOLSETS=core,extended`; otherwise use `paperclipApiRequest`. `companyId` is optional on company-scoped tools and defaults to your company.
+**Toolset:** `paperclipListSkills` is in the default `core` toolset. Every other tool on this page is in the `extended` toolset: it is available when the operator enables `PAPERCLIP_MCP_TOOLSETS=full`; otherwise use `paperclipApiRequest`. `companyId` is optional on company-scoped tools and defaults to your company.
 
 ## What Exists
 
@@ -50,7 +50,7 @@ Company library:
 
 Agent attach and hire/create composition:
 
-- `paperclipListAgentSkills` — `{ "id": "<agent-id>" }`
+- `paperclipListAgentSkills` — `{ "agentId": "<agent-id>" }`
 - `paperclipSyncAgentSkill` — attach or detach company skills on an agent
 - `paperclipCreateAgentHire` — hire with `desiredSkills`
 - `paperclipCreateAgent` — direct create with `desiredSkills`
@@ -72,7 +72,7 @@ source. Bundled skills are the curated defaults for any company; optional
 skills are role- or domain-specific.
 
 Browse with `paperclipGetSkillCatalog`, inspect one entry with
-`paperclipGetSkillCatalogByCatalogId`, then install:
+`paperclipGetSkillCatalogByCatalogId`, then install with `paperclipInstallCatalogSkill`:
 
 ```json
 {
@@ -152,14 +152,14 @@ The server persists canonical company skill keys.
 
 ```json
 {
-  "id": "<agent-id>",
+  "agentId": "<agent-id>",
   "mode": "add",
   "desiredSkills": ["vercel-labs/agent-browser/agent-browser"]
 }
 ```
 
 If you need the current state first, call `paperclipListAgentSkills` with
-`{ "id": "<agent-id>" }`.
+`{ "agentId": "<agent-id>" }`.
 
 ## Include Skills During Hire Or Create
 

package/skills/paperclip/references/issue-workspaces.md

@@ -62,4 +62,4 @@ For QA/browser checks, use the service whose `status` is `running` and whose `he
 
 ## Workspace-Scoped Read
 
-When you already hold an execution workspace id — for example from another agent's comment — `paperclipGetExecutionWorkspace` with `{ "id": "<execution-workspace-id>" }` returns that workspace and its runtime services. Prefer the issue-scoped tools above when you start from an issue: they resolve the workspace id for you.
+When you already hold an execution workspace id — for example from another agent's comment — `paperclipGetExecutionWorkspace` with `{ "executionWorkspaceId": "<execution-workspace-id>" }` returns that workspace and its runtime services. Prefer the issue-scoped tools above when you start from an issue: they resolve the workspace id for you.