FLOPPY 1.0.5 (private beta, unsigned) — key backup fixed for containers

Private beta build, unsigned. Fixes a serious problem for anyone running FLOPPY in a container or opening the interface from another machine.

Your key was unreachable. Reveal, Copy and Save all failed silently: the app only returns the key to the machine it runs on, and a browser outside the container arrives from the Docker gateway instead. Now:

• Save the rescue file works from any browser — the app writes the file on its own machine and only the path travels back. In a container it lands in /data (your mounted volume); copy it out with docker cp.
• Reveal, when blocked, tells you where to read the key: docker exec <container> cat /data/engine/seed.hex.
• Confirming the backup now warns you if you never revealed nor saved the key in that window.
• FLOPPY_ALLOW_REMOTE_KEY=1 opts into sending the key over the network. Off by default, on purpose.

If you are already running from an earlier build: read your key now with the docker exec command above and store it. It cannot be recovered if the volume goes.

Install notes and requirements are in the README. SHA-256 in SHA256SUMS.txt.