# HyperTwist Alpha R19 Windows Installer Evidence

## Authority

This directory is the durable evidence index for the first validated
HyperTwist Windows installer above the Release 19 Shipping Alpha payload.

Current operator delivery:

- installer:
  `C:\Users\Anthracite Ace\Downloads\HyperTwist-Alpha-Test-20260723-R19-Setup.exe`
- size: `851049086` bytes
- SHA-256:
  `c31ed6b0b2ae1feb449c27e484d72dc2e07ba220e3cdafa4c3605429d638e0ea`
- Authenticode: `NotSigned`

The unsigned status is an explicit Alpha limitation. Production distribution
still requires a trusted Authenticode certificate and signed-artifact proof.

## Installer Ownership

The NSIS installer owns a per-machine, 64-bit installation with:

- Windows 10 22H2 / Windows 11 and x64 preflight
- a valid Microsoft-signed Visual C++ 2015-2022 x64 redistributable
- the complete `143`-file Release 19 runtime payload
- PDB and debug-manifest exclusion
- a complete SHA-256 payload manifest
- Add/Remove Programs registration
- Start Menu app, readiness, and uninstall shortcuts
- an optional all-users desktop shortcut
- marker-and-registry-gated upgrade and uninstall ownership
- a hard `HyperTwist` install-directory leaf contract
- refusal of unowned non-empty install directories
- user-visible, manifest-aware readiness reporting
- preservation of settings, saves, replays, and diagnostics during uninstall

The prior payload is not cleaned for upgrade until the bundled prerequisite
has succeeded. Failed builds remove incomplete installer output rather than
leaving a corrupt executable at the release destination.

## Validation

The final build passed with:

- NSIS `3.12`
- `0` compiler warnings
- payload files: `143`
- payload bytes: `1585341236`
- exact solver table: `676207080` bytes
- exact solver SHA-256:
  `dc6de3d909a37afe2ba7f1f978543a13eae215bd20d954d66813524a8ca20034`
- source readiness: `ready-with-warnings`
- required readiness failures: `0`
- optional warnings: unsigned desktop code and no active OpenXR runtime

Bounded contract proof also passed:

- all `3` PowerShell scripts parsed on Linux PowerShell and Windows PowerShell
- disposable NSIS contract compilation completed with `0` warnings
- an unsafe install-directory leaf was refused with exit code `13`
- an unowned non-empty `HyperTwist` directory was refused with exit code `14`
- the unrelated sentinel survived and no product registration was created
- manifest traversal input was blocked as `invalid-path:../escape.txt`
- manifest file-count and total-size tampering were blocked
- the interactive readiness wait completed under redirected-input proof

The final lifecycle used a path containing spaces and passed:

- unowned-directory refusal
- first silent install, exit `0`
- first `143`-entry payload hash parity
- Add/Remove Programs and product-registration ownership
- resolved app, readiness, uninstall, and desktop shortcut contracts
- installed readiness with `0` required failures
- stock-Shipping launch diagnostics with runtime initialization
- `0` fatal lines and `0` package-owned listeners
- in-place upgrade, exit `0`
- second `143`-entry payload hash parity
- silent uninstall, exit `0`
- user-data sentinel preservation
- install-root, registration, and shortcut removal
- final owned-process count `0`

The validation class is `isolated-current-host`. No Windows Sandbox, clean
Hyper-V VM, or base VHD was available, so this evidence does not masquerade as
a fresh-machine proof.

## Failure Lineage

`pre-release-shortcut-failure-report.json` records the intentionally rejected
candidate whose readiness shortcut embedded the installing administrator's
temporary path. That report proved first-install payload parity and successful
failure cleanup. The final installer supersedes it with a per-user report path,
manifest-aware arguments, an interactive wait, and resolved shortcut-target
validation.

## Evidence Map

- `windows-installer-build-report.json`: final build and installer identity
- `windows-installer-payload-manifest.json`: complete payload hashes and sizes
- `windows-installer-source-readiness-report.json`: source-host readiness
- `windows-installer-lifecycle-report.json`: final install-to-uninstall proof
- `installed-readiness-report.json`: installed-host and manifest proof
- `installed-runtime.hyperdiagnostics.log`: Shipping runtime initialization
- `installed-first-run-launch.log`: first-run menu launch authority
- `manifest-hardening-positive.json`: full manifest reconciliation proof
- `makensis.log`: final compiler transcript
- `pre-release-shortcut-failure-report.json`: superseded failure lineage
- `post-task-hygiene-report.json`: doctrine-ordered artifact disposition
- `post-task-hygiene-reconciliation-report.json`: duplicate proof and final
  retirement of the formerly protected Windows staging roots

## Remaining External Gates

- trusted Authenticode code signing
- a genuinely fresh Windows VM install and first-launch proof
- entitlement-backed public release URL wiring
- update-channel, rollback, and staged-rollout proof
- real headset/controller observation
- configured-provider, microphone, and audible-TTS observation

## Staging Retirement

The initial hygiene report conservatively retained
`C:\HyperTwist_worktrees\phase10validate` and the package-production roots
because complete duplicate proof had not yet cleared four relative symlinks.
The additive reconciliation report closes that uncertainty.

The follow-up compared `19,789` regular snapshot files, isolated all `4`
symlinks, matched `19,723` files byte-for-byte against the current VPS source,
matched another `28` changed tracked files to committed history, and proved the
remaining tracked differences were strictly superseded. No unique unlanded
source was found.

The current Release 19 package then matched the retained Downloads delivery for
all `145` package files and `1,920,300,068` bytes. The staging ZIP and installer
also matched their retained Downloads copies exactly. This made every artifact
under `C:\HyperTwist_worktrees` redundant, so the whole staging root was
removed while the Release 19 operator deliveries, Release 17 rollback
deliveries, and operator saved data were retained.
