A volume attachment connects a cloud storage resource to an instance through a supported attachment path. The control-plane record isn't a filesystem mount. The guest still needs the appropriate device and filesystem handling, and the application needs its own access and consistency checks.
The original tasks use paravirtualized local attachments with explicit read-only intent. They require the supplied instance and volume to share an Availability Domain. The checker distinguishes the intended identifiers from another instance or attachment. The browser doesn't contact a device, run guest commands or flush application buffers. Before a real detach, the operator needs a safe quiescence and unmount plan; after attachment, validate the actual data and business operation.
Keep attachment state, guest mounts and application behavior as separate outcomes.