Write a Tiger Data Docs integration guide

End state: a .mdx file at src/content/docs/integrate/<category>/<slug>.mdx, a sidebar entry in astro.config.ts, and (optionally) a logo asset. Most guides are bilateral: configuration on the third-party side, configuration on the database side, and optionally a step that triggers data flow. Short integrations may collapse to one part; long ones may have three or four.

In every AskUserQuestion call, treat options as equal — no (Recommended) labels.

Start by reading two files

Before writing anything, read:

1. src/content/docs/integrate/_template-integration.mdx — the canonical skeleton you copy from. This file is the source of truth for placeholder wording in scaffold mode.
2. One existing page in the same category as a tone/depth reference:
   • BI/visualization → bi-vizualization/tableau.mdx
   • Data engineering/ETL → data-engineering-etl/apache-kafka.mdx (long, multipart) or debezium.mdx (short, two-part)
   • Observability/alerting → observability-alerting/grafana.mdx
   • Workflow orchestration → data-engineering-etl/apache-airflow.mdx

Match the depth and tone of an existing page in the same category. Don't invent a new structure.