@topolo/sdk 0.9.7 → 0.9.8

package/README.md

@@ -131,6 +131,18 @@ schemas, read-only and destructive hints, and the stable MCP/agent tool name.
 from `input`, and routes the request through the same auth, audit-header, and
 write-confirmation flow as `request()`.
 
+`TopoloClient.uploadAction(actionRef, bytes, input, options)` requires an
+`agentContract.upload` profile. `inline-base64` declares the content, MIME-type,
+and file-name input fields; the SDK validates and base64-encodes the file before
+calling the action. `url-session` declares the initiation fields, response path
+for the returned URL, upload method, and optional completion action mapping; the
+SDK initiates, uploads the raw bytes, and completes the session in one call.
+Both profiles declare a maximum byte length and accepted MIME patterns, and use
+the same authorization and confirmation path as `callAction()`.
+`TopoloClient.uploadActionBase64()` provides the same contract for MCP and
+other transports that already hold canonical base64. `completionInput` supplies
+any additional fields required by a declared URL-session completion action.
+
 `APPLICATION_REQUIREMENTS` is the versioned app-build contract agents should
 read before creating or expanding a Topolo app. `requirementsForApplication()`
 filters the shared contract to the browser/API/tooling scopes implied by the app