@womp/mcp-ui 0.1.8 → 0.1.9

package/README.md

@@ -243,8 +243,8 @@ own refusal text on 4xx, 409/410 terminal. It never touches the model: the
 bytes go disk → API.
 
 Two things outside this repo make that PUT possible, and both fail as a bare
-network error inside the card if missing (which it turns into an "open the
-upload page instead" button rather than a dead end):
+network error inside the card if missing (the status line names that layer,
+since there is no console in the sandbox):
 
 - **`connectDomains` must name the API origin**, and the origin differs per
   environment — so `bake-html.mjs` bakes `{}` for this card and swan-backend
@@ -256,7 +256,12 @@ upload page instead" button rather than a dead end):
 
 While pending the card polls the app-callable `get_upload`, so a file the agent
 pushed itself (`curl -T` from a shell that has it) flips the card to done
-instead of leaving a drop zone for a file that already landed. The dev stub
+instead of leaving a drop zone for a file that already landed.
+
+There is **no link out to an upload page**. swan-frontend had one at
+`/upload/<token>` before this card existed; it was removed 2026-09-15 (Anuj)
+so there is exactly one place a user sends a file from. The recovery for a
+blocked PUT is the agent's own `curl -T`, which its tool text gives it. The dev stub
 (`dev/server.mjs`) carries `create_upload` / `get_upload` and a `PUT
 /mcp/v1/uploads/:token` sink with the GLB-magic sniff, so the refusal strip is
 reachable locally too.