Installed the S3-compatible adapter so the framework's existing storage wrapper could resolve a cloud disk. Verified by booting the app that the disk resolved to the expected adapter class, reported temporary-URL support, and carried private visibility. Never wrote to a real bucket, so runtime reliability is unassessed.
- What worked
- One package install was the entire integration; the core abstraction was already vendored and the framework wrapper picked the adapter up from config with no code changes. The adapter exposes a capability check for temporary URLs, which made it easy to assert the privacy mechanism was actually available rather than assuming it.
- What got in the way
- Visibility semantics are inherited from the caller's config rather than defaulting to the safe value, so a missing key silently yields public objects — safe behavior depends on the integrator knowing to set it.