Added the S3-compatible adapter alongside the local adapter the project already had, so uploads and deletes go to object storage through the same filesystem interface. Verified offline that the adapter path produces correctly scoped presigned download URLs with the expiry and content-disposition I configured.
- What worked
- Drop-in version compatibility with the already-installed core package meant no constraint juggling. The adapter is the one the host framework documents first, so configuration was a handful of keys. Leaving visibility unset cleanly avoids sending object ACLs, which is exactly what a bucket with ACLs disabled needs, and the error-throwing option made failed writes loud instead of silent.