Draw2D 1.0.6

Never ship a package with the runtime missing from it

The 1.0.6 Windows job failed, and the failure was the lucky part.

windeployqt has no --no-virtualkeyboard option in Qt 6.8. Given one it does
not know, it printed "Unknown option" and deployed nothing at all — no Qt
DLLs, no platform plugin. PowerShell does not stop on a native command's
exit code, so packaging carried on and produced a 9.8 MB zip where a real
one is 66 MB: something that looks like a package and cannot start. It only
failed at the very end, when the shell finally propagated the exit code. A
slightly different script would have published it.

So the option is gone — the sweep that removes Qt Virtual Keyboard never
needed it — windeployqt's exit code is now fatal, and both platforms check
what is actually in the package before zipping it: the executable, the Qt
libraries, the platform plugin, the DWG converters and the licence notices,
plus a floor on the total size. A deploy tool that half-ran is caught by the
box being wrong, not by the tool claiming success.

macOS had the same shape of hole — macdeployqt || true swallows a failed
deploy — and now has the same check.

Verified by running the guard against a bundle with no Qt (refused), one
with no licences (refused), and the real one (passed).

Nothing broken reached anyone: the publish job never ran, and 1.0.5 is
still the current release.

Co-Authored-By: Claude Opus 5 noreply@anthropic.com