HyperSnatch v1.6.12 — Critical Packaged UI Interaction Hotfix

HyperSnatch v1.6.12 — Critical Packaged UI Interaction Hotfix

This hotfix repairs the packaged UI being inert (window opened, but no control responded). It supersedes v1.6.11.

What was wrong

The Content-Security-Policy in the packaged build used script-src 'self', which blocked the inline renderer <script> in the UI from executing. Renderer state never initialized, no event listeners attached, and the whole UI was unresponsive.

Fixes

• CSP: script-src now allows 'unsafe-inline' so the inline renderer initializes in the packaged build (emergency compatibility patch).
• Missing require: added require('./core/security/sovereign_auth') that was causing a ReferenceError in the get-app-info IPC handler.
• Null-guards: optional window/license controls (btnWinMinimize/Maximize/Close, btnImportLicense) no longer throw before renderer init when absent.
• Branding preserved: The Proof Foundry™.

Verified through the actual installer

• Visible window (MainWindowHandle != 0), title HyperSnatch — The Proof Foundry™
• v1.6.12 shown everywhere
• getAppInfo OK, getForensicSnapshot success
• A real UI click produces a visible state change

Downloads

• HyperSnatch-Setup-1.6.12.exe — Windows installer
• HyperSnatch_Vanguard_v1.6.12.zip — release bundle

SHA256

HyperSnatch-Setup-1.6.12.exe      9ef2035a305e2fe95fed43351bca15d4c28a4c607e97cb373b89ece60e92feb4
HyperSnatch_Vanguard_v1.6.12.zip  b748daecf5d7bf4b3a07116ae90e5cbefd2c6211d5cecb602a1c841dbc536692

Verify:

Get-FileHash .\HyperSnatch-Setup-1.6.12.exe -Algorithm SHA256

Full proof record: docs/release/RELEASE_PROOF_v1.6.12.md.

Security follow-up

'unsafe-inline' is an emergency compatibility patch. A separate hardening lane will move the inline renderer JS into a packaged .js file and restore script-src 'self'.