Smoke-test matrix

Run smoke tests from the downloaded release media, not only from local build outputs. This catches publishing mistakes as well as installer mistakes.

Installer Media

Platform	File	Basic checks
macOS	`DeepPhe-7.1.dmg`	Mounts, opens `DeepPhe Installer.app`, installs without Gatekeeper errors.
Windows	`DeepPhe_windows-7.1.exe`	Starts with elevation, installs to a no-space path such as `C:\DeepPhe`.
Linux	`DeepPhe_linux-x64-7.1.sh`	Starts with `sh DeepPhe_linux-x64-7.1.sh`, installs to the chosen directory.

Verify downloaded media before testing:

For each platform:

Install from the downloaded media.
Confirm the installer downloads payloads from GitHub.
Confirm <install dir>/.DeepPhe/ exists.
Confirm ~/DeepPheDocs/ exists.
Confirm the current platform's visualizer, data API, and DB-creator binaries are present under .DeepPhe/tools/.
Confirm Unix tool binaries are executable on macOS and Linux.

For each platform:

Open DeepPhe Launcher.
Confirm the GUI starts without a Java or classpath error.
Confirm the example project is listed.
Run the example flow far enough to verify the NLP pipeline, DB creator, data API, and visualizer can be started.
Check .DeepPhe/logs/launcher/, .DeepPhe/logs/deepphe/, and .DeepPhe/logs/viz/ for obvious startup errors.

For each platform:

Run the platform uninstaller.
Leave the DeepPheDocs deletion checkbox unchecked.
Confirm .DeepPhe and the launcher are removed.
Confirm ~/DeepPheDocs/ remains.
Reinstall, then uninstall again with the deletion checkbox checked on a test machine.
Confirm ~/DeepPheDocs/ is removed only when the checkbox is checked.

After running sign-windows-assets.sh, smoke-test each signed Windows payload at least once:

Release tag	Asset
`deepphe-visualizer-v2-7.1`	`deepphe-visualizer-v2-win-x64.exe`
`dphe-data-api-7.1`	`dphe-data-api-win-x64.exe`
`dphe-db-pipeline-7.1`	`DeepPheVizDbCreator-windows-x86_64.exe`

These are single-file bundles. Authenticode signing usually works, but can break payloads that store data in the executable overlay.