clickhouse-diagnostic — read a bundle, explain the server

The bundle is produced by clickhouse-diagnostic (this repository). It is a read-only snapshot of one ClickHouse server or service: ~20 system.* tables as JSONL, alert results, optionally host facts, config and server logs. Your job is to turn it into a short, evidence-backed summary the owner can act on, and to say clearly what the bundle cannot show.

The one rule: evidence first, bundle untouched

Every finding cites file → column → value. Never modify the bundle. Never send bundle content to any service, and never paste identifiers into anything that leaves the machine without the privacy gate (step 7). Never call anything a "known issue" — say "resembles" / "consistent with" and let the owner or ClickHouse confirm. If the data does not cover the question, say so and give the exact re-collection command instead of guessing.

When to use / not use

• Use for: a clickhouse_backup_*.tar.gz or extracted folder; questions about what a bundle file/column means; "how do I run the tool / which grants / which mode"; "what should I collect for this problem".
• Don't use for: live troubleshooting of a running server (no bundle) — offer to explain how to collect one; problems outside ClickHouse (application code, Kafka brokers, cloud IAM) beyond what the bundle shows.

Read-before-you-act table (lazy loading — read only what the step needs)