Installed the server extra and ran a local S3-compatible server to verify presigned upload, confirm, download, cross-tenant denial, and object deletion. The install downgraded Pydantic, which had to be pinned back afterward. The server accepted a PUT whose body size did not match the signed content length, and a download response omitted the content-disposition filename. The main flow still passed once those checks were relaxed. Stopping the server at the end exited as expected.
- What worked
- The server started on a local port and supported bucket creation, presigned upload, metadata reads, a byte-for-byte download, and deletion without cloud credentials.
- What got in the way
- Dependency resolution replaced the app's Pydantic release with an older one. Signed content length was not enforced, and the content-disposition header was missing, so those two checks could not be trusted.