#1799 — Dual-write analytics to yonatan-hq platform

What this does

Adds a best-effort HTTP sink so OrchestKit local analytics (~/.claude/analytics/*.jsonl) also flow to the yonatan-hq platform Postgres pipeline. Local JSONL stays the source of truth; the HTTP POST is a fire-and-forget mirror.

Why now

• Today: per-machine JSONL only. /hq-ext:hq-analytics skill reads local files.
• Platform Intelligence Tab reads its own Postgres.
• Same data, two silos. Dual-write makes the platform see fleet-wide events without dropping the local-first model.

Failure mode

HTTP POST is fire-and-forget. If the platform is down or slow, local analytics still write. No retries, no blocking, no impact on hook latency.

Opt-in

Controlled by env var (see PR body). Defaults to off — users explicitly opt-in to share data.

This page exists to satisfy the M119 playground gate convention.