App HTTP handlers can use the existing FileLifecycleRecorder and FileDeliveryAttempts contracts to record generated downloads without retaining the file in Media. File-owner and legal-entity access checks still apply. A completed transmission records the runtime finishing its stream; it does not prove that the browser saved the file.

App GET requests using the SDK HTTP client's responseType: 'blob' now preserve file bytes and safe file metadata through the App frame. Existing runtime, App, actor, MIME and response-size checks remain in effect.

POST file-generation requests also preserve their first binary response. If that response is lost, the same request cannot replay the file or run the operation again; the client receives an explicit consumed-response result. File bytes are not retained in the request receipt.

App imports use the actor's live import permission and attach source evidence to the App-owned target. Work with an unconfirmed result is not automatically replayed as a new request. Interruption handling distinguishes work that has not started from work already running.

Deploy Core support before adopting the corresponding runtime image to use the download fix. No public SDK API update or App source change is required for this fix.