MZI Desktop Host 0.8 for Windows x64

Recommended installation:
- Download mzi-host-windows-x64-setup.exe from mzi.app/downloads.
- Run it once. It installs only for the current user and does not require admin access.
- Double-click a signed .mzi application to open it in MZI Host.
- Use "Check for host updates" inside the native window to verify the Ed25519-signed beta feed.
- `mzi dev . --launch` keeps one Host 0.8 process open and reloads validated revisions in place.
- Remove it later from Windows Settings > Apps > Installed apps.

The beta setup is not code-signed yet, so Windows SmartScreen can display a warning.
Automatic update installation remains disabled until code signing is available.
The ZIP remains available as a portable option and makes no system changes.

This archive contains:
- mzi-host-windows.exe: native Win32 MZI application host
- mzi-component-runner.exe: Wasmtime Component Model runtime
- field-notes.mzi: the exact migratable-state package used by Browser Host
- capability-clock.mzi: Application 0.4 host-owned wall-clock proof
- capability-http.mzi: Application 0.5 authorized HTTP host-task proof
- benchmark.json: reference timings produced by the hostcore test harness

Run:
1. Keep both executables and field-notes.mzi in the same directory.
2. Start mzi-host-windows.exe.
3. Review the package authority prompt.
4. Choose Yes to open the application.

You can also drag a different application-profile .mzi path onto the executable
or start it from a terminal:

  mzi-host-windows.exe path\to\application.mzi

Current security boundary:
- ZIP structure and declared paths are validated.
- Package identity is SHA-256 of the complete archive.
- Ed25519 verifies the canonical payload and binds stable state to a publisher key.
- Clock imports and HTTP tasks are denied unless the manifest declares matching authority.
- Relative HTTP tasks resolve against the signed distribution origin; redirects, credentials and responses above 256 KiB are rejected.
- Component actions run through typed WIT bindings with fuel and a host deadline.
- Application state is stored under a stable application key across package updates.
- Declared migrations execute inside Wasmtime after a versioned backup is created.
- Development reload accepts code and interface changes but refuses publisher, storage, WASI or capability changes without a new review.

The included signature uses a public development fixture key; this is not production software.
