fix(docs): restore install doc corrections lost in #213 merge

#219 replaced just install with clawdie binary commands but #213
merge (0aeebee) overwrote controlplane-install.md, index.md, and
requirements.md — restoring the corrected versions from f60aca1.

docs/guide/install/controlplane-install.md

@@ -1,24 +1,23 @@
 ---
 title: 'Control Plane Install'
-description: Install the Clawdie control plane with the standard orchestrator.
+description: Install the Clawdie control-plane host service with the clawdie binary.
 ---
 
-The control plane is installed by the standard orchestrator:
+The control plane runs as the host-managed `clawdie` service (`colibri-daemon`),
+provisioned by the `clawdie` binary:
 
 ```bash
-just install
+cargo build -p clawdie --release
+clawdie apply --yes
 ```
 
-The root install runs the control plane as the host-managed Clawdie service.
-The orchestrator configures PF, worker jails, PostgreSQL, hostd, service
-installation, checkpoints, and resume state together.
+This installs the storage datasets, the `clawdie` service user, and the rc.d
+(FreeBSD) / systemd (Linux) unit that runs `colibri-daemon`. Preview first with
+`clawdie plan`; `apply` is a dry-run until you pass `--yes`. See
+[Install](./install/) for the full command set, storage strategy, and safety
+notes.
 
-If an install fails, resume from the failed step:
-
-```bash
-just install-from-db
-just install-from hosts
-just install -- --dry-run
-```
-
-The canonical Bastille/Warden bridge name is `warden0`.
+> **Scope.** This provisions the control-plane host service only. PF egress,
+> worker jails, PostgreSQL, and the CMS/web service were handled by the legacy
+> clawdie-ai `just` + Ansible orchestrator and are not yet part of the colibri
+> installer. The canonical Bastille/Warden bridge name remains `warden0`.

docs/guide/install/index.md

@@ -21,5 +21,5 @@ Use this path for a new machine or a reinstall from boot media.
 Use this path when FreeBSD 15.x is already installed and you manage the host.
 
 - [Requirements](./requirements/) — host, runtime, and toolchain requirements.
-- [Install orchestrator](./install/) — run `just install` and resume failed steps.
+- [Install](./install/) — provision the host service with the `clawdie` binary (`clawdie discover` / `plan` / `apply --yes`).
 - [Fresh install checklist](./fresh-install-checklist/) — verify the completed install.

docs/guide/install/requirements.md

@@ -5,7 +5,7 @@ description: Host, runtime, and toolchain requirements for Clawdie.
 
 What you need on the host before installing Clawdie. The ISO installer
 provisions most of this automatically; existing-host installs should verify
-these requirements before running `just install`.
+these requirements before running `clawdie apply`.
 
 ## Host
 
@@ -18,13 +18,15 @@ these requirements before running `just install`.
 
 ## Toolchain
 
-- **Rust** via rustup, installed under `/opt/clawdie/rustup`.
-  Required for native dependencies (SWC, tree-sitter). The ISO
-  installs this; existing-host installs run it from
-  [`Install orchestrator`](./install).
-- **Node.js + tsx** for the install scripts and runtime.
+- **Rust** (Cargo) — the colibri control plane and the `clawdie`
+  installer are a Cargo workspace. Build the installer with
+  `cargo build -p clawdie --release`. See [Install](./install/).
 - **Bastille** for jail management.
 
+> The legacy clawdie-ai `just` + Node/`tsx` orchestrator is not used in this
+> repo; the sections below still describe the clawdie-ai product runtime and are
+> being reconciled to the colibri model.
+
 ## Runtime philosophy
 
 Clawdie is a single Node.js process that orchestrates jailed