Document post-release install validation

[chezzof]

Summary

• Adds docs/post-release-validation.md for the public v1.1.1 post-release validation pass.
• Records public GitHub Release asset names, sizes, checksums, extraction/runtime verification evidence, silent installer evidence, executable manifest evidence, non-admin direct-launch behavior, and packaged EII_PYTHON fail-closed probes.
• Links the new validation note from README and release-readiness docs.
• Extends bug and compatibility issue templates so reports identify the release artifact and packaged EII_PYTHON context.

Public download validation

Verified against GitHub Release downloads, not local ui/dist-packaged output:

• Esports.Isolator.PRO.Setup.1.1.1.exe
• Esports-Isolator-PRO-1.1.1-portable.exe
• SHA256SUMS.txt

Checks performed:

• Downloaded public assets with gh release download v1.1.1 --repo chezzof/ultraisolator.
• Recomputed SHA-256 hashes and matched SHA256SUMS.txt.
• Extracted public installer and portable payloads with 7-Zip.
• Verified both extracted payloads contain resources/backend and pass packaged runtime verification.
• Ran the public NSIS installer silently into a temporary user directory; it wrote Esports Isolator PRO.exe, resources/app.asar, resources/backend, and the uninstaller, then uninstalled and removed the temp install root.
• Inspected executable manifests: public wrappers are asInvoker; extracted packaged Esports Isolator PRO.exe requests requireAdministrator in both installer and portable payloads.
• From a non-elevated shell, direct CreateProcess launch of the extracted packaged app failed with Windows error 740 for both installer and portable payloads instead of running partially without Administrator.
• Probed packaged Python policy for missing, relative, PATH-style, and untrusted absolute EII_PYTHON rejection.

First-run coverage

The document includes a manual clean Windows profile first-run matrix for installer and portable paths, wrapper versus packaged-app Administrator behavior, SmartScreen caveat, trusted absolute EII_PYTHON, and safe support evidence. The PR does not silently approve UAC or run the unsigned Administrator-level app with elevated privileges on a maintainer machine.

Support/debug path

Bug and compatibility templates now ask for:

• release artifact used;
• Python version plus packaged EII_PYTHON context;
• existing Administrator, background-jailing, game, anti-cheat, and log/redaction context.

What did not change

• No runtime behavior changes.
• No UI redesign.
• No backend/server changes.
• No Electron security boundary changes.
• No config schema or tuning logic changes.
• No dependency updates.

Verification

• gh release view v1.1.1 --repo chezzof/ultraisolator --json tagName,name,isDraft,isPrerelease,targetCommitish,assets,url
• Public release asset download and SHA-256 verification with Get-FileHash -Algorithm SHA256
• Public installer/portable 7-Zip extraction plus packaged runtime verification
• Public NSIS silent install into a temporary user directory, expected payload inspection, silent uninstall, and temp-root cleanup check
• Public wrapper and extracted packaged app executable manifest inspection
• Non-elevated direct CreateProcess probe against extracted packaged app executable returned Windows error 740 for both installer and portable payloads
• Packaged EII_PYTHON rejection probe for missing, relative, PATH-style, and untrusted absolute values
• npm.cmd --prefix ui ci
• python -m unittest tests.test_react_frontend -v
• python -m unittest discover -s tests -p "test_*.py" -v
• powershell -ExecutionPolicy Bypass -File scripts\verify.ps1
• npm.cmd --prefix ui run build:renderer
• npm.cmd --prefix ui run smoke
• git diff --check