UUI Py 1.0.0.4 - this build
===========================
1. Updated various dead links
2. Safer drive targeting for Prepare, Wipe Disk and OS Image
   - A drive fingerprint (disk, size, model, serial/WWN, partition signature,
     bus) is taken when you confirm and re-checked by the worker right before
     anything is written. It works on drives that have no serial number, and a
     mismatch stops the job.
   - The worker itself refuses the running-from / system disk, and refuses to
     erase a drive that is not a UUI/YUMI drive when the job is a wipe.
   - Linux: the same-disk pin - size, serial, WWN and partition-table id are
     re-checked inside the root script after the sudo prompt.
   - The second "are you sure" for a disk is skipped only when it is positively
     on a USB bus (UASP USB SSDs count as USB); any other bus still asks.
   - Update: the partition table is read before and after, and a changed layout
     is reported.
   - Disk identity, size and layout are read directly from Windows (no
     PowerShell needed), with PowerShell/WMI kept as a fallback.
3. Prepare / Update options moved into a window
   - The "Boot Prep Options" box is gone from the Step 1 sidebar. Prepare Drive
     opens a window with the drive, the erase warning, the filesystem, the
     reserved space (slider, presets, room-for-ISOs estimate) and Secure Boot.
   - Update opens the same kind of window with installed vs. bundled version
     and the Secure Boot choice (it applies to updates too).
   - Drives that are not removable USB need the device name typed to confirm.
   - Filesystem and reserved space are remembered; Secure Boot starts at its
     default every time. Linux always formats exFAT.
   - Cancel changes nothing.
   - UUI Drive Options now shows the bootloader version on a prepared drive
     (read in the background, never during a job). "Update" is a button shown
     only when the drive's copy is older than the bundled one; otherwise a
     "Reinstall / Secure Boot..." link opens the same window to repair the
     bootloader or switch Secure Boot support on or off. If the version can't
     be read there is no Update button, only Retry and the reinstall link.
   - Added tests/ (hardware-free: python3 -I -m unittest discover -s tests).
4. Step 2 is now an invitation, not a to-do
   - A drive that isn't set up shows a soft card: "This drive isn't set up for
     UUI", what UUI can do, an "If you set it up" outline and the erase notice.
     It says choosing another drive is fine, and nothing changes until you
     confirm in the window that opens.
   - If the drive already holds files, or isn't removable USB, the card says it
     may not be the one you want, and the Prepare button is outlined instead of
     filled. The button reads "Prepare this drive..." (the dots mean a window
     follows).
5. One look across the app
   - Shared card, heading (small blue step label + bold title) and primary
     button, used on every tab and dialog: Install steps 1-4, Add Multiple,
     Manage Installed, OS Image, Test Boot, About, the Prepare / Update window,
     the Windows edition chooser and the first-run disclaimer.
   - Each tab's main action is the filled button (Create, Add All to Drive,
     Test Boot Selected ISO, Install OS Image, Accept, OK). Erase and prepare
     is red. A disabled primary button turns flat gray-blue.
   - Remove Selected (Manage Installed) stays a plain button on purpose: it is
     destructive and not a "next step".
   - The outlined Prepare button now has a light-blue fill (it was white until
     hovered, which didn't look like a button).
   - OS Image tab is shorter: the status and Install button share one row, the
     boot choices and Apply share one row, and the Windows admin note and the
     auto-start explanation are shorter / tooltips. An installed OS shows in
     dark green.
   - Wipe Disk is a button with a confirmation window (red "Wipe drive"), not a
     checkbox that fires when ticked.
   - Status chip beside Step 1: Prepared / Not set up / Protected.
   - Finish card tinted by outcome, with next steps (Add another / Add a
     distro, Open drive, Eject).
   - Plain-words phases and an elapsed timer while Prepare / Update / Wipe /
     OS Image run.
   - Sliders (reserved space, persistence size) have a visible track and a
     thin outline instead of a near-white one.
   - One job at a time, enforced: while anything runs the drive picker is locked
     (the status chip reads "Working..."), Prepare, Install OS Image and Remove
     Selected are disabled, and starting a second job is refused with a message.
     An Add Multiple run keeps sending every file to the drive it started on.
   - All buttons are one rounded, flat button: solid blue for the main action
     (red when it erases), soft blue for an optional one, and a white face with a
     thin light outline for the rest (red text for Wipe Disk and Remove Selected).
     Hover, pressed, focus and disabled states are drawn, and it looks the same
     on Windows and Linux.
   - Adding one ISO or downloading one distro goes through the Add Multiple
     queue, so you can keep adding while it runs; each queue row has its own Stop.
6. Prepared drives are locked against erasing
   - After a successful Prepare or Update, UUI writes a small UUIDRV file in the
     drive's main partition (unless a UUIDRV, YUMIDRV or APPND file is already
     there). Prepare and Wipe Disk refuse a drive that has one. Update, Reinstall /
     Secure Boot, and adding or removing ISOs still work.
   - Wipe Disk is greyed out for a locked drive. Hovering it says: "Wipe Disk is
     turned off because this drive has a UUIDRV file in its main partition. Delete
     the UUIDRV file to turn it back on." Deleting the file is how you erase the
     drive on purpose.
   - UUIDRV is used rather than APPND because APPND is also the OS Image state
     file; a bare APPND on every drive would make the OS Image tab report a broken
     install. A drive that holds only the UUIDRV lock still shows as "Prepared" (no
     "Protected" chip or "[protected]" tag); "Protected" stays for the running
     system, a drive holding an installed OS image, and a drive that isn't prepared.
   - Drives prepared by an older build get the file the next time you run Update.
     A drive organized by another tool (the YUMI-style folder) is left as it is.
     If the file can't be written, the log says so and the Prepare / Update still
     succeeds.
7. Linux build scripts
   - build-manylinux2014.sh now produces uui_py-<version>-legacy (and the
     .tar.xz) as it reports; the container previously built uui_py-<version>.
   - The two Linux build scripts no longer share a cache: the container uses
     .pybuild-manylinux/ and .venv-manylinux/, build-onefile.sh keeps .pybuild/
     and .venv/. Tcl bakes in its build folder (/io in the container), so a shared
     one made the normal build fail with "Can't find a usable init.tcl".
   - Both scripts now reject a cached toolchain that was built for another path
     and rebuild it from scratch; build-onefile.sh also points TCL_LIBRARY /
     TK_LIBRARY at its own Tcl/Tk inside the venv.
   - Neither script deletes the other's output in dist/ and build/.
8. Version bumped to 1.0.0.4.

