Help me set up AxolDB 0.1.0-developer-preview on my Windows x64 computer. You need terminal access to this computer. Work step by step and report only what you actually verify.

Before setup, confirm that I personally accepted the applicable terms and downloaded the Windows package from https://axoldb.com/downloads/. If not, ask me to do that there. Do not accept any license, request a download grant or bypass the download authorization for me.

Use this versioned guide: https://axoldb.com/documentation/setup/0.1.0-developer-preview/
Support/evidence boundaries: https://axoldb.com/documentation/release-status/

1. Identify the actual Windows OS and OS architecture. This package is Windows x64, not ARM or macOS. Locate my downloaded archive, or ask only for its path if unavailable. Expected filename: axoldb-0.1.0-developer-preview-win-x64-security-r2-crt-final-r1.zip (474513388 bytes). Before running ANY packaged executable, calculate SHA-256 with Get-FileHash and compare with both the versioned official metadata at https://axoldb.com/releases/0.1.0-developer-preview/SHA256SUMS and this pinned value: 670a006a41cb6fd49fa18cf81aa5038ba64c7f69d8d72e3b53cbf7a9cfc52949. Stop on any mismatch, incomplete download or unexpected package identity.

2. Check the actual host prerequisites. The archive contains the product runtimes, PostgreSQL 16.15, app-local ICU and CRT dependencies. Do not require a development SDK, a separate .NET install, Docker or system PostgreSQL. Native Studio additionally needs Microsoft Edge WebView2 Evergreen and a suitable graphical session. Check for it without silently installing anything. Explain a missing system dependency and obtain my specific permission before installing it. Run as the normal non-elevated owner; do not use an Administrator workaround.

3. Extract the verified complete archive safely into a NEW user-owned program directory, rejecting unsafe archive paths. Choose a NEW, separate absolute instance root under my user application-state directory, with a unique name, and a NEW client connection name. Never reuse the default instance or overwrite an existing install, profile or data directory. Record the chosen paths. If owner-only storage protection fails, stop and explain; do not weaken ACLs.

4. After verification/extraction, inspect the packaged CLI help before using commands. Set $Bundle and $Instance to those exact absolute paths, and $Axol to Join-Path $Bundle 'bin\axol.exe'. Use the documented --local server status/start/trust commands with BOTH --bundle-root $Bundle and --instance-root $Instance and --output json. Start only the new intended instance; Ready alone is not successful setup. Read its non-secret config\server.json for publicHttpsPort and instance identity. Keep the listener loopback-only.

5. Follow the guide's CLI-first connection/bootstrap procedure: create unique safe connection metadata using connection add, the actual https://localhost:<publicHttpsPort> endpoint and the public CA exported by server trust through --ca-file. Keep hostname and certificate verification enabled. Bootstrap requires a private interactive terminal: give me the exact non-secret commands for this instance and ask me to supply the one-time assertion there, outside your transcript. Never run a secret reveal into captured output, request a token/assertion in chat, read private keys, or silently regenerate a consumed delivery. Preserve the bootstrap request ID on an uncertain outcome; do not retry with a new identity blindly.

6. Continue after that step and prove authenticated public reading with credential list --connection <the-new-profile> --output json, then connection test <the-new-profile> --output json and require authentication: succeeded. Do not confuse --local reads, liveness, Ready or a friendly profile name with authenticated access. Do not create example Populations or grant broad permissions just to pass setup.

7. If WebView2 and a graphical session are available, open the same instance with --local studio --bundle-root $Bundle --instance-root $Instance. Follow the guide for private Studio connection/credential input; the CLI credential store is separate from Studio. If you cannot perform a GUI or secret-input action, give me one short precise private step, then resume what you can verify. Never claim you observed a human action you did not observe. Without GUI, report CLI success and Studio not opened.

8. Finish with the install path, exact instance root/ID, localhost endpoint, client profile name, observed authenticated-read result and any pending human step. Give the exact restart/status commands for the SAME roots and the documented safe stop command: & $Axol --local server stop --bundle-root $Bundle --instance-root $Instance --output json. Closing Studio does not stop Server. Do not stop unrelated instances, kill arbitrary processes, delete data, open public ports, disable TLS verification or perform uncontrolled sudo/admin actions.

Operator 0.1.5 is optional guidance only: https://axoldb.com/documentation/agent-skills/ . Do not require or modify a Skill to complete this setup.