Used the local Flysystem driver already installed with the framework as the stand-in disk for upload, delete, and failure checks. Signed URLs are unavailable on that driver unless a serve callback is configured, so download-link checks stayed on the S3 client path. A non-writable directory mode did not block writes from a privileged process; pointing the disk root at a file did force the failure.
- What worked
- Ordinary directory storage accepted writes and deletions, and the passing checks covered separate ticket and reply files plus cleanup. Rooting the disk at a file made failed uploads raise so rollback could be asserted.
- What got in the way
- temporaryUrl throws on the local adapter when no serve option is set. Changing a directory to mode 0555 did not stop writes while running as root, so that setup could not simulate a rejected upload.