Help me set up AxolDB 0.1.0-developer-preview on my Linux x86-64 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 product terms and downloaded the Linux package from https://axoldb.com/downloads/. If not, ask me to do that there. Do not accept a 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 distribution/version and architecture with /etc/os-release and uname -m. The package is linux-x64 for x86_64, not ARM, macOS or a Windows executable. The recorded Linux CLI/Server evidence covers Fedora 44, Ubuntu 26.04.1 and Debian 13.7; do not assume another distribution/version, WSL or a desktop is qualified. Explain any different context before proceeding. Locate my downloaded archive, or ask only for its path. Expected filename: axoldb-0.1.0-developer-preview-linux-x64-security-r2.tar.gz (134942458 bytes). Before running ANY packaged executable, calculate sha256sum and compare with both https://axoldb.com/releases/0.1.0-developer-preview/SHA256SUMS and this pinned SHA-256: ec66d658f5630c4136908d8fba07782f4eefdd71d68052b8311dbaf69f995db4. Stop on mismatch, incomplete download or unexpected package identity.

2. Check actual system/runtime prerequisites using the shipped runtime metadata and existing host inspection tools. The bundle includes the .NET runtime and PostgreSQL 16.15; do not require a development SDK, Docker or a separate PostgreSQL installation. The packaged PostgreSQL runtime baseline is glibc 2.36 or newer; this is not proof that every other product dependency is present. Inspect dynamic library availability for the packaged apphost and PostgreSQL. Native Studio additionally needs a graphical session, GTK 3 and WebKitGTK 4.1 (2.40 or later). Do not invent a universal distro package list. Explain each missing dependency and obtain my specific permission before installing it. Work as the normal owner, not root.

3. Safely extract the complete verified tar.gz into a NEW user-owned program directory, preserving executable bits and valid in-tree links and rejecting traversal/unsafe links. Do not overwrite an existing install. Choose a NEW, separate absolute instance root below my user state directory with a unique name and a NEW client connection name; never reuse the default instance. Record paths, and verify bundle-manifest.sha256 with sha256sum --check from the extracted root. Do not weaken owner-only permissions or use chmod 777 to fix a failure.

4. Inspect packaged CLI help before composing commands. Let bundle and instance be those exact absolute paths and axol="$bundle/bin/axol". Use "$axol" --local server status/start/trust with BOTH --bundle-root "$bundle" and --instance-root "$instance" and --output json. Start only this new intended instance; Ready alone is not successful setup. Read non-secret config/server.json for publicHttpsPort and instance identity. Keep listeners loopback-only.

5. Follow the guide's CLI-first connection/bootstrap procedure: connection add with a unique name, actual https://localhost:<publicHttpsPort> endpoint and --ca-file pointing to the public CA exported by server trust. Keep hostname/chain verification enabled. Bootstrap needs 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. Do not reveal secrets in captured output, ask for tokens/assertions in chat, read private keys or regenerate a consumed delivery. On an uncertain bootstrap outcome, preserve the original request identity and use documented outcome resolution rather than blindly retrying with a new one.

6. Resume and prove authenticated public reading with "$axol" credential list --connection <the-new-profile> --output json. Also run connection test <the-new-profile> --output json and require authentication: succeeded. A --local read, liveness, Ready or a profile name alone does not prove this. Do not populate a database or grant broad permissions just to pass setup.

7. If a suitable graphical session and Studio libraries exist, open the SAME instance with "$axol" --local studio --bundle-root "$bundle" --instance-root "$instance". Follow the guide's private Studio connection/credential step; the CLI store is separate from Studio. If a GUI or secret-entry action is unavailable to you, give me one short precise private action and then continue what you can verify. Do not claim an unobserved human action happened. On a headless host, report CLI success and Studio not opened; do not install a desktop or change X/Wayland access automatically.

8. Finish with installation path, exact instance root/ID, localhost endpoint, new profile name, authenticated-read result and any pending human step. Give exact same-root start/status commands and safe stop: "$axol" --local server stop --bundle-root "$bundle" --instance-root "$instance" --output json. Closing Studio leaves Server running. Never delete existing data, stop unrelated instances, kill arbitrary PIDs, open public ports, bypass TLS 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.