From ed89604ad87686d993dee6b24eaf50b62efd3060 Mon Sep 17 00:00:00 2001 From: xarmian Date: Sat, 17 Oct 2026 19:11:58 -0400 Subject: [PATCH] fix(mcp): a refused call names its cause on both transports (BUG-3864) (#2218) * fix(mcp): a refused call names its cause on both transports (BUG-3864) A 403 from one of the shared gates now carries details.reason (role, token_scope, no_access, workspace_not_authorized), with code and message unchanged. MCP builds one permission_denied envelope from it on both transports, with a hint that says what to do next. It used to lead with "Insufficient role" for every 403, so a bot with a read-only API token was told to ask for a role. An unverified Cloud email is reported as the server's own email_not_verified code. Stdio gets the same envelope from a structured marker the CLI root writes for a 403 coded forbidden, permission_denied or email_not_verified. Before it, the token-scope and unverified-email refusals said server_error there. ToolSurfaceVersion 0.99 -> 0.100 (behavior). Claude-Session: https://claude.ai/code/session_01MPeShv3DBfM9C94PTvMnqi * fix(server): the inline workspace-role gates name their reason too (BUG-3864) The bulk endpoint, the owner-only member doors and the owner-only app install and upgrade doors say role, or no_access for a guest. Claude-Session: https://claude.ai/code/session_01MPeShv3DBfM9C94PTvMnqi * fix(mcp): the permission hint is the same on both transports (BUG-3864) The remote hint appended the route, which stdio has no way to know, so one refusal reached the two transports with different hints. The tests compared prefixes only and missed it; both now assert the transports agree exactly. Claude-Session: https://claude.ai/code/session_01MPeShv3DBfM9C94PTvMnqi * fix(server): no role hint for a caller with no role to change (BUG-3864) requireMinRole and the grants list said role for a guest, who holds grants rather than a role, and for a caller with no workspace role at all. Both now go through roleGateReason, which answers no_access for either. Claude-Session: https://claude.ai/code/session_01MPeShv3DBfM9C94PTvMnqi --- README.md | 4 +- cmd/pad/bug3864_permission_reasons_test.go | 278 ++++++++++++++++++ cmd/pad/main.go | 5 + .../testdata/mcp_wire/remote_initialize.json | 4 +- .../testdata/mcp_wire/stdio_initialize.json | 4 +- docs/api.md | 1 + docs/mcp.md | 2 +- internal/cli/client.go | 38 +++ .../mcp/bug3864_permission_reasons_test.go | 87 ++++++ internal/mcp/dispatch_http.go | 27 +- internal/mcp/dispatch_http_artifact.go | 6 +- .../mcp/dispatch_http_verified_email_test.go | 13 +- internal/mcp/errors.go | 114 +++++-- internal/mcp/instructions.md | 2 +- internal/mcp/too_large_test.go | 3 + internal/mcp/version.go | 22 +- internal/server/authz_cross_workspace.go | 8 +- .../server/bug3864_forbidden_reason_test.go | 154 ++++++++++ internal/server/handlers_apps_provision.go | 2 +- internal/server/handlers_apps_upgrade.go | 2 +- internal/server/handlers_grants.go | 2 +- internal/server/handlers_items_bulk.go | 2 +- internal/server/handlers_members.go | 12 +- internal/server/middleware_auth.go | 12 +- internal/server/server.go | 35 ++- 25 files changed, 765 insertions(+), 74 deletions(-) create mode 100644 cmd/pad/bug3864_permission_reasons_test.go create mode 100644 internal/mcp/bug3864_permission_reasons_test.go create mode 100644 internal/server/bug3864_forbidden_reason_test.go diff --git a/README.md b/README.md index af0a52bc2..77b900194 100644 --- a/README.md +++ b/README.md @@ -402,7 +402,7 @@ directory for `claude-code`, and an `[mcp_servers.pad]` table in project-scoped, it's install-on-request only — `--all` and `pad mcp status` cover the per-user clients (including Codex) and skip it. -**Tool catalog (v0.99)** — ten resource × action tools plus `pad_set_workspace`. Undeclared input keys are rejected with a structured error rather than silently dropped, and field values are typed against the collection schema on the server: +**Tool catalog (v0.100)** — ten resource × action tools plus `pad_set_workspace`. Undeclared input keys are rejected with a structured error rather than silently dropped, and field values are typed against the collection schema on the server: | Tool | Actions | |---|---| @@ -426,7 +426,7 @@ Plus resources at `pad://workspaces`, `pad://workspace/{ws}/dashboard`, and `pad://_meta/version`. **Stability contract.** The catalog is versioned -(`tool_surface_version: "0.99"`) and advertised in the initialize handshake and at +(`tool_surface_version: "0.100"`) and advertised in the initialize handshake and at `pad://_meta/version`, so external agents can pin against it; the per-version changelog lives in [`internal/mcp/version.go`](internal/mcp/version.go). Errors come back as structured envelopes (`{error: {code, message, hint, ...}}`) from a diff --git a/cmd/pad/bug3864_permission_reasons_test.go b/cmd/pad/bug3864_permission_reasons_test.go new file mode 100644 index 000000000..b635ef5a3 --- /dev/null +++ b/cmd/pad/bug3864_permission_reasons_test.go @@ -0,0 +1,278 @@ +package main + +import ( + "bytes" + "context" + "encoding/json" + "net/http" + "net/http/httptest" + "os" + "strings" + "testing" + + "github.com/PerpetualSoftware/pad/internal/mcp" + "github.com/PerpetualSoftware/pad/internal/models" +) + +// BUG-3864: a refused MCP call names its cause. Before, every 403 reached a +// remote caller as permission_denied with a hint that LED with "Insufficient +// role for this operation", whatever the cause, and the stdio transport, +// which reads the CLI's stderr, said server_error for any refusal whose +// message did not happen to contain "forbidden". The support case was a bot +// with a read-only API token: reads worked, writes were refused, and the +// agent was told its role was the problem. +// +// Each row is a real refusal from the real server, reached through the +// shipped dispatchers on both transports: wireMCP's /mcp for remote, and the +// real command tree run as a subprocess for stdio. Both must report the same +// code, details.reason and hint. + +const ( + bug3864HintRole = "Your role in this workspace does not allow this. Ask a workspace owner to change your role." + bug3864HintScope = "This API token's access does not include this action: a 'Read only' token cannot make changes. Create a token with 'Read and write' access under Account settings → API Tokens, and use it instead." + bug3864HintNoAccess = "You do not have access to this workspace or collection. Ask a workspace owner for access." + bug3864HintEmail = "Verify your account's email address (the link is in your inbox, and the web app can send a new one). Changes are refused until then." +) + +// bug3864Op is one refused write, in both transports' terms. +type bug3864Op struct { + remote map[string]any // pad_item arguments, less workspace + cmdPath []string // the CLI command stdio runs + argv []string // its flags and, after "--", its positionals +} + +var bug3864Create = bug3864Op{ + remote: map[string]any{"action": "create", "collection": "tasks", "title": bug3864Title}, + cmdPath: []string{"item", "create"}, + argv: []string{"--", "tasks", bug3864Title}, +} + +type bug3864Want struct { + code mcp.ErrorCode + reason string // details.reason; "" means the field must be absent + hint string // the hint must START with this +} + +func TestBUG3864_RefusalsNameTheirCauseOnBothTransports(t *testing.T) { + f := newCapFixture(t, cfgHTTP, false, nil, "true") + if err := f.store.SeedCollectionsFromTemplate(f.ws.ID, "startup"); err != nil { + t.Fatal(err) + } + viewer := bug3864User(t, f, "viewer@example.com", false) + if err := f.store.AddWorkspaceMember(f.ws.ID, viewer.ID, "viewer"); err != nil { + t.Fatal(err) + } + + // A guest holds a view grant on one item. Editing it reaches the edit + // check, which a role change cannot satisfy: the guest has no role. + guest := bug3864User(t, f, "guest@example.com", false) + granted, err := f.store.CreateItem(f.ws.ID, bug3864TasksID(t, f), models.ItemCreate{Title: "granted"}) + if err != nil { + t.Fatal(err) + } + if _, err := f.store.CreateItemGrant(f.ws.ID, granted.ID, guest.ID, "view", f.member.ID); err != nil { + t.Fatal(err) + } + guestEdit := bug3864Op{ + remote: map[string]any{"action": "update", "ref": granted.Ref, "title": bug3864Title}, + cmdPath: []string{"item", "update"}, + argv: []string{"--title", bug3864Title, "--", granted.Ref}, + } + + rows := []struct { + name string + token string + op bug3864Op + want bug3864Want + }{ + {"role", bug3864Token(t, f, viewer, `["*"]`), bug3864Create, bug3864Want{mcp.ErrPermissionDenied, "role", bug3864HintRole}}, + {"token_scope", bug3864Token(t, f, f.member, `["read"]`), bug3864Create, bug3864Want{mcp.ErrPermissionDenied, "token_scope", bug3864HintScope}}, + // A non-member is answered 404, which hides that the workspace exists. + // The 403 is a platform admin's bearer token, which reaches only the + // workspaces the admin is a member of (BUG-1616). + {"no_access", bug3864Token(t, f, f.admin, `["*"]`), bug3864Create, bug3864Want{mcp.ErrPermissionDenied, "no_access", bug3864HintNoAccess}}, + {"guest edit", bug3864Token(t, f, guest, `["*"]`), guestEdit, bug3864Want{mcp.ErrPermissionDenied, "no_access", bug3864HintNoAccess}}, + } + for _, r := range rows { + var remote, stdio mcp.ErrorEnvelope + t.Run(r.name+"/remote", func(t *testing.T) { + remote = bug3864Remote(t, f, r.token, r.op) + bug3864Check(t, remote, r.want) + }) + t.Run(r.name+"/stdio", func(t *testing.T) { + stdio = bug3864Stdio(t, f, r.token, r.op) + bug3864Check(t, stdio, r.want) + }) + bug3864Same(t, r.name, remote, stdio) + } + if n := bug3864CountTitled(t, f); n != 0 { + t.Errorf("a refused write created %d items", n) + } +} + +// The Cloud-only cause: an account whose email is unverified may read and may +// not write. The remote transport refuses in its own gate before the request +// is built; stdio reaches the server's RequireVerifiedEmail middleware. +func TestBUG3864_UnverifiedEmailIsItsOwnCodeOnBothTransports(t *testing.T) { + f := newCapFixture(t, cfgHTTP, true, nil, "true") + if err := f.store.SeedCollectionsFromTemplate(f.ws.ID, "startup"); err != nil { + t.Fatal(err) + } + unverified := bug3864User(t, f, "unverified@example.com", true) + if err := f.store.AddWorkspaceMember(f.ws.ID, unverified.ID, "owner"); err != nil { + t.Fatal(err) + } + tok := bug3864Token(t, f, unverified, `["*"]`) + want := bug3864Want{mcp.ErrorCode("email_not_verified"), "", bug3864HintEmail} + var remote, stdio mcp.ErrorEnvelope + t.Run("remote", func(t *testing.T) { remote = bug3864Remote(t, f, tok, bug3864Create); bug3864Check(t, remote, want) }) + t.Run("stdio", func(t *testing.T) { stdio = bug3864Stdio(t, f, tok, bug3864Create); bug3864Check(t, stdio, want) }) + bug3864Same(t, "unverified email", remote, stdio) +} + +func bug3864User(t *testing.T, f *capFixture, email string, unverified bool) *models.User { + t.Helper() + u, err := f.store.CreateUser(models.UserCreate{Email: email, Name: email, Password: "correct-horse-battery-staple", Unverified: unverified}) + if err != nil { + t.Fatal(err) + } + return u +} + +func bug3864Token(t *testing.T, f *capFixture, u *models.User, scopes string) string { + t.Helper() + tok, err := f.store.CreateAPIToken(u.ID, models.APITokenCreate{Name: "bot", Scopes: scopes}, 30, 0) + if err != nil { + t.Fatal(err) + } + return tok.Token +} + +const bug3864Title = "bug3864 refused write" + +func bug3864Remote(t *testing.T, f *capFixture, token string, op bug3864Op) mcp.ErrorEnvelope { + t.Helper() + const proto = "2025-11-25" + call := func(id int, method string, params map[string]any) []byte { + t.Helper() + body, _ := json.Marshal(map[string]any{"jsonrpc": "2.0", "id": id, "method": method, "params": params}) + req := httptest.NewRequest("POST", "/mcp", bytes.NewReader(body)) + req.Host = f.host + req.RemoteAddr = "192.0.2.10:4242" + req.Header.Set("Content-Type", "application/json") + req.Header.Set("Accept", "application/json, text/event-stream") + req.Header.Set("MCP-Protocol-Version", proto) + req.Header.Set("Authorization", "Bearer "+token) + rr := newMCPRecorder() + f.srv.ServeHTTP(rr, req) + if rr.Code != http.StatusOK { + t.Fatalf("%s: %d %s", method, rr.Code, rr.Body.String()) + } + return rr.Body.Bytes() + } + call(1, "initialize", map[string]any{ + "protocolVersion": proto, "capabilities": map[string]any{}, + "clientInfo": map[string]any{"name": "bug3864", "version": "1"}, + }) + args := map[string]any{"workspace": f.ws.Slug} + for k, v := range op.remote { + args[k] = v + } + out := call(2, "tools/call", map[string]any{"name": "pad_item", "arguments": args}) + var rpc struct { + Result struct { + IsError bool `json:"isError"` + StructuredContent mcp.ErrorEnvelope `json:"structuredContent"` + } `json:"result"` + } + if err := json.Unmarshal(out, &rpc); err != nil { + t.Fatalf("decode tools/call: %v: %s", err, out) + } + if !rpc.Result.IsError { + t.Fatalf("PRECONDITION: the write should have been refused: %s", out) + } + return rpc.Result.StructuredContent +} + +func bug3864Stdio(t *testing.T, f *capFixture, token string, op bug3864Op) mcp.ErrorEnvelope { + t.Helper() + ts := httptest.NewServer(http.HandlerFunc(func(w http.ResponseWriter, r *http.Request) { + r.Host = f.host + r.RemoteAddr = "192.0.2.10:4242" + f.srv.ServeHTTP(w, r) + })) + defer ts.Close() + + t.Setenv(padHelperEnv, "1") + t.Setenv("HOME", t.TempDir()) + t.Setenv("PAD_TOKEN", token) + bin, err := os.Executable() + if err != nil { + t.Fatal(err) + } + d := &mcp.ExecDispatcher{Binary: bin} + argv := append([]string{"--url", ts.URL, "--workspace", f.ws.Slug, "--format", "json"}, op.argv...) + res, err := d.Dispatch(context.Background(), op.cmdPath, argv) + if err != nil { + t.Fatalf("Dispatch: %v", err) + } + env, ok := res.StructuredContent.(mcp.ErrorEnvelope) + if !ok { + t.Fatalf("PRECONDITION: the write should have been refused; got %T %+v", res.StructuredContent, res.Content) + } + return env +} + +func bug3864Check(t *testing.T, env mcp.ErrorEnvelope, want bug3864Want) { + t.Helper() + got := "" + if len(env.Error.Details) > 0 { + var d struct { + Reason string `json:"reason"` + } + _ = json.Unmarshal(env.Error.Details, &d) + got = d.Reason + } + if env.Error.Code != want.code || got != want.reason || !strings.HasPrefix(env.Error.Hint, want.hint) { + t.Errorf("got code=%q reason=%q hint=%q (message %q)\nwant code=%q reason=%q hint starting %q", + env.Error.Code, got, env.Error.Hint, env.Error.Message, want.code, want.reason, want.hint) + } + if want.reason != "role" && strings.Contains(strings.ToLower(env.Error.Hint), "role") { + t.Errorf("a %q refusal must not blame a role: hint %q", want.reason, env.Error.Hint) + } +} + +func bug3864CountTitled(t *testing.T, f *capFixture) int { + t.Helper() + items, err := f.store.ListItems(f.ws.ID, models.ItemListParams{}) + if err != nil { + t.Fatal(err) + } + n := 0 + for _, it := range items { + if it.Title == bug3864Title { + n++ + } + } + return n +} + +func bug3864TasksID(t *testing.T, f *capFixture) string { + t.Helper() + c, err := f.store.GetCollectionBySlug(f.ws.ID, "tasks") + if err != nil || c == nil { + t.Fatalf("tasks collection: %v", err) + } + return c.ID +} + +// bug3864Same: one refusal, one answer. The message may differ (the remote +// dispatcher refuses some writes before the server sees them), but the code, +// details and hint an agent acts on may not. +func bug3864Same(t *testing.T, name string, remote, stdio mcp.ErrorEnvelope) { + t.Helper() + if remote.Error.Code != stdio.Error.Code || remote.Error.Hint != stdio.Error.Hint || string(remote.Error.Details) != string(stdio.Error.Details) { + t.Errorf("%s: the transports differ:\n remote code=%q details=%s hint=%q\n stdio code=%q details=%s hint=%q", name, + remote.Error.Code, remote.Error.Details, remote.Error.Hint, stdio.Error.Code, stdio.Error.Details, stdio.Error.Hint) + } +} diff --git a/cmd/pad/main.go b/cmd/pad/main.go index bb583452d..0d45110c6 100644 --- a/cmd/pad/main.go +++ b/cmd/pad/main.go @@ -95,6 +95,11 @@ func writeRootStructuredError(w io.Writer, err error) { // PLAN-3578: a patch whose anchor no longer matches, or an open item. if apiErr, ok := cli.IsPatchRefusal(err); ok { cli.WritePatchRefusalError(w, apiErr) + return + } + // BUG-3864: a 403 refusing the caller, with the server's details.reason. + if apiErr, ok := cli.IsPermissionDenied(err); ok { + cli.WritePermissionDeniedError(w, apiErr) } } diff --git a/cmd/pad/testdata/mcp_wire/remote_initialize.json b/cmd/pad/testdata/mcp_wire/remote_initialize.json index e37591b79..5fe76f2f7 100644 --- a/cmd/pad/testdata/mcp_wire/remote_initialize.json +++ b/cmd/pad/testdata/mcp_wire/remote_initialize.json @@ -8,7 +8,7 @@ }, "padToolSurface": { "tool_surface_stable": true, - "version": "0.99" + "version": "0.100" } }, "prompts": {}, @@ -21,5 +21,5 @@ "name": "pad-mcp", "version": "" }, - "instructions": "Pad is a project tracker for developers and AI agents — issues (TASK, BUG), plans (PLAN), ideas (IDEA), docs (DOC), conventions, comments, and dependencies. Use this server when a user mentions:\n\n- Issue refs like `TASK-5`, `BUG-12`, `PLAN-3`, `IDEA-8` — they are stable, human-readable IDs and the canonical way to address items. Use them, never slugs; they are what audit trails and PR titles show.\n- Tasks / issues / items / plans / progress / \"what's on my plate\" / \"what to work on next\" / standup / changelog / retrospective.\n- Project conventions, decision records, or \"how should this team do X.\"\n\nIf the user is asking general code questions with no project-management thread, you don't need this server.\n\n## Tool surface (v0.99)\n\nTen resource × action tools, plus `pad_set_workspace`. Eleven tools total.\n\nInputs are validated strictly: an undeclared top-level key is rejected with a structured `validation_failed` naming it, never accepted and silently dropped.\n\n- `pad_item` — Items: create / update / delete / get / list / move / restore / link / unlink / deps / context / star / unstar / starred / comment / list-comments / edit-comment / delete-comment / backlinks / bulk-update / note / decide / export / import / history / remind / ack-reminder / reminders / unremind / link-pr / unlink-pr / claim / release / patch. On create/update, field values may be passed as a `fields` OBJECT (the same shape reads return, e.g. `{\"status\":\"done\",\"effort\":\"l\"}`) — it merges into the same path as the dedicated params and `field: [\"key=value\"]`; the same key in two places with CONFLICTING values is refused, not silently resolved. `list` accepts `unparented: true` to keep items with no parent or implements relationship (mutually exclusive with `parent`). `list` results are SUMMARY-shaped by default on both transports — no content bodies; pass `full: true` for complete bodies (token-expensive), or prefer `get` for a single item's body. `update` field writes are a server-side field-level merge (only the keys you set change); pass `expected_seq` for optimistic concurrency — the `seq` you last read, which is on every item AND every list summary — and a stale value fails with a structured 409 `update_conflict` whose details carry `actual_seq` to retry with. PREFER IT over `expected_updated_at`, which cannot tell two writes inside one second apart; that one still works, and if you send both, seq decides. To change PART of a body, prefer `patch`: `edits: [{old, new}]`, where each `old` is exact text occurring once in the current body (read it with `get` and `lines: \"A-B\"` to quote it). The answer is a unified `diff`: read it, because anchors guarantee position, not meaning. A moved `expected_seq` is applied over and reported as `rebased` with the intervening writes. On an item open in a browser editor, the editor applies the patch to its live document, merging with the typing there, and the answer says `content_state: \"applied_pending_flush\"`. `patch_anchor_missing` / `patch_anchor_ambiguous` mean re-read and quote current text; `patch_unstable_roundtrip` means the open editor would also change content you did not edit, so send a whole-body update; `patch_room_open` means an older editor that cannot apply patches holds the item. Every patch answer carries a `patch_id`; `patch` with `undo: \u003cpatch_id\u003e` inverts it, and is refused when the text it changed has changed since. Send an `op_key` (any unique string, e.g. a UUID) with a patch whenever you might retry it: the same request with the same key returns the first answer instead of applying twice. `patch_outcome_unknown` means an earlier attempt's editor never confirmed it and is gone; read `details.diff` before deciding. `content` REPLACES the whole body, so send `expected_seq` with it: `get` the item, edit that body, and send it back with the `seq` you read. An `update_conflict` whose details carry `content_write` means someone changed the item after your read. Do NOT resend your body, because it would undo their change: re-read, apply your edit to the current content, and send that with the new seq. `replace: true` overwrites on purpose instead. A content write with neither carries `warnings.unguarded_content_write`, and a later release refuses it. A token cannot see a browser tab's unsaved edits, so `content` sent WITH one is refused with 409 `content_pending_flush` while any exist; re-reading will not clear it. Wait for the editor to save, or pass `overwrite_pending_edits: true` to replace them. `content_state: \"superseded_set_aside\"` is different and wins when both apply: an editor upgrade set aside edits no tab can restore, so EVERY content write is refused (token or not; `details.set_aside_rows`) and waiting never clears it. Tell the user, or pass `overwrite_pending_edits: true` to discard them. Writing `content` while a browser tab has the item open routes the markdown through that live document; the stored row updates only on a later collab-snapshot flush, which nothing guarantees. The 200 echoes what you SENT with `warnings.content_outcome: \"applied_pending_flush\"`, which describes your WRITE (it went to the document, not the row). A `get` (or a `list` with `full: true`; a default list carries no content) before the flush returns the PREVIOUS content: that is lag, not a failed write, so do not re-send. A read whose body the server knows is behind the live document carries `content_state: \"applied_pending_flush\"`, also when someone ELSE's tab holds the edits and you wrote nothing: same value, but it describes the ROW, not your request. Treat it as re-read later, never as re-send, and do not wait on it in a loop: the server normally recovers the stored copy itself about a minute after the last tab leaves the item, but that is not guaranteed (a recovery can fail, and an operator can turn it off), and otherwise the row catches up only when a tab next opens the item. The stored form may also not be byte-identical to what you sent, since the markdown round-trips through the editor (bullet markers, emphasis characters, list numbering and blank-line runs normalise; already-canonical markdown survives unchanged), so compare on meaning rather than bytes. `move` changes an item's COLLECTION within its workspace: system metadata (implementation notes, decision log, linked PR) survives it, and any field value the target schema has no home for is dropped AND reported in the move's activity entry — check there rather than assuming a move is lossless. A carried unique-field collision is dropped, named in `warnings.not_unique`. Three system keys — `implementation_notes`, `decision_log`, `convention` — cannot be set through `field` on update or move; the call is refused with `validation_failed`, naming the key and the write path that does maintain it (`note`, `decide`, and library activation respectively). `github_pr` is refused as well (BUG-2696): a `field` value arrived as a string, so the PR data was stored double-encoded and no link appeared. Its writers are `action=link-pr` (`pr_number` + `pr_url`, metadata you supply; nothing is fetched from GitHub) and `action=unlink-pr`. On `create` they are refused too (BUG-3163), with the same `validation_failed`: create the item first, then use `note` / `decide` on it; convention metadata comes from library activation. `context` (`intent`, `role`, `budget`): one brief before you start work, with parents, matching convention bodies, deps and links. `history` returns read-only item version metadata (newest-first), bounded to the NEWEST 50 versions by default (max 300 — pass `limit` to change the window); pass `full: true` to include each version's resolved content body (token-expensive). There is no `offset`: versions are stored as reverse patches, so only a newest-end window is cheap to reconstruct. Unassign or detach with the `clear_assigned_user` / `clear_agent_role` / `clear_parent` booleans; an empty `assign` / `role` / `parent` does NOT clear. `remind` / `ack-reminder`: a fired reminder shows in `pad_project` next / ready (the delivery path on an instance with no webhook) until acknowledged, and one on a completed item is hidden there. `claim` / `release`: claim an item before you work it; a loser's 409 is `lease_held` (pick another, don't retry), and a lease bumps neither `updated_at` nor `seq`. A claim answers your `worker_id`; pass it to resume elsewhere. next / ready skip items other workers hold. `edit-comment` / `delete-comment` take a `comment_id` from `list-comments` (whose rows carry `edited`); only a comment's author may edit it. Correct a comment in place rather than appending a correction. Deleting a comment that has replies leaves a placeholder (`deleted: true`, empty body) so the replies keep their parent; editing, replying to or reacting to it answers 409 `comment_deleted`.\n\n**List filters must name a field (v0.75).** A `pad_item` `list` filter on a key no collection in scope declares, and no item stores, is refused with `validation_failed` (\"invalid list filter\"), where it used to return an empty list; a stored undeclared key still filters. Check the schema; don't retry.\n\n**Library words in a blank workspace (v0.67).** A brand-new blank workspace lists one convention trigger (`always`) and one scope (`all`). Activating a library entry, or creating a convention or playbook with a trigger or scope the library itself uses, adds that word to the collection's options and says so in `warnings.options_added`. A trigger you invent is still refused until the workspace owner adds it to the collection's schema.\n\n**App attribution (v0.65).** An item an installed app created, a comment an app wrote and a history row an app's write made carry `via_app` (the install id) and `via_app_name` (the app's name). On an item they name the app that CREATED it, not the last writer. They are absent for anything a person or an agent wrote.\n\n**Relation fields (v0.31).** A `relation` value may be a UUID, an issue ref (`COLO-3`) or the target's EXACT TITLE, tried in that order (a title that is also a ref resolves as the ref). A title matches only inside the declared collection, among items you can see; found only elsewhere, it is refused naming that collection; several matches are `ambiguous`. Full rules: docs/mcp.md.\n\nReads carry a `relation_targets` member beside `fields`: field key → `{id, ref, title}`, so you can render a relation without a request per value. `fields` still holds the canonical id, which is what you write back. An entry with an `id` and NO `ref`/`title` means the target is gone **or** you may not see it — the two are deliberately indistinguishable, so do not render it as either \"deleted\" or \"hidden\"; \"unavailable\" is the honest word. An entry with `stored_as_text: true` differs: the stored value is not UUID-shaped, so it was never an id (an imported title, legacy text). Render it as text, not as unavailable.\n\n**`multi_relation` fields (v0.33).** An ORDERED LIST of references, each resolved like a `relation` (UUID, ref, or exact title in the declared collection). Declare one as `owners:multi_relation:people`; the target collection is required. Rules: `[]` means absent; a blank element is refused by index; order is part of the value; duplicates are refused after resolution (`duplicate_referent`); any failing element refuses the whole write; `required` needs one resolved element; a cross-workspace copy drops the whole value (in `warnings.dropped_fields`). `relation_targets` holds an ARRAY of `{id, ref, title}` in stored order (`id`-only where unresolved); scalar keys stay single objects. Full rules: docs/mcp.md.\n\n- `pad_workspace` — Workspaces: list / members / invite / storage / audit-log / create / claim / deleted / restore.\n- `pad_collection` — Collections: list / create / update / delete / list-archived / restore. `delete` archives: the collection and its items leave every view, and `restore` brings them back. An `update` that removes a field or a select option still in use answers with `warnings.orphaned`: tell the user how many items keep the removed value.\n- `pad_project` — Project intelligence: dashboard / next / ready / stale / standup / changelog / report / activity. Use `ready` for the ranked top items to work on next (blocked work is left out) and `stale` for items needing attention; `activity` to catch up on what other agents/users changed since you last worked (non-streaming feed with item refs + change details).\n- `pad_role` — Agent roles: list / create / update / delete.\n- `pad_search` — Full-text search across items: query.\n- `pad_playbook` — Invokable procedures: list / get / run / match. Use `run` to bind args against a playbook's declared spec and get the rendered body back; side-effect-free. `run` refuses a playbook whose status isn't `active` (a draft still being authored) with a `playbook_not_active` error — pass `allow_draft: true` to override. Both `run` and `get` echo the playbook's `status`. Both may also carry `content_state` (`\"applied_pending_flush\"`, or `\"superseded_set_aside\"` as under `pad_item`), meaning the BODY you are about to execute is behind the item's live collaborative document — an editor holds unflushed edits, so the steps may be superseded. It is a reason to re-read or to ask, not a reason to refuse to run; the body is still the best the server has. `match` finds a playbook from text.\n- `pad_library` — Convention + playbook library (the global catalog of pre-built entries workspaces activate): list / get / activate.\n- `pad_attachment` — Read-only attachment metadata: list / show. `list` enumerates a workspace's attachments (filter by item / category / collection / attached / unattached); `show` returns one attachment's MIME, size, filename, and ETag via a HEAD request. Uploading and general file downloads stay CLI-only; bounded image bytes are available through the attachment resource below.\n- `pad_meta` — Server introspection: server-info / version / tool-surface / bootstrap. The `bootstrap` action returns one-shot workspace context (user + collections + always-on conventions + a metadata-only `convention_index` of every active convention + roles + playbook metadata + dashboard + recent activity).\n- `pad_set_workspace` — Load workspace context; response embeds the bootstrap blob so you load context in one call. Whether it also pins a session default: see Workspace context below. Takes `workspace: \u003cslug\u003e` only (no `action`).\n\nFor the ten resource × action tools, always pass `action` as a top-level field. Per-action required parameters are documented in each tool's description.\n\n## Resources are cheaper than tool calls\n\nRead these directly when you need workspace state (described in the resource listings): `pad://workspaces`, `pad://workspace/{ws}/dashboard`, `.../collections`, `.../items` (use `pad_item` `list` to filter), `.../items/{ref}` (markdown), `.../attachments/{id}` (images only, at most 1 MiB, as base64 `thumb-md`), `.../bootstrap` (the same payload as `pad_meta` `bootstrap`), and `pad://_meta/version`. A host can prefetch them once per session.\n\nLoad the bootstrap resource once per workspace and reuse its collections, conventions, roles, and playbook metadata. Refresh it after switching workspaces, after changing those configuration surfaces, when Pad reports stale schema/context, or when the user asks. For changing work state, read the affected item or use a targeted project tool instead of fetching the whole bootstrap again.\n\n## Workspace context\n\nEvery action that operates within a workspace accepts an optional `workspace` parameter. Resolution order:\n\n1. Explicit `workspace` argument on the call (always wins).\n2. On a single-user local server only: the session default set via `pad_set_workspace`.\n3. On a single-user local server only: the CWD-linked workspace from `.pad.toml`.\n\nA multi-user/remote server does **not** persist a session default — pass `workspace` explicitly on every call. If none resolves, the action returns a structured `no_workspace` error with `available_workspaces`, on both the local and the remote transport.\n\n## Update flow: read first, then patch\n\nFor `pad_item.action: update`, the server merges your patch with the item's current state. Pass only the fields you want to change. When changing `status`, ALWAYS include a `comment` explaining why — it builds the audit trail that helps the team understand history.\n\n## One error code you must not retry\n\nErrors come back as a structured envelope with a `code`. Most failures are worth a retry after you fix something, and a `server_error` may be transient. `stored_state_unreadable` is neither.\n\nIt means the ITEM'S STORED DATA cannot be decoded — your input was fine. Today it fires when `note` / `decide` would append to an `implementation_notes` / `decision_log` value that is not a list of entries. The operation is refused precisely because completing it would overwrite that value. The refusal is fully deterministic, so retrying — immediately or after a backoff — fails identically every time and changes nothing.\n\nWhen you see it: tell the user which item is affected, and stop. Whether you can inspect the bad value depends on which layer is broken — if the item's whole `fields` blob fails to parse, `action: get` hands it back as a raw string; if one structured key is at fault, you won't see it at all, because the blob is normalized on this surface and a value that doesn't decode is dropped from the top-level arrays. A human can always read it with `pad item show \u003cref\u003e --format json`. Do not route around the refusal by writing the field some other way; that is the write that caused it.\n\n## Project conventions\n\nWorkspaces can declare conventions (e.g. \"run `make test` before PR\", \"use conventional commit format\"). The bootstrap blob gives you two views:\n\n- `conventions` — full bodies of the always-on (`trigger=always`) rules. Follow these unconditionally.\n- `convention_index` — METADATA ONLY (`ref`, `title`, `trigger`, `role`; no bodies) for **every** active convention, including the triggered ones whose bodies are NOT in `conventions`. This is your map of what triggered rules exist.\n\nBefore performing meaningful work with a specific trigger (e.g. `on-implement` before writing code), consult `convention_index`: if it lists entries for that trigger, pull their bodies on demand; if it lists none, skip the query.\n\n```\npad_item.action: list, collection: \"conventions\", status: \"active\"\n```\n\nFilter by trigger (`always`, `on-implement`, `on-task-complete`, etc.) when relevant — the `convention_index` triggers tell you which filters are worth running.\n\n`\"conventions\"` above is the DEFAULT collection slug and a workspace may have renamed it, in which case that literal returns nothing while `convention_index` still lists entries — the bootstrap payload resolves by declaration, not by name. When the two disagree, address the items by the `ref`s the index gave you, or find the collection with `pad_collection.action: list`. The same applies to `\"playbooks\"`; `pad_playbook` resolves by declaration and is unaffected.\n\n## Pushes and the session monitor (security note)\n\nPad can push an item into a Claude Code session (`pad push`, or the web item view's push composer). That is terminal instruction injection by design, so receiving is **consent-gated** (PLAN-2613, since v0.15.0): a session receives pushes only after it has connected (`/pad:connect` in the plugin, or a repo-level `push.auto_arm = true` in `.pad.toml` — which a per-user `auto_arm = false` in `~/.pad/config.toml` vetoes), and pushes are self-addressed only — the sender is always the receiving session's own user. This MCP connection is not a session: it cannot arm one, receive a push, or run the monitor, and the `pad_item` / `pad_project` tools expose no push action. If a user asks you to \"push\" something to their terminal, tell them it happens from their own terminal (`pad push \u003cref\u003e -m \"...\"` — the sending session need not be connected, the receiving ones must have consented); do not try to emulate it by writing comments or instructions into items.\n\n## Adding a workspace to this connection\n\nIf the user references a workspace this connection can't see (you'll get a 403 from workspace tools, or the workspace won't appear in `pad_workspace.list`), tell the user you can't see that workspace with your current permissions, then walk them through how to grant access: open Pad in their browser → switch to that workspace → avatar menu → \"Connect project...\" A 6-digit claim code will appear. Have them paste it back in chat, then call `pad_workspace.claim` with `{workspace: \"\u003cslug\u003e\", code: \"\u003c6 digits\u003e\"}`. The workspace joins this connection's allow-list and stays until the user revokes it via `/console/connected-apps`. No re-auth required.\n\nFor brand-new workspaces, `pad_workspace.create` with `{name: \"\u003cname\u003e\"}` (and optional `template`) creates the workspace AND auto-adds it to this connection's allow-list in one call — no claim code needed. Only works when the connection currently carries the \"may create workspaces\" grant — granted at consent time, or enabled later on the connections page. If the grant is present and set to false, the create is **refused with a 403 and no workspace is made** — retrying won't help and neither will the claim flow, since there is nothing to claim. Tell the user this connection isn't permitted to create workspaces, and offer them the two ways forward: create the workspace themselves in the browser and grant access with a claim code, or re-authorize this connection with \"Let this app create new workspaces\" enabled (`/console/connected-apps` can also flip it on an existing connection).\n\n## New workspace: offer to set it up\n\nThe bootstrap blob carries `needs_onboarding: bool` — true when the workspace has zero user-created items (template seeds don't count). When it's true, **lead with an active offer before anything else**: *\"This workspace is brand new and isn't set up yet. Want me to set it up? I'll ask a few quick questions and adapt it to your project.\"*\n\nThis is an **offer, not an auto-run** — wait for the user to say yes before running onboarding. If they accept, run the `onboard` playbook (use the `pad_onboard` prompt, or load the body via `pad_playbook` `action: get`, `ref: onboard`). If they decline, or already declined earlier in the session, respect that and skip the offer. The flag flips to false the moment any item exists, so it won't nag past first setup.\n\n## Built-in updates: mention once\n\nThe bootstrap blob may carry `builtin_updates: int` (absent when there are none): how many of the conventions and playbooks Pad ships have newer text in Pad's library than this workspace's copy. When it is present, mention it **once per session**, in one line, then carry on. **Never apply an update yourself**: a person reviews each one and accepts it or not.\n\n## Multi-step workflows\n\nFour prompts ship with the server: `pad_plan`, `pad_ideate`, `pad_retro`, `pad_onboard`. Use them when the user wants help planning, brainstorming, retrospecting, or onboarding into a workspace — they encode the multi-step Pad-aware playbook for each.\n" + "instructions": "Pad is a project tracker for developers and AI agents — issues (TASK, BUG), plans (PLAN), ideas (IDEA), docs (DOC), conventions, comments, and dependencies. Use this server when a user mentions:\n\n- Issue refs like `TASK-5`, `BUG-12`, `PLAN-3`, `IDEA-8` — they are stable, human-readable IDs and the canonical way to address items. Use them, never slugs; they are what audit trails and PR titles show.\n- Tasks / issues / items / plans / progress / \"what's on my plate\" / \"what to work on next\" / standup / changelog / retrospective.\n- Project conventions, decision records, or \"how should this team do X.\"\n\nIf the user is asking general code questions with no project-management thread, you don't need this server.\n\n## Tool surface (v0.100)\n\nTen resource × action tools, plus `pad_set_workspace`. Eleven tools total.\n\nInputs are validated strictly: an undeclared top-level key is rejected with a structured `validation_failed` naming it, never accepted and silently dropped.\n\n- `pad_item` — Items: create / update / delete / get / list / move / restore / link / unlink / deps / context / star / unstar / starred / comment / list-comments / edit-comment / delete-comment / backlinks / bulk-update / note / decide / export / import / history / remind / ack-reminder / reminders / unremind / link-pr / unlink-pr / claim / release / patch. On create/update, field values may be passed as a `fields` OBJECT (the same shape reads return, e.g. `{\"status\":\"done\",\"effort\":\"l\"}`) — it merges into the same path as the dedicated params and `field: [\"key=value\"]`; the same key in two places with CONFLICTING values is refused, not silently resolved. `list` accepts `unparented: true` to keep items with no parent or implements relationship (mutually exclusive with `parent`). `list` results are SUMMARY-shaped by default on both transports — no content bodies; pass `full: true` for complete bodies (token-expensive), or prefer `get` for a single item's body. `update` field writes are a server-side field-level merge (only the keys you set change); pass `expected_seq` for optimistic concurrency — the `seq` you last read, which is on every item AND every list summary — and a stale value fails with a structured 409 `update_conflict` whose details carry `actual_seq` to retry with. PREFER IT over `expected_updated_at`, which cannot tell two writes inside one second apart; that one still works, and if you send both, seq decides. To change PART of a body, prefer `patch`: `edits: [{old, new}]`, where each `old` is exact text occurring once in the current body (read it with `get` and `lines: \"A-B\"` to quote it). The answer is a unified `diff`: read it, because anchors guarantee position, not meaning. A moved `expected_seq` is applied over and reported as `rebased` with the intervening writes. On an item open in a browser editor, the editor applies the patch to its live document, merging with the typing there, and the answer says `content_state: \"applied_pending_flush\"`. `patch_anchor_missing` / `patch_anchor_ambiguous` mean re-read and quote current text; `patch_unstable_roundtrip` means the open editor would also change content you did not edit, so send a whole-body update; `patch_room_open` means an older editor that cannot apply patches holds the item. Every patch answer carries a `patch_id`; `patch` with `undo: \u003cpatch_id\u003e` inverts it, and is refused when the text it changed has changed since. Send an `op_key` (any unique string, e.g. a UUID) with a patch whenever you might retry it: the same request with the same key returns the first answer instead of applying twice. `patch_outcome_unknown` means an earlier attempt's editor never confirmed it and is gone; read `details.diff` before deciding. `content` REPLACES the whole body, so send `expected_seq` with it: `get` the item, edit that body, and send it back with the `seq` you read. An `update_conflict` whose details carry `content_write` means someone changed the item after your read. Do NOT resend your body, because it would undo their change: re-read, apply your edit to the current content, and send that with the new seq. `replace: true` overwrites on purpose instead. A content write with neither carries `warnings.unguarded_content_write`, and a later release refuses it. A token cannot see a browser tab's unsaved edits, so `content` sent WITH one is refused with 409 `content_pending_flush` while any exist; re-reading will not clear it. Wait for the editor to save, or pass `overwrite_pending_edits: true` to replace them. `content_state: \"superseded_set_aside\"` is different and wins when both apply: an editor upgrade set aside edits no tab can restore, so EVERY content write is refused (token or not; `details.set_aside_rows`) and waiting never clears it. Tell the user, or pass `overwrite_pending_edits: true` to discard them. Writing `content` while a browser tab has the item open routes the markdown through that live document; the stored row updates only on a later collab-snapshot flush, which nothing guarantees. The 200 echoes what you SENT with `warnings.content_outcome: \"applied_pending_flush\"`, which describes your WRITE (it went to the document, not the row). A `get` (or a `list` with `full: true`; a default list carries no content) before the flush returns the PREVIOUS content: that is lag, not a failed write, so do not re-send. A read whose body the server knows is behind the live document carries `content_state: \"applied_pending_flush\"`, also when someone ELSE's tab holds the edits and you wrote nothing: same value, but it describes the ROW, not your request. Treat it as re-read later, never as re-send, and do not wait on it in a loop: the server normally recovers the stored copy itself about a minute after the last tab leaves the item, but that is not guaranteed (a recovery can fail, and an operator can turn it off), and otherwise the row catches up only when a tab next opens the item. The stored form may also not be byte-identical to what you sent, since the markdown round-trips through the editor (bullet markers, emphasis characters, list numbering and blank-line runs normalise; already-canonical markdown survives unchanged), so compare on meaning rather than bytes. `move` changes an item's COLLECTION within its workspace: system metadata (implementation notes, decision log, linked PR) survives it, and any field value the target schema has no home for is dropped AND reported in the move's activity entry — check there rather than assuming a move is lossless. A carried unique-field collision is dropped, named in `warnings.not_unique`. Three system keys — `implementation_notes`, `decision_log`, `convention` — cannot be set through `field` on update or move; the call is refused with `validation_failed`, naming the key and the write path that does maintain it (`note`, `decide`, and library activation respectively). `github_pr` is refused as well (BUG-2696): a `field` value arrived as a string, so the PR data was stored double-encoded and no link appeared. Its writers are `action=link-pr` (`pr_number` + `pr_url`, metadata you supply; nothing is fetched from GitHub) and `action=unlink-pr`. On `create` they are refused too (BUG-3163), with the same `validation_failed`: create the item first, then use `note` / `decide` on it; convention metadata comes from library activation. `context` (`intent`, `role`, `budget`): one brief before you start work, with parents, matching convention bodies, deps and links. `history` returns read-only item version metadata (newest-first), bounded to the NEWEST 50 versions by default (max 300 — pass `limit` to change the window); pass `full: true` to include each version's resolved content body (token-expensive). There is no `offset`: versions are stored as reverse patches, so only a newest-end window is cheap to reconstruct. Unassign or detach with the `clear_assigned_user` / `clear_agent_role` / `clear_parent` booleans; an empty `assign` / `role` / `parent` does NOT clear. `remind` / `ack-reminder`: a fired reminder shows in `pad_project` next / ready (the delivery path on an instance with no webhook) until acknowledged, and one on a completed item is hidden there. `claim` / `release`: claim an item before you work it; a loser's 409 is `lease_held` (pick another, don't retry), and a lease bumps neither `updated_at` nor `seq`. A claim answers your `worker_id`; pass it to resume elsewhere. next / ready skip items other workers hold. `edit-comment` / `delete-comment` take a `comment_id` from `list-comments` (whose rows carry `edited`); only a comment's author may edit it. Correct a comment in place rather than appending a correction. Deleting a comment that has replies leaves a placeholder (`deleted: true`, empty body) so the replies keep their parent; editing, replying to or reacting to it answers 409 `comment_deleted`.\n\n**List filters must name a field (v0.75).** A `pad_item` `list` filter on a key no collection in scope declares, and no item stores, is refused with `validation_failed` (\"invalid list filter\"), where it used to return an empty list; a stored undeclared key still filters. Check the schema; don't retry.\n\n**Library words in a blank workspace (v0.67).** A brand-new blank workspace lists one convention trigger (`always`) and one scope (`all`). Activating a library entry, or creating a convention or playbook with a trigger or scope the library itself uses, adds that word to the collection's options and says so in `warnings.options_added`. A trigger you invent is still refused until the workspace owner adds it to the collection's schema.\n\n**App attribution (v0.65).** An item an installed app created, a comment an app wrote and a history row an app's write made carry `via_app` (the install id) and `via_app_name` (the app's name). On an item they name the app that CREATED it, not the last writer. They are absent for anything a person or an agent wrote.\n\n**Relation fields (v0.31).** A `relation` value may be a UUID, an issue ref (`COLO-3`) or the target's EXACT TITLE, tried in that order (a title that is also a ref resolves as the ref). A title matches only inside the declared collection, among items you can see; found only elsewhere, it is refused naming that collection; several matches are `ambiguous`. Full rules: docs/mcp.md.\n\nReads carry a `relation_targets` member beside `fields`: field key → `{id, ref, title}`, so you can render a relation without a request per value. `fields` still holds the canonical id, which is what you write back. An entry with an `id` and NO `ref`/`title` means the target is gone **or** you may not see it — the two are deliberately indistinguishable, so do not render it as either \"deleted\" or \"hidden\"; \"unavailable\" is the honest word. An entry with `stored_as_text: true` differs: the stored value is not UUID-shaped, so it was never an id (an imported title, legacy text). Render it as text, not as unavailable.\n\n**`multi_relation` fields (v0.33).** An ORDERED LIST of references, each resolved like a `relation` (UUID, ref, or exact title in the declared collection). Declare one as `owners:multi_relation:people`; the target collection is required. Rules: `[]` means absent; a blank element is refused by index; order is part of the value; duplicates are refused after resolution (`duplicate_referent`); any failing element refuses the whole write; `required` needs one resolved element; a cross-workspace copy drops the whole value (in `warnings.dropped_fields`). `relation_targets` holds an ARRAY of `{id, ref, title}` in stored order (`id`-only where unresolved); scalar keys stay single objects. Full rules: docs/mcp.md.\n\n- `pad_workspace` — Workspaces: list / members / invite / storage / audit-log / create / claim / deleted / restore.\n- `pad_collection` — Collections: list / create / update / delete / list-archived / restore. `delete` archives: the collection and its items leave every view, and `restore` brings them back. An `update` that removes a field or a select option still in use answers with `warnings.orphaned`: tell the user how many items keep the removed value.\n- `pad_project` — Project intelligence: dashboard / next / ready / stale / standup / changelog / report / activity. Use `ready` for the ranked top items to work on next (blocked work is left out) and `stale` for items needing attention; `activity` to catch up on what other agents/users changed since you last worked (non-streaming feed with item refs + change details).\n- `pad_role` — Agent roles: list / create / update / delete.\n- `pad_search` — Full-text search across items: query.\n- `pad_playbook` — Invokable procedures: list / get / run / match. Use `run` to bind args against a playbook's declared spec and get the rendered body back; side-effect-free. `run` refuses a playbook whose status isn't `active` (a draft still being authored) with a `playbook_not_active` error — pass `allow_draft: true` to override. Both `run` and `get` echo the playbook's `status`. Both may also carry `content_state` (`\"applied_pending_flush\"`, or `\"superseded_set_aside\"` as under `pad_item`), meaning the BODY you are about to execute is behind the item's live collaborative document — an editor holds unflushed edits, so the steps may be superseded. It is a reason to re-read or to ask, not a reason to refuse to run; the body is still the best the server has. `match` finds a playbook from text.\n- `pad_library` — Convention + playbook library (the global catalog of pre-built entries workspaces activate): list / get / activate.\n- `pad_attachment` — Read-only attachment metadata: list / show. `list` enumerates a workspace's attachments (filter by item / category / collection / attached / unattached); `show` returns one attachment's MIME, size, filename, and ETag via a HEAD request. Uploading and general file downloads stay CLI-only; bounded image bytes are available through the attachment resource below.\n- `pad_meta` — Server introspection: server-info / version / tool-surface / bootstrap. The `bootstrap` action returns one-shot workspace context (user + collections + always-on conventions + a metadata-only `convention_index` of every active convention + roles + playbook metadata + dashboard + recent activity).\n- `pad_set_workspace` — Load workspace context; response embeds the bootstrap blob so you load context in one call. Whether it also pins a session default: see Workspace context below. Takes `workspace: \u003cslug\u003e` only (no `action`).\n\nFor the ten resource × action tools, always pass `action` as a top-level field. Per-action required parameters are documented in each tool's description.\n\n## Resources are cheaper than tool calls\n\nRead these directly when you need workspace state (described in the resource listings): `pad://workspaces`, `pad://workspace/{ws}/dashboard`, `.../collections`, `.../items` (use `pad_item` `list` to filter), `.../items/{ref}` (markdown), `.../attachments/{id}` (images only, at most 1 MiB, as base64 `thumb-md`), `.../bootstrap` (the same payload as `pad_meta` `bootstrap`), and `pad://_meta/version`. A host can prefetch them once per session.\n\nLoad the bootstrap resource once per workspace and reuse its collections, conventions, roles, and playbook metadata. Refresh it after switching workspaces, after changing those configuration surfaces, when Pad reports stale schema/context, or when the user asks. For changing work state, read the affected item or use a targeted project tool instead of fetching the whole bootstrap again.\n\n## Workspace context\n\nEvery action that operates within a workspace accepts an optional `workspace` parameter. Resolution order:\n\n1. Explicit `workspace` argument on the call (always wins).\n2. On a single-user local server only: the session default set via `pad_set_workspace`.\n3. On a single-user local server only: the CWD-linked workspace from `.pad.toml`.\n\nA multi-user/remote server does **not** persist a session default — pass `workspace` explicitly on every call. If none resolves, the action returns a structured `no_workspace` error with `available_workspaces`, on both the local and the remote transport.\n\n## Update flow: read first, then patch\n\nFor `pad_item.action: update`, the server merges your patch with the item's current state. Pass only the fields you want to change. When changing `status`, ALWAYS include a `comment` explaining why — it builds the audit trail that helps the team understand history.\n\n## One error code you must not retry\n\nErrors come back as a structured envelope with a `code`. Most failures are worth a retry after you fix something, and a `server_error` may be transient. `stored_state_unreadable` is neither.\n\nIt means the ITEM'S STORED DATA cannot be decoded — your input was fine. Today it fires when `note` / `decide` would append to an `implementation_notes` / `decision_log` value that is not a list of entries. The operation is refused precisely because completing it would overwrite that value. The refusal is fully deterministic, so retrying — immediately or after a backoff — fails identically every time and changes nothing.\n\nWhen you see it: tell the user which item is affected, and stop. Whether you can inspect the bad value depends on which layer is broken — if the item's whole `fields` blob fails to parse, `action: get` hands it back as a raw string; if one structured key is at fault, you won't see it at all, because the blob is normalized on this surface and a value that doesn't decode is dropped from the top-level arrays. A human can always read it with `pad item show \u003cref\u003e --format json`. Do not route around the refusal by writing the field some other way; that is the write that caused it.\n\n## Project conventions\n\nWorkspaces can declare conventions (e.g. \"run `make test` before PR\", \"use conventional commit format\"). The bootstrap blob gives you two views:\n\n- `conventions` — full bodies of the always-on (`trigger=always`) rules. Follow these unconditionally.\n- `convention_index` — METADATA ONLY (`ref`, `title`, `trigger`, `role`; no bodies) for **every** active convention, including the triggered ones whose bodies are NOT in `conventions`. This is your map of what triggered rules exist.\n\nBefore performing meaningful work with a specific trigger (e.g. `on-implement` before writing code), consult `convention_index`: if it lists entries for that trigger, pull their bodies on demand; if it lists none, skip the query.\n\n```\npad_item.action: list, collection: \"conventions\", status: \"active\"\n```\n\nFilter by trigger (`always`, `on-implement`, `on-task-complete`, etc.) when relevant — the `convention_index` triggers tell you which filters are worth running.\n\n`\"conventions\"` above is the DEFAULT collection slug and a workspace may have renamed it, in which case that literal returns nothing while `convention_index` still lists entries — the bootstrap payload resolves by declaration, not by name. When the two disagree, address the items by the `ref`s the index gave you, or find the collection with `pad_collection.action: list`. The same applies to `\"playbooks\"`; `pad_playbook` resolves by declaration and is unaffected.\n\n## Pushes and the session monitor (security note)\n\nPad can push an item into a Claude Code session (`pad push`, or the web item view's push composer). That is terminal instruction injection by design, so receiving is **consent-gated** (PLAN-2613, since v0.15.0): a session receives pushes only after it has connected (`/pad:connect` in the plugin, or a repo-level `push.auto_arm = true` in `.pad.toml` — which a per-user `auto_arm = false` in `~/.pad/config.toml` vetoes), and pushes are self-addressed only — the sender is always the receiving session's own user. This MCP connection is not a session: it cannot arm one, receive a push, or run the monitor, and the `pad_item` / `pad_project` tools expose no push action. If a user asks you to \"push\" something to their terminal, tell them it happens from their own terminal (`pad push \u003cref\u003e -m \"...\"` — the sending session need not be connected, the receiving ones must have consented); do not try to emulate it by writing comments or instructions into items.\n\n## Adding a workspace to this connection\n\nIf the user references a workspace this connection can't see (you'll get a 403 from workspace tools, or the workspace won't appear in `pad_workspace.list`), tell the user you can't see that workspace with your current permissions, then walk them through how to grant access: open Pad in their browser → switch to that workspace → avatar menu → \"Connect project...\" A 6-digit claim code will appear. Have them paste it back in chat, then call `pad_workspace.claim` with `{workspace: \"\u003cslug\u003e\", code: \"\u003c6 digits\u003e\"}`. The workspace joins this connection's allow-list and stays until the user revokes it via `/console/connected-apps`. No re-auth required.\n\nFor brand-new workspaces, `pad_workspace.create` with `{name: \"\u003cname\u003e\"}` (and optional `template`) creates the workspace AND auto-adds it to this connection's allow-list in one call — no claim code needed. Only works when the connection currently carries the \"may create workspaces\" grant — granted at consent time, or enabled later on the connections page. If the grant is present and set to false, the create is **refused with a 403 and no workspace is made** — retrying won't help and neither will the claim flow, since there is nothing to claim. Tell the user this connection isn't permitted to create workspaces, and offer them the two ways forward: create the workspace themselves in the browser and grant access with a claim code, or re-authorize this connection with \"Let this app create new workspaces\" enabled (`/console/connected-apps` can also flip it on an existing connection).\n\n## New workspace: offer to set it up\n\nThe bootstrap blob carries `needs_onboarding: bool` — true when the workspace has zero user-created items (template seeds don't count). When it's true, **lead with an active offer before anything else**: *\"This workspace is brand new and isn't set up yet. Want me to set it up? I'll ask a few quick questions and adapt it to your project.\"*\n\nThis is an **offer, not an auto-run** — wait for the user to say yes before running onboarding. If they accept, run the `onboard` playbook (use the `pad_onboard` prompt, or load the body via `pad_playbook` `action: get`, `ref: onboard`). If they decline, or already declined earlier in the session, respect that and skip the offer. The flag flips to false the moment any item exists, so it won't nag past first setup.\n\n## Built-in updates: mention once\n\nThe bootstrap blob may carry `builtin_updates: int` (absent when there are none): how many of the conventions and playbooks Pad ships have newer text in Pad's library than this workspace's copy. When it is present, mention it **once per session**, in one line, then carry on. **Never apply an update yourself**: a person reviews each one and accepts it or not.\n\n## Multi-step workflows\n\nFour prompts ship with the server: `pad_plan`, `pad_ideate`, `pad_retro`, `pad_onboard`. Use them when the user wants help planning, brainstorming, retrospecting, or onboarding into a workspace — they encode the multi-step Pad-aware playbook for each.\n" } diff --git a/cmd/pad/testdata/mcp_wire/stdio_initialize.json b/cmd/pad/testdata/mcp_wire/stdio_initialize.json index e37591b79..5fe76f2f7 100644 --- a/cmd/pad/testdata/mcp_wire/stdio_initialize.json +++ b/cmd/pad/testdata/mcp_wire/stdio_initialize.json @@ -8,7 +8,7 @@ }, "padToolSurface": { "tool_surface_stable": true, - "version": "0.99" + "version": "0.100" } }, "prompts": {}, @@ -21,5 +21,5 @@ "name": "pad-mcp", "version": "" }, - "instructions": "Pad is a project tracker for developers and AI agents — issues (TASK, BUG), plans (PLAN), ideas (IDEA), docs (DOC), conventions, comments, and dependencies. Use this server when a user mentions:\n\n- Issue refs like `TASK-5`, `BUG-12`, `PLAN-3`, `IDEA-8` — they are stable, human-readable IDs and the canonical way to address items. Use them, never slugs; they are what audit trails and PR titles show.\n- Tasks / issues / items / plans / progress / \"what's on my plate\" / \"what to work on next\" / standup / changelog / retrospective.\n- Project conventions, decision records, or \"how should this team do X.\"\n\nIf the user is asking general code questions with no project-management thread, you don't need this server.\n\n## Tool surface (v0.99)\n\nTen resource × action tools, plus `pad_set_workspace`. Eleven tools total.\n\nInputs are validated strictly: an undeclared top-level key is rejected with a structured `validation_failed` naming it, never accepted and silently dropped.\n\n- `pad_item` — Items: create / update / delete / get / list / move / restore / link / unlink / deps / context / star / unstar / starred / comment / list-comments / edit-comment / delete-comment / backlinks / bulk-update / note / decide / export / import / history / remind / ack-reminder / reminders / unremind / link-pr / unlink-pr / claim / release / patch. On create/update, field values may be passed as a `fields` OBJECT (the same shape reads return, e.g. `{\"status\":\"done\",\"effort\":\"l\"}`) — it merges into the same path as the dedicated params and `field: [\"key=value\"]`; the same key in two places with CONFLICTING values is refused, not silently resolved. `list` accepts `unparented: true` to keep items with no parent or implements relationship (mutually exclusive with `parent`). `list` results are SUMMARY-shaped by default on both transports — no content bodies; pass `full: true` for complete bodies (token-expensive), or prefer `get` for a single item's body. `update` field writes are a server-side field-level merge (only the keys you set change); pass `expected_seq` for optimistic concurrency — the `seq` you last read, which is on every item AND every list summary — and a stale value fails with a structured 409 `update_conflict` whose details carry `actual_seq` to retry with. PREFER IT over `expected_updated_at`, which cannot tell two writes inside one second apart; that one still works, and if you send both, seq decides. To change PART of a body, prefer `patch`: `edits: [{old, new}]`, where each `old` is exact text occurring once in the current body (read it with `get` and `lines: \"A-B\"` to quote it). The answer is a unified `diff`: read it, because anchors guarantee position, not meaning. A moved `expected_seq` is applied over and reported as `rebased` with the intervening writes. On an item open in a browser editor, the editor applies the patch to its live document, merging with the typing there, and the answer says `content_state: \"applied_pending_flush\"`. `patch_anchor_missing` / `patch_anchor_ambiguous` mean re-read and quote current text; `patch_unstable_roundtrip` means the open editor would also change content you did not edit, so send a whole-body update; `patch_room_open` means an older editor that cannot apply patches holds the item. Every patch answer carries a `patch_id`; `patch` with `undo: \u003cpatch_id\u003e` inverts it, and is refused when the text it changed has changed since. Send an `op_key` (any unique string, e.g. a UUID) with a patch whenever you might retry it: the same request with the same key returns the first answer instead of applying twice. `patch_outcome_unknown` means an earlier attempt's editor never confirmed it and is gone; read `details.diff` before deciding. `content` REPLACES the whole body, so send `expected_seq` with it: `get` the item, edit that body, and send it back with the `seq` you read. An `update_conflict` whose details carry `content_write` means someone changed the item after your read. Do NOT resend your body, because it would undo their change: re-read, apply your edit to the current content, and send that with the new seq. `replace: true` overwrites on purpose instead. A content write with neither carries `warnings.unguarded_content_write`, and a later release refuses it. A token cannot see a browser tab's unsaved edits, so `content` sent WITH one is refused with 409 `content_pending_flush` while any exist; re-reading will not clear it. Wait for the editor to save, or pass `overwrite_pending_edits: true` to replace them. `content_state: \"superseded_set_aside\"` is different and wins when both apply: an editor upgrade set aside edits no tab can restore, so EVERY content write is refused (token or not; `details.set_aside_rows`) and waiting never clears it. Tell the user, or pass `overwrite_pending_edits: true` to discard them. Writing `content` while a browser tab has the item open routes the markdown through that live document; the stored row updates only on a later collab-snapshot flush, which nothing guarantees. The 200 echoes what you SENT with `warnings.content_outcome: \"applied_pending_flush\"`, which describes your WRITE (it went to the document, not the row). A `get` (or a `list` with `full: true`; a default list carries no content) before the flush returns the PREVIOUS content: that is lag, not a failed write, so do not re-send. A read whose body the server knows is behind the live document carries `content_state: \"applied_pending_flush\"`, also when someone ELSE's tab holds the edits and you wrote nothing: same value, but it describes the ROW, not your request. Treat it as re-read later, never as re-send, and do not wait on it in a loop: the server normally recovers the stored copy itself about a minute after the last tab leaves the item, but that is not guaranteed (a recovery can fail, and an operator can turn it off), and otherwise the row catches up only when a tab next opens the item. The stored form may also not be byte-identical to what you sent, since the markdown round-trips through the editor (bullet markers, emphasis characters, list numbering and blank-line runs normalise; already-canonical markdown survives unchanged), so compare on meaning rather than bytes. `move` changes an item's COLLECTION within its workspace: system metadata (implementation notes, decision log, linked PR) survives it, and any field value the target schema has no home for is dropped AND reported in the move's activity entry — check there rather than assuming a move is lossless. A carried unique-field collision is dropped, named in `warnings.not_unique`. Three system keys — `implementation_notes`, `decision_log`, `convention` — cannot be set through `field` on update or move; the call is refused with `validation_failed`, naming the key and the write path that does maintain it (`note`, `decide`, and library activation respectively). `github_pr` is refused as well (BUG-2696): a `field` value arrived as a string, so the PR data was stored double-encoded and no link appeared. Its writers are `action=link-pr` (`pr_number` + `pr_url`, metadata you supply; nothing is fetched from GitHub) and `action=unlink-pr`. On `create` they are refused too (BUG-3163), with the same `validation_failed`: create the item first, then use `note` / `decide` on it; convention metadata comes from library activation. `context` (`intent`, `role`, `budget`): one brief before you start work, with parents, matching convention bodies, deps and links. `history` returns read-only item version metadata (newest-first), bounded to the NEWEST 50 versions by default (max 300 — pass `limit` to change the window); pass `full: true` to include each version's resolved content body (token-expensive). There is no `offset`: versions are stored as reverse patches, so only a newest-end window is cheap to reconstruct. Unassign or detach with the `clear_assigned_user` / `clear_agent_role` / `clear_parent` booleans; an empty `assign` / `role` / `parent` does NOT clear. `remind` / `ack-reminder`: a fired reminder shows in `pad_project` next / ready (the delivery path on an instance with no webhook) until acknowledged, and one on a completed item is hidden there. `claim` / `release`: claim an item before you work it; a loser's 409 is `lease_held` (pick another, don't retry), and a lease bumps neither `updated_at` nor `seq`. A claim answers your `worker_id`; pass it to resume elsewhere. next / ready skip items other workers hold. `edit-comment` / `delete-comment` take a `comment_id` from `list-comments` (whose rows carry `edited`); only a comment's author may edit it. Correct a comment in place rather than appending a correction. Deleting a comment that has replies leaves a placeholder (`deleted: true`, empty body) so the replies keep their parent; editing, replying to or reacting to it answers 409 `comment_deleted`.\n\n**List filters must name a field (v0.75).** A `pad_item` `list` filter on a key no collection in scope declares, and no item stores, is refused with `validation_failed` (\"invalid list filter\"), where it used to return an empty list; a stored undeclared key still filters. Check the schema; don't retry.\n\n**Library words in a blank workspace (v0.67).** A brand-new blank workspace lists one convention trigger (`always`) and one scope (`all`). Activating a library entry, or creating a convention or playbook with a trigger or scope the library itself uses, adds that word to the collection's options and says so in `warnings.options_added`. A trigger you invent is still refused until the workspace owner adds it to the collection's schema.\n\n**App attribution (v0.65).** An item an installed app created, a comment an app wrote and a history row an app's write made carry `via_app` (the install id) and `via_app_name` (the app's name). On an item they name the app that CREATED it, not the last writer. They are absent for anything a person or an agent wrote.\n\n**Relation fields (v0.31).** A `relation` value may be a UUID, an issue ref (`COLO-3`) or the target's EXACT TITLE, tried in that order (a title that is also a ref resolves as the ref). A title matches only inside the declared collection, among items you can see; found only elsewhere, it is refused naming that collection; several matches are `ambiguous`. Full rules: docs/mcp.md.\n\nReads carry a `relation_targets` member beside `fields`: field key → `{id, ref, title}`, so you can render a relation without a request per value. `fields` still holds the canonical id, which is what you write back. An entry with an `id` and NO `ref`/`title` means the target is gone **or** you may not see it — the two are deliberately indistinguishable, so do not render it as either \"deleted\" or \"hidden\"; \"unavailable\" is the honest word. An entry with `stored_as_text: true` differs: the stored value is not UUID-shaped, so it was never an id (an imported title, legacy text). Render it as text, not as unavailable.\n\n**`multi_relation` fields (v0.33).** An ORDERED LIST of references, each resolved like a `relation` (UUID, ref, or exact title in the declared collection). Declare one as `owners:multi_relation:people`; the target collection is required. Rules: `[]` means absent; a blank element is refused by index; order is part of the value; duplicates are refused after resolution (`duplicate_referent`); any failing element refuses the whole write; `required` needs one resolved element; a cross-workspace copy drops the whole value (in `warnings.dropped_fields`). `relation_targets` holds an ARRAY of `{id, ref, title}` in stored order (`id`-only where unresolved); scalar keys stay single objects. Full rules: docs/mcp.md.\n\n- `pad_workspace` — Workspaces: list / members / invite / storage / audit-log / create / claim / deleted / restore.\n- `pad_collection` — Collections: list / create / update / delete / list-archived / restore. `delete` archives: the collection and its items leave every view, and `restore` brings them back. An `update` that removes a field or a select option still in use answers with `warnings.orphaned`: tell the user how many items keep the removed value.\n- `pad_project` — Project intelligence: dashboard / next / ready / stale / standup / changelog / report / activity. Use `ready` for the ranked top items to work on next (blocked work is left out) and `stale` for items needing attention; `activity` to catch up on what other agents/users changed since you last worked (non-streaming feed with item refs + change details).\n- `pad_role` — Agent roles: list / create / update / delete.\n- `pad_search` — Full-text search across items: query.\n- `pad_playbook` — Invokable procedures: list / get / run / match. Use `run` to bind args against a playbook's declared spec and get the rendered body back; side-effect-free. `run` refuses a playbook whose status isn't `active` (a draft still being authored) with a `playbook_not_active` error — pass `allow_draft: true` to override. Both `run` and `get` echo the playbook's `status`. Both may also carry `content_state` (`\"applied_pending_flush\"`, or `\"superseded_set_aside\"` as under `pad_item`), meaning the BODY you are about to execute is behind the item's live collaborative document — an editor holds unflushed edits, so the steps may be superseded. It is a reason to re-read or to ask, not a reason to refuse to run; the body is still the best the server has. `match` finds a playbook from text.\n- `pad_library` — Convention + playbook library (the global catalog of pre-built entries workspaces activate): list / get / activate.\n- `pad_attachment` — Read-only attachment metadata: list / show. `list` enumerates a workspace's attachments (filter by item / category / collection / attached / unattached); `show` returns one attachment's MIME, size, filename, and ETag via a HEAD request. Uploading and general file downloads stay CLI-only; bounded image bytes are available through the attachment resource below.\n- `pad_meta` — Server introspection: server-info / version / tool-surface / bootstrap. The `bootstrap` action returns one-shot workspace context (user + collections + always-on conventions + a metadata-only `convention_index` of every active convention + roles + playbook metadata + dashboard + recent activity).\n- `pad_set_workspace` — Load workspace context; response embeds the bootstrap blob so you load context in one call. Whether it also pins a session default: see Workspace context below. Takes `workspace: \u003cslug\u003e` only (no `action`).\n\nFor the ten resource × action tools, always pass `action` as a top-level field. Per-action required parameters are documented in each tool's description.\n\n## Resources are cheaper than tool calls\n\nRead these directly when you need workspace state (described in the resource listings): `pad://workspaces`, `pad://workspace/{ws}/dashboard`, `.../collections`, `.../items` (use `pad_item` `list` to filter), `.../items/{ref}` (markdown), `.../attachments/{id}` (images only, at most 1 MiB, as base64 `thumb-md`), `.../bootstrap` (the same payload as `pad_meta` `bootstrap`), and `pad://_meta/version`. A host can prefetch them once per session.\n\nLoad the bootstrap resource once per workspace and reuse its collections, conventions, roles, and playbook metadata. Refresh it after switching workspaces, after changing those configuration surfaces, when Pad reports stale schema/context, or when the user asks. For changing work state, read the affected item or use a targeted project tool instead of fetching the whole bootstrap again.\n\n## Workspace context\n\nEvery action that operates within a workspace accepts an optional `workspace` parameter. Resolution order:\n\n1. Explicit `workspace` argument on the call (always wins).\n2. On a single-user local server only: the session default set via `pad_set_workspace`.\n3. On a single-user local server only: the CWD-linked workspace from `.pad.toml`.\n\nA multi-user/remote server does **not** persist a session default — pass `workspace` explicitly on every call. If none resolves, the action returns a structured `no_workspace` error with `available_workspaces`, on both the local and the remote transport.\n\n## Update flow: read first, then patch\n\nFor `pad_item.action: update`, the server merges your patch with the item's current state. Pass only the fields you want to change. When changing `status`, ALWAYS include a `comment` explaining why — it builds the audit trail that helps the team understand history.\n\n## One error code you must not retry\n\nErrors come back as a structured envelope with a `code`. Most failures are worth a retry after you fix something, and a `server_error` may be transient. `stored_state_unreadable` is neither.\n\nIt means the ITEM'S STORED DATA cannot be decoded — your input was fine. Today it fires when `note` / `decide` would append to an `implementation_notes` / `decision_log` value that is not a list of entries. The operation is refused precisely because completing it would overwrite that value. The refusal is fully deterministic, so retrying — immediately or after a backoff — fails identically every time and changes nothing.\n\nWhen you see it: tell the user which item is affected, and stop. Whether you can inspect the bad value depends on which layer is broken — if the item's whole `fields` blob fails to parse, `action: get` hands it back as a raw string; if one structured key is at fault, you won't see it at all, because the blob is normalized on this surface and a value that doesn't decode is dropped from the top-level arrays. A human can always read it with `pad item show \u003cref\u003e --format json`. Do not route around the refusal by writing the field some other way; that is the write that caused it.\n\n## Project conventions\n\nWorkspaces can declare conventions (e.g. \"run `make test` before PR\", \"use conventional commit format\"). The bootstrap blob gives you two views:\n\n- `conventions` — full bodies of the always-on (`trigger=always`) rules. Follow these unconditionally.\n- `convention_index` — METADATA ONLY (`ref`, `title`, `trigger`, `role`; no bodies) for **every** active convention, including the triggered ones whose bodies are NOT in `conventions`. This is your map of what triggered rules exist.\n\nBefore performing meaningful work with a specific trigger (e.g. `on-implement` before writing code), consult `convention_index`: if it lists entries for that trigger, pull their bodies on demand; if it lists none, skip the query.\n\n```\npad_item.action: list, collection: \"conventions\", status: \"active\"\n```\n\nFilter by trigger (`always`, `on-implement`, `on-task-complete`, etc.) when relevant — the `convention_index` triggers tell you which filters are worth running.\n\n`\"conventions\"` above is the DEFAULT collection slug and a workspace may have renamed it, in which case that literal returns nothing while `convention_index` still lists entries — the bootstrap payload resolves by declaration, not by name. When the two disagree, address the items by the `ref`s the index gave you, or find the collection with `pad_collection.action: list`. The same applies to `\"playbooks\"`; `pad_playbook` resolves by declaration and is unaffected.\n\n## Pushes and the session monitor (security note)\n\nPad can push an item into a Claude Code session (`pad push`, or the web item view's push composer). That is terminal instruction injection by design, so receiving is **consent-gated** (PLAN-2613, since v0.15.0): a session receives pushes only after it has connected (`/pad:connect` in the plugin, or a repo-level `push.auto_arm = true` in `.pad.toml` — which a per-user `auto_arm = false` in `~/.pad/config.toml` vetoes), and pushes are self-addressed only — the sender is always the receiving session's own user. This MCP connection is not a session: it cannot arm one, receive a push, or run the monitor, and the `pad_item` / `pad_project` tools expose no push action. If a user asks you to \"push\" something to their terminal, tell them it happens from their own terminal (`pad push \u003cref\u003e -m \"...\"` — the sending session need not be connected, the receiving ones must have consented); do not try to emulate it by writing comments or instructions into items.\n\n## Adding a workspace to this connection\n\nIf the user references a workspace this connection can't see (you'll get a 403 from workspace tools, or the workspace won't appear in `pad_workspace.list`), tell the user you can't see that workspace with your current permissions, then walk them through how to grant access: open Pad in their browser → switch to that workspace → avatar menu → \"Connect project...\" A 6-digit claim code will appear. Have them paste it back in chat, then call `pad_workspace.claim` with `{workspace: \"\u003cslug\u003e\", code: \"\u003c6 digits\u003e\"}`. The workspace joins this connection's allow-list and stays until the user revokes it via `/console/connected-apps`. No re-auth required.\n\nFor brand-new workspaces, `pad_workspace.create` with `{name: \"\u003cname\u003e\"}` (and optional `template`) creates the workspace AND auto-adds it to this connection's allow-list in one call — no claim code needed. Only works when the connection currently carries the \"may create workspaces\" grant — granted at consent time, or enabled later on the connections page. If the grant is present and set to false, the create is **refused with a 403 and no workspace is made** — retrying won't help and neither will the claim flow, since there is nothing to claim. Tell the user this connection isn't permitted to create workspaces, and offer them the two ways forward: create the workspace themselves in the browser and grant access with a claim code, or re-authorize this connection with \"Let this app create new workspaces\" enabled (`/console/connected-apps` can also flip it on an existing connection).\n\n## New workspace: offer to set it up\n\nThe bootstrap blob carries `needs_onboarding: bool` — true when the workspace has zero user-created items (template seeds don't count). When it's true, **lead with an active offer before anything else**: *\"This workspace is brand new and isn't set up yet. Want me to set it up? I'll ask a few quick questions and adapt it to your project.\"*\n\nThis is an **offer, not an auto-run** — wait for the user to say yes before running onboarding. If they accept, run the `onboard` playbook (use the `pad_onboard` prompt, or load the body via `pad_playbook` `action: get`, `ref: onboard`). If they decline, or already declined earlier in the session, respect that and skip the offer. The flag flips to false the moment any item exists, so it won't nag past first setup.\n\n## Built-in updates: mention once\n\nThe bootstrap blob may carry `builtin_updates: int` (absent when there are none): how many of the conventions and playbooks Pad ships have newer text in Pad's library than this workspace's copy. When it is present, mention it **once per session**, in one line, then carry on. **Never apply an update yourself**: a person reviews each one and accepts it or not.\n\n## Multi-step workflows\n\nFour prompts ship with the server: `pad_plan`, `pad_ideate`, `pad_retro`, `pad_onboard`. Use them when the user wants help planning, brainstorming, retrospecting, or onboarding into a workspace — they encode the multi-step Pad-aware playbook for each.\n" + "instructions": "Pad is a project tracker for developers and AI agents — issues (TASK, BUG), plans (PLAN), ideas (IDEA), docs (DOC), conventions, comments, and dependencies. Use this server when a user mentions:\n\n- Issue refs like `TASK-5`, `BUG-12`, `PLAN-3`, `IDEA-8` — they are stable, human-readable IDs and the canonical way to address items. Use them, never slugs; they are what audit trails and PR titles show.\n- Tasks / issues / items / plans / progress / \"what's on my plate\" / \"what to work on next\" / standup / changelog / retrospective.\n- Project conventions, decision records, or \"how should this team do X.\"\n\nIf the user is asking general code questions with no project-management thread, you don't need this server.\n\n## Tool surface (v0.100)\n\nTen resource × action tools, plus `pad_set_workspace`. Eleven tools total.\n\nInputs are validated strictly: an undeclared top-level key is rejected with a structured `validation_failed` naming it, never accepted and silently dropped.\n\n- `pad_item` — Items: create / update / delete / get / list / move / restore / link / unlink / deps / context / star / unstar / starred / comment / list-comments / edit-comment / delete-comment / backlinks / bulk-update / note / decide / export / import / history / remind / ack-reminder / reminders / unremind / link-pr / unlink-pr / claim / release / patch. On create/update, field values may be passed as a `fields` OBJECT (the same shape reads return, e.g. `{\"status\":\"done\",\"effort\":\"l\"}`) — it merges into the same path as the dedicated params and `field: [\"key=value\"]`; the same key in two places with CONFLICTING values is refused, not silently resolved. `list` accepts `unparented: true` to keep items with no parent or implements relationship (mutually exclusive with `parent`). `list` results are SUMMARY-shaped by default on both transports — no content bodies; pass `full: true` for complete bodies (token-expensive), or prefer `get` for a single item's body. `update` field writes are a server-side field-level merge (only the keys you set change); pass `expected_seq` for optimistic concurrency — the `seq` you last read, which is on every item AND every list summary — and a stale value fails with a structured 409 `update_conflict` whose details carry `actual_seq` to retry with. PREFER IT over `expected_updated_at`, which cannot tell two writes inside one second apart; that one still works, and if you send both, seq decides. To change PART of a body, prefer `patch`: `edits: [{old, new}]`, where each `old` is exact text occurring once in the current body (read it with `get` and `lines: \"A-B\"` to quote it). The answer is a unified `diff`: read it, because anchors guarantee position, not meaning. A moved `expected_seq` is applied over and reported as `rebased` with the intervening writes. On an item open in a browser editor, the editor applies the patch to its live document, merging with the typing there, and the answer says `content_state: \"applied_pending_flush\"`. `patch_anchor_missing` / `patch_anchor_ambiguous` mean re-read and quote current text; `patch_unstable_roundtrip` means the open editor would also change content you did not edit, so send a whole-body update; `patch_room_open` means an older editor that cannot apply patches holds the item. Every patch answer carries a `patch_id`; `patch` with `undo: \u003cpatch_id\u003e` inverts it, and is refused when the text it changed has changed since. Send an `op_key` (any unique string, e.g. a UUID) with a patch whenever you might retry it: the same request with the same key returns the first answer instead of applying twice. `patch_outcome_unknown` means an earlier attempt's editor never confirmed it and is gone; read `details.diff` before deciding. `content` REPLACES the whole body, so send `expected_seq` with it: `get` the item, edit that body, and send it back with the `seq` you read. An `update_conflict` whose details carry `content_write` means someone changed the item after your read. Do NOT resend your body, because it would undo their change: re-read, apply your edit to the current content, and send that with the new seq. `replace: true` overwrites on purpose instead. A content write with neither carries `warnings.unguarded_content_write`, and a later release refuses it. A token cannot see a browser tab's unsaved edits, so `content` sent WITH one is refused with 409 `content_pending_flush` while any exist; re-reading will not clear it. Wait for the editor to save, or pass `overwrite_pending_edits: true` to replace them. `content_state: \"superseded_set_aside\"` is different and wins when both apply: an editor upgrade set aside edits no tab can restore, so EVERY content write is refused (token or not; `details.set_aside_rows`) and waiting never clears it. Tell the user, or pass `overwrite_pending_edits: true` to discard them. Writing `content` while a browser tab has the item open routes the markdown through that live document; the stored row updates only on a later collab-snapshot flush, which nothing guarantees. The 200 echoes what you SENT with `warnings.content_outcome: \"applied_pending_flush\"`, which describes your WRITE (it went to the document, not the row). A `get` (or a `list` with `full: true`; a default list carries no content) before the flush returns the PREVIOUS content: that is lag, not a failed write, so do not re-send. A read whose body the server knows is behind the live document carries `content_state: \"applied_pending_flush\"`, also when someone ELSE's tab holds the edits and you wrote nothing: same value, but it describes the ROW, not your request. Treat it as re-read later, never as re-send, and do not wait on it in a loop: the server normally recovers the stored copy itself about a minute after the last tab leaves the item, but that is not guaranteed (a recovery can fail, and an operator can turn it off), and otherwise the row catches up only when a tab next opens the item. The stored form may also not be byte-identical to what you sent, since the markdown round-trips through the editor (bullet markers, emphasis characters, list numbering and blank-line runs normalise; already-canonical markdown survives unchanged), so compare on meaning rather than bytes. `move` changes an item's COLLECTION within its workspace: system metadata (implementation notes, decision log, linked PR) survives it, and any field value the target schema has no home for is dropped AND reported in the move's activity entry — check there rather than assuming a move is lossless. A carried unique-field collision is dropped, named in `warnings.not_unique`. Three system keys — `implementation_notes`, `decision_log`, `convention` — cannot be set through `field` on update or move; the call is refused with `validation_failed`, naming the key and the write path that does maintain it (`note`, `decide`, and library activation respectively). `github_pr` is refused as well (BUG-2696): a `field` value arrived as a string, so the PR data was stored double-encoded and no link appeared. Its writers are `action=link-pr` (`pr_number` + `pr_url`, metadata you supply; nothing is fetched from GitHub) and `action=unlink-pr`. On `create` they are refused too (BUG-3163), with the same `validation_failed`: create the item first, then use `note` / `decide` on it; convention metadata comes from library activation. `context` (`intent`, `role`, `budget`): one brief before you start work, with parents, matching convention bodies, deps and links. `history` returns read-only item version metadata (newest-first), bounded to the NEWEST 50 versions by default (max 300 — pass `limit` to change the window); pass `full: true` to include each version's resolved content body (token-expensive). There is no `offset`: versions are stored as reverse patches, so only a newest-end window is cheap to reconstruct. Unassign or detach with the `clear_assigned_user` / `clear_agent_role` / `clear_parent` booleans; an empty `assign` / `role` / `parent` does NOT clear. `remind` / `ack-reminder`: a fired reminder shows in `pad_project` next / ready (the delivery path on an instance with no webhook) until acknowledged, and one on a completed item is hidden there. `claim` / `release`: claim an item before you work it; a loser's 409 is `lease_held` (pick another, don't retry), and a lease bumps neither `updated_at` nor `seq`. A claim answers your `worker_id`; pass it to resume elsewhere. next / ready skip items other workers hold. `edit-comment` / `delete-comment` take a `comment_id` from `list-comments` (whose rows carry `edited`); only a comment's author may edit it. Correct a comment in place rather than appending a correction. Deleting a comment that has replies leaves a placeholder (`deleted: true`, empty body) so the replies keep their parent; editing, replying to or reacting to it answers 409 `comment_deleted`.\n\n**List filters must name a field (v0.75).** A `pad_item` `list` filter on a key no collection in scope declares, and no item stores, is refused with `validation_failed` (\"invalid list filter\"), where it used to return an empty list; a stored undeclared key still filters. Check the schema; don't retry.\n\n**Library words in a blank workspace (v0.67).** A brand-new blank workspace lists one convention trigger (`always`) and one scope (`all`). Activating a library entry, or creating a convention or playbook with a trigger or scope the library itself uses, adds that word to the collection's options and says so in `warnings.options_added`. A trigger you invent is still refused until the workspace owner adds it to the collection's schema.\n\n**App attribution (v0.65).** An item an installed app created, a comment an app wrote and a history row an app's write made carry `via_app` (the install id) and `via_app_name` (the app's name). On an item they name the app that CREATED it, not the last writer. They are absent for anything a person or an agent wrote.\n\n**Relation fields (v0.31).** A `relation` value may be a UUID, an issue ref (`COLO-3`) or the target's EXACT TITLE, tried in that order (a title that is also a ref resolves as the ref). A title matches only inside the declared collection, among items you can see; found only elsewhere, it is refused naming that collection; several matches are `ambiguous`. Full rules: docs/mcp.md.\n\nReads carry a `relation_targets` member beside `fields`: field key → `{id, ref, title}`, so you can render a relation without a request per value. `fields` still holds the canonical id, which is what you write back. An entry with an `id` and NO `ref`/`title` means the target is gone **or** you may not see it — the two are deliberately indistinguishable, so do not render it as either \"deleted\" or \"hidden\"; \"unavailable\" is the honest word. An entry with `stored_as_text: true` differs: the stored value is not UUID-shaped, so it was never an id (an imported title, legacy text). Render it as text, not as unavailable.\n\n**`multi_relation` fields (v0.33).** An ORDERED LIST of references, each resolved like a `relation` (UUID, ref, or exact title in the declared collection). Declare one as `owners:multi_relation:people`; the target collection is required. Rules: `[]` means absent; a blank element is refused by index; order is part of the value; duplicates are refused after resolution (`duplicate_referent`); any failing element refuses the whole write; `required` needs one resolved element; a cross-workspace copy drops the whole value (in `warnings.dropped_fields`). `relation_targets` holds an ARRAY of `{id, ref, title}` in stored order (`id`-only where unresolved); scalar keys stay single objects. Full rules: docs/mcp.md.\n\n- `pad_workspace` — Workspaces: list / members / invite / storage / audit-log / create / claim / deleted / restore.\n- `pad_collection` — Collections: list / create / update / delete / list-archived / restore. `delete` archives: the collection and its items leave every view, and `restore` brings them back. An `update` that removes a field or a select option still in use answers with `warnings.orphaned`: tell the user how many items keep the removed value.\n- `pad_project` — Project intelligence: dashboard / next / ready / stale / standup / changelog / report / activity. Use `ready` for the ranked top items to work on next (blocked work is left out) and `stale` for items needing attention; `activity` to catch up on what other agents/users changed since you last worked (non-streaming feed with item refs + change details).\n- `pad_role` — Agent roles: list / create / update / delete.\n- `pad_search` — Full-text search across items: query.\n- `pad_playbook` — Invokable procedures: list / get / run / match. Use `run` to bind args against a playbook's declared spec and get the rendered body back; side-effect-free. `run` refuses a playbook whose status isn't `active` (a draft still being authored) with a `playbook_not_active` error — pass `allow_draft: true` to override. Both `run` and `get` echo the playbook's `status`. Both may also carry `content_state` (`\"applied_pending_flush\"`, or `\"superseded_set_aside\"` as under `pad_item`), meaning the BODY you are about to execute is behind the item's live collaborative document — an editor holds unflushed edits, so the steps may be superseded. It is a reason to re-read or to ask, not a reason to refuse to run; the body is still the best the server has. `match` finds a playbook from text.\n- `pad_library` — Convention + playbook library (the global catalog of pre-built entries workspaces activate): list / get / activate.\n- `pad_attachment` — Read-only attachment metadata: list / show. `list` enumerates a workspace's attachments (filter by item / category / collection / attached / unattached); `show` returns one attachment's MIME, size, filename, and ETag via a HEAD request. Uploading and general file downloads stay CLI-only; bounded image bytes are available through the attachment resource below.\n- `pad_meta` — Server introspection: server-info / version / tool-surface / bootstrap. The `bootstrap` action returns one-shot workspace context (user + collections + always-on conventions + a metadata-only `convention_index` of every active convention + roles + playbook metadata + dashboard + recent activity).\n- `pad_set_workspace` — Load workspace context; response embeds the bootstrap blob so you load context in one call. Whether it also pins a session default: see Workspace context below. Takes `workspace: \u003cslug\u003e` only (no `action`).\n\nFor the ten resource × action tools, always pass `action` as a top-level field. Per-action required parameters are documented in each tool's description.\n\n## Resources are cheaper than tool calls\n\nRead these directly when you need workspace state (described in the resource listings): `pad://workspaces`, `pad://workspace/{ws}/dashboard`, `.../collections`, `.../items` (use `pad_item` `list` to filter), `.../items/{ref}` (markdown), `.../attachments/{id}` (images only, at most 1 MiB, as base64 `thumb-md`), `.../bootstrap` (the same payload as `pad_meta` `bootstrap`), and `pad://_meta/version`. A host can prefetch them once per session.\n\nLoad the bootstrap resource once per workspace and reuse its collections, conventions, roles, and playbook metadata. Refresh it after switching workspaces, after changing those configuration surfaces, when Pad reports stale schema/context, or when the user asks. For changing work state, read the affected item or use a targeted project tool instead of fetching the whole bootstrap again.\n\n## Workspace context\n\nEvery action that operates within a workspace accepts an optional `workspace` parameter. Resolution order:\n\n1. Explicit `workspace` argument on the call (always wins).\n2. On a single-user local server only: the session default set via `pad_set_workspace`.\n3. On a single-user local server only: the CWD-linked workspace from `.pad.toml`.\n\nA multi-user/remote server does **not** persist a session default — pass `workspace` explicitly on every call. If none resolves, the action returns a structured `no_workspace` error with `available_workspaces`, on both the local and the remote transport.\n\n## Update flow: read first, then patch\n\nFor `pad_item.action: update`, the server merges your patch with the item's current state. Pass only the fields you want to change. When changing `status`, ALWAYS include a `comment` explaining why — it builds the audit trail that helps the team understand history.\n\n## One error code you must not retry\n\nErrors come back as a structured envelope with a `code`. Most failures are worth a retry after you fix something, and a `server_error` may be transient. `stored_state_unreadable` is neither.\n\nIt means the ITEM'S STORED DATA cannot be decoded — your input was fine. Today it fires when `note` / `decide` would append to an `implementation_notes` / `decision_log` value that is not a list of entries. The operation is refused precisely because completing it would overwrite that value. The refusal is fully deterministic, so retrying — immediately or after a backoff — fails identically every time and changes nothing.\n\nWhen you see it: tell the user which item is affected, and stop. Whether you can inspect the bad value depends on which layer is broken — if the item's whole `fields` blob fails to parse, `action: get` hands it back as a raw string; if one structured key is at fault, you won't see it at all, because the blob is normalized on this surface and a value that doesn't decode is dropped from the top-level arrays. A human can always read it with `pad item show \u003cref\u003e --format json`. Do not route around the refusal by writing the field some other way; that is the write that caused it.\n\n## Project conventions\n\nWorkspaces can declare conventions (e.g. \"run `make test` before PR\", \"use conventional commit format\"). The bootstrap blob gives you two views:\n\n- `conventions` — full bodies of the always-on (`trigger=always`) rules. Follow these unconditionally.\n- `convention_index` — METADATA ONLY (`ref`, `title`, `trigger`, `role`; no bodies) for **every** active convention, including the triggered ones whose bodies are NOT in `conventions`. This is your map of what triggered rules exist.\n\nBefore performing meaningful work with a specific trigger (e.g. `on-implement` before writing code), consult `convention_index`: if it lists entries for that trigger, pull their bodies on demand; if it lists none, skip the query.\n\n```\npad_item.action: list, collection: \"conventions\", status: \"active\"\n```\n\nFilter by trigger (`always`, `on-implement`, `on-task-complete`, etc.) when relevant — the `convention_index` triggers tell you which filters are worth running.\n\n`\"conventions\"` above is the DEFAULT collection slug and a workspace may have renamed it, in which case that literal returns nothing while `convention_index` still lists entries — the bootstrap payload resolves by declaration, not by name. When the two disagree, address the items by the `ref`s the index gave you, or find the collection with `pad_collection.action: list`. The same applies to `\"playbooks\"`; `pad_playbook` resolves by declaration and is unaffected.\n\n## Pushes and the session monitor (security note)\n\nPad can push an item into a Claude Code session (`pad push`, or the web item view's push composer). That is terminal instruction injection by design, so receiving is **consent-gated** (PLAN-2613, since v0.15.0): a session receives pushes only after it has connected (`/pad:connect` in the plugin, or a repo-level `push.auto_arm = true` in `.pad.toml` — which a per-user `auto_arm = false` in `~/.pad/config.toml` vetoes), and pushes are self-addressed only — the sender is always the receiving session's own user. This MCP connection is not a session: it cannot arm one, receive a push, or run the monitor, and the `pad_item` / `pad_project` tools expose no push action. If a user asks you to \"push\" something to their terminal, tell them it happens from their own terminal (`pad push \u003cref\u003e -m \"...\"` — the sending session need not be connected, the receiving ones must have consented); do not try to emulate it by writing comments or instructions into items.\n\n## Adding a workspace to this connection\n\nIf the user references a workspace this connection can't see (you'll get a 403 from workspace tools, or the workspace won't appear in `pad_workspace.list`), tell the user you can't see that workspace with your current permissions, then walk them through how to grant access: open Pad in their browser → switch to that workspace → avatar menu → \"Connect project...\" A 6-digit claim code will appear. Have them paste it back in chat, then call `pad_workspace.claim` with `{workspace: \"\u003cslug\u003e\", code: \"\u003c6 digits\u003e\"}`. The workspace joins this connection's allow-list and stays until the user revokes it via `/console/connected-apps`. No re-auth required.\n\nFor brand-new workspaces, `pad_workspace.create` with `{name: \"\u003cname\u003e\"}` (and optional `template`) creates the workspace AND auto-adds it to this connection's allow-list in one call — no claim code needed. Only works when the connection currently carries the \"may create workspaces\" grant — granted at consent time, or enabled later on the connections page. If the grant is present and set to false, the create is **refused with a 403 and no workspace is made** — retrying won't help and neither will the claim flow, since there is nothing to claim. Tell the user this connection isn't permitted to create workspaces, and offer them the two ways forward: create the workspace themselves in the browser and grant access with a claim code, or re-authorize this connection with \"Let this app create new workspaces\" enabled (`/console/connected-apps` can also flip it on an existing connection).\n\n## New workspace: offer to set it up\n\nThe bootstrap blob carries `needs_onboarding: bool` — true when the workspace has zero user-created items (template seeds don't count). When it's true, **lead with an active offer before anything else**: *\"This workspace is brand new and isn't set up yet. Want me to set it up? I'll ask a few quick questions and adapt it to your project.\"*\n\nThis is an **offer, not an auto-run** — wait for the user to say yes before running onboarding. If they accept, run the `onboard` playbook (use the `pad_onboard` prompt, or load the body via `pad_playbook` `action: get`, `ref: onboard`). If they decline, or already declined earlier in the session, respect that and skip the offer. The flag flips to false the moment any item exists, so it won't nag past first setup.\n\n## Built-in updates: mention once\n\nThe bootstrap blob may carry `builtin_updates: int` (absent when there are none): how many of the conventions and playbooks Pad ships have newer text in Pad's library than this workspace's copy. When it is present, mention it **once per session**, in one line, then carry on. **Never apply an update yourself**: a person reviews each one and accepts it or not.\n\n## Multi-step workflows\n\nFour prompts ship with the server: `pad_plan`, `pad_ideate`, `pad_retro`, `pad_onboard`. Use them when the user wants help planning, brainstorming, retrospecting, or onboarding into a workspace — they encode the multi-step Pad-aware playbook for each.\n" } diff --git a/docs/api.md b/docs/api.md index 4cec459be..a17622992 100644 --- a/docs/api.md +++ b/docs/api.md @@ -7,6 +7,7 @@ Moved verbatim from CLAUDE.md (TASK-3485), where it had pushed the file past Cla REST API at `/api/v1/`. Key endpoints: - **A workspace that does not resolve for the caller answers `404 not_found` with `details: {"scope": "workspace"}`** (BUG-3069) — a non-member and a deleted workspace alike, so it is not an existence oracle. A 404 about something INSIDE a workspace the caller can read (an item, a collection, a guest's ungranted item) carries no such marker. Code, status and message are unchanged from before the marker, so a consumer keyed on `not_found` is unaffected; key on `details.scope` to tell the two apart. A workspace addressed by UUID that the caller is not a member of answers `403 forbidden` instead, a separate refusal +- **A 403 from one of the shared gates names the gate in `details.reason`** (BUG-3864): `role` (the caller's workspace role is too low: `requireMinRole`, the edit check for a viewer, the grants list), `token_scope` (the API token's access does not include the action, i.e. a "Read only" token writing), `no_access` (not a member, a platform admin's bearer token on a workspace they are not in, an editor outside their collection access, a guest without the grant, or the cross-workspace check), and `workspace_not_authorized` (an OAuth connection's consent allow-list excludes the workspace; code `permission_denied`). Code and message are unchanged, so a consumer keyed on `forbidden` is unaffected. Any other 403 carries no reason, and its message is the only account of the cause. MCP reads the reason to tell the caller what to fix, on both transports; before this it said "Insufficient role" for every 403. An unverified Cloud email keeps its own code, `403 email_not_verified`, which MCP now reports as that code instead of `permission_denied` - `GET/POST /workspaces/{ws}/collections` — collection CRUD. `DELETE /collections/{slug}` ARCHIVES: a soft delete of the collection row, its items untouched and only hidden with it; nothing purges an archived collection (TASK-2189). A create or update whose `schema` has a field with no key, two fields with one key, or a select or multi_select field with an empty option or the same option twice answers **400 `validation_error`** naming it (`field key "status" is defined more than once`, `field "status" lists the option "open" more than once`, …), and nothing is written (TASK-3539): every client renders these as lists keyed by the value. It is a write check only: a schema already stored with a repeat still reads, an update that sends no `schema` still applies, and the web renders such a schema with each field and option once - **Work or reference: `settings.tracks_work`** (PLAN-3535). `false` makes a collection REFERENCE material (docs, conventions, playbooks): its items do not count toward parent progress (every progress endpoint and the dashboard's active plans), do not block a parent from closing (`open_children`), stay out of a default report (`?collections` unset; naming the collection still includes it), and stay out of open-work counts (dashboard active items, attention, suggestions, `by_role`, `pad project next|ready|stale|standup|changelog`, the attention decision set, the admin `items_open`). They still count in the sidebar and dashboard summary totals, item lists, search and links. A workspace bundle written before the key existed imports its system collections as reference, as the migration marked them. **Absent means work**, today's behaviour, so old rows and writers that never send it are unchanged. A collection CREATE that does not set it gets `false` for a system collection and otherwise `true` iff its items can finish: its done field is a select and one of its options is terminal (its `terminal_options`, or the default terminal list when it declares none, so `open, done` counts). A NEW template Docs collection is created as reference, existing collections keep work except Conventions and Playbooks (migration 135 / PG 107), and owners flip any of them. Because settings are written WHOLESALE, an update whose `settings` omit the key KEEPS the stored value, never resetting it to work. A typed top-level `tracks_work` boolean on POST and PATCH sets that one key without touching the rest of settings, and is what the CLI (`pad collection create|update --tracks-work=true|false`) and MCP (`pad_collection` `tracks_work`, v0.81) send. Any non-boolean value is refused 400. An older server ignores the member and answers 200, so the CLI checks the response - `GET /workspaces/{ws}/collections/{coll}/field-usage` — per field key, how many live items hold a value, and per string value how many hold it (TASK-2188): what the web schema editor shows before a field or option is removed. Owner-only plus full visibility, the PATCH's gates. The PATCH itself answers with an additive `omitempty` `warnings.orphaned` [{field, option?, items}] for each removed field, or option removed from a field that stays a select/multi_select, that live items still hold, read after the commit (a renamed option's migrated values are not listed). The values stay stored: a removed field's come back if a field with that key is declared again; a removed option's stay on their items, survive a `fields_patch` of other keys, and are refused on a write that sets them or a full `fields` blob that carries them. The CLI prints the list to stderr diff --git a/docs/mcp.md b/docs/mcp.md index 94012a22d..cf327ab66 100644 --- a/docs/mcp.md +++ b/docs/mcp.md @@ -26,7 +26,7 @@ Surface: **Stability contract.** Two version constants live in `internal/mcp/version.go`, advertised in the handshake under `capabilities.experimental.padCmdhelp` and `capabilities.experimental.padToolSurface`: - `CmdhelpVersion` (the constant in `internal/mcp/version.go` is the current value) — the cmdhelp CLI help-tree contract. Bump when CLI flag/arg schemas change incompatibly. -- `ToolSurfaceVersion` (the constant in `internal/mcp/version.go` is the current value; this list is its changelog, newest first) — the MCP tool catalog contract. Bump when tool names, action enums, or parameter shapes change incompatibly. **v0.99** (BUG-3790) bounds `pad_item` `starred` the same way: at most 300 items, most recently starred first, with `has_more: true` and the truncation note when more exist. It never pages. Both transports ask for one row past the cap (remote `GET /starred?limit=301`, stdio `pad item starred --limit 301`, a new CLI flag; without `--limit` the CLI walks every page). Starred used to return everything. Additive, on the v0.53 grounds. **v0.98** (BUG-3704) makes `pad_item` `list` say when it is truncated: it asks for one row past its limit and, when that row comes back, returns `limit` rows with `has_more: true` on the structured result and a second text block telling the agent to narrow the filters or raise `limit` (max 300). It never pages for the agent. A list that fits is unchanged. Additive, on the v0.53 grounds. **v0.97** (TASK-3613) adds an optional `worker_id` to `pad_item` (`claim`, `release`) and `pad_project` (`next`, `ready`): a lease is now held under a worker id plus the account, the holder label is display only, a claim answers with the caller's `worker_id`, and passing it back resumes the lease from another connection (see **Leases** above). `lease_held` details gain `worker` (the short id). The remote default holder label is the bare client name. ADDITIVE bump on the v0.53 grounds. **v0.96** (PLAN-3598 slice (c)) adds `pad_item.action=context` (`ref`; optional `intent`, `role`, `budget`), read-only, which returns one brief for working an item: the body of `GET /items/{ref}/context`, with the item and its seq, its parent chain with parsed acceptance criteria, the conventions whose trigger matches the intent (plus the always-on ones), matching playbooks, deps, decisions, links, conflicts, and what was omitted for size. New codes are `unknown_intent` (400, with `details.valid_intents`) and `unknown_role` (400). Both transports (`pad item context [--intent] [--role] [--budget]`). ADDITIVE bump on the v0.53 grounds. **v0.95** (TASK-3611) adds `pad_item.action=link-pr` (`ref`, `pr_number`, `pr_url`; optional `pr_title`, `pr_state`, `pr_branch`, `pr_repo`), which links a pull request from metadata the agent supplies, fetching nothing from GitHub, through the typed `github_pr` member; and `action=unlink-pr` (`ref`), which removes the link and refuses an item with none, as `pad github unlink` does. Both transports (`pad github link --pr-number N --pr-url U ...`, new flags). ADDITIVE bump on the v0.53 grounds. **v0.94** (TASK-3611) adds `pad_item.action=reminders` (`ref`), which lists an item's reminders with their ids (armed, fired, acknowledged), and `action=unremind` (`reminder_id`), which disarms one, on both transports. Listing is read-only; disarming needs edit permission on the item, as on the CLI. Re-arm stays CLI-only (`pad item remind --rearm`). ADDITIVE bump on the v0.53 grounds. **v0.93** (TASK-3611) makes `pad_item.action=create` and `update` over the local stdio transport WRITE a `fields` value that is an object or array, which they used to refuse (BUG-2850): the stdio door passes those keys, and every other non-string value (numbers and booleans, which `--field key=value` delivered as text unless the schema typed them), to the CLI as one `--fields-json` object (a new additive flag on `pad item create` / `update`), keeping their JSON types, as the remote door sends them. Any other action still refuses one. ADDITIVE bump on the v0.53 grounds. **v0.92** (TASK-3585) adds `op_key` to `pad_item.action=comment`, `note` and `decide`: retrying the same request with the same key answers the comment or entry the first attempt made instead of appending again, recorded in the write's own transaction. On the item-update route a key is accepted only with an append (and `source`); any other member alongside it is refused 400. `idempotency_target_gone` (410: the item or comment the key wrote has since been deleted) is now a structured code on both transports, with its own hint; at 0.91 it reached MCP as a generic error. No name, enum or param moved. ADDITIVE bump on the v0.53 grounds. **v0.91** (TASK-3585) adds `op_key` to `pad_item.action=create`: retrying the same create with the same key answers the item the first attempt created (as it stands now) instead of creating a second one; the answer is recorded in the create's own transaction. A key reused for a different create is refused `idempotency_key_reused`; one still in flight answers `idempotency_in_flight` (both codes already existed, and are structured on both transports for any route). A replay whose item has since been deleted answers HTTP 410 `idempotency_target_gone`, which at 0.91 reached MCP as a generic error. No name, enum or param moved. ADDITIVE bump on the v0.53 grounds. **v0.90** (TASK-3585) adds `pad_item.action=patch` `op_key`, an idempotency key: the same request retried with the same key returns its first answer instead of applying again; new codes `idempotency_key_reused` (422), `idempotency_in_flight` (409) and `patch_outcome_unknown` (409, with `seq` and the diff since). ADDITIVE bump on the v0.53 grounds. **v0.89** (PLAN-3578 step 3) adds `pad_item.action=patch` `undo` (a `patch_id`), which inverts that patch, anchored on the text around each edit as it landed, refusing when that text has changed since, and the code `patch_not_found` (404). ADDITIVE bump on the v0.53 grounds. **v0.88** (PLAN-3578 step 2) makes `pad_item.action=patch` on an item open in a browser editor APPLY (the editor applies it as a narrowed replace of its live document; the answer adds `content_state: "applied_pending_flush"`) where it was refused `patch_room_open`, and adds the code `patch_unstable_roundtrip`. `patch_room_open` now means only an older editor holds the item. BEHAVIOR bump on the v0.84 grounds. **v0.87** (PLAN-3578 step 1) adds `pad_item.action=patch {ref, edits:[{old, new, line_hint?}], expected_seq?}`: exact-text edits to the body (each `old` occurs exactly once, applied in order, all or nothing) answered with `{seq, patch_id, version_id, rebased, intervening?, diff}`. A moved `expected_seq` is applied over and reported, never refused. Refusals write nothing: `patch_anchor_missing`, `patch_anchor_ambiguous` (`details.lines`), `patch_room_open`. `get` gains `lines` for numbered body lines with `seq`. ADDITIVE bump on the v0.38 grounds. **v0.86** (PLAN-3555 phase 1) adds `pad_item.action=update` `replace` (bool): the deliberate overwrite of content with no version token, refused with `expected_seq` / `expected_updated_at` or without `content`. A content write with neither carries `warnings.unguarded_content_write: true`, and a later release refuses it. A seq `update_conflict` on a content write gains `details.content_write`, `changed_at` and `changed_by_kind`, a message naming both seqs that says not to resend the body, and the same "re-read and merge, do not resend" hint on both transports. ADDITIVE bump on the v0.53 grounds. **v0.85** (BUG-3544) makes `pad_workspace.action=invite` on an instance with no account yet (the setup window, reachable over local stdio) answer 409 `setup_required` ("This Pad instance must be initialized with pad auth setup") and write nothing, where it answered 500 (`server_error`) from the invitation's inviter foreign key. BEHAVIOR bump on the v0.58 / v0.45 grounds. **v0.84** (BUG-3542) makes a `pad_item` content update answer 409 `content_not_applied` with `details.apply_reason: "unconfirmed_edits"` when a browser tab holding the item open still has typing the server has not stored; token or not, other fields land and the content does not. Wait, re-read and resend; `overwrite_pending_edits: true` is the only override. BEHAVIOR bump on the v0.39 / v0.43 grounds. **v0.83** (TASK-3539) makes `pad_collection` create and update REFUSE a `schema` in which a field has no key, two fields share a key, or a select field lists an empty option or the same option twice, with 400 `validation_error` naming it (`field key "status" is defined more than once`). BEHAVIOR bump on the v0.43 / v0.48 grounds: a write door refuses a call it used to accept. Write-only: a schema already stored with a repeat still reads, and an update that sends no schema still applies. **v0.82** (PLAN-3535 PR 2) makes the items of a REFERENCE collection (`tracks_work: false`) stop counting as open work on every agent surface: `pad_project` next / ready / stale / standup / changelog, the dashboard and bootstrap dashboard, item progress, the `open_children` close guard and the attention decision set leave them out, and a report with no `collections` leaves the collection out as it already did a system one. Sidebar counts, item lists, search and links are unchanged; a collection without the key counts as work. BEHAVIOR bump on the v0.49 grounds. **v0.81** (PLAN-3535 PR 1) adds a `tracks_work` boolean to `pad_collection` create and update: false makes the collection REFERENCE material whose items stop counting toward parent progress, close blocking, Insights and open-work counts (applied by the follow-up PRs). On update it sets that one settings key server-side and leaves the rest alone; omitted, create picks work iff the done field can finish and update leaves it unchanged. ADDITIVE. **v0.80** (BUG-3533) makes `pad_item.action=import` work over remote `/mcp`: it answered `validation_failed` "artifact is required" on every call, because the catalog action dropped `artifact` from the input the HTTP dispatcher reads. Stdio is unchanged. ADDITIVE bump. **v0.79** (TASK-2863) lets a read-only grant (`read` / `pad:read`) run a playbook: `pad_playbook.action=run` stores nothing, and was refused only because it is a POST. It is the one POST a read grant may make (an exact-path allowlist); `match` and every write stay refused. BEHAVIOR bump, additive in effect. **v0.78** (TASK-2308) answers a remote `/mcp` WRITE action from an OAuth connection that can only read (`pad:read`), in a `tools/call` request of up to 1 MiB, with HTTP 403 and a `WWW-Authenticate` `error="insufficient_scope"` challenge naming `scope="pad:read pad:write"` and the metadata document, before dispatch, where it got a `permission_denied` tool result; that challenge is what lets a client re-authorize with the wider grant. Every such call was already refused, so nothing that worked is refused now. A read-scoped PAT keeps the tool error (it cannot re-authorize), as does a larger request, and the ChatGPT mount keeps its own challenge. The 401 challenge also names `scope`. BEHAVIOR bump. **v0.77** (BUG-2772) records a remote `/mcp` write as an AGENT write named by the client's declared MCP `clientInfo.name`, where it was recorded as the human, and gives a remote call a per-connection default lease holder (`claude-code#3f9a12c4`); see "Remote caller identity" below. A claim on an item another holder leases now answers `lease_held` with `details.holder` and `details.expires_at` on both transports, where remote said `conflict` and stdio `server_error` (BUG-3496). BEHAVIOR bump. **v0.76** (TASK-1809) makes a `pad_item` `claim` / `release` with no `holder` hold the lease under the caller's agent name (the `X-Pad-Agent` the CLI sends), else the account's email, where it was the email alone: several agents on one account silently shared one lease, a second claim answering 200 by refreshing the first. It now answers 409 `lease_held` naming the first agent. `pad_project.action=next` / `ready` leave out items whose live lease a claim by the caller would lose (same identity, the claim's own predicate, filtered before the cap of three; reminders are not filtered). Remote /mcp sends no agent name, so its default is still the email (TASK-3495). A lease taken before the upgrade is another holder's to the same agent for up to its TTL. BEHAVIOR bump on the v0.70 grounds. **v0.75** (BUG-3480) makes `pad_item.action=list` on both transports refuse a filter key no schema in scope declares and no item in scope stores (400 `validation_failed`, "invalid list filter ..."), where it answered an empty list, and refuse a key that is not a field key, which the store used to drop (answering the unfiltered list). BEHAVIOR bump on the v0.43 / v0.29 grounds; see the item list endpoint bullet under API. **v0.74** (TASK-2188) makes `pad_collection.action=update` answer, on both transports, with an `omitempty` `warnings.orphaned` [{field, option?, items}] naming each field, or select option, its schema removed that live items still hold. Nothing is refused. ADDITIVE, the v0.67 grounds; 0.73 is BUG-3480's. **v0.72** (TASK-2189) adds `pad_collection` `list-archived` (read-only) and `restore` (owner-only, by slug or id), backed by the new `GET /workspaces/{ws}/archived-collections` and `POST /workspaces/{ws}/archived-collections/{ref}/restore`: an agent's archive is recoverable by an agent. ADDITIVE. **v0.71** (TASK-3462 U3a) adds an `omitempty` `builtin_updates` count to the bootstrap on every door that returns it (the conventions and playbooks Pad ships whose library text changed since the workspace's copy, among the items the caller sees in full), and a server-instructions section telling the agent to mention it once and never apply an update itself. ADDITIVE. **v0.70** (BUG-3453) makes `pad_project.action=next` / `ready` fill any slot the existing tiers leave empty with ordinary open items from non-system collections that declare `priority` or `severity` (an initial status like `new` counts), ranked below every item admitted before, so a full list is unchanged and a moved-in backlog with no priorities is no longer "nothing ready". BEHAVIOR bump on the v0.49 grounds. **v0.69** (TASK-2314) makes every REMOTE route that needs a workspace and lacks one answer `no_workspace` with `available_workspaces` and a hint, as stdio always did, where it answered `validation_failed` "workspace is required"; the single-workspace default now runs before the `assign` / `role` resolvers. BEHAVIOR bump on the v0.42 / v0.45 grounds. **v0.68** (BUG-3448) makes the item resource render a structured field as compact JSON instead of Go's map syntax, keep a number above 2^53 to its digits and render a JSON null as `null`; the agent projection stops rounding large numbers. BEHAVIOR bump on the v0.62 / v0.64 grounds: an output shape changed, no name, enum or param moved; scalar fields render as before. **v0.67** (BUG-3446) lets a create in a system conventions or playbooks collection ADD a trigger/scope word the library itself uses to the select options instead of refusing it, so `pad_library.activate` and B3's literal create succeed in a `blank` workspace, and adds an `omitempty` `warnings.options_added` to the create result on both transports. A word the library does not use is refused as before. ADDITIVE. **v0.66** (BUG-2136) makes `pad_workspace.action=invite` always create a pending invitation, never add an existing account directly; see `internal/mcp/version.go`. **v0.65** (TASK-3413, SPEC-6 U9c) adds `omitempty` `via_app` and `via_app_name` to items an installed app CREATED (items.created_via_app, never the last app writer), comments an app wrote and version rows an app's write made, on both transports (`pad_item` get, list summary and full, comments, history summary and full). The name is the app's bot display name, else its origin, and survives uninstall. ADDITIVE. **v0.64** (BUG-3379) adds an `omitempty` `imported: true` to comments, attachment rows and version rows a workspace import wrote, on both transports (`pad_item` comments, `pad_attachment.list`, and `pad_item.history` with `full: true`; history summary rows and attachment `show` do not carry it): import keeps the export's author strings and uploader ids verbatim, and the flag says they were not verified here. ADDITIVE. **v0.63** (TASK-3321) adds an `omitempty` `actor_name` to every `pad_item.action=history` summary row on both transports, the display name of who made the change, where rows said only `user` or `agent`. ADDITIVE. **v0.62** (BUG-3326) makes remote /mcp `pad_set_workspace` embed the workspace bootstrap, as stdio always did: the in-process bootstrap resource read, run as the token's user under the same scope/consent perimeter, so a workspace the caller cannot read embeds nothing. ADDITIVE; no name, enum or param changed, and stdio is unchanged. **v0.61** (TASK-3321 U0b) marks `pad_workspace` destructiveHint:true and openWorldHint:true, because `invite` sends an email to an arbitrary address, and `pad_playbook` openWorldHint:true, because `match` sends text to the decision provider. Annotation-only BEHAVIOR bump on the v0.20 grounds; every other tool's block is unchanged. **v0.60** (TASK-2198 U4) makes `content_state: "applied_pending_flush"` clear ON ITS OWN on every door that carries it: after the item's collab room closes (or a one-minute sweep finds it dormant) the server rebuilds the body from the op-log and stores it, moving `seq` (a held `expected_seq` then answers `update_conflict` instead of `content_pending_flush`) and adding a `system` / `recovery` version. BEHAVIOR bump on the v0.59 / v0.39 grounds; no name, enum or param changed. Not a guarantee (failures, set-aside rows, `PAD_MATERIALIZE=off`), so re-read later, never re-send, still stands. **v0.59** (BUG-3252, tombstone ruled over cascade) makes `pad_item.action=delete-comment` on a comment with replies SUCCEED, leaving a tombstone (body emptied, author and timestamps kept, additive `deleted: true`) its replies stay under; it is removed when its last reply is deleted. `edit-comment` on a tombstone answers 409 `comment_deleted` on every transport. BEHAVIOR bump on the v0.58 grounds; `comment_has_replies` stays classified for older servers. **v0.58** (BUG-3252) makes `pad_item.action=delete-comment` on a comment that still has replies answer 409 `comment_has_replies` (details `comment_id`, `reply_count`) on every transport instead of `server_error`: `comments.parent_id` has no ON DELETE, so the delete failed the FK inside the store. Nothing is deleted either way. Tombstone was then ruled over cascade; v0.59 replaced this refusal with it. BEHAVIOR bump on the v0.45 grounds. **v0.57** (TASK-2695) adds `pad_item` `edit-comment` (ref, comment_id, message) and `delete-comment` (ref, comment_id) on all three transports, backed by the item-scoped routes `PATCH/DELETE /workspaces/{ws}/items/{ref}/comments/{id}`, which answer 404 unless the comment is on `ref` and otherwise run the workspace routes' handlers (edit author-only, delete item-edit). CLI: `pad item comment-edit` / `comment-delete`, refused against a server without the `item_scoped_comment_writes` capability. Every serialised comment gains a derived `edited` bool (updated_at > created_at), and `pad item comments` prints each comment's id. ADDITIVE. **v0.56** (BUG-3244) gives `content_state` a second value, `superseded_set_aside`, on every MCP door that carries it (`pad_item` get / full list, `pad_playbook` run, the item resource's line above the body): edits an editor schema-version rebuild set aside, which opening the item will NOT restore, so the resource line and the `content_pending_flush` hint (chosen by `details.set_aside_rows`) name `pad item set-aside` and `overwrite_pending_edits` instead. ADDITIVE bump: no name, enum or param changed, but an agent branching on the one-word vocabulary meets a word whose remedy differs. Reading or discarding the rows alone is not on the catalog. **v0.55** (BUG-2659) sends `pad_item.action=search`'s `collection` to /search as typed, and /search resolves it exact-first per workspace in scope (the item routes' resolver). In a workspace holding both `task` and `tasks`, `collection: "task"` now answers from `task` instead of `tasks`; every other workspace is unchanged, because the shorthand still resolves server-side. Stdio reaches it through the CLI, which sends the name as typed only to a server advertising `search_collection_resolution`. BEHAVIOR bump on the v0.36 / v0.40 grounds. **v0.54** (BUG-3217) keeps a `fields` number's literal through MCP on both transports (mcp-go's argument decode rounded anything above 2^53, and stdio's `--field` stringify carried the rounded value), and REFUSES a `fields` number beside a `field` entry for the same key when they differ as exact numbers — two values that differ only above 2^53 used to collapse into one rounded write; a matching pair (3.0 beside n=3) still collapses. BEHAVIOR bump on the v0.48 grounds. **v0.53** (BUG-2819) adds `filename_source` (caller / normalised / substituted / derived / unknown) to every `pad_attachment.action=list` row on both transports, because a stored filename cannot say whether the caller sent it or the server substituted it. ADDITIVE, the v0.28 / v0.13 disposition; `show` does not carry it, and `mcp_audit_log.tool_name_source` reaches no catalog action. Rows written before it read `unknown`, never `caller`. **v0.52** (BUG-2367 item 4) refuses a move or copy (every migrate door) that would change an item between open, done and abandoned unless the caller names the destination done field. Only the STATE is compared, so two values that both mean done carry. Move answers 400 `state_change_requires_value` with details `{field, options, from, to}`; bulk move puts it in a `failed[]` row; the copy answers 400 `validation_error` with the same sentence; the preflight emits a needs_value row with reason `state_change`, which the web dialog picker renders. A destination with no done select field is exempt. BEHAVIOR bump. **v0.51** (BUG-2367) stops every migrate door (single move, bulk move, cross-workspace copy and its preflight) carrying a value into a field the destination marks `computed` (preflight drop reason `target_computed`) or a value that collides on a destination `unique_scope` field. Provenance decides, the TASK-2878 rule: a CARRIED collision is dropped and reported (`not_unique`), a supplied override or injected default that collides is refused 409 `conflict`, and a required field emptied by the drop is refused as required, which is the existing needs_value route. Before it, single move answered 500 on the indexed `invocation_slug`, bulk move leaked the SQL error, and an unindexed unique field stored a duplicate. Reporting is additive and omitempty: `warnings.not_unique` [{key, value, holder?, message}] on the move response, bulk `updated[]` rows and the copy response, and a `detail` sentence on the preflight's dropped row. `holder` is present only when the caller may see that item, so the drop is not an existence oracle. BEHAVIOR bump on the v0.43 / v0.29 grounds. **v0.50** (BUG-3014) adds an ADDITIVE `omitempty` `stored_as_text: true` to a `relation_targets` entry whose stored value is not UUID-shaped (a title a bundle import carried verbatim, or legacy free text). Such a value was never an id and used to hydrate as a plain id-only entry, which reads as "gone or hidden"; an id-only entry without the flag keeps that meaning, and a UUID-shaped value, resolved or not, is byte-identical to v0.49. The predicate is syntactic, decided from the stored bytes and never from a lookup, so it discloses nothing, and deliberately not coupled to the resolver ladder. The CLI prints `"" (text, not a reference)` and the web chip says the same. **v0.49** (BUG-2410) makes `pad_project.action=report` with no `collections` param leave out SYSTEM collections (`Collection.IsSystem`: Conventions and Playbooks), which were counted in Insights' created, WIP and status totals; naming one explicitly still includes it. BEHAVIOR bump on the v0.40 / v0.42 grounds: a default call's content changed for every caller (web Insights, print, `pad project report`, both MCP transports, all through the one store rule). **v0.48** (BUG-3163) makes `pad_item.action=create` REFUSE a `field` / `fields` entry naming any reserved metadata key (`implementation_notes`, `decision_log`, `github_pr`, `convention`) on every transport, with 400 `validation_error`, creating nothing: create was the last door that stored one, as a string no extractor reads. Library activation, its one system writer, moves to an additive typed `convention` create member (not on the catalog; `pad_library.activate` is unchanged), and the CLI verifies from the stored fields that it landed, because an older server ignores the member and answers 201. BEHAVIOR bump on the v0.47 grounds. **v0.47** (BUG-2696) makes `pad_item.action=update` REFUSE a field setter naming `github_pr` on every transport (400 `validation_error` naming `pad github link` / `unlink`), closing the exemption v0.23 left: that door stored the PR as an unreadable string, so no link ever rendered. The writer is a new additive, typed update member (`github_pr` object + `clear_github_pr`) used by `pad github link` / `unlink` / `project reconcile`, deliberately NOT on the catalog (a remote PR-link action waits on the catalog-trim decision). BEHAVIOR bump; item create is BUG-3163. **v0.46** (BUG-3156) makes `pad_item.action=bulk-update` over stdio and remote REFUSE, per item, a status or priority change on an item whose collection does not declare that field, writing nothing for that item: the answer WebMCP has given since v0.44, so the three transports agree. Rows keep each transport's shape (stdio `failed[]` with `validation_error`, remote `results[]` with `validation_failed` and the server message in `hint`). The mechanism is the update door's new `refuse_undeclared_fields` member, which both bulk-update transports set; `pad_item.update` does not, and still accepts-and-warns. A server that predates the member ignores it, which is the old accept-and-warn. BEHAVIOR bump on the v0.44 / v0.43 grounds. **v0.45** (BUG-2829) reports an HTTP 413 as `too_large` on BOTH transports, with the server's own code in `details.reason`, where it used to be `server_error`: three deliberate caps are reachable from the catalog (a title rename's link cascade, an oversized outbox event, an oversized artifact import), and the old code read as transient and invited a retry that fails identically. Remote maps 413 in `classifyHTTPStatusKind`; stdio gets it from a structured marker the CLI root writes for any 413, and `too_large` joins `allowedStructuredErrorCodes`, which a test now proves contains every code any CLI marker writer emits. BEHAVIOR bump on the v0.42 grounds; no name, enum or param shape changed. **v0.44** (BUG-3154) makes `pad_item.action=bulk-update` over the WebMCP browser transport REFUSE, per item, a status or priority change on an item whose collection does not declare that field: the item lands in the bulk response's `failed` array with `validation_error` naming the collection and field, nothing is written, and the rest of the call applies. The door is `POST /items/bulk` (`set-priority`, and `move` with a `status`, with or without a `collection`, where the target's schema decides), where the request carries an operation and a value and the SERVER chooses the key; it used to store an orphan field and report the item updated. BEHAVIOR bump on the v0.43 / v0.40 grounds. The transports disagreed after it, stated rather than implied: stdio and remote issued a per-item PATCH, the single-item update door, which ACCEPTED the key with `warnings.undeclared_fields` (v0.27), until v0.46 converged them. **v0.43** (BUG-2379) makes `pad_item.action=move` REFUSE a field override naming a field the destination schema does not declare, with 400 `malformed_override` — the same check, code and message the cross-workspace copy already used. BEHAVIOR bump on the v0.40 / v0.29 grounds: a write door refuses a call it used to accept, where it used to store the key as an orphan field no schema renders. Create and update still ACCEPT undeclared keys with `warnings.undeclared_fields` (v0.27), because callers round-trip the whole fields blob; an override is a fresh assertion about the destination schema, not round-tripped state. **v0.42** (BUG-3142 + BUG-3147) changes the error CODE a LOCAL STDIO caller receives for two failure families that used to arrive as retryable `server_error`: an argv refusal (cobra/pflag: unknown flag, arg count, …) is now `validation_failed` with its message kept, and a 429 on any command is now `rate_limited` with `details.retry_after_seconds`, via the structured marker line the CLI writes at its root. It also stops the refusal that caused most of the first family: `BuildCLIArgs` now emits flags first and the positionals behind `--`, so free text starting with `-` (`item search "-ship it"`) is no longer parsed as a flag. BEHAVIOR bump; no name, enum or param shape changed, and the remote transport is untouched. **v0.41** (PLAN-3114 U5 / TASK-3120) adds a `match` action to `pad_playbook`: given free `text`, a Choice question over the workspace's ACTIVE playbooks plus a reserved `"none"` option returns the best match's ref (or `"none"`), confidence, per-option probabilities and the model. No provider configured → 404 `decision_provider_unavailable`; a provider error or an out-of-set answer → 502 `decision_provider_error`. Pure ADDITIVE bump (new action + param, nothing existing moved), read-only and side-effect-free. **v0.40** (BUG-3028) gives a scalar `relation` ONE stored form for "no target", the key ABSENT, converging on multi_relation's rule. A blank (`""` or whitespace) a write SETS — create, `fields_patch`, a changed value in full `fields`, a move/copy override — is normalised to absent before validation, so a `required` relation is refused as required (a patch blanking it now gets the answer deleting it always got). A legacy blank a write only CARRIES — an untouched key under `fields_patch` (normalised by the store under its write lock, via `ItemUpdate.BlankRelationKeys`), an unchanged value in full `fields`, move, copy, artifact import — is normalised after validation and never refused. An empty list filter on a scalar relation key of a collection-scoped list (`owner=`) matches all three spellings. BEHAVIOR bump; no shape change. Workspace import (`store.ImportWorkspace`) still stores blobs verbatim; its legacy blanks normalise on the next write. **v0.39** (BUG-3133) refuses `pad_item.update` that sets content WITH a version token (`expected_seq` / `expected_updated_at`) while the item's op-log holds content-bearing rows above its flush watermark, with 409 `content_pending_flush` (details `ref`, `pending_rows`). BEHAVIOR bump on the v0.35 / v0.36 grounds, carrying one additive param: `overwrite_pending_edits` lifts it, on the API, the CLI (`--overwrite-pending-edits`; `pad item edit --force` sets it on the save) and MCP alike, because an agent must be able to clear the refusal without a browser. The token guards the ROW and a tab's unflushed typing is not in it, so the write used to replace those edits — through the applier's setContent with a tab open, and by the direct path's op-log prune, which DELETES them, with none. Its own code rather than `update_conflict` because re-reading returns the same row and seq. A write without a token, without content, or to an item with nothing pending is unchanged, except that a direct write now reports `warnings.pruned_pending_edits` (additive, omitempty) when its prune deleted such rows. The check runs in the write's own tx; on the direct path it is under the item lock and appendMu and exact, on the applier path a tab can still type in the one server hop between the check and setContent. (v0.37 and v0.38 — the `agent` projection on `pad_item.get` and `claim` / `release` — are in `internal/mcp/version.go`; this paragraph had stopped at v0.36.) **v0.36** (BUG-3082) stops a REF-SHAPED `relation` value falling back to matching by item NUMBER when its prefix names a collection that is LIVE in the workspace; such a value is now `not_found`. BEHAVIOR bump on the v0.35 / v0.30 / v0.29 / v0.16 grounds — no tool name, action enum or param shape changed, but a write door refuses a value it used to accept. It finishes v0.29: that entry closed free-text corruption ("red" resolving to whatever is slugged `red` today) and left the same corruption open for anything shaped like a REF, which is the spelling the docs tell callers to prefer. Item numbers are workspace-unique and sequential ACROSS collections, so `CONVE-1` and `SECRE-1` are never both real — the fallback dropped the prefix, matched on the number alone, and landed on an item that was usually inside the field's declared collection, so the wrong-collection check above it passed and NOTHING was raised: a caller wrote `CONVE-1`, the item stored a different item's UUID, and the write answered 201 with the substitution visible only in `relation_targets`. The predicate is about the PREFIX rather than the item because a collection RENAME changes its prefix and a relation already written as the old ref must keep resolving (BUG-2873) — that ref's prefix names nothing afterwards, so the fallback still fires for it, while a prefix that IS live and simply holds no item at that number is the caller naming a real collection that does not contain what they said. A SOFT-DELETED collection counts as absent IN THAT PREDICATE, for the same reason a renamed one does — a claim about the fallback only: the exact-prefix lookup ahead of it never filtered on the collection’s own `deleted_at`, so an item whose collection was soft-deleted still matches THERE and never reaches the predicate. That is left alone rather than made consistent, because it cannot retarget — the downstream collection check refuses it. RESIDUAL, stated rather than implied and pinned by a test: a ref pasted from ANOTHER workspace whose prefix also names no collection here still resolves by number, because nothing in the value distinguishes it from a rename's leftover. No escape hatch, for v0.29's reason. Out of scope and unchanged: `GetItemByRef`, the navigational read path, where landing on the moved item is the helpful answer. **v0.35** (BUG-3079) makes an injected schema DEFAULT take the same `validateFieldType` check a caller-supplied value takes; one that fails is DISCARDED and named in `warnings.dropped_fields` instead of being stored. BEHAVIOR bump on the v0.30 / v0.29 / v0.16 grounds — no tool name, action enum or param shape changed, but a write door stores something different from what it stored before. Unlike v0.29, which turned an accepted value into a refusal, this turns a stored value into a reported drop: a create that used to land WITH a bad field still lands, without it. What it closes is two doors disagreeing about one value, decided only by who put it there. It also widens `dropped_fields` from the single relation case v0.29 introduced to a field of ANY type. No escape hatch, for v0.29's reason. ONE exception, which is the rule finishing its sentence rather than a carve-out: dropping leaves a REQUIRED field absent, which is exactly what the required check reports, so such a write is refused — naming the default as the cause, because a bare "field is required" points its reader at a request that never mentioned the field. **v0.34** (BUG-3037) adds an `expected_seq` param to `pad_item.action=update` — the STRONG optimistic-concurrency token, preferred over `expected_updated_at`. ADDITIVE (the v0.13 / v0.11 / v0.8 disposition): nothing existing moved and `expected_updated_at` still works. It is needed rather than nice because `updated_at` is stored at ONE-SECOND resolution, so two writes to a row inside one second both match the token and NEITHER conflicts — the loser is accepted and silently overwrites the winner, both callers seeing success. That is the shape of agent traffic, so the token agents were offered could not refuse the race it exists to refuse. `seq` is bumped on every mutation of the row under the write lock. Raising `updated_at`'s resolution instead was measured and REJECTED: the column is TEXT on both dialects and compared LEXICALLY in SQL (the since-cursor read plus eight `ORDER BY` sites), and Go's `RFC3339Nano` omits trailing zeros, so a sub-second value sorts BEFORE a whole-second value of the same second and the cursor would start skipping rows. The read side is what makes the token reachable: `seq` now serialises without `omitempty` on `models.Item` AND on the item SUMMARY shape (`cli.ItemSummary`), which is what `pad_item.list` returns by default since v0.9 — a token absent from the shape a caller reads is a token that caller cannot send. A value below 1 is a 400, not a 409: the server never issues one, so a 409 would read as contention that never clears. **v0.30** (BUG-2870) is a BEHAVIOR bump on the v0.29/v0.27/v0.26/v0.16/v0.10/v0.9 grounds — no tool name, action enum or param shape changed. **Every door refuses a padded KEY now**, and each was accepting it differently: /mcp trimmed it and wrote the declared field, the CLI stored a ghost field beside it — so both refuse something they used to accept. What is /mcp-only is the VALUE half, which it used to trim and type and now passes through to the same validation the CLI has always applied. A caller writing canonical entries sees no difference at either door. A second, separately-noticeable fix rides with it: `detectFieldConflicts` swallowed `parseFieldArray`'s refusal as "the caller owns this error surface", which held only while the sole possible error was a shape error — `reshapeItemFields` returns early with no `fields` object, so on the no-`fields` path (this bug's own path) four existing refusals were landing as successes. No escape hatch, for v0.29's reason: there is no legitimate call this refuses, only calls whose two readings a door used to choose between silently. **v0.29** (PLAN-2857 U1 / TASK-2878) is a BEHAVIOR bump on the v0.27/v0.26/v0.16/v0.10/v0.9 grounds (NOT v0.28's, which was purely additive) — no tool name, action enum, or param shape changed, but a `relation` field value must now name a live item in the collection that field declares, so every write door refuses values it used to store. Refused: names nothing (`not_found`), names an item in the wrong collection, the field declares no target collection (`target_missing`), or the value is a SLUG — a deliberate divergence from `ResolveItem`'s UUID→ref→slug ladder, since a slug is neither an ID nor stable and free text like "red" resolving to whatever is slugged `red` today is exactly the corruption this closes. Ordinary `validation_error`, no new code and no new details key, because stdio classifies errors by matching CLI stderr prose. A CARRIED value — already on the item, asserted by nobody — is never refused, since refusing would make every legacy item un-updatable, un-movable and un-copyable: within a workspace it resolves and SURVIVES, across a workspace boundary it is dropped without a lookup (a source-workspace id cannot mean anything in the destination) and reported through the same `warnings.dropped_fields` channel BUG-2674 established. No escape hatch, deliberately: unlike v0.10's `allow_draft` there is no legitimate call this refuses, and the case with a real claim to leniency is already exempt by provenance rather than by a flag. **v0.28** (IDEA-2641 / GitHub #1010) adds two ADDITIVE `pad_item` actions and two optional params: `remind` arms a one-shot reminder at an RFC3339 `remind_at` INSTANT, and `ack-reminder` acknowledges a fired one by `reminder_id`. Purely additive — nothing existing moved, and a v0.27 consumer that enumerates neither action is unaffected; same disposition as v0.13 / v0.11 / v0.8, which likewise wired existing CLI verbs onto the catalog. Agents already RECEIVED reminders (the poll surface is `pad_project.next` / `ready`, long exposed); what was missing is the half where an agent that defers work can say when it wants to be asked again. `remind_at` REFUSES a bare date rather than reading it as midnight — the `date` schema type accepts `YYYY-MM-DD` so a caller will try it, but a bare date names a 24-hour span and choosing an hour inside it would fire at a time nobody picked. Re-arm and disarm stay CLI-only: both address a reminder by an id the agent would have to list first, and no listing action exists on this surface yet — a door with no handle. **v0.27** (BUG-2850) types field values SERVER-SIDE at all eight validate sites, carries the `fields` object to the remote door with its JSON types intact, accepts undeclared keys while NAMING them in `warnings.undeclared_fields`, and replaces five accreted conflict guards with one canonical pass; the merge refuses several ambiguities it used to resolve silently. (This entry was missing from CLAUDE.md — the 0.27 unit swept `instructions.md` and `README.md` and not this file.) **v0.27** (BUG-2850) types field values server-side at all eight `Validate*` call sites so a declared number/json field is writable from the remote transport at all, carries the `fields` OBJECT with its JSON types intact, names undeclared keys back in `warnings.undeclared_fields` (accepted rather than refused — a census of 1012 items found 14 such keys across 168 live values, so refusing would have broken read-modify-write on items nobody had edited wrongly), and replaces the accreted per-site conflict guards with ONE check over a canonical view of every source; that check refuses ambiguities v0.26 resolved silently, chiefly two names for one target in a single call (`parent`/`plan`, `assign`/`assigned_user_id`, `role`/`agent_role_id`), refused even when the values match because the names address one thing through incomparable vocabularies and the two doors resolved them differently. **v0.26** (IDEA-2756) is a BEHAVIOR bump on the v0.9/v0.16/v0.25 grounds — no tool name, action enum, or param shape changed, but `pad_workspace.create` now refuses a call it used to permit. Closest precedent is v0.10, which likewise turned a server-side gate into a structured refusal; unlike v0.10 there is no `allow_draft`-style override, because the gate encodes a decision the USER made at consent time and a bypass param would be the app overriding its own grant. `POST /workspaces/import` is gated by the same shared helper (import mints a workspace through `store.ImportWorkspace`), though it has no MCP action today. **v0.25** (TASK-2657 / BUG-2702) resolves `pad_library.activate`'s destination collection from the target's declared artifact kind rather than the literal `conventions` / `playbooks` slugs, so activating into a workspace that renamed either collection lands correctly; a lookup ERROR is surfaced rather than silently falling back. **v0.24** (#1066) adds the `fields` OBJECT param to `pad_item` create/update — an alias merging into the same path as `field`/the dedicated params, so the shape reads return is finally a valid write shape; the same key supplied twice with conflicting values is REFUSED (refuse-on-ambiguity, the v0.18/v0.19 disposition), equal duplicates collapse to one write, and non-writer actions refuse a `fields` param loudly. It also makes input validation STRICT for every catalog tool: undeclared top-level keys are rejected with a structured error naming them, instead of being accepted and silently dropped by `BuildCLIArgs` — which is the mechanism that made the `fields` object a session-scoped silent no-op in the first place. Compat carve-out: `pad_item`'s v0.16 `assigned_user_id` / `agent_role_id` remote-transport clear form stays accepted (documented, undeprecated, deliberately never schema-declared). The strict half changes behaviour for inputs that previously "succeeded", but that reliance was indistinguishable from a caller bug (the key never did anything), so the break is the fix; one bump covers both halves. **v0.23** (BUG-2627 part 2 + BUG-2675) refuses system-metadata keys through `fields_patch` on all three doors at once, `github_pr` exempt on update (move/copy still refuse it), and adds the retry-hostile `stored_state_unreadable` code. **v0.22** (BUG-2674) stops `pad_item.action=move` destroying system metadata and refuses `field` setters naming the reserved keys there. **v0.21** bounds `pad_item.action=history` (BUG-2608): the `limit` param now covers it, default 50 / max 300, applied in the CATALOG action so it reaches both transports (HTTP reads the input; stdio gets the CLI's new `--limit` via BuildCLIArgs). The window is the NEWEST N and there is deliberately no `offset` — versions are reverse patches, so only a newest-end window is cheap to reconstruct. Additive param bump; a v0.20 consumer sending no limit now receives the newest 50 rather than every version, which is the fix. Summary mode additionally asks the server to skip patch resolution rather than resolving bodies the dispatcher discards. **v0.19** adds a `clear_parent` boolean to `pad_item` (BUG-2078) — an ADDITIVE param bump, same grounds as v0.18; nothing existing changed shape. The server has supported clearing a parent since BUG-2013 (`extractParentLink` treats a present-but-empty `parent` key in `fields_patch` as detach), but neither client surface could reach it — `--parent ""` was a silent no-op on the CLI and the MCP `parent` param has the same "empty means not provided" convention every other declared string on the tool has. Boolean rather than overloading the empty string, same two reasons as v0.18: keeps that invariant intact for every other param, and only a boolean reaches LOCAL STDIO via `BuildCLIArgs`, mapping to a new `--clear-parent` bareword flag exactly as `clear_assigned_user` maps to `--clear-assigned-user`. Update-only, same asymmetry as v0.18. A simultaneous `parent` + `clear_parent` — including via `field: ["parent=..."]` or the `plan` alias `extractParentLink` also accepts — is REFUSED on both transports, not silently resolved (codex round 1). Also refused, not silently applied: `clear_parent` against a collection whose schema declares its own `parent`/`plan` field — `extractParentLink` skips hierarchy handling entirely for a schema-shadowed key and lets it fall through as an ordinary field write, so the wire shape `{"parent":""}` can no longer distinguish clear-hierarchy intent from a legitimate blank-a-real-field write once it reaches the server; the ambiguity is created at the client surface that accepted `clear_parent`, so that surface refuses rather than guessing (codex round 2). **v0.18** adds `clear_assigned_user` / `clear_agent_role` booleans to `pad_item` (IDEA-2584) — an ADDITIVE param bump (v0.5/v0.6 precedent); nothing existing changed shape and v0.16/v0.17's empty-string forms still work, undeprecated. v0.16 and v0.17 made the clear WORK; nothing advertised it, because the params that do it were never in the catalog, so an agent reading the schema reached for `assign: ""` (a no-op, and it stays one). Booleans rather than declaring the string params, for two reasons: an empty DECLARED string is inert everywhere else on the tool, so giving one a destructive meaning would let a param-padding client silently unassign everything; and only a boolean can reach LOCAL STDIO, since `BuildCLIArgs` emits the CLI's real flags and a param with no flag behind it is dropped — these map to new `--clear-assigned-user` / `--clear-agent-role` bareword flags, exactly as `allow_draft` maps to `--allow-draft`. Update-only, deliberately asymmetric with create (clearing at create has no honest behaviour but a no-op; a test fails if someone adds them there). Server-side it is wiring, not new semantics: `models.ItemUpdate.ClearAssignedUser`/`ClearAgentRole` already existed with store support since BUG-2566. **v0.17** closes the transport gap v0.16 documented: local stdio MCP shells out to the CLI, which wrote `--field assigned_user_id=` into the item's FIELDS BLOB while the column stayed stale and then printed "Updated TASK-9". `cmd/pad/cmd_item.go` now lifts `columnFieldKeys` onto the columns on create AND update, mirroring `liftFieldsToColumns` and its INVARIANT. Two compat changes, ruled separately: non-empty values move to the column and stop writing the blob key (relying on the old behaviour is relying on a shadowing defect), and empty values clear (falls out of the lift, inherits BUG-2566). Existing stray blob keys are left alone — the fix stops minting new ones. Another behaviour-only bump (BUG-2583). **v0.16** lets an MCP agent UNASSIGN an item over the REMOTE transport (TASK-2571). No tool/action/param shape changed — this is a BEHAVIOR bump on the same grounds as v0.9: an empty-string `assigned_user_id` / `agent_role_id`, passed at the top level or as `field: ["assigned_user_id="]`, was silently dropped by two dispatch-path filters (`mapItemUpdate`, `liftFieldsToColumns`) and is now forwarded as a clear-to-NULL. The store has had defined clear semantics for exactly these two columns since BUG-2566 and HTTP inherited them, so this is uniformity restoration — MCP was the only surface with no way to unassign. Compat posture accepted deliberately: today's `""` senders get a no-op, and a no-op is the surprising reading. The empty-string filter on `tags` at the same call site STAYS (codex #547 r3 P2) — `tags: ""` is a corrupt JSONB/TEXT write, not a clear; same-looking guard, opposite justification. `clear_assigned_user` / `clear_agent_role` schema flags (option (b)) deliberately skipped as additive sugar, though codex review reopened the case — the catalog exposes `assign` / `role`, NOT the ID params, so an agent reading the schema still can't discover the clear (IDEA-2584); an empty `assign` is deliberately left inert because every other schema-declared string on that mapper treats empty as not-provided. **Transport scope:** v0.16 fixed the REMOTE /mcp transport only; v0.17 (BUG-2583) closed the local-stdio half at the CLI. **v0.15** adds the `unparented` boolean to `pad_item.list`, mutually exclusive with `parent`, for structural loose-item filtering (TASK-2096). **v0.14** added a `history` action to `pad_item` (read-only item version history — newest-first metadata; content body omitted for token thrift) and an `expected_updated_at` param for optimistic concurrency on `update` (round-trip the `updated_at` you last read; a stale value fails with a structured 409 `code=update_conflict`). The `update` action's field writes are now a server-side field-level MERGE (only the keys you set change) rather than a full-blob replace, closing the concurrent-update lost-write race (IDEA-1480 / TASK-2022) — pure addition to the action enum + param vocabulary; existing `pad_item` actions/params are unchanged and backwards-compatible. **v0.13** adds `ready` + `stale` actions to `pad_project`, mirroring the existing CLI `pad project ready` / `pad project stale` (TASK-2019): `ready` (read-only) returns the actionable backlog — the query-oriented counterpart to `next`, reusing the dashboard's suggested-next logic; `stale` (read-only) lists items needing attention (stalled, blocked, overdue, or out of the active workflow). Both HTTP dispatchers already existed (`dispatch_http_project.go`); this just wires them onto the catalog. `pad project reconcile` stays CLI-only (shells out to `gh` for live PR state — a local-git dependency MCP agents lack). Pure addition of two read-only actions — existing actions unchanged; backwards-compatible for v0.12 consumers that don't enumerate the new actions. **v0.12** adds an `activity` action to `pad_project`, mirroring the new CLI `pad project activity [--limit N] [--actor user|agent] [--since DATE]` (TASK-2018) — the non-streaming, bounded query counterpart to the CLI-only `pad project watch` SSE stream. Read-only snapshot of the workspace's enriched activity feed (item refs, titles, field-level change details) backed by the existing `GET /workspaces/{ws}/activity` endpoint (previously web-UI-only, now extended with a server-side `since` date filter so `limit`/`actor`/`since` behave identically across CLI, stdio MCP, and cloud HTTP), so agents can catch up on what other agents/users did since they last worked. Adds `actor` + `limit` params to the `pad_project` vocabulary (`since` already existed for changelog); pure addition — existing actions unchanged; backwards-compatible for v0.11 consumers that don't enumerate the new action. **v0.11** adds the read-only `pad_attachment` tool (the tenth resource × action tool) with `list` + `show` actions, mirroring the CLI `pad attachment list` / `pad attachment show` (TASK-2017): `list` enumerates a workspace's attachments (optional filters: item / category / collection / attached / unattached / sort / limit / offset); `show` returns one attachment's metadata (MIME, size, filename, ETag, last-modified) via a HEAD request without transferring bytes. Both HTTP dispatchers already existed (`dispatch_http_attachments.go`); this just wires them onto the catalog. Upload / download / view stay CLI-only (filesystem-bound, excluded per the catalog's exclusion rules). Pure addition — existing tools/actions unchanged; backwards-compatible for v0.10 consumers that don't enumerate the new tool. The base64 image RESOURCE for multimodal agents (`pad://workspace/{ws}/attachments/{id}`) shipped later in TASK-2077 (PR #930) as a bounded, image-only resource; TASK-2101 brought it — and the full read-only resource set — to the remote /mcp transport via the in-process `HTTPResourceFetcher`, so resources are no longer local-stdio-only. **v0.10** enforces the draft-playbook gate server-side: `pad_playbook.run` (and the underlying `POST /playbooks/{ref}/run`) now refuses a playbook whose `status` isn't `active` with a structured `playbook_not_active` error, adds an `allow_draft` boolean param (bareword `--allow-draft` on the CLI) as the escape hatch, and echoes the playbook `status` on both the `run` and `get` responses (BUG-2020). **v0.9** makes `pad_item.list` summary-shaped by default (drops item `content`, adds a default result limit of 50 / hard max 300 on MCP; CLI `--full` restores the complete shape) — a behavior change to the tool's return shape, hence the bump, though tool names, action enums, and parameter shapes are unchanged (TASK-2000). **v0.8** adds `restore` + `deleted` actions to `pad_workspace`, mirroring the CLI `pad workspace restore` / `pad workspace deleted` (TASK-1972): `deleted` (read-only) lists the caller's soft-deleted workspaces still inside the 30-day restore window; `restore` (mutating, not destructive, owner-only) un-soft-deletes a workspace by `slug` while it's still restorable. Both reuse the existing `slug` param — no new params; pure addition. **v0.7** adds `export` + `import` actions to `pad_item`, mirroring the CLI `pad item export` / `pad item import` (covers playbooks AND conventions). `export` (read-only) takes `ref` and returns the portable artifact text — it forces the CLI's stdout sink (`-o -`) so the bytes come back as the result instead of a file. `import` (mutating, not destructive) takes a new `artifact` param (the full artifact text) and returns `{ref, slug, warnings}`; the ExecDispatcher can't pipe stdin, so it spills the artifact to a temp file and dispatches `item import `. v0.6 added the `pad_item.backlinks` action; v0.5 added `pad_library`. v0.3 (PLAN-1377 / TASK-1380) introduced `pad_meta.action: bootstrap`, `pad_set_workspace`'s embedded-bootstrap response, and the `pad://workspace/{ws}/bootstrap` resource. **v0.4 (PLAN-1410)** is a comprehensive bootstrap-payload trim — same tool catalog, slimmer JSON shape inside bootstrap responses: `BootstrapCollection` projection drops `id`/`workspace_id`/timestamps/`settings` and emits `schema` as a nested object; `BootstrapRole` projection drops UUIDs/timestamps/`tools`; convention `slug` dropped; top-level `recent_activity` (a duplicate of `dashboard.recent_activity`) removed; new `BootstrapDashboard` wrapper caps five sub-arrays (`attention`, `recent_activity`, `active_items`, `active_plans`, `by_role`) at 5 entries each with parallel `*_overflow_count` fields; redundant schema labels omitted when `label == TitleCase(key)`. Cumulative size reduction: ~40% on a representative workspace, ~54% on the fixture (see PLAN-1410's Result section for per-section deltas). Compatibility: most changes are subtractive (dropped fields) or additive (overflow counts), but **one type change is breaking**: `collections[].schema` went from a JSON-encoded string to a nested JSON object — clients that JSON.parse()'d the string need to consume it directly as an object now. The dropped fields (UUIDs, timestamps, settings, duplicate `recent_activity`, convention `slug`) have canonical alternatives (slugs for addressing; `pad collection list` / `pad role list` for the full models when needed). +- `ToolSurfaceVersion` (the constant in `internal/mcp/version.go` is the current value; this list is its changelog, newest first) — the MCP tool catalog contract. Bump when tool names, action enums, or parameter shapes change incompatibly. **v0.100** (BUG-3864) makes a refused call name its cause on BOTH transports: `permission_denied` gains `details.reason` (`role`, `token_scope`, `no_access`, `workspace_not_authorized`) when the server names the gate, with a hint per reason saying what to do next (a read-only API token is told to create a "Read and write" one). With no reason, the hint leads with the server's message and claims no cause; it used to say "Insufficient role" for every 403. An unverified Cloud email is the new code `email_not_verified`, the server's own, where remote said `permission_denied`. Stdio gets both from a structured marker the CLI root writes for a 403 coded `forbidden`, `permission_denied` or `email_not_verified`; before it, the token-scope and unverified-email refusals said `server_error` there. BEHAVIOR bump on the v0.45 grounds; no name, enum or param shape changed. **v0.99** (BUG-3790) bounds `pad_item` `starred` the same way: at most 300 items, most recently starred first, with `has_more: true` and the truncation note when more exist. It never pages. Both transports ask for one row past the cap (remote `GET /starred?limit=301`, stdio `pad item starred --limit 301`, a new CLI flag; without `--limit` the CLI walks every page). Starred used to return everything. Additive, on the v0.53 grounds. **v0.98** (BUG-3704) makes `pad_item` `list` say when it is truncated: it asks for one row past its limit and, when that row comes back, returns `limit` rows with `has_more: true` on the structured result and a second text block telling the agent to narrow the filters or raise `limit` (max 300). It never pages for the agent. A list that fits is unchanged. Additive, on the v0.53 grounds. **v0.97** (TASK-3613) adds an optional `worker_id` to `pad_item` (`claim`, `release`) and `pad_project` (`next`, `ready`): a lease is now held under a worker id plus the account, the holder label is display only, a claim answers with the caller's `worker_id`, and passing it back resumes the lease from another connection (see **Leases** above). `lease_held` details gain `worker` (the short id). The remote default holder label is the bare client name. ADDITIVE bump on the v0.53 grounds. **v0.96** (PLAN-3598 slice (c)) adds `pad_item.action=context` (`ref`; optional `intent`, `role`, `budget`), read-only, which returns one brief for working an item: the body of `GET /items/{ref}/context`, with the item and its seq, its parent chain with parsed acceptance criteria, the conventions whose trigger matches the intent (plus the always-on ones), matching playbooks, deps, decisions, links, conflicts, and what was omitted for size. New codes are `unknown_intent` (400, with `details.valid_intents`) and `unknown_role` (400). Both transports (`pad item context [--intent] [--role] [--budget]`). ADDITIVE bump on the v0.53 grounds. **v0.95** (TASK-3611) adds `pad_item.action=link-pr` (`ref`, `pr_number`, `pr_url`; optional `pr_title`, `pr_state`, `pr_branch`, `pr_repo`), which links a pull request from metadata the agent supplies, fetching nothing from GitHub, through the typed `github_pr` member; and `action=unlink-pr` (`ref`), which removes the link and refuses an item with none, as `pad github unlink` does. Both transports (`pad github link --pr-number N --pr-url U ...`, new flags). ADDITIVE bump on the v0.53 grounds. **v0.94** (TASK-3611) adds `pad_item.action=reminders` (`ref`), which lists an item's reminders with their ids (armed, fired, acknowledged), and `action=unremind` (`reminder_id`), which disarms one, on both transports. Listing is read-only; disarming needs edit permission on the item, as on the CLI. Re-arm stays CLI-only (`pad item remind --rearm`). ADDITIVE bump on the v0.53 grounds. **v0.93** (TASK-3611) makes `pad_item.action=create` and `update` over the local stdio transport WRITE a `fields` value that is an object or array, which they used to refuse (BUG-2850): the stdio door passes those keys, and every other non-string value (numbers and booleans, which `--field key=value` delivered as text unless the schema typed them), to the CLI as one `--fields-json` object (a new additive flag on `pad item create` / `update`), keeping their JSON types, as the remote door sends them. Any other action still refuses one. ADDITIVE bump on the v0.53 grounds. **v0.92** (TASK-3585) adds `op_key` to `pad_item.action=comment`, `note` and `decide`: retrying the same request with the same key answers the comment or entry the first attempt made instead of appending again, recorded in the write's own transaction. On the item-update route a key is accepted only with an append (and `source`); any other member alongside it is refused 400. `idempotency_target_gone` (410: the item or comment the key wrote has since been deleted) is now a structured code on both transports, with its own hint; at 0.91 it reached MCP as a generic error. No name, enum or param moved. ADDITIVE bump on the v0.53 grounds. **v0.91** (TASK-3585) adds `op_key` to `pad_item.action=create`: retrying the same create with the same key answers the item the first attempt created (as it stands now) instead of creating a second one; the answer is recorded in the create's own transaction. A key reused for a different create is refused `idempotency_key_reused`; one still in flight answers `idempotency_in_flight` (both codes already existed, and are structured on both transports for any route). A replay whose item has since been deleted answers HTTP 410 `idempotency_target_gone`, which at 0.91 reached MCP as a generic error. No name, enum or param moved. ADDITIVE bump on the v0.53 grounds. **v0.90** (TASK-3585) adds `pad_item.action=patch` `op_key`, an idempotency key: the same request retried with the same key returns its first answer instead of applying again; new codes `idempotency_key_reused` (422), `idempotency_in_flight` (409) and `patch_outcome_unknown` (409, with `seq` and the diff since). ADDITIVE bump on the v0.53 grounds. **v0.89** (PLAN-3578 step 3) adds `pad_item.action=patch` `undo` (a `patch_id`), which inverts that patch, anchored on the text around each edit as it landed, refusing when that text has changed since, and the code `patch_not_found` (404). ADDITIVE bump on the v0.53 grounds. **v0.88** (PLAN-3578 step 2) makes `pad_item.action=patch` on an item open in a browser editor APPLY (the editor applies it as a narrowed replace of its live document; the answer adds `content_state: "applied_pending_flush"`) where it was refused `patch_room_open`, and adds the code `patch_unstable_roundtrip`. `patch_room_open` now means only an older editor holds the item. BEHAVIOR bump on the v0.84 grounds. **v0.87** (PLAN-3578 step 1) adds `pad_item.action=patch {ref, edits:[{old, new, line_hint?}], expected_seq?}`: exact-text edits to the body (each `old` occurs exactly once, applied in order, all or nothing) answered with `{seq, patch_id, version_id, rebased, intervening?, diff}`. A moved `expected_seq` is applied over and reported, never refused. Refusals write nothing: `patch_anchor_missing`, `patch_anchor_ambiguous` (`details.lines`), `patch_room_open`. `get` gains `lines` for numbered body lines with `seq`. ADDITIVE bump on the v0.38 grounds. **v0.86** (PLAN-3555 phase 1) adds `pad_item.action=update` `replace` (bool): the deliberate overwrite of content with no version token, refused with `expected_seq` / `expected_updated_at` or without `content`. A content write with neither carries `warnings.unguarded_content_write: true`, and a later release refuses it. A seq `update_conflict` on a content write gains `details.content_write`, `changed_at` and `changed_by_kind`, a message naming both seqs that says not to resend the body, and the same "re-read and merge, do not resend" hint on both transports. ADDITIVE bump on the v0.53 grounds. **v0.85** (BUG-3544) makes `pad_workspace.action=invite` on an instance with no account yet (the setup window, reachable over local stdio) answer 409 `setup_required` ("This Pad instance must be initialized with pad auth setup") and write nothing, where it answered 500 (`server_error`) from the invitation's inviter foreign key. BEHAVIOR bump on the v0.58 / v0.45 grounds. **v0.84** (BUG-3542) makes a `pad_item` content update answer 409 `content_not_applied` with `details.apply_reason: "unconfirmed_edits"` when a browser tab holding the item open still has typing the server has not stored; token or not, other fields land and the content does not. Wait, re-read and resend; `overwrite_pending_edits: true` is the only override. BEHAVIOR bump on the v0.39 / v0.43 grounds. **v0.83** (TASK-3539) makes `pad_collection` create and update REFUSE a `schema` in which a field has no key, two fields share a key, or a select field lists an empty option or the same option twice, with 400 `validation_error` naming it (`field key "status" is defined more than once`). BEHAVIOR bump on the v0.43 / v0.48 grounds: a write door refuses a call it used to accept. Write-only: a schema already stored with a repeat still reads, and an update that sends no schema still applies. **v0.82** (PLAN-3535 PR 2) makes the items of a REFERENCE collection (`tracks_work: false`) stop counting as open work on every agent surface: `pad_project` next / ready / stale / standup / changelog, the dashboard and bootstrap dashboard, item progress, the `open_children` close guard and the attention decision set leave them out, and a report with no `collections` leaves the collection out as it already did a system one. Sidebar counts, item lists, search and links are unchanged; a collection without the key counts as work. BEHAVIOR bump on the v0.49 grounds. **v0.81** (PLAN-3535 PR 1) adds a `tracks_work` boolean to `pad_collection` create and update: false makes the collection REFERENCE material whose items stop counting toward parent progress, close blocking, Insights and open-work counts (applied by the follow-up PRs). On update it sets that one settings key server-side and leaves the rest alone; omitted, create picks work iff the done field can finish and update leaves it unchanged. ADDITIVE. **v0.80** (BUG-3533) makes `pad_item.action=import` work over remote `/mcp`: it answered `validation_failed` "artifact is required" on every call, because the catalog action dropped `artifact` from the input the HTTP dispatcher reads. Stdio is unchanged. ADDITIVE bump. **v0.79** (TASK-2863) lets a read-only grant (`read` / `pad:read`) run a playbook: `pad_playbook.action=run` stores nothing, and was refused only because it is a POST. It is the one POST a read grant may make (an exact-path allowlist); `match` and every write stay refused. BEHAVIOR bump, additive in effect. **v0.78** (TASK-2308) answers a remote `/mcp` WRITE action from an OAuth connection that can only read (`pad:read`), in a `tools/call` request of up to 1 MiB, with HTTP 403 and a `WWW-Authenticate` `error="insufficient_scope"` challenge naming `scope="pad:read pad:write"` and the metadata document, before dispatch, where it got a `permission_denied` tool result; that challenge is what lets a client re-authorize with the wider grant. Every such call was already refused, so nothing that worked is refused now. A read-scoped PAT keeps the tool error (it cannot re-authorize), as does a larger request, and the ChatGPT mount keeps its own challenge. The 401 challenge also names `scope`. BEHAVIOR bump. **v0.77** (BUG-2772) records a remote `/mcp` write as an AGENT write named by the client's declared MCP `clientInfo.name`, where it was recorded as the human, and gives a remote call a per-connection default lease holder (`claude-code#3f9a12c4`); see "Remote caller identity" below. A claim on an item another holder leases now answers `lease_held` with `details.holder` and `details.expires_at` on both transports, where remote said `conflict` and stdio `server_error` (BUG-3496). BEHAVIOR bump. **v0.76** (TASK-1809) makes a `pad_item` `claim` / `release` with no `holder` hold the lease under the caller's agent name (the `X-Pad-Agent` the CLI sends), else the account's email, where it was the email alone: several agents on one account silently shared one lease, a second claim answering 200 by refreshing the first. It now answers 409 `lease_held` naming the first agent. `pad_project.action=next` / `ready` leave out items whose live lease a claim by the caller would lose (same identity, the claim's own predicate, filtered before the cap of three; reminders are not filtered). Remote /mcp sends no agent name, so its default is still the email (TASK-3495). A lease taken before the upgrade is another holder's to the same agent for up to its TTL. BEHAVIOR bump on the v0.70 grounds. **v0.75** (BUG-3480) makes `pad_item.action=list` on both transports refuse a filter key no schema in scope declares and no item in scope stores (400 `validation_failed`, "invalid list filter ..."), where it answered an empty list, and refuse a key that is not a field key, which the store used to drop (answering the unfiltered list). BEHAVIOR bump on the v0.43 / v0.29 grounds; see the item list endpoint bullet under API. **v0.74** (TASK-2188) makes `pad_collection.action=update` answer, on both transports, with an `omitempty` `warnings.orphaned` [{field, option?, items}] naming each field, or select option, its schema removed that live items still hold. Nothing is refused. ADDITIVE, the v0.67 grounds; 0.73 is BUG-3480's. **v0.72** (TASK-2189) adds `pad_collection` `list-archived` (read-only) and `restore` (owner-only, by slug or id), backed by the new `GET /workspaces/{ws}/archived-collections` and `POST /workspaces/{ws}/archived-collections/{ref}/restore`: an agent's archive is recoverable by an agent. ADDITIVE. **v0.71** (TASK-3462 U3a) adds an `omitempty` `builtin_updates` count to the bootstrap on every door that returns it (the conventions and playbooks Pad ships whose library text changed since the workspace's copy, among the items the caller sees in full), and a server-instructions section telling the agent to mention it once and never apply an update itself. ADDITIVE. **v0.70** (BUG-3453) makes `pad_project.action=next` / `ready` fill any slot the existing tiers leave empty with ordinary open items from non-system collections that declare `priority` or `severity` (an initial status like `new` counts), ranked below every item admitted before, so a full list is unchanged and a moved-in backlog with no priorities is no longer "nothing ready". BEHAVIOR bump on the v0.49 grounds. **v0.69** (TASK-2314) makes every REMOTE route that needs a workspace and lacks one answer `no_workspace` with `available_workspaces` and a hint, as stdio always did, where it answered `validation_failed` "workspace is required"; the single-workspace default now runs before the `assign` / `role` resolvers. BEHAVIOR bump on the v0.42 / v0.45 grounds. **v0.68** (BUG-3448) makes the item resource render a structured field as compact JSON instead of Go's map syntax, keep a number above 2^53 to its digits and render a JSON null as `null`; the agent projection stops rounding large numbers. BEHAVIOR bump on the v0.62 / v0.64 grounds: an output shape changed, no name, enum or param moved; scalar fields render as before. **v0.67** (BUG-3446) lets a create in a system conventions or playbooks collection ADD a trigger/scope word the library itself uses to the select options instead of refusing it, so `pad_library.activate` and B3's literal create succeed in a `blank` workspace, and adds an `omitempty` `warnings.options_added` to the create result on both transports. A word the library does not use is refused as before. ADDITIVE. **v0.66** (BUG-2136) makes `pad_workspace.action=invite` always create a pending invitation, never add an existing account directly; see `internal/mcp/version.go`. **v0.65** (TASK-3413, SPEC-6 U9c) adds `omitempty` `via_app` and `via_app_name` to items an installed app CREATED (items.created_via_app, never the last app writer), comments an app wrote and version rows an app's write made, on both transports (`pad_item` get, list summary and full, comments, history summary and full). The name is the app's bot display name, else its origin, and survives uninstall. ADDITIVE. **v0.64** (BUG-3379) adds an `omitempty` `imported: true` to comments, attachment rows and version rows a workspace import wrote, on both transports (`pad_item` comments, `pad_attachment.list`, and `pad_item.history` with `full: true`; history summary rows and attachment `show` do not carry it): import keeps the export's author strings and uploader ids verbatim, and the flag says they were not verified here. ADDITIVE. **v0.63** (TASK-3321) adds an `omitempty` `actor_name` to every `pad_item.action=history` summary row on both transports, the display name of who made the change, where rows said only `user` or `agent`. ADDITIVE. **v0.62** (BUG-3326) makes remote /mcp `pad_set_workspace` embed the workspace bootstrap, as stdio always did: the in-process bootstrap resource read, run as the token's user under the same scope/consent perimeter, so a workspace the caller cannot read embeds nothing. ADDITIVE; no name, enum or param changed, and stdio is unchanged. **v0.61** (TASK-3321 U0b) marks `pad_workspace` destructiveHint:true and openWorldHint:true, because `invite` sends an email to an arbitrary address, and `pad_playbook` openWorldHint:true, because `match` sends text to the decision provider. Annotation-only BEHAVIOR bump on the v0.20 grounds; every other tool's block is unchanged. **v0.60** (TASK-2198 U4) makes `content_state: "applied_pending_flush"` clear ON ITS OWN on every door that carries it: after the item's collab room closes (or a one-minute sweep finds it dormant) the server rebuilds the body from the op-log and stores it, moving `seq` (a held `expected_seq` then answers `update_conflict` instead of `content_pending_flush`) and adding a `system` / `recovery` version. BEHAVIOR bump on the v0.59 / v0.39 grounds; no name, enum or param changed. Not a guarantee (failures, set-aside rows, `PAD_MATERIALIZE=off`), so re-read later, never re-send, still stands. **v0.59** (BUG-3252, tombstone ruled over cascade) makes `pad_item.action=delete-comment` on a comment with replies SUCCEED, leaving a tombstone (body emptied, author and timestamps kept, additive `deleted: true`) its replies stay under; it is removed when its last reply is deleted. `edit-comment` on a tombstone answers 409 `comment_deleted` on every transport. BEHAVIOR bump on the v0.58 grounds; `comment_has_replies` stays classified for older servers. **v0.58** (BUG-3252) makes `pad_item.action=delete-comment` on a comment that still has replies answer 409 `comment_has_replies` (details `comment_id`, `reply_count`) on every transport instead of `server_error`: `comments.parent_id` has no ON DELETE, so the delete failed the FK inside the store. Nothing is deleted either way. Tombstone was then ruled over cascade; v0.59 replaced this refusal with it. BEHAVIOR bump on the v0.45 grounds. **v0.57** (TASK-2695) adds `pad_item` `edit-comment` (ref, comment_id, message) and `delete-comment` (ref, comment_id) on all three transports, backed by the item-scoped routes `PATCH/DELETE /workspaces/{ws}/items/{ref}/comments/{id}`, which answer 404 unless the comment is on `ref` and otherwise run the workspace routes' handlers (edit author-only, delete item-edit). CLI: `pad item comment-edit` / `comment-delete`, refused against a server without the `item_scoped_comment_writes` capability. Every serialised comment gains a derived `edited` bool (updated_at > created_at), and `pad item comments` prints each comment's id. ADDITIVE. **v0.56** (BUG-3244) gives `content_state` a second value, `superseded_set_aside`, on every MCP door that carries it (`pad_item` get / full list, `pad_playbook` run, the item resource's line above the body): edits an editor schema-version rebuild set aside, which opening the item will NOT restore, so the resource line and the `content_pending_flush` hint (chosen by `details.set_aside_rows`) name `pad item set-aside` and `overwrite_pending_edits` instead. ADDITIVE bump: no name, enum or param changed, but an agent branching on the one-word vocabulary meets a word whose remedy differs. Reading or discarding the rows alone is not on the catalog. **v0.55** (BUG-2659) sends `pad_item.action=search`'s `collection` to /search as typed, and /search resolves it exact-first per workspace in scope (the item routes' resolver). In a workspace holding both `task` and `tasks`, `collection: "task"` now answers from `task` instead of `tasks`; every other workspace is unchanged, because the shorthand still resolves server-side. Stdio reaches it through the CLI, which sends the name as typed only to a server advertising `search_collection_resolution`. BEHAVIOR bump on the v0.36 / v0.40 grounds. **v0.54** (BUG-3217) keeps a `fields` number's literal through MCP on both transports (mcp-go's argument decode rounded anything above 2^53, and stdio's `--field` stringify carried the rounded value), and REFUSES a `fields` number beside a `field` entry for the same key when they differ as exact numbers — two values that differ only above 2^53 used to collapse into one rounded write; a matching pair (3.0 beside n=3) still collapses. BEHAVIOR bump on the v0.48 grounds. **v0.53** (BUG-2819) adds `filename_source` (caller / normalised / substituted / derived / unknown) to every `pad_attachment.action=list` row on both transports, because a stored filename cannot say whether the caller sent it or the server substituted it. ADDITIVE, the v0.28 / v0.13 disposition; `show` does not carry it, and `mcp_audit_log.tool_name_source` reaches no catalog action. Rows written before it read `unknown`, never `caller`. **v0.52** (BUG-2367 item 4) refuses a move or copy (every migrate door) that would change an item between open, done and abandoned unless the caller names the destination done field. Only the STATE is compared, so two values that both mean done carry. Move answers 400 `state_change_requires_value` with details `{field, options, from, to}`; bulk move puts it in a `failed[]` row; the copy answers 400 `validation_error` with the same sentence; the preflight emits a needs_value row with reason `state_change`, which the web dialog picker renders. A destination with no done select field is exempt. BEHAVIOR bump. **v0.51** (BUG-2367) stops every migrate door (single move, bulk move, cross-workspace copy and its preflight) carrying a value into a field the destination marks `computed` (preflight drop reason `target_computed`) or a value that collides on a destination `unique_scope` field. Provenance decides, the TASK-2878 rule: a CARRIED collision is dropped and reported (`not_unique`), a supplied override or injected default that collides is refused 409 `conflict`, and a required field emptied by the drop is refused as required, which is the existing needs_value route. Before it, single move answered 500 on the indexed `invocation_slug`, bulk move leaked the SQL error, and an unindexed unique field stored a duplicate. Reporting is additive and omitempty: `warnings.not_unique` [{key, value, holder?, message}] on the move response, bulk `updated[]` rows and the copy response, and a `detail` sentence on the preflight's dropped row. `holder` is present only when the caller may see that item, so the drop is not an existence oracle. BEHAVIOR bump on the v0.43 / v0.29 grounds. **v0.50** (BUG-3014) adds an ADDITIVE `omitempty` `stored_as_text: true` to a `relation_targets` entry whose stored value is not UUID-shaped (a title a bundle import carried verbatim, or legacy free text). Such a value was never an id and used to hydrate as a plain id-only entry, which reads as "gone or hidden"; an id-only entry without the flag keeps that meaning, and a UUID-shaped value, resolved or not, is byte-identical to v0.49. The predicate is syntactic, decided from the stored bytes and never from a lookup, so it discloses nothing, and deliberately not coupled to the resolver ladder. The CLI prints `"" (text, not a reference)` and the web chip says the same. **v0.49** (BUG-2410) makes `pad_project.action=report` with no `collections` param leave out SYSTEM collections (`Collection.IsSystem`: Conventions and Playbooks), which were counted in Insights' created, WIP and status totals; naming one explicitly still includes it. BEHAVIOR bump on the v0.40 / v0.42 grounds: a default call's content changed for every caller (web Insights, print, `pad project report`, both MCP transports, all through the one store rule). **v0.48** (BUG-3163) makes `pad_item.action=create` REFUSE a `field` / `fields` entry naming any reserved metadata key (`implementation_notes`, `decision_log`, `github_pr`, `convention`) on every transport, with 400 `validation_error`, creating nothing: create was the last door that stored one, as a string no extractor reads. Library activation, its one system writer, moves to an additive typed `convention` create member (not on the catalog; `pad_library.activate` is unchanged), and the CLI verifies from the stored fields that it landed, because an older server ignores the member and answers 201. BEHAVIOR bump on the v0.47 grounds. **v0.47** (BUG-2696) makes `pad_item.action=update` REFUSE a field setter naming `github_pr` on every transport (400 `validation_error` naming `pad github link` / `unlink`), closing the exemption v0.23 left: that door stored the PR as an unreadable string, so no link ever rendered. The writer is a new additive, typed update member (`github_pr` object + `clear_github_pr`) used by `pad github link` / `unlink` / `project reconcile`, deliberately NOT on the catalog (a remote PR-link action waits on the catalog-trim decision). BEHAVIOR bump; item create is BUG-3163. **v0.46** (BUG-3156) makes `pad_item.action=bulk-update` over stdio and remote REFUSE, per item, a status or priority change on an item whose collection does not declare that field, writing nothing for that item: the answer WebMCP has given since v0.44, so the three transports agree. Rows keep each transport's shape (stdio `failed[]` with `validation_error`, remote `results[]` with `validation_failed` and the server message in `hint`). The mechanism is the update door's new `refuse_undeclared_fields` member, which both bulk-update transports set; `pad_item.update` does not, and still accepts-and-warns. A server that predates the member ignores it, which is the old accept-and-warn. BEHAVIOR bump on the v0.44 / v0.43 grounds. **v0.45** (BUG-2829) reports an HTTP 413 as `too_large` on BOTH transports, with the server's own code in `details.reason`, where it used to be `server_error`: three deliberate caps are reachable from the catalog (a title rename's link cascade, an oversized outbox event, an oversized artifact import), and the old code read as transient and invited a retry that fails identically. Remote maps 413 in `classifyHTTPStatusKind`; stdio gets it from a structured marker the CLI root writes for any 413, and `too_large` joins `allowedStructuredErrorCodes`, which a test now proves contains every code any CLI marker writer emits. BEHAVIOR bump on the v0.42 grounds; no name, enum or param shape changed. **v0.44** (BUG-3154) makes `pad_item.action=bulk-update` over the WebMCP browser transport REFUSE, per item, a status or priority change on an item whose collection does not declare that field: the item lands in the bulk response's `failed` array with `validation_error` naming the collection and field, nothing is written, and the rest of the call applies. The door is `POST /items/bulk` (`set-priority`, and `move` with a `status`, with or without a `collection`, where the target's schema decides), where the request carries an operation and a value and the SERVER chooses the key; it used to store an orphan field and report the item updated. BEHAVIOR bump on the v0.43 / v0.40 grounds. The transports disagreed after it, stated rather than implied: stdio and remote issued a per-item PATCH, the single-item update door, which ACCEPTED the key with `warnings.undeclared_fields` (v0.27), until v0.46 converged them. **v0.43** (BUG-2379) makes `pad_item.action=move` REFUSE a field override naming a field the destination schema does not declare, with 400 `malformed_override` — the same check, code and message the cross-workspace copy already used. BEHAVIOR bump on the v0.40 / v0.29 grounds: a write door refuses a call it used to accept, where it used to store the key as an orphan field no schema renders. Create and update still ACCEPT undeclared keys with `warnings.undeclared_fields` (v0.27), because callers round-trip the whole fields blob; an override is a fresh assertion about the destination schema, not round-tripped state. **v0.42** (BUG-3142 + BUG-3147) changes the error CODE a LOCAL STDIO caller receives for two failure families that used to arrive as retryable `server_error`: an argv refusal (cobra/pflag: unknown flag, arg count, …) is now `validation_failed` with its message kept, and a 429 on any command is now `rate_limited` with `details.retry_after_seconds`, via the structured marker line the CLI writes at its root. It also stops the refusal that caused most of the first family: `BuildCLIArgs` now emits flags first and the positionals behind `--`, so free text starting with `-` (`item search "-ship it"`) is no longer parsed as a flag. BEHAVIOR bump; no name, enum or param shape changed, and the remote transport is untouched. **v0.41** (PLAN-3114 U5 / TASK-3120) adds a `match` action to `pad_playbook`: given free `text`, a Choice question over the workspace's ACTIVE playbooks plus a reserved `"none"` option returns the best match's ref (or `"none"`), confidence, per-option probabilities and the model. No provider configured → 404 `decision_provider_unavailable`; a provider error or an out-of-set answer → 502 `decision_provider_error`. Pure ADDITIVE bump (new action + param, nothing existing moved), read-only and side-effect-free. **v0.40** (BUG-3028) gives a scalar `relation` ONE stored form for "no target", the key ABSENT, converging on multi_relation's rule. A blank (`""` or whitespace) a write SETS — create, `fields_patch`, a changed value in full `fields`, a move/copy override — is normalised to absent before validation, so a `required` relation is refused as required (a patch blanking it now gets the answer deleting it always got). A legacy blank a write only CARRIES — an untouched key under `fields_patch` (normalised by the store under its write lock, via `ItemUpdate.BlankRelationKeys`), an unchanged value in full `fields`, move, copy, artifact import — is normalised after validation and never refused. An empty list filter on a scalar relation key of a collection-scoped list (`owner=`) matches all three spellings. BEHAVIOR bump; no shape change. Workspace import (`store.ImportWorkspace`) still stores blobs verbatim; its legacy blanks normalise on the next write. **v0.39** (BUG-3133) refuses `pad_item.update` that sets content WITH a version token (`expected_seq` / `expected_updated_at`) while the item's op-log holds content-bearing rows above its flush watermark, with 409 `content_pending_flush` (details `ref`, `pending_rows`). BEHAVIOR bump on the v0.35 / v0.36 grounds, carrying one additive param: `overwrite_pending_edits` lifts it, on the API, the CLI (`--overwrite-pending-edits`; `pad item edit --force` sets it on the save) and MCP alike, because an agent must be able to clear the refusal without a browser. The token guards the ROW and a tab's unflushed typing is not in it, so the write used to replace those edits — through the applier's setContent with a tab open, and by the direct path's op-log prune, which DELETES them, with none. Its own code rather than `update_conflict` because re-reading returns the same row and seq. A write without a token, without content, or to an item with nothing pending is unchanged, except that a direct write now reports `warnings.pruned_pending_edits` (additive, omitempty) when its prune deleted such rows. The check runs in the write's own tx; on the direct path it is under the item lock and appendMu and exact, on the applier path a tab can still type in the one server hop between the check and setContent. (v0.37 and v0.38 — the `agent` projection on `pad_item.get` and `claim` / `release` — are in `internal/mcp/version.go`; this paragraph had stopped at v0.36.) **v0.36** (BUG-3082) stops a REF-SHAPED `relation` value falling back to matching by item NUMBER when its prefix names a collection that is LIVE in the workspace; such a value is now `not_found`. BEHAVIOR bump on the v0.35 / v0.30 / v0.29 / v0.16 grounds — no tool name, action enum or param shape changed, but a write door refuses a value it used to accept. It finishes v0.29: that entry closed free-text corruption ("red" resolving to whatever is slugged `red` today) and left the same corruption open for anything shaped like a REF, which is the spelling the docs tell callers to prefer. Item numbers are workspace-unique and sequential ACROSS collections, so `CONVE-1` and `SECRE-1` are never both real — the fallback dropped the prefix, matched on the number alone, and landed on an item that was usually inside the field's declared collection, so the wrong-collection check above it passed and NOTHING was raised: a caller wrote `CONVE-1`, the item stored a different item's UUID, and the write answered 201 with the substitution visible only in `relation_targets`. The predicate is about the PREFIX rather than the item because a collection RENAME changes its prefix and a relation already written as the old ref must keep resolving (BUG-2873) — that ref's prefix names nothing afterwards, so the fallback still fires for it, while a prefix that IS live and simply holds no item at that number is the caller naming a real collection that does not contain what they said. A SOFT-DELETED collection counts as absent IN THAT PREDICATE, for the same reason a renamed one does — a claim about the fallback only: the exact-prefix lookup ahead of it never filtered on the collection’s own `deleted_at`, so an item whose collection was soft-deleted still matches THERE and never reaches the predicate. That is left alone rather than made consistent, because it cannot retarget — the downstream collection check refuses it. RESIDUAL, stated rather than implied and pinned by a test: a ref pasted from ANOTHER workspace whose prefix also names no collection here still resolves by number, because nothing in the value distinguishes it from a rename's leftover. No escape hatch, for v0.29's reason. Out of scope and unchanged: `GetItemByRef`, the navigational read path, where landing on the moved item is the helpful answer. **v0.35** (BUG-3079) makes an injected schema DEFAULT take the same `validateFieldType` check a caller-supplied value takes; one that fails is DISCARDED and named in `warnings.dropped_fields` instead of being stored. BEHAVIOR bump on the v0.30 / v0.29 / v0.16 grounds — no tool name, action enum or param shape changed, but a write door stores something different from what it stored before. Unlike v0.29, which turned an accepted value into a refusal, this turns a stored value into a reported drop: a create that used to land WITH a bad field still lands, without it. What it closes is two doors disagreeing about one value, decided only by who put it there. It also widens `dropped_fields` from the single relation case v0.29 introduced to a field of ANY type. No escape hatch, for v0.29's reason. ONE exception, which is the rule finishing its sentence rather than a carve-out: dropping leaves a REQUIRED field absent, which is exactly what the required check reports, so such a write is refused — naming the default as the cause, because a bare "field is required" points its reader at a request that never mentioned the field. **v0.34** (BUG-3037) adds an `expected_seq` param to `pad_item.action=update` — the STRONG optimistic-concurrency token, preferred over `expected_updated_at`. ADDITIVE (the v0.13 / v0.11 / v0.8 disposition): nothing existing moved and `expected_updated_at` still works. It is needed rather than nice because `updated_at` is stored at ONE-SECOND resolution, so two writes to a row inside one second both match the token and NEITHER conflicts — the loser is accepted and silently overwrites the winner, both callers seeing success. That is the shape of agent traffic, so the token agents were offered could not refuse the race it exists to refuse. `seq` is bumped on every mutation of the row under the write lock. Raising `updated_at`'s resolution instead was measured and REJECTED: the column is TEXT on both dialects and compared LEXICALLY in SQL (the since-cursor read plus eight `ORDER BY` sites), and Go's `RFC3339Nano` omits trailing zeros, so a sub-second value sorts BEFORE a whole-second value of the same second and the cursor would start skipping rows. The read side is what makes the token reachable: `seq` now serialises without `omitempty` on `models.Item` AND on the item SUMMARY shape (`cli.ItemSummary`), which is what `pad_item.list` returns by default since v0.9 — a token absent from the shape a caller reads is a token that caller cannot send. A value below 1 is a 400, not a 409: the server never issues one, so a 409 would read as contention that never clears. **v0.30** (BUG-2870) is a BEHAVIOR bump on the v0.29/v0.27/v0.26/v0.16/v0.10/v0.9 grounds — no tool name, action enum or param shape changed. **Every door refuses a padded KEY now**, and each was accepting it differently: /mcp trimmed it and wrote the declared field, the CLI stored a ghost field beside it — so both refuse something they used to accept. What is /mcp-only is the VALUE half, which it used to trim and type and now passes through to the same validation the CLI has always applied. A caller writing canonical entries sees no difference at either door. A second, separately-noticeable fix rides with it: `detectFieldConflicts` swallowed `parseFieldArray`'s refusal as "the caller owns this error surface", which held only while the sole possible error was a shape error — `reshapeItemFields` returns early with no `fields` object, so on the no-`fields` path (this bug's own path) four existing refusals were landing as successes. No escape hatch, for v0.29's reason: there is no legitimate call this refuses, only calls whose two readings a door used to choose between silently. **v0.29** (PLAN-2857 U1 / TASK-2878) is a BEHAVIOR bump on the v0.27/v0.26/v0.16/v0.10/v0.9 grounds (NOT v0.28's, which was purely additive) — no tool name, action enum, or param shape changed, but a `relation` field value must now name a live item in the collection that field declares, so every write door refuses values it used to store. Refused: names nothing (`not_found`), names an item in the wrong collection, the field declares no target collection (`target_missing`), or the value is a SLUG — a deliberate divergence from `ResolveItem`'s UUID→ref→slug ladder, since a slug is neither an ID nor stable and free text like "red" resolving to whatever is slugged `red` today is exactly the corruption this closes. Ordinary `validation_error`, no new code and no new details key, because stdio classifies errors by matching CLI stderr prose. A CARRIED value — already on the item, asserted by nobody — is never refused, since refusing would make every legacy item un-updatable, un-movable and un-copyable: within a workspace it resolves and SURVIVES, across a workspace boundary it is dropped without a lookup (a source-workspace id cannot mean anything in the destination) and reported through the same `warnings.dropped_fields` channel BUG-2674 established. No escape hatch, deliberately: unlike v0.10's `allow_draft` there is no legitimate call this refuses, and the case with a real claim to leniency is already exempt by provenance rather than by a flag. **v0.28** (IDEA-2641 / GitHub #1010) adds two ADDITIVE `pad_item` actions and two optional params: `remind` arms a one-shot reminder at an RFC3339 `remind_at` INSTANT, and `ack-reminder` acknowledges a fired one by `reminder_id`. Purely additive — nothing existing moved, and a v0.27 consumer that enumerates neither action is unaffected; same disposition as v0.13 / v0.11 / v0.8, which likewise wired existing CLI verbs onto the catalog. Agents already RECEIVED reminders (the poll surface is `pad_project.next` / `ready`, long exposed); what was missing is the half where an agent that defers work can say when it wants to be asked again. `remind_at` REFUSES a bare date rather than reading it as midnight — the `date` schema type accepts `YYYY-MM-DD` so a caller will try it, but a bare date names a 24-hour span and choosing an hour inside it would fire at a time nobody picked. Re-arm and disarm stay CLI-only: both address a reminder by an id the agent would have to list first, and no listing action exists on this surface yet — a door with no handle. **v0.27** (BUG-2850) types field values SERVER-SIDE at all eight validate sites, carries the `fields` object to the remote door with its JSON types intact, accepts undeclared keys while NAMING them in `warnings.undeclared_fields`, and replaces five accreted conflict guards with one canonical pass; the merge refuses several ambiguities it used to resolve silently. (This entry was missing from CLAUDE.md — the 0.27 unit swept `instructions.md` and `README.md` and not this file.) **v0.27** (BUG-2850) types field values server-side at all eight `Validate*` call sites so a declared number/json field is writable from the remote transport at all, carries the `fields` OBJECT with its JSON types intact, names undeclared keys back in `warnings.undeclared_fields` (accepted rather than refused — a census of 1012 items found 14 such keys across 168 live values, so refusing would have broken read-modify-write on items nobody had edited wrongly), and replaces the accreted per-site conflict guards with ONE check over a canonical view of every source; that check refuses ambiguities v0.26 resolved silently, chiefly two names for one target in a single call (`parent`/`plan`, `assign`/`assigned_user_id`, `role`/`agent_role_id`), refused even when the values match because the names address one thing through incomparable vocabularies and the two doors resolved them differently. **v0.26** (IDEA-2756) is a BEHAVIOR bump on the v0.9/v0.16/v0.25 grounds — no tool name, action enum, or param shape changed, but `pad_workspace.create` now refuses a call it used to permit. Closest precedent is v0.10, which likewise turned a server-side gate into a structured refusal; unlike v0.10 there is no `allow_draft`-style override, because the gate encodes a decision the USER made at consent time and a bypass param would be the app overriding its own grant. `POST /workspaces/import` is gated by the same shared helper (import mints a workspace through `store.ImportWorkspace`), though it has no MCP action today. **v0.25** (TASK-2657 / BUG-2702) resolves `pad_library.activate`'s destination collection from the target's declared artifact kind rather than the literal `conventions` / `playbooks` slugs, so activating into a workspace that renamed either collection lands correctly; a lookup ERROR is surfaced rather than silently falling back. **v0.24** (#1066) adds the `fields` OBJECT param to `pad_item` create/update — an alias merging into the same path as `field`/the dedicated params, so the shape reads return is finally a valid write shape; the same key supplied twice with conflicting values is REFUSED (refuse-on-ambiguity, the v0.18/v0.19 disposition), equal duplicates collapse to one write, and non-writer actions refuse a `fields` param loudly. It also makes input validation STRICT for every catalog tool: undeclared top-level keys are rejected with a structured error naming them, instead of being accepted and silently dropped by `BuildCLIArgs` — which is the mechanism that made the `fields` object a session-scoped silent no-op in the first place. Compat carve-out: `pad_item`'s v0.16 `assigned_user_id` / `agent_role_id` remote-transport clear form stays accepted (documented, undeprecated, deliberately never schema-declared). The strict half changes behaviour for inputs that previously "succeeded", but that reliance was indistinguishable from a caller bug (the key never did anything), so the break is the fix; one bump covers both halves. **v0.23** (BUG-2627 part 2 + BUG-2675) refuses system-metadata keys through `fields_patch` on all three doors at once, `github_pr` exempt on update (move/copy still refuse it), and adds the retry-hostile `stored_state_unreadable` code. **v0.22** (BUG-2674) stops `pad_item.action=move` destroying system metadata and refuses `field` setters naming the reserved keys there. **v0.21** bounds `pad_item.action=history` (BUG-2608): the `limit` param now covers it, default 50 / max 300, applied in the CATALOG action so it reaches both transports (HTTP reads the input; stdio gets the CLI's new `--limit` via BuildCLIArgs). The window is the NEWEST N and there is deliberately no `offset` — versions are reverse patches, so only a newest-end window is cheap to reconstruct. Additive param bump; a v0.20 consumer sending no limit now receives the newest 50 rather than every version, which is the fix. Summary mode additionally asks the server to skip patch resolution rather than resolving bodies the dispatcher discards. **v0.19** adds a `clear_parent` boolean to `pad_item` (BUG-2078) — an ADDITIVE param bump, same grounds as v0.18; nothing existing changed shape. The server has supported clearing a parent since BUG-2013 (`extractParentLink` treats a present-but-empty `parent` key in `fields_patch` as detach), but neither client surface could reach it — `--parent ""` was a silent no-op on the CLI and the MCP `parent` param has the same "empty means not provided" convention every other declared string on the tool has. Boolean rather than overloading the empty string, same two reasons as v0.18: keeps that invariant intact for every other param, and only a boolean reaches LOCAL STDIO via `BuildCLIArgs`, mapping to a new `--clear-parent` bareword flag exactly as `clear_assigned_user` maps to `--clear-assigned-user`. Update-only, same asymmetry as v0.18. A simultaneous `parent` + `clear_parent` — including via `field: ["parent=..."]` or the `plan` alias `extractParentLink` also accepts — is REFUSED on both transports, not silently resolved (codex round 1). Also refused, not silently applied: `clear_parent` against a collection whose schema declares its own `parent`/`plan` field — `extractParentLink` skips hierarchy handling entirely for a schema-shadowed key and lets it fall through as an ordinary field write, so the wire shape `{"parent":""}` can no longer distinguish clear-hierarchy intent from a legitimate blank-a-real-field write once it reaches the server; the ambiguity is created at the client surface that accepted `clear_parent`, so that surface refuses rather than guessing (codex round 2). **v0.18** adds `clear_assigned_user` / `clear_agent_role` booleans to `pad_item` (IDEA-2584) — an ADDITIVE param bump (v0.5/v0.6 precedent); nothing existing changed shape and v0.16/v0.17's empty-string forms still work, undeprecated. v0.16 and v0.17 made the clear WORK; nothing advertised it, because the params that do it were never in the catalog, so an agent reading the schema reached for `assign: ""` (a no-op, and it stays one). Booleans rather than declaring the string params, for two reasons: an empty DECLARED string is inert everywhere else on the tool, so giving one a destructive meaning would let a param-padding client silently unassign everything; and only a boolean can reach LOCAL STDIO, since `BuildCLIArgs` emits the CLI's real flags and a param with no flag behind it is dropped — these map to new `--clear-assigned-user` / `--clear-agent-role` bareword flags, exactly as `allow_draft` maps to `--allow-draft`. Update-only, deliberately asymmetric with create (clearing at create has no honest behaviour but a no-op; a test fails if someone adds them there). Server-side it is wiring, not new semantics: `models.ItemUpdate.ClearAssignedUser`/`ClearAgentRole` already existed with store support since BUG-2566. **v0.17** closes the transport gap v0.16 documented: local stdio MCP shells out to the CLI, which wrote `--field assigned_user_id=` into the item's FIELDS BLOB while the column stayed stale and then printed "Updated TASK-9". `cmd/pad/cmd_item.go` now lifts `columnFieldKeys` onto the columns on create AND update, mirroring `liftFieldsToColumns` and its INVARIANT. Two compat changes, ruled separately: non-empty values move to the column and stop writing the blob key (relying on the old behaviour is relying on a shadowing defect), and empty values clear (falls out of the lift, inherits BUG-2566). Existing stray blob keys are left alone — the fix stops minting new ones. Another behaviour-only bump (BUG-2583). **v0.16** lets an MCP agent UNASSIGN an item over the REMOTE transport (TASK-2571). No tool/action/param shape changed — this is a BEHAVIOR bump on the same grounds as v0.9: an empty-string `assigned_user_id` / `agent_role_id`, passed at the top level or as `field: ["assigned_user_id="]`, was silently dropped by two dispatch-path filters (`mapItemUpdate`, `liftFieldsToColumns`) and is now forwarded as a clear-to-NULL. The store has had defined clear semantics for exactly these two columns since BUG-2566 and HTTP inherited them, so this is uniformity restoration — MCP was the only surface with no way to unassign. Compat posture accepted deliberately: today's `""` senders get a no-op, and a no-op is the surprising reading. The empty-string filter on `tags` at the same call site STAYS (codex #547 r3 P2) — `tags: ""` is a corrupt JSONB/TEXT write, not a clear; same-looking guard, opposite justification. `clear_assigned_user` / `clear_agent_role` schema flags (option (b)) deliberately skipped as additive sugar, though codex review reopened the case — the catalog exposes `assign` / `role`, NOT the ID params, so an agent reading the schema still can't discover the clear (IDEA-2584); an empty `assign` is deliberately left inert because every other schema-declared string on that mapper treats empty as not-provided. **Transport scope:** v0.16 fixed the REMOTE /mcp transport only; v0.17 (BUG-2583) closed the local-stdio half at the CLI. **v0.15** adds the `unparented` boolean to `pad_item.list`, mutually exclusive with `parent`, for structural loose-item filtering (TASK-2096). **v0.14** added a `history` action to `pad_item` (read-only item version history — newest-first metadata; content body omitted for token thrift) and an `expected_updated_at` param for optimistic concurrency on `update` (round-trip the `updated_at` you last read; a stale value fails with a structured 409 `code=update_conflict`). The `update` action's field writes are now a server-side field-level MERGE (only the keys you set change) rather than a full-blob replace, closing the concurrent-update lost-write race (IDEA-1480 / TASK-2022) — pure addition to the action enum + param vocabulary; existing `pad_item` actions/params are unchanged and backwards-compatible. **v0.13** adds `ready` + `stale` actions to `pad_project`, mirroring the existing CLI `pad project ready` / `pad project stale` (TASK-2019): `ready` (read-only) returns the actionable backlog — the query-oriented counterpart to `next`, reusing the dashboard's suggested-next logic; `stale` (read-only) lists items needing attention (stalled, blocked, overdue, or out of the active workflow). Both HTTP dispatchers already existed (`dispatch_http_project.go`); this just wires them onto the catalog. `pad project reconcile` stays CLI-only (shells out to `gh` for live PR state — a local-git dependency MCP agents lack). Pure addition of two read-only actions — existing actions unchanged; backwards-compatible for v0.12 consumers that don't enumerate the new actions. **v0.12** adds an `activity` action to `pad_project`, mirroring the new CLI `pad project activity [--limit N] [--actor user|agent] [--since DATE]` (TASK-2018) — the non-streaming, bounded query counterpart to the CLI-only `pad project watch` SSE stream. Read-only snapshot of the workspace's enriched activity feed (item refs, titles, field-level change details) backed by the existing `GET /workspaces/{ws}/activity` endpoint (previously web-UI-only, now extended with a server-side `since` date filter so `limit`/`actor`/`since` behave identically across CLI, stdio MCP, and cloud HTTP), so agents can catch up on what other agents/users did since they last worked. Adds `actor` + `limit` params to the `pad_project` vocabulary (`since` already existed for changelog); pure addition — existing actions unchanged; backwards-compatible for v0.11 consumers that don't enumerate the new action. **v0.11** adds the read-only `pad_attachment` tool (the tenth resource × action tool) with `list` + `show` actions, mirroring the CLI `pad attachment list` / `pad attachment show` (TASK-2017): `list` enumerates a workspace's attachments (optional filters: item / category / collection / attached / unattached / sort / limit / offset); `show` returns one attachment's metadata (MIME, size, filename, ETag, last-modified) via a HEAD request without transferring bytes. Both HTTP dispatchers already existed (`dispatch_http_attachments.go`); this just wires them onto the catalog. Upload / download / view stay CLI-only (filesystem-bound, excluded per the catalog's exclusion rules). Pure addition — existing tools/actions unchanged; backwards-compatible for v0.10 consumers that don't enumerate the new tool. The base64 image RESOURCE for multimodal agents (`pad://workspace/{ws}/attachments/{id}`) shipped later in TASK-2077 (PR #930) as a bounded, image-only resource; TASK-2101 brought it — and the full read-only resource set — to the remote /mcp transport via the in-process `HTTPResourceFetcher`, so resources are no longer local-stdio-only. **v0.10** enforces the draft-playbook gate server-side: `pad_playbook.run` (and the underlying `POST /playbooks/{ref}/run`) now refuses a playbook whose `status` isn't `active` with a structured `playbook_not_active` error, adds an `allow_draft` boolean param (bareword `--allow-draft` on the CLI) as the escape hatch, and echoes the playbook `status` on both the `run` and `get` responses (BUG-2020). **v0.9** makes `pad_item.list` summary-shaped by default (drops item `content`, adds a default result limit of 50 / hard max 300 on MCP; CLI `--full` restores the complete shape) — a behavior change to the tool's return shape, hence the bump, though tool names, action enums, and parameter shapes are unchanged (TASK-2000). **v0.8** adds `restore` + `deleted` actions to `pad_workspace`, mirroring the CLI `pad workspace restore` / `pad workspace deleted` (TASK-1972): `deleted` (read-only) lists the caller's soft-deleted workspaces still inside the 30-day restore window; `restore` (mutating, not destructive, owner-only) un-soft-deletes a workspace by `slug` while it's still restorable. Both reuse the existing `slug` param — no new params; pure addition. **v0.7** adds `export` + `import` actions to `pad_item`, mirroring the CLI `pad item export` / `pad item import` (covers playbooks AND conventions). `export` (read-only) takes `ref` and returns the portable artifact text — it forces the CLI's stdout sink (`-o -`) so the bytes come back as the result instead of a file. `import` (mutating, not destructive) takes a new `artifact` param (the full artifact text) and returns `{ref, slug, warnings}`; the ExecDispatcher can't pipe stdin, so it spills the artifact to a temp file and dispatches `item import `. v0.6 added the `pad_item.backlinks` action; v0.5 added `pad_library`. v0.3 (PLAN-1377 / TASK-1380) introduced `pad_meta.action: bootstrap`, `pad_set_workspace`'s embedded-bootstrap response, and the `pad://workspace/{ws}/bootstrap` resource. **v0.4 (PLAN-1410)** is a comprehensive bootstrap-payload trim — same tool catalog, slimmer JSON shape inside bootstrap responses: `BootstrapCollection` projection drops `id`/`workspace_id`/timestamps/`settings` and emits `schema` as a nested object; `BootstrapRole` projection drops UUIDs/timestamps/`tools`; convention `slug` dropped; top-level `recent_activity` (a duplicate of `dashboard.recent_activity`) removed; new `BootstrapDashboard` wrapper caps five sub-arrays (`attention`, `recent_activity`, `active_items`, `active_plans`, `by_role`) at 5 entries each with parallel `*_overflow_count` fields; redundant schema labels omitted when `label == TitleCase(key)`. Cumulative size reduction: ~40% on a representative workspace, ~54% on the fixture (see PLAN-1410's Result section for per-section deltas). Compatibility: most changes are subtractive (dropped fields) or additive (overflow counts), but **one type change is breaking**: `collections[].schema` went from a JSON-encoded string to a nested JSON object — clients that JSON.parse()'d the string need to consume it directly as an object now. The dropped fields (UUIDs, timestamps, settings, duplicate `recent_activity`, convention `slug`) have canonical alternatives (slugs for addressing; `pad collection list` / `pad role list` for the full models when needed). Post-0.30 without a bump (BUG-2995): a successful content write through the designated applier used to answer with the item's PREVIOUS content — on that path the markdown goes to a live tab's Y.Doc and the row write runs with `Content` nil, so the response described the item as it stood before the request. It now carries the content as SENT plus an additive `omitempty` `warnings.content_outcome: "applied_pending_flush"`. No bump, on the BUG-2304 rather than the v0.9 grounds: v0.9 bumped because list rows LOST fields consumers read, whereas here nothing is removed or retyped — what changed is the VALUE of one field on one path, which a caller does observe. The claim is that no DOCUMENTED OR SUPPORTED reliance breaks, not that none can exist: a consumer could have detected the applier path by noticing the response echoed something other than what it sent, and that stops working — but it was never documented, a genuinely lost write produced the same mismatch, and `warnings.content_outcome` answers that question properly in the same change. Reads are unchanged: during the window a `get` (or `list` with `full: true`) still answers from the row, so the warning means re-read later, not re-send. diff --git a/internal/cli/client.go b/internal/cli/client.go index da8b0f102..6d9b86861 100644 --- a/internal/cli/client.go +++ b/internal/cli/client.go @@ -3014,6 +3014,44 @@ func WriteTooLargeError(w io.Writer, apiErr *APIError) { } } +// IsPermissionDenied reports whether err is a server 403 refusing the caller: +// code forbidden or permission_denied, or an unverified Cloud email +// (BUG-3864). Other 403 codes (plan_limit_exceeded and the like) have writers +// of their own, and a marker from this one would replace theirs. +func IsPermissionDenied(err error) (*APIError, bool) { + var apiErr *APIError + if !errors.As(err, &apiErr) || apiErr.Status != http.StatusForbidden { + return nil, false + } + switch apiErr.Code { + case "forbidden", "permission_denied", "email_not_verified": + return apiErr, true + } + return nil, false +} + +// WritePermissionDeniedError writes the structured marker line for a refused +// caller (BUG-3864), carrying the server's details.reason, so the stdio MCP +// transport reports which gate refused instead of inferring permission_denied, +// or server_error, from the message's wording. No hint: the MCP side builds it +// from the reason, the same way for both transports. +func WritePermissionDeniedError(w io.Writer, apiErr *APIError) { + code := "permission_denied" + if apiErr.Code == "email_not_verified" { + code = apiErr.Code + } + body := map[string]any{"code": code, "message": apiErr.Message} + var details struct { + Reason string `json:"reason"` + } + if len(apiErr.Details) > 0 && json.Unmarshal(apiErr.Details, &details) == nil && details.Reason != "" { + body["details"] = map[string]any{"reason": details.Reason} + } + if data, err := json.Marshal(map[string]any{"error": body}); err == nil { + fmt.Fprintln(w, StructuredErrorMarker+string(data)) + } +} + // WriteRateLimitedError writes the structured marker line for a 429 // (BUG-3147), so the stdio MCP transport reports rate_limited — with the // server's wait — instead of inferring server_error from prose that matches diff --git a/internal/mcp/bug3864_permission_reasons_test.go b/internal/mcp/bug3864_permission_reasons_test.go new file mode 100644 index 000000000..c0edecb96 --- /dev/null +++ b/internal/mcp/bug3864_permission_reasons_test.go @@ -0,0 +1,87 @@ +package mcp + +import ( + "bytes" + "context" + "encoding/json" + "net/http" + "strings" + "testing" + + "github.com/PerpetualSoftware/pad/internal/cli" +) + +// BUG-3864, the classifier half: the same 403 body reaches the same envelope +// on both transports. Remote reads the body; stdio reads the marker the CLI +// root writes from the same body. cmd/pad's end-to-end test drives the rows a +// fixture can reach; these are the ones it cannot (an OAuth allow-list, an +// older server, a newer server's reason). +func TestBUG3864_A403ReadsTheSameOnBothTransports(t *testing.T) { + for _, tc := range []struct { + name, code, message, reason string + wantCode ErrorCode + wantReason string + wantHint string + }{ + {"workspace allow-list", "permission_denied", "Token is not authorized for this workspace", "workspace_not_authorized", + ErrPermissionDenied, "workspace_not_authorized", PermissionWorkspaceNotAuthorizedHint}, + {"role", "forbidden", "Insufficient permissions", "role", ErrPermissionDenied, "role", PermissionRoleHint}, + // An older server says no reason. The hint must not guess one. + {"no reason", "forbidden", "Only the comment author can edit it.", "", + ErrPermissionDenied, "", "The server refused this operation: Only the comment author can edit it."}, + // A newer server's reason this build has no words for: dropped, so + // details.reason stays a closed vocabulary, and the message speaks. + {"unknown reason", "forbidden", "Refused by a gate from the future", "future_gate", + ErrPermissionDenied, "", "The server refused this operation: Refused by a gate from the future."}, + {"unverified email", "email_not_verified", "Verify your email address to perform this action.", "", + ErrEmailNotVerified, "", EmailNotVerifiedHint}, + } { + t.Run(tc.name, func(t *testing.T) { + api := &cli.APIError{Code: tc.code, Message: tc.message, Status: http.StatusForbidden} + if tc.reason != "" { + api.Details, _ = json.Marshal(map[string]string{"reason": tc.reason}) + } + body, _ := json.Marshal(map[string]any{"error": api}) + + remote := decodeEnvelope(t, classifyHTTPStatus(context.Background(), "item create", http.StatusForbidden, body, nil)) + + var stderr bytes.Buffer + stderr.WriteString("Error: " + tc.message + "\n") + if _, ok := cli.IsPermissionDenied(api); !ok { + t.Fatalf("the CLI root would write no marker for code %q", tc.code) + } + cli.WritePermissionDeniedError(&stderr, api) + lifted := extractStructuredCLIError(stderr.String()) + if lifted == nil { + t.Fatalf("stdio did not lift the marker: %s", stderr.String()) + } + stdio := decodeEnvelope(t, lifted) + + if remote.Error.Hint != stdio.Error.Hint || remote.Error.Code != stdio.Error.Code || string(remote.Error.Details) != string(stdio.Error.Details) { + t.Errorf("the transports differ:\n remote %+v\n stdio %+v", remote.Error, stdio.Error) + } + for door, env := range map[string]ErrorEnvelope{"remote": remote, "stdio": stdio} { + if env.Error.Code != tc.wantCode || reasonOf(t, env) != tc.wantReason || !strings.HasPrefix(env.Error.Hint, tc.wantHint) { + t.Errorf("%s: code=%q reason=%q hint=%q, want %q %q hint starting %q", + door, env.Error.Code, reasonOf(t, env), env.Error.Hint, tc.wantCode, tc.wantReason, tc.wantHint) + } + if tc.wantReason != "role" && strings.Contains(strings.ToLower(env.Error.Hint), "role") { + t.Errorf("%s: hint blames a role: %q", door, env.Error.Hint) + } + } + }) + } +} + +// Other 403 codes keep their own writers. A permission_denied marker from the +// root would come after theirs and, last marker winning, replace it. +func TestBUG3864_TheRootWriterLeavesOtherRefusalsAlone(t *testing.T) { + for _, code := range []string{"plan_limit_exceeded", "workspace_member_limit", "insufficient_scope", "account_disabled"} { + if _, ok := cli.IsPermissionDenied(&cli.APIError{Code: code, Status: http.StatusForbidden}); ok { + t.Errorf("IsPermissionDenied claims %q", code) + } + } + if _, ok := cli.IsPermissionDenied(&cli.APIError{Code: "forbidden", Status: http.StatusBadRequest}); ok { + t.Error("IsPermissionDenied claims a non-403") + } +} diff --git a/internal/mcp/dispatch_http.go b/internal/mcp/dispatch_http.go index 01602b3be..87d428aaa 100644 --- a/internal/mcp/dispatch_http.go +++ b/internal/mcp/dispatch_http.go @@ -544,22 +544,14 @@ func buildRequestErrorResult(cmdKey string, err error) *CallToolResult { // agents see the same code as a backend 403, not a // generic server_error. if strings.HasPrefix(err.Error(), "permission_denied:") { - return NewErrorResult(ErrorPayload{ - Code: ErrPermissionDenied, - Message: fmt.Sprintf("%s: %s", cmdKey, err.Error()), - Hint: "Token scope does not permit this operation. Re-issue with the required scopes (read for GET; write for POST/PATCH; admin for workspace settings).", - }) + return NewErrorResult(tokenScopeDeniedPayload(cmdKey, err)) } - // PLAN-1933 DR-4: the RequireVerifiedEmail gate rejected this - // write because the cloud user hasn't verified their email. - // Surface as permission_denied (the closest closed-set code) so - // agents branch consistently with a backend 403. + // PLAN-1933 DR-4: the RequireVerifiedEmail gate rejected this write + // because the cloud user hasn't verified their email. The server's own + // code for the same refusal (BUG-3864), so stdio, which reaches the + // server's gate instead of this one, reports the same thing. if strings.HasPrefix(err.Error(), errEmailNotVerifiedPrefix+":") { - return NewErrorResult(ErrorPayload{ - Code: ErrPermissionDenied, - Message: fmt.Sprintf("%s: %s", cmdKey, err.Error()), - Hint: "Verify your email address (check your inbox for the verification link) before creating or editing content.", - }) + return NewErrorResult(emailNotVerifiedPayload(fmt.Sprintf("%s: %s", cmdKey, err.Error()))) } return dispatcherErrorResult(cmdKey, "build request", err) } @@ -596,6 +588,13 @@ func buildRequestErrorResult(cmdKey string, err error) *CallToolResult { // dispatch_http_project.go's bulk-update path (PATCH issued // directly via buildAuthedRequest + ServeHTTP, bypassing // executeRequest's previous scope check). +// tokenScopeDeniedPayload is buildAuthedRequest's scope refusal. That check +// mirrors the server's own token-scope gate, so it reports what the server +// would have (BUG-3864): permission_denied with reason token_scope. +func tokenScopeDeniedPayload(cmdKey string, err error) ErrorPayload { + return permissionDeniedPayload(cmdKey+": "+err.Error(), "token_scope") +} + // errEmailNotVerifiedPrefix tags the build-request error the // RequireVerifiedEmail gate returns so executeRequest can map it to a // clean permission_denied envelope (mirrors the "permission_denied:" diff --git a/internal/mcp/dispatch_http_artifact.go b/internal/mcp/dispatch_http_artifact.go index 71aa42766..7e6e84452 100644 --- a/internal/mcp/dispatch_http_artifact.go +++ b/internal/mcp/dispatch_http_artifact.go @@ -63,11 +63,7 @@ func (d *HTTPHandlerDispatcher) dispatchItemImport( req, err := d.buildAuthedRequest(ctx, http.MethodPost, urlPath, []byte(artifact), user) if err != nil { if strings.HasPrefix(err.Error(), "permission_denied:") { - return NewErrorResult(ErrorPayload{ - Code: ErrPermissionDenied, - Message: cmdKey + ": " + err.Error(), - Hint: "Token scope does not permit this operation. Re-issue with a write scope (POST).", - }), nil + return NewErrorResult(tokenScopeDeniedPayload(cmdKey, err)), nil } return dispatcherErrorResult(cmdKey, "build request", err), nil } diff --git a/internal/mcp/dispatch_http_verified_email_test.go b/internal/mcp/dispatch_http_verified_email_test.go index 2422147ab..2b313cae6 100644 --- a/internal/mcp/dispatch_http_verified_email_test.go +++ b/internal/mcp/dispatch_http_verified_email_test.go @@ -3,7 +3,6 @@ package mcp import ( "context" "net/http" - "strings" "testing" "github.com/mark3labs/mcp-go/mcp" @@ -57,13 +56,11 @@ func TestHTTPHandlerDispatcher_VerifiedEmail_BlocksUnverifiedWrite(t *testing.T) msg = tc.Text } } - // Surfaced as permission_denied (closed-set code) with the - // email_not_verified marker in the message. - if !strings.Contains(msg, "permission_denied") { - t.Errorf("error envelope missing permission_denied marker: %q", msg) - } - if !strings.Contains(msg, "email_not_verified") { - t.Errorf("error envelope missing email_not_verified marker: %q", msg) + // The server's own code for the same refusal (BUG-3864), not + // permission_denied: no role or token fixes it. + env, ok := res.StructuredContent.(ErrorEnvelope) + if !ok || env.Error.Code != ErrEmailNotVerified || env.Error.Hint != EmailNotVerifiedHint { + t.Errorf("want code %q with EmailNotVerifiedHint, got %q", ErrEmailNotVerified, msg) } } diff --git a/internal/mcp/errors.go b/internal/mcp/errors.go index aec881884..2b3f2c168 100644 --- a/internal/mcp/errors.go +++ b/internal/mcp/errors.go @@ -56,10 +56,19 @@ const ( // CLI: ~/.pad/credentials.json missing or expired; HTTP: 401. ErrAuthRequired ErrorCode = "auth_required" - // ErrPermissionDenied fires when authentication succeeds but role - // is insufficient for the operation. HTTP: 403. + // ErrPermissionDenied fires when authentication succeeds but the + // operation is refused. HTTP: 403. details.reason names the gate when the + // server said which (BUG-3864): role, token_scope, no_access or + // workspace_not_authorized. With no reason, the message is the only + // account of the cause, and the hint claims none. ErrPermissionDenied ErrorCode = "permission_denied" + // ErrEmailNotVerified fires when a Cloud account whose email address is + // unverified attempts a write (BUG-3864). The server's own code on every + // door that enforces it. Not permission_denied: no role, token or grant + // fixes it, and retrying never helps until the address is verified. + ErrEmailNotVerified ErrorCode = "email_not_verified" + // ErrItemNotFound fires when an item ref / slug doesn't resolve. // Distinct from ErrNotFound: this code is reserved for the // specific case where a tool was looking up an item by ref @@ -534,6 +543,15 @@ var allowedStructuredErrorCodes = map[string]struct{}{ // (cli.WriteTooLargeError), with the server's own code in details.reason. // Before this both transports said server_error for a deliberate cap. "too_large": {}, + // BUG-3864. Written at the CLI's root for a 403 whose code is forbidden or + // permission_denied (cli.WritePermissionDeniedError), with the server's + // details.reason, and for email_not_verified. Before this stdio said + // server_error for any refusal whose message lacked "forbidden", which + // included the token-scope and unverified-email refusals. Both lifts + // rebuild the hint from the reason (permissionDeniedPayload), so the two + // transports cannot word the same refusal differently. + "permission_denied": {}, + "email_not_verified": {}, } // extractStructuredCLIError scans stderr for the @@ -587,6 +605,12 @@ func extractStructuredCLIError(stderr string) *CallToolResult { // Unknown code. Don't forward — regex classifier handles it. return nil } + switch ErrorCode(env.Error.Code) { + case ErrPermissionDenied: + return NewErrorResult(permissionDeniedPayload(env.Error.Message, permissionReasonIn(env.Error.Details))) + case ErrEmailNotVerified: + return NewErrorResult(emailNotVerifiedPayload(env.Error.Message)) + } // Hint is forwarded when the writer set one (BUG-2675, Codex round 2). // Without this the two transports delivered the same CODE and different // guidance: remote MCP told the agent retrying is pointless and how to @@ -1002,6 +1026,12 @@ func classifyHTTPStatusKind( // open_children on 409) so unknown 403 codes still collapse to // ErrPermissionDenied. upstream403 := extractUpstreamErrorEnvelope(bodyText) + switch ErrorCode(upstream403.Code) { + case ErrEmailNotVerified: + return NewErrorResult(emailNotVerifiedPayload(upstream403.Message)) + case ErrPermissionDenied: + return NewErrorResult(permissionDeniedPayload(bodyMessage, permissionReasonIn(upstream403.Details))) + } if _, allowed := allowedStructuredErrorCodes[upstream403.Code]; allowed { return NewErrorResult(ErrorPayload{ Code: ErrorCode(upstream403.Code), @@ -1010,11 +1040,7 @@ func classifyHTTPStatusKind( Details: upstream403.Details, }) } - return NewErrorResult(ErrorPayload{ - Code: ErrPermissionDenied, - Message: "Permission denied for this operation.", - Hint: permissionHintFor(bodyMessage, route), - }) + return NewErrorResult(permissionDeniedPayload(bodyMessage, permissionReasonIn(upstream403.Details))) case http.StatusNotFound: // PLAN-3578 step 3: an undo naming a patch this item does not have is // a 404 about the PATCH, not the item; the generic classifier would @@ -1416,18 +1442,72 @@ func authHintFor(bodyMsg, route string) string { return strings.Join(parts, " ") } -// permissionHintFor generates the actionable hint for -// ErrPermissionDenied. References the route + the inner backend -// message (which often names the missing role / workspace). -func permissionHintFor(bodyMsg, route string) string { - parts := []string{"Insufficient role for this operation."} - if route != "" { - parts = append(parts, fmt.Sprintf("Route: %s.", route)) +// The permission_denied hints, by the server's details.reason (BUG-3864). +// Each says what the caller does next, in the words the web app uses. A +// reason outside this table, or none, gets permissionUnknownHintPrefix and +// the server's message instead: the old hint led with "Insufficient role" +// for every 403, which sent a bot with a read-only token to ask for a role +// it already had. +const ( + PermissionRoleHint = "Your role in this workspace does not allow this. Ask a workspace owner to change your role." + PermissionTokenScopeHint = "This API token's access does not include this action: a 'Read only' token cannot make changes. " + + "Create a token with 'Read and write' access under Account settings → API Tokens, and use it instead." + PermissionNoAccessHint = "You do not have access to this workspace or collection. Ask a workspace owner for access." + PermissionWorkspaceNotAuthorizedHint = "This connection was not granted access to this workspace. " + + "Reconnect and include it, or use a workspace it was granted." + permissionUnknownHintPrefix = "The server refused this operation" + + EmailNotVerifiedHint = "Verify your account's email address (the link is in your inbox, and the web app can send a new one). " + + "Changes are refused until then." +) + +var permissionReasonHints = map[string]string{ + "role": PermissionRoleHint, + "token_scope": PermissionTokenScopeHint, + "no_access": PermissionNoAccessHint, + "workspace_not_authorized": PermissionWorkspaceNotAuthorizedHint, +} + +// permissionReasonIn reads details.reason from an upstream error's details. +func permissionReasonIn(details json.RawMessage) string { + var d struct { + Reason string `json:"reason"` } - if bodyMsg != "" { - parts = append(parts, fmt.Sprintf("Backend: %s", bodyMsg)) + if len(details) == 0 || json.Unmarshal(details, &d) != nil { + return "" } - return strings.Join(parts, " ") + return d.Reason +} + +// permissionDeniedPayload is the one permission_denied envelope, for every +// door that produces one: the remote 403, the remote dispatcher's own scope +// gate, and the stdio marker. details.reason is forwarded only when it is a +// reason this build knows, so the field stays a closed vocabulary. No route in +// the hint: stdio has none, and the two transports must say the same thing. +func permissionDeniedPayload(message, reason string) ErrorPayload { + p := ErrorPayload{Code: ErrPermissionDenied, Message: message} + if p.Message == "" { + p.Message = "Permission denied for this operation." + } + hint, known := permissionReasonHints[reason] + if known { + p.Details, _ = json.Marshal(map[string]string{"reason": reason}) + } else { + hint = permissionUnknownHintPrefix + if message != "" { + hint += ": " + strings.TrimRight(message, ".") + } + hint += "." + } + p.Hint = hint + return p +} + +func emailNotVerifiedPayload(message string) ErrorPayload { + if message == "" { + message = "Verify your email address to perform this action." + } + return ErrorPayload{Code: ErrEmailNotVerified, Message: message, Hint: EmailNotVerifiedHint} } // CommentHasRepliesHint is the recovery guidance for ErrCommentHasReplies on diff --git a/internal/mcp/instructions.md b/internal/mcp/instructions.md index b55e745d6..53565619e 100644 --- a/internal/mcp/instructions.md +++ b/internal/mcp/instructions.md @@ -6,7 +6,7 @@ Pad is a project tracker for developers and AI agents — issues (TASK, BUG), pl If the user is asking general code questions with no project-management thread, you don't need this server. -## Tool surface (v0.99) +## Tool surface (v0.100) Ten resource × action tools, plus `pad_set_workspace`. Eleven tools total. diff --git a/internal/mcp/too_large_test.go b/internal/mcp/too_large_test.go index ab0a0d6d6..ecc95af04 100644 --- a/internal/mcp/too_large_test.go +++ b/internal/mcp/too_large_test.go @@ -205,6 +205,9 @@ func TestEveryCLIMarkerCodeIsInTheStdioVocabulary(t *testing.T) { "WritePatchRefusalError": func(w *bytes.Buffer) { cli.WritePatchRefusalError(w, api("patch_anchor_missing")) }, + "WritePermissionDeniedError": func(w *bytes.Buffer) { + cli.WritePermissionDeniedError(w, api("forbidden")) + }, } for name, write := range writers { diff --git a/internal/mcp/version.go b/internal/mcp/version.go index e21748a59..1c98b0871 100644 --- a/internal/mcp/version.go +++ b/internal/mcp/version.go @@ -1738,6 +1738,26 @@ const CmdhelpVersion = "0.1" // caller cannot read embeds nothing; a failed fetch stays non-fatal, // as on stdio. Stdio is unchanged. // +// 0.100 — BUG-3864. BEHAVIOR bump on the 0.45 grounds; no name, enum +// or param shape changed. A refused call names its cause, on BOTH +// transports. `permission_denied` gains `details.reason` when the server +// says which gate refused (`role`, `token_scope`, `no_access`, +// `workspace_not_authorized`), and a hint per reason that says what to +// do next. With no reason, or one this build does not know, the hint +// leads with the server's message and claims no cause. The old hint led +// with "Insufficient role" for every 403, so a bot with a read-only API +// token was told to ask for a role. New code `email_not_verified` (the +// server's own, on every door that enforces it) replaces the +// `permission_denied` the remote gate reported for an unverified Cloud +// email. REMOTE: classifyHTTPStatus reads the body's reason, and the +// dispatcher's own scope and email gates build the same envelopes. +// STDIO: the CLI root writes a structured marker for a 403 coded +// forbidden, permission_denied or email_not_verified +// (cli.WritePermissionDeniedError); before it, a refusal whose message +// lacked "forbidden" (token scope, unverified email) said server_error. +// Both lifts build the hint in permissionDeniedPayload. "0.100" follows +// "0.99": the version is an opaque dotted string, compared by no code. +// // 0.99 — BUG-3790, starred truncation. ADDITIVE bump on the v0.53 // grounds: `pad_item.action=starred` returns at most 300 items, most // recently starred first, and when more exist says `has_more: true` @@ -2187,7 +2207,7 @@ const CmdhelpVersion = "0.1" // this surface can receive it; the entry exists so a future action does // not collapse it to permission_denied. When an action that can reach // it is added, that addition is the contract change and owns the bump. -const ToolSurfaceVersion = "0.99" +const ToolSurfaceVersion = "0.100" // MetaVersionURI is the canonical URI of the queryable version document. // Lives outside the pad://workspace/{ws}/... namespace because it's a diff --git a/internal/server/authz_cross_workspace.go b/internal/server/authz_cross_workspace.go index bc24198ff..f77d5a2e3 100644 --- a/internal/server/authz_cross_workspace.go +++ b/internal/server/authz_cross_workspace.go @@ -235,11 +235,11 @@ func (a CrossWorkspaceAccess) WriteDenied(w http.ResponseWriter) { case CrossWorkspaceLookupFailed: writeInternalError(w, a.Err) case CrossWorkspaceTokenNotAllowed: - writeError(w, http.StatusForbidden, "permission_denied", - "Token is not authorized for this workspace") + writeForbidden(w, "permission_denied", + "Token is not authorized for this workspace", forbiddenReasonWorkspaceNotAuthorized) default: - writeError(w, http.StatusForbidden, "forbidden", - "You do not have access to the requested workspace") + writeForbidden(w, "forbidden", + "You do not have access to the requested workspace", forbiddenReasonNoAccess) } } diff --git a/internal/server/bug3864_forbidden_reason_test.go b/internal/server/bug3864_forbidden_reason_test.go new file mode 100644 index 000000000..6f372b421 --- /dev/null +++ b/internal/server/bug3864_forbidden_reason_test.go @@ -0,0 +1,154 @@ +package server + +import ( + "context" + "encoding/json" + "net/http" + "net/http/httptest" + "strings" + "testing" + + "github.com/PerpetualSoftware/pad/internal/models" +) + +// BUG-3864: the shared 403 gates name which gate refused, in details.reason, +// with code and message unchanged. cmd/pad's end-to-end test drives the role, +// token-scope and not-a-member gates through /mcp and the CLI; these are the +// gates a PAT fixture cannot reach (an OAuth consent allow-list) and the +// cross-workspace writer's two arms. + +func bug3864Refusal(t *testing.T, rr *httptest.ResponseRecorder) (code, message, reason string) { + t.Helper() + if rr.Code != http.StatusForbidden { + t.Fatalf("status %d, want 403: %s", rr.Code, rr.Body.String()) + } + var env struct { + Error struct { + Code string `json:"code"` + Message string `json:"message"` + Details struct { + Reason string `json:"reason"` + } `json:"details"` + } `json:"error"` + } + if err := json.Unmarshal(rr.Body.Bytes(), &env); err != nil { + t.Fatalf("decode: %v: %s", err, rr.Body.String()) + } + return env.Error.Code, env.Error.Message, env.Error.Details.Reason +} + +func TestBUG3864_TheConsentAllowListNamesItself(t *testing.T) { + srv := testServer(t) + owner := mustCreateUser(t, srv, "owner@example.com", "Owner", "") + ws := mustCreateOwnedWorkspace(t, srv, "Refused", owner) + + rr := httptest.NewRecorder() + req := consentScopedRequest(http.MethodGet, "/api/v1/workspaces/"+ws.Slug, owner, []string{"some-other-workspace"}, map[string]string{"slug": ws.Slug}) + srv.RequireWorkspaceAccess(http.HandlerFunc(func(http.ResponseWriter, *http.Request) { + t.Fatal("the allow-list gate let the request through") + })).ServeHTTP(rr, req) + + code, message, reason := bug3864Refusal(t, rr) + if code != "permission_denied" || message != "Token is not authorized for this workspace" || reason != forbiddenReasonWorkspaceNotAuthorized { + t.Errorf("got %q %q reason %q", code, message, reason) + } +} + +func TestBUG3864_CrossWorkspaceRefusalsNameTheirGate(t *testing.T) { + for _, tc := range []struct { + access CrossWorkspaceAccess + code string + wantReason string + }{ + {CrossWorkspaceAccess{Reason: CrossWorkspaceTokenNotAllowed}, "permission_denied", forbiddenReasonWorkspaceNotAuthorized}, + {CrossWorkspaceAccess{}, "forbidden", forbiddenReasonNoAccess}, + } { + rr := httptest.NewRecorder() + tc.access.WriteDenied(rr) + code, _, reason := bug3864Refusal(t, rr) + if code != tc.code || reason != tc.wantReason { + t.Errorf("%+v: got %q reason %q, want %q reason %q", tc.access, code, reason, tc.code, tc.wantReason) + } + } +} + +// A viewer can be given a higher role. A guest holds grants, not a role, and +// a caller with no workspace role (a platform admin who is not a member) has +// no role to change, so neither is told to ask for one. +func TestBUG3864_RequireMinRoleSaysRoleOnlyWhenARoleCanFixIt(t *testing.T) { + for role, want := range map[string]string{ + "viewer": forbiddenReasonRole, + "guest": forbiddenReasonNoAccess, + "": forbiddenReasonNoAccess, + } { + req := httptest.NewRequest(http.MethodPost, "/", nil) + if role != "" { + req = req.WithContext(context.WithValue(req.Context(), ctxWorkspaceRole, role)) + } + rr := httptest.NewRecorder() + if requireMinRole(rr, req, "editor") { + t.Fatalf("role %q passed requireMinRole(editor)", role) + } + code, message, reason := bug3864Refusal(t, rr) + if code != "forbidden" || message != "Insufficient permissions" || reason != want { + t.Errorf("role %q: got %q %q reason %q, want reason %q", role, code, message, reason, want) + } + } +} + +// The workspace-role gates that check the role inline rather than through +// requireMinRole (the lead's Codex round found the bulk endpoint). Driven +// through the router with real tokens, so the role on context is the one the +// auth middleware put there. A guest holds grants, not a role. +func TestBUG3864_InlineRoleGatesSayRoleOrNoAccess(t *testing.T) { + srv := testServer(t) + owner := mustCreateUser(t, srv, "owner@example.com", "Owner", "") + ws := mustCreateOwnedWorkspace(t, srv, "Gated", owner) + member := func(email, role string) string { + u := mustCreateUser(t, srv, email, email, "") + if role != "" { + if err := srv.store.AddWorkspaceMember(ws.ID, u.ID, role); err != nil { + t.Fatal(err) + } + } + tok, err := srv.store.CreateAPIToken(u.ID, models.APITokenCreate{Name: "t"}, 30, 0) + if err != nil { + t.Fatal(err) + } + if role == "" { // a guest: one grant, no membership + coll, err := srv.store.CreateCollection(ws.ID, models.CollectionCreate{Name: "Notes"}) + if err != nil { + t.Fatal(err) + } + item, err := srv.store.CreateItem(ws.ID, coll.ID, models.ItemCreate{Title: "granted"}) + if err != nil { + t.Fatal(err) + } + if _, err := srv.store.CreateItemGrant(ws.ID, item.ID, u.ID, "view", owner.ID); err != nil { + t.Fatal(err) + } + } + return tok.Token + } + viewer, editor, guest := member("viewer@example.com", "viewer"), member("editor@example.com", "editor"), member("guest@example.com", "") + + for _, tc := range []struct { + name, token, method, path, want string + }{ + {"bulk by a viewer", viewer, http.MethodPost, "/items/bulk", forbiddenReasonRole}, + {"bulk by a guest", guest, http.MethodPost, "/items/bulk", forbiddenReasonNoAccess}, + {"invite by an editor", editor, http.MethodPost, "/members/invite", forbiddenReasonRole}, + {"another member's grants, by a guest", guest, http.MethodGet, "/users/" + owner.ID + "/grants", forbiddenReasonNoAccess}, + } { + t.Run(tc.name, func(t *testing.T) { + req := httptest.NewRequest(tc.method, "/api/v1/workspaces/"+ws.Slug+tc.path, strings.NewReader(`{}`)) + req.Header.Set("Content-Type", "application/json") + req.Header.Set("Authorization", "Bearer "+tc.token) + rr := httptest.NewRecorder() + srv.ServeHTTP(rr, req) + if _, _, reason := bug3864Refusal(t, rr); reason != tc.want { + t.Errorf("reason %q, want %q: %s", reason, tc.want, rr.Body.String()) + } + }) + } +} diff --git a/internal/server/handlers_apps_provision.go b/internal/server/handlers_apps_provision.go index d0c57ffde..92c34f462 100644 --- a/internal/server/handlers_apps_provision.go +++ b/internal/server/handlers_apps_provision.go @@ -101,7 +101,7 @@ func (s *Server) handleConfirmAppInstall(w http.ResponseWriter, r *http.Request) case errors.As(err, &ae): ae.write(w) case errors.Is(err, store.ErrNotWorkspaceOwner): - writeError(w, http.StatusForbidden, "forbidden", "Only a workspace owner can install apps") + writeForbidden(w, "forbidden", "Only a workspace owner can install apps", roleGateReason(r)) case errors.As(err, &pc): details := map[string]interface{}{} if pc.Field != "" { diff --git a/internal/server/handlers_apps_upgrade.go b/internal/server/handlers_apps_upgrade.go index 897294423..192321487 100644 --- a/internal/server/handlers_apps_upgrade.go +++ b/internal/server/handlers_apps_upgrade.go @@ -237,7 +237,7 @@ func (s *Server) handleAppUpgradeConfirm(w http.ResponseWriter, r *http.Request) case errors.Is(err, store.ErrPendingManifestChanged): writeError(w, http.StatusConflict, "install_review_mismatch", "This pending upgrade is not the manifest you reviewed; preview it again") case errors.Is(err, store.ErrNotWorkspaceOwner): - writeError(w, http.StatusForbidden, "forbidden", "Only a workspace owner can upgrade apps") + writeForbidden(w, "forbidden", "Only a workspace owner can upgrade apps", roleGateReason(r)) default: s.writeInstallLifecycleError(w, err) } diff --git a/internal/server/handlers_grants.go b/internal/server/handlers_grants.go index 57101eb26..76352bd6f 100644 --- a/internal/server/handlers_grants.go +++ b/internal/server/handlers_grants.go @@ -351,7 +351,7 @@ func (s *Server) handleListUserGrants(w http.ResponseWriter, r *http.Request) { // Only workspace owners or the user themselves can view grants if !requireRole(r, "owner") && currentUserID(r) != userID { - writeError(w, http.StatusForbidden, "forbidden", "Insufficient permissions") + writeForbidden(w, "forbidden", "Insufficient permissions", roleGateReason(r)) return } diff --git a/internal/server/handlers_items_bulk.go b/internal/server/handlers_items_bulk.go index 9632dcdc3..576b6c2b2 100644 --- a/internal/server/handlers_items_bulk.go +++ b/internal/server/handlers_items_bulk.go @@ -122,7 +122,7 @@ func (s *Server) handleBulkItems(w http.ResponseWriter, r *http.Request) { // Owner/editor gated. Bulk lane actions are canEdit-only; viewers // and guests (grant-based access) cannot bulk-mutate. if !requireRole(r, "editor") { - writeError(w, http.StatusForbidden, "forbidden", "Bulk mutations require editor or owner role") + writeForbidden(w, "forbidden", "Bulk mutations require editor or owner role", roleGateReason(r)) return } diff --git a/internal/server/handlers_members.go b/internal/server/handlers_members.go index dbc29ce07..5c9438716 100644 --- a/internal/server/handlers_members.go +++ b/internal/server/handlers_members.go @@ -104,7 +104,7 @@ func (s *Server) handleInviteMember(w http.ResponseWriter, r *http.Request) { // Only owners can invite if !requireRole(r, "owner") { - writeError(w, http.StatusForbidden, "forbidden", "Only workspace owners can invite members") + writeForbidden(w, "forbidden", "Only workspace owners can invite members", roleGateReason(r)) return } // An invitation carries no scope, so the member it makes sees every @@ -264,7 +264,7 @@ func (s *Server) handleRemoveMember(w http.ResponseWriter, r *http.Request) { } if !requireRole(r, "owner") { - writeError(w, http.StatusForbidden, "forbidden", "Only workspace owners can remove members") + writeForbidden(w, "forbidden", "Only workspace owners can remove members", roleGateReason(r)) return } @@ -311,7 +311,7 @@ func (s *Server) handleUpdateMemberRole(w http.ResponseWriter, r *http.Request) } if !requireRole(r, "owner") { - writeError(w, http.StatusForbidden, "forbidden", "Only workspace owners can change roles") + writeForbidden(w, "forbidden", "Only workspace owners can change roles", roleGateReason(r)) return } @@ -416,7 +416,7 @@ func (s *Server) handleCancelInvitation(w http.ResponseWriter, r *http.Request) } if !requireRole(r, "owner") { - writeError(w, http.StatusForbidden, "forbidden", "Only workspace owners can cancel invitations") + writeForbidden(w, "forbidden", "Only workspace owners can cancel invitations", roleGateReason(r)) return } @@ -776,7 +776,7 @@ func (s *Server) handleGetMemberCollectionAccess(w http.ResponseWriter, r *http. // Only workspace owners or the user themselves can view collection access userID := chi.URLParam(r, "userID") if !requireRole(r, "owner") && currentUserID(r) != userID { - writeError(w, http.StatusForbidden, "forbidden", "Only workspace owners can view other members' collection access") + writeForbidden(w, "forbidden", "Only workspace owners can view other members' collection access", roleGateReason(r)) return } member, err := s.store.GetWorkspaceMember(workspaceID, userID) @@ -810,7 +810,7 @@ func (s *Server) handleSetMemberCollectionAccess(w http.ResponseWriter, r *http. } if !requireRole(r, "owner") { - writeError(w, http.StatusForbidden, "forbidden", "Only workspace owners can manage collection access") + writeForbidden(w, "forbidden", "Only workspace owners can manage collection access", roleGateReason(r)) return } diff --git a/internal/server/middleware_auth.go b/internal/server/middleware_auth.go index 1be08d4b8..f53006f5c 100644 --- a/internal/server/middleware_auth.go +++ b/internal/server/middleware_auth.go @@ -225,7 +225,7 @@ func (s *Server) TokenAuth(next http.Handler) http.Handler { // Enforce token scopes if !tokenScopeAllows(apiToken.Scopes, r.Method, r.URL.Path) { - writeError(w, http.StatusForbidden, "forbidden", "Token scope does not permit this action") + writeForbidden(w, "forbidden", "Token scope does not permit this action", forbiddenReasonTokenScope) return } @@ -732,8 +732,8 @@ func (s *Server) RequireWorkspaceAccess(next http.Handler) http.Handler { // today, but might in a future PAT-with-allow-list world // — doesn't pollute the MCP-specific counter. s.recordMCPAuthzDenial(r, "workspace_not_in_allowlist") - writeError(w, http.StatusForbidden, "permission_denied", - "Token is not authorized for this workspace") + writeForbidden(w, "permission_denied", + "Token is not authorized for this workspace", forbiddenReasonWorkspaceNotAuthorized) return } @@ -821,7 +821,7 @@ func (s *Server) RequireWorkspaceAccess(next http.Handler) http.Handler { // non-members hit. if user.Role == "admin" && isBearer { s.recordMCPAuthzDenial(r, "not_a_member") - writeError(w, http.StatusForbidden, "forbidden", "You are not a member of this workspace") + writeForbidden(w, "forbidden", "You are not a member of this workspace", forbiddenReasonNoAccess) return } // Not a member — check for guest access via grants @@ -837,7 +837,7 @@ func (s *Server) RequireWorkspaceAccess(next http.Handler) http.Handler { // the regular /api/v1 403s would inflate the MCP- // specific counter). s.recordMCPAuthzDenial(r, "not_a_member") - writeError(w, http.StatusForbidden, "forbidden", "You are not a member of this workspace") + writeForbidden(w, "forbidden", "You are not a member of this workspace", forbiddenReasonNoAccess) return } ctx = context.WithValue(ctx, ctxWorkspaceRole, "guest") @@ -922,7 +922,7 @@ func requireMinRole(w http.ResponseWriter, r *http.Request, minRole string) bool if requireRole(r, minRole) { return true } - writeError(w, http.StatusForbidden, "forbidden", "Insufficient permissions") + writeForbidden(w, "forbidden", "Insufficient permissions", roleGateReason(r)) return false } diff --git a/internal/server/server.go b/internal/server/server.go index 9b61f404d..b71a746ad 100644 --- a/internal/server/server.go +++ b/internal/server/server.go @@ -2777,6 +2777,33 @@ func writeError(w http.ResponseWriter, status int, code, message string) { }) } +// Values of details.reason on a 403, naming which gate refused (BUG-3864). +// Code and message are unchanged, so the web app and CLI read what they always +// did; MCP reads the reason to tell a caller what to fix, which used to be +// "Insufficient role" whatever the cause. A 403 with no reason is any other +// refusal, and its message is the only account of it. +const ( + forbiddenReasonRole = "role" + forbiddenReasonTokenScope = "token_scope" + forbiddenReasonNoAccess = "no_access" + forbiddenReasonWorkspaceNotAuthorized = "workspace_not_authorized" +) + +// roleGateReason is the reason for a refusal by a workspace-role gate. A +// guest holds grants, not a role, and a caller with no workspace role at all +// (a platform admin who is not a member) has none to change: no role change +// admits either. +func roleGateReason(r *http.Request) string { + if role := workspaceRole(r); role == "guest" || role == "" { + return forbiddenReasonNoAccess + } + return forbiddenReasonRole +} + +func writeForbidden(w http.ResponseWriter, code, message, reason string) { + writeError2(w, http.StatusForbidden, code, message, map[string]interface{}{"reason": reason}) +} + // workspaceNotFoundDetails marks a 404 as the WORKSPACE failing to resolve // for this caller (a non-member, or a deleted workspace), as opposed to a // sub-resource inside a workspace the caller can read (BUG-3069). The two @@ -3757,7 +3784,13 @@ func (s *Server) requireEditPermission(w http.ResponseWriter, r *http.Request, w return false } if !ok { - writeError(w, http.StatusForbidden, "forbidden", "Insufficient permissions") + // An editor or owner refused here is outside their collection access, + // and a guest holds grants, not a role: neither is fixed by a role change. + reason := roleGateReason(r) + if requireRole(r, "editor") { + reason = forbiddenReasonNoAccess + } + writeForbidden(w, "forbidden", "Insufficient permissions", reason) return false } return true