fix: apply /review feedback on legacy URL cleanup

Reviewer caught real misses on the consumer-swap claim:

- TypeScript SDK still defined and re-exported `CloseWorkstreamRequest`
  (types.ts + index.ts) — drop both. Now matches the Python-side
  removal.
- Four `tests/test_auth.py` cases (`test_write_full_token_ok`,
  `test_approve_full_token_ok`, `test_bearer_takes_precedence_over_cookie`,
  `test_cookie_full_on_write_ok`) were tautological after the legacy
  URL removal: they posted to `/api/send` / `/api/approve` and asserted
  `allowed is True`, but those paths now classify as `read` so a read
  token would also pass — they no longer tested the write/approve
  scope enforcement. Swap to path-keyed URLs to restore the original
  intent.
- `is_public_path("/api/send")` test renamed + retargeted to a
  path-keyed URL.

Doc-table drift the previous commit missed:

- `docs/security.md` path-to-scope mapping rewritten for the
  path-keyed verb family (write set, DELETE-on-/send dequeue,
  per-ws_id approve).
- `docs/architecture.md` scope-model row text swap from `/api/send`
  / `/api/approve` to the path-keyed equivalents.
- `docs/diagrams/01-system-context.puml` channel→server edge label
  swap.
- `docs/diagrams/15-auth-architecture.puml` scope class swap.

Cosmetic comment-only stragglers:

- `tests/test_session_worker.py` module docstring URL update.
- `tests/test_ratelimit.py` ~11 `/api/send` fixture-key strings
  retargeted to `/api/workstreams/abc/send` so the URL fixtures
  reflect the post-1.5 surface (rate limiter is path-agnostic; the
  swap is purely cosmetic).

4557 tests still passing under -m "not live"; ruff + mypy clean.

docs/architecture.md

@@ -1100,8 +1100,8 @@ Three hierarchical scopes control endpoint access:
 | Scope | Grants | Endpoints |
 |-------|--------|-----------|
 | `read` | SSE streams, workstream listing, history | GET endpoints |
-| `write` | `read` + send, command, workstream create/close | POST to `/api/send`, `/api/command`, etc. |
-| `approve` | `write` + tool approval, admin operations | POST to `/api/approve`, `/api/admin/*` |
+| `write` | `read` + send, command, workstream create/close | POST to `/api/workstreams/{ws_id}/send`, `/api/command`, etc. |
+| `approve` | `write` + tool approval, admin operations | POST to `/api/workstreams/{ws_id}/approve`, `/api/admin/*` |
 
 ### Middleware Flow
 

docs/diagrams/01-system-context.puml

@@ -43,7 +43,7 @@ eval --> sqlite : SQLite
 
 console --> server : HTTP proxy\n(hash-ring bucket lookup,\nproxy /node/{id}/* traffic)
 
-channel --> server : HTTP + SSE\n(POST /v1/api/send,\nGET /v1/api/events)
+channel --> server : HTTP + SSE\n(POST /v1/api/workstreams/{ws_id}/send,\nGET /v1/api/workstreams/{ws_id}/events)
 
 ' Notes
 note right of console

docs/diagrams/15-auth-architecture.puml

@@ -79,7 +79,7 @@ class "Scope Hierarchy" as SH <<scope>> {
     --
     GET → read
     POST write paths → write
-    POST /api/approve → approve
+    POST /api/workstreams/{ws_id}/approve → approve
     /api/admin/* → approve
 }
 

docs/security.md

@@ -67,10 +67,11 @@ Scopes are hierarchical — higher scopes imply all lower ones.
 | Method | Path pattern | Required scope |
 |--------|-------------|----------------|
 | GET | Any protected path | `read` |
-| POST | `/api/send`, `/api/plan`, `/api/command` | `write` |
-| POST | `/api/workstreams/new`, `/api/workstreams/close` | `write` |
-| POST | `/api/cluster/workstreams/new` | `write` |
-| POST | `/api/approve` | `approve` |
+| POST | `/api/plan`, `/api/command` | `write` |
+| POST | `/api/workstreams/new`, `/api/cluster/workstreams/new` | `write` |
+| POST | `/api/workstreams/{ws_id}/{send,cancel,close,delete,open,refresh-title,title,attachments}` | `write` |
+| DELETE | `/api/workstreams/{ws_id}/send` (dequeue), `/api/workstreams/{ws_id}/attachments/{attachment_id}` | `write` |
+| POST | `/api/workstreams/{ws_id}/approve` | `approve` |
 | Any | `/api/admin/*` | `approve` |
 
 Public paths bypass authentication entirely: `/`, `/health`, `/metrics`,