xarmian 5c9c650ac3 feat(server): a read-scoped token may run a playbook (TASK-2863) (#1987) ...

* feat(server): a read-scoped token may run a playbook (TASK-2863)

POST /api/v1/workspaces/{ws}/playbooks/{ref}/run is side-effect-free:
it binds the caller's args and returns the body, storing nothing. It is
now the one POST a read or pad:read token may make, through an
exact-path allowlist in tokenScopeAllows (lead ruling, option A).
/playbooks/match stays refused, as do every write and the item
claim/release routes.

Both variable segments must be plain names (RFC 3986 unreserved
characters, not a dot segment). The MCP dispatcher checks the path
string it built from caller input before http.NewRequest parses it, so
without that a ref of "match?" passed as eight segments ending in run
and routed as POST /playbooks/match. Pinned through the real catalog
action and dispatcher.

* test(server): key the read refusal on TokenAuth's scope message (TASK-2863, codex r1)

* chore(mcp): ToolSurfaceVersion 0.79, a read grant may run a playbook (TASK-2863)

2026-10-09 18:56:44 -04:00

..

loadtest-collab

fix(collab): close a peer the op bus had to drop an op for (TASK-1273) (#1981)

2026-10-09 13:52:27 -04:00

pad

feat(server): a read-scoped token may run a playbook (TASK-2863) (#1987)

2026-10-09 18:56:44 -04:00