feat(setup): add unshackle setup command and cross-platform install scripts

setup downloads the external tools, writes a first config and imports CDM devices; install.sh and install.bat bootstrap uv and run it.

docs/guide/cli-reference.md

@@ -5,12 +5,16 @@ A complete reference for every `unshackle` command, subcommand, and flag. This p
 - **[`dl`](#dl)**: the download pipeline (the command you use most).
 - **[`search`](#search)**: find titles on a service.
 - **[`import`](#import)**: rebuild a download from an export file.
+- **[`setup`](#setup)**: install the external tools and make a first config.
 - **[`cfg`](#cfg)**, **[`env`](#env)**: manage configuration and the environment.
 - **[`kv`](#kv)**: Key Vault operations.
 - **[`wvd`](#wvd)**, **[`prd`](#prd)**: Widevine / PlayReady device management.
 - **[`serve`](#serve)**: operate the local CDM and REST API server.
 - **[`util`](#util)**: helper media utilities.
 
+!!! note "Running commands from a clone"
+    This page uses the bare `unshackle` command. From a git clone, the recommended install, run each command as `uv run unshackle ...`.
+
 !!! tip "Getting help on any command"
     Every command accepts `-h`, `--help`, or `-?`. For example `unshackle dl --help` or `unshackle wvd new --help`. Each service defines its own arguments for `dl` and `search` (such as a title ID or a query), so examine `unshackle dl SERVICE --help` for those.
 
@@ -268,6 +272,24 @@ The export file can be a `mediaexport` file from `dl --export`, an export from a
 
 ---
 
+## `setup`
+
+Install the external tools and make a first config.
+
+```
+unshackle setup
+```
+
+The command takes no options and asks its questions at the prompt. It shows the missing [external tools](../getting-started/installation.md#external-tools-on-your-path) and downloads the ones you accept. It puts them in a `binaries` folder, in the package folder of a git clone or in your user data directory for a `uv` tool install. If no `unshackle.yaml` exists, it writes a first one: inside the clone, or to your user config directory for a `uv` tool install. It then makes the data folders and imports `.wvd` and `.prd` devices, one file or folder per answer, until you give an empty answer. It ends with a summary of the tools, the path of a config that it wrote, and a pointer to `env check`. You can run it again: it skips the tools it finds and never overwrites a config. [Installation](../getting-started/installation.md#what-unshackle-setup-does) gives the full steps and where each file goes.
+
+!!! example
+    ```shell
+    uv run unshackle setup   # from a git clone
+    unshackle setup          # from a uv tool install
+    ```
+
+---
+
 ## `cfg`
 
 Read, set, delete, or show configuration values in `unshackle.yaml` without hand-editing YAML.
@@ -312,7 +334,7 @@ unshackle env COMMAND [ARGS]...
 unshackle env check
 ```
 
-Prints a dependency table (Category / Tool / Status / Required / Purpose) that shows which external tools unshackle finds on your `PATH`. It also gives a summary of how many required tools are present.
+Prints a dependency table (Category / Tool / Status / Required / Purpose) that shows which external tools unshackle finds on your `PATH`. It also gives a summary of how many required tools are present. If a required tool is missing, it tells you to run [`unshackle setup`](#setup).
 
 | Category | Tools |
 |---|---|

docs/guide/downloading.md

@@ -148,8 +148,8 @@ unshackle dl -q 2160 -r HDR10,DV EXAMPLE '...'
 !!! warning "HYBRID requires dovi_tool"
     `-r HYBRID` makes a single hybrid track by injecting the Dolby Vision RPU
     metadata onto an HDR10/HDR10+ base layer with **dovi_tool**.
-    It requires the `dovi_tool` binary, resolved from unshackle's `binaries/` folder or
-    your `PATH`. The normal case is a DV track plus an HDR10 or HDR10+ base. With HDR10+
+    It requires the `dovi_tool` binary, resolved from unshackle's `binaries/` folder,
+    the `binaries` folder of your user data directory, or your `PATH`. The normal case is a DV track plus an HDR10 or HDR10+ base. With HDR10+
     and no DV, unshackle converts the HDR10+ metadata to DV instead, which also needs
     `hdr10plus_tool`. With no DV and no HDR10+, the title fails.
     When HDR10+ is present, unshackle prefers it over HDR10 as the base layer.

docs/guide/drm-and-cdm.md

@@ -407,8 +407,8 @@ encrypted file (for Widevine, PlayReady, and ClearKey-CENC):
 - **shaka-packager** is the default.
 - **mp4decrypt** is part of the Bento4 tools.
 
-Both must be discoverable in unshackle's bundled `binaries/` directory or on your
-`PATH`. If the selected tool's binary is missing at decrypt time, unshackle raises an
+Both must be discoverable in unshackle's bundled `binaries/` directory, the
+`binaries` folder of your user data directory, or on your `PATH`. If the selected tool's binary is missing at decrypt time, unshackle raises an
 "executable not found but is required" error. See [dependencies](../getting-started/installation.md) for
 installation.
 

docs/guide/troubleshooting.md

@@ -241,7 +241,7 @@ Each command reports how many files it removed and how much space it freed, then
 !!! example "A required tool is missing"
     **Symptom:** decryption, muxing, or analysis fails early, sometimes with a "binary not found" style error.
 
-    **Inspect:** use `unshackle env check` and look for a red `✗` on a **required** row. Install the missing tool and re-run.
+    **Inspect:** use `unshackle env check` and look for a red `✗` on a **required** row. Run `unshackle setup` to install it, or install it by hand, and re-run.
 
 !!! example "Decryption produces garbage or fails"
     **Symptom:** the download completes but the file will not play, or the decrypt step errors.