docs-site: annotate imperative SQL, add section anchor, drop ClickHouse

- Wire numbered red badges to each problematic span in the "Without KTX"
  SQL with hover sync between SQL gutter, lines, and the notes list.
- Add #imperative-vs-declarative anchor on the flow section header so
  the eyebrow link is shareable; reveals a # glyph on hover/focus.
- Align the compiled-SQL note dots to the first-line midpoint
  (mt-[6px] instead of mt-1) so 4px dots sit at y=8 in a 16px line.
- Remove all ClickHouse references from docs-site (primary-sources,
  quickstart, ktx-setup, contributing, agents-setup, mechanics test,
  warehouse drivers in the flow diagram).

docs-site/content/docs/integrations/primary-sources.mdx

@@ -1,6 +1,6 @@
 ---
 title: Primary Sources
-description: Connect KTX to PostgreSQL, Snowflake, BigQuery, ClickHouse, MySQL, SQL Server, or SQLite.
+description: Connect KTX to PostgreSQL, Snowflake, BigQuery, MySQL, SQL Server, or SQLite.
 ---
 
 KTX connects to your data warehouse or database to build schema context,
@@ -26,9 +26,9 @@ Agents should prefer environment or file references over literal secrets.
 
 | Field | Required | Applies to | Description |
 |-------|----------|------------|-------------|
-| `driver` | Yes | all connections | Connector driver such as `postgres`, `snowflake`, `bigquery`, `clickhouse`, `mysql`, `sqlserver`, or `sqlite` |
+| `driver` | Yes | all connections | Connector driver such as `postgres`, `snowflake`, `bigquery`, `mysql`, `sqlserver`, or `sqlite` |
 | `url` | One of the connection methods | URL-style connectors | Database URL, `env:NAME`, or `file:/path/to/secret` |
-| `host`, `port`, `database`, `username`, `password` | One of the connection methods | PostgreSQL, MySQL, ClickHouse, SQL Server | Field-by-field connection values |
+| `host`, `port`, `database`, `username`, `password` | One of the connection methods | PostgreSQL, MySQL, SQL Server | Field-by-field connection values |
 | `schema` or `schemas` | No | schema-aware warehouses | Single schema or list of schemas to scan |
 | `context.queryHistory` | No | PostgreSQL, Snowflake, BigQuery | Enables query-history ingestion when the warehouse supports it |
 | `path` | Yes for path-style SQLite | SQLite | Local SQLite database path or `env:NAME` reference |
@@ -269,63 +269,6 @@ staged artifact shape as Postgres and Snowflake.
 
 ---
 
-## ClickHouse
-
-Connects over HTTP (port 8123) or HTTPS (port 8443). Supports the ClickHouse native type system including `Nullable`, `LowCardinality`, and `Array` wrappers.
-
-### Connection config
-
-```yaml title="ktx.yaml"
-connections:
-  my-clickhouse:
-    driver: clickhouse
-    url: http://localhost:8123/analytics
-```
-
-Or with individual fields:
-
-```yaml title="ktx.yaml"
-connections:
-  my-clickhouse:
-    driver: clickhouse
-    host: clickhouse.internal
-    port: 8123
-    database: analytics
-    username: default
-    password: env:CH_PASSWORD
-    ssl: false
-```
-
-### Authentication
-
-| Method | Config |
-|--------|--------|
-| Basic auth | `username` + `password` (HTTP basic auth) |
-| No auth | Default user `default` with no password |
-| HTTPS | Set `ssl: true` (uses port 8443 by default) |
-
-### Features
-
-| Feature | Supported | Notes |
-|---------|-----------|-------|
-| Tables & views | Yes | Via `system.tables`, engine-based detection |
-| Primary keys | Yes | Via `system.columns` |
-| Foreign keys | No | Not a ClickHouse concept |
-| Row count estimates | Yes | Via `system.parts` aggregation |
-| Column statistics | No | - |
-| Query history | No | - |
-| Table sampling | Yes | - |
-
-### Dialect notes
-
-- Parameter binding uses `{param:Type}` syntax (e.g., `{database:String}`)
-- Detects views vs. tables by engine name (`View`, `MaterializedView`)
-- Handles `Nullable(T)` and `LowCardinality(Nullable(T))` type wrappers
-- Dictionary tables are excluded from scanning
-- Results returned in JSONCompact or JSONEachRow format
-
----
-
 ## MySQL
 
 Standard MySQL/MariaDB connector with full foreign key support and schema introspection.