OpenServer 0.2: the provider says how to install its CLI (#171)

A directory that lists a host's plans is asked the next question at once:
how do I drive this thing from a terminal? Every provider answers it on a
page of its own, in its own words, and a reader that wants the install line
has to find and read that page for each host. nichedb.dev's hosting
collection just did exactly that for 46 providers, copying the commands
off each vendor's guide, and the exercise is the argument for putting the
facts in the descriptor.

`provider.developer` names the official CLI, its install commands keyed by
package manager and copied as the guide prints them, the install guide and
source, the API docs, the Terraform provider and the GitHub organisation. A
provider with no CLI says `"cli": null`, which is a fact, while a missing
block means unknown. Commands are copied, never composed: a reader that
invents `brew install <name>` sends a buyer to a formula that may not exist.

c0mpute.md gains the same block for the compute market, with the one
install line c0mpute.com prints, and the landing page says what 0.2 adds.


Claude-Session: https://claude.ai/code/session_01Khk1C6Ese6xjdHAWLVstca

Co-authored-by: Claude Fable 5.1 <noreply@anthropic.com>

apps/logicsrc-web/src/app/openserver/page.tsx

@@ -105,10 +105,14 @@ export default function OpenServerPage(): ReactNode {
           reader agrees on, so an offer can be found instead of scraped.
         </p>
         <p style={{ color: "#5b6b7a" }}>
-          Status: 0.1. It covers cloud, VPS, dedicated and bare-metal servers, colocation,
+          Status: 0.2. It covers cloud, VPS, dedicated and bare-metal servers, colocation,
           hardware for your own premises, shared and managed hosting, platforms, functions,
-          storage, GPU, edge and peer-to-peer markets. The first directory reading it is the hosting
-          collection at <a href="https://nichedb.dev/c/hosting">nichedb.dev</a>.
+          storage, GPU, edge and peer-to-peer markets. Since 0.2 the provider also says how a
+          developer drives it: the official CLI with its install commands as the vendor's own guide
+          prints them, the API docs, the Terraform provider and the GitHub organisation. The first
+          directory reading it is the hosting collection at{" "}
+          <a href="https://nichedb.dev/c/hosting">nichedb.dev</a>, which lists every host with a CLI
+          at <a href="https://nichedb.dev/f/hosting-cli">/f/hosting-cli</a>.
         </p>
       </div>