One site bucket on one page (Settings → Media → Buckets → the bucket's name): what it is, which storage profiles use it, what it holds, whether it is healthy, and who changed it. Editing stays on BucketForm; this page links to it.

Nothing is read in mount/3. The bucket, the profiles that use it and its history load in handle_params/3; the contents and the location health scan every location row of the bucket, so they run in start_async. The connection probe writes, reads and deletes a real object, so it runs only when someone clicks Test connection.

A user's own bucket (V206) never opens here: it is loaded through Storage.get_site_bucket/1. A user's storage profile and library are counted, never named.