docs(ts): document pip/Homebrew install and the cants command

- codeanalyzer-ts backend page: lead with an Install section (pip install
  codeanalyzer-typescript / brew) that yields the `cants` CLI; rename binary
  references from codeanalyzer-typescript to cants; note the package-vs-command
  naming; correct the -a row (level 2 = call graph, not CodeQL).
- installing.mdx: add a TypeScript Analysis dependency tab covering the same
  pip/brew install and the cants command.

Author: rahlk

src/content/docs/backends/codeanalyzer-ts.mdx

@@ -34,38 +34,60 @@ Walks the ts-morph AST and indexes all declarations (classes, methods, interface
 
 Both maintain the no-dangling-edges invariant: every call-graph edge endpoint is a real `Callable.signature`.
 
-## Building and running
+## Installing
 
-### Prerequisites
-- **bun** ≥ 1.3, or **Node** ≥ 20
-- **npm** on PATH (to materialize dependencies)
+The fastest way to get the `cants` CLI is from **PyPI** or **Homebrew**. Both ship a prebuilt, self-contained binary for your platform — no Bun or Node is needed to *run* it:
+
+<Tabs>
+  <TabItem label="pip">
+    ```bash
+    pip install codeanalyzer-typescript
+    cants --help
+    ```
+  </TabItem>
+  <TabItem label="Homebrew">
+    ```bash
+    brew install codellm-devkit/homebrew-tap/codeanalyzer-typescript
+    cants --help
+    ```
+  </TabItem>
+</Tabs>
+
+The PyPI package `codeanalyzer-typescript` is also what the CLDK Python SDK depends on to locate this backend — it exposes `bin_path()` to point at the bundled binary.
+
+<Aside type="note">
+The distributable is named **`codeanalyzer-typescript`** (the PyPI package and the Homebrew formula), but the command it installs on your `PATH` is **`cants`** — the analyzer's short binary name. Run `cants`, not `codeanalyzer-typescript`.
+</Aside>
+
+### Building from source
+
+To hack on the analyzer, build it with **bun** ≥ 1.3 (Node ≥ 20 also works to run from source). **npm** must be on PATH to materialize dependencies:
 
-### Install and build
 ```bash
 cd codeanalyzer-ts
 bun install
-bun run build    # → dist/codeanalyzer-typescript (standalone binary)
+bun run build    # → dist/cants (standalone binary)
 ```
 
 Or run from source without compilation:
 ```bash
-bun run src/index.ts -i <project> -a 2
+bun run src/index.ts -i <project>
 ```
 
 ## CLI
 
 The analyzer accepts these command-line options:
 
 ```bash
-codeanalyzer-typescript -i <path> [options]
+cants -i <path> [options]
 ```
 
 | Option | Description |
 |--------|-------------|
 | `-i, --input <path>` | Project root to analyze **(required)** |
 | `-o, --output <dir>` | Write `analysis.json` to this directory; omit to emit compact JSON to stdout (used by the SDK) |
 | `-f, --format <fmt>` | Output format: `json` or `msgpack` (default: `json`) |
-| `-a, --analysis-level <n>` | `1` = tsc resolver call graph + RTA (default); `2` = + CodeQL enrichment |
+| `-a, --analysis-level <n>` | `1` = symbol table + tsc resolver call graph + RTA (default); `2` = call graph |
 | `-t, --target-files <paths...>` | Restrict analysis to specific files (for incremental builds) |
 | `--skip-tests` / `--include-tests` | Skip or include test files (default: skip) |
 | `--eager` / `--lazy` | Force clean rebuild vs. reuse cache (default: reuse) |

src/content/docs/installing.mdx

@@ -128,6 +128,29 @@ The Python SDK can be installed directly from
       ```
       This should output the version of the installed Maven.
   </TabItem>
+  <TabItem label="TypeScript Analysis">
+    For TypeScript and JavaScript analysis, CLDK relies on a companion backend, [`codeanalyzer-ts`](/backends/codeanalyzer-ts/). It ships as a prebuilt, self-contained binary, so you do **not** need Bun or Node installed to run it — just install the `codeanalyzer-typescript` package, which puts a `cants` command on your `PATH`.
+
+    Install it from PyPI:
+
+    ```bash
+    pip install codeanalyzer-typescript
+    ```
+
+    Or with Homebrew:
+
+    ```bash
+    brew install codellm-devkit/homebrew-tap/codeanalyzer-typescript
+    ```
+
+    Verify the installation:
+
+    ```bash
+    cants --help
+    ```
+
+    The package is named `codeanalyzer-typescript`, but the installed command is **`cants`**. To analyze a project's *dependencies* (so library call targets resolve), keep `npm` on your `PATH`; the analyzer materializes `node_modules` automatically (skip with `--no-build`). See the [codeanalyzer-ts backend reference](/backends/codeanalyzer-ts/) for full CLI options.
+  </TabItem>
   <TabItem label="Rust Installation">
     Rustup is the recommended tool for installing Rust and managing its toolchains. It simplifies the process of keeping Rust up to date and allows switching between different Rust versions and toolchains seamlessly.