Track OpenDots browser setup and Intelligence signup usage

[jerelvelarde]

OpenDots runtime events lack an application tag, Docker drops the CLI telemetry identity, and the browser setup flow has no installation funnel. This change tags existing SDK events, forwards identity and opt-outs through Compose, and adds browser setup tracking using the existing CopilotKit ingest contract.

Setup views, bounded failure categories, abandonment, and first successful assistant answer are tracked with a persistent installation UUID. The CLI account identity remains authoritative for transport and runtime events. A SQLite queue holds up to 256 events with stable IDs/timestamps, retries offline delivery, bounds shutdown flushing, and clears tracking state on opt-out. The authenticated browser endpoint accepts a closed schema; activation is generated by successful server-side assistant streams and excludes errors, aborts, and timeouts. Setup/settings disclose collection and link to opt-out details.

Four saved HogQL queries cover signup accounts with usage, daily usage, setup events, and installation conversion. Account lookup uses resolved startup/runtime events with the same telemetry ID if a request lacks Clerk enrichment. Queries exclude marked validation probes. Setup and runtime share an installation UUID for the setup-to-account bridge.

Validation:

• 254 tests across 43 files passed, including offline replay, queue bounds, opt-out purge, protected routing, activation deduplication, and abort/timeout suppression.
• Final formatting, lint, explicit typecheck, client/server build, and diff hygiene passed. Static disclosure copy was added after the full test run; formatting/lint/typecheck/build were then rerun successfully.
• Live PostHog queries verified marked SDK events and the new setup emitter. An updated probe delivered all three event types with one shared installation UUID; startup resolved the Clerk account. A marked reporting query returned one request and one resolved account via the identity fallback.
• All four normal reporting queries execute successfully and exclude validation probes. The validation account is staff and is excluded from signup sync, so a fresh external signup remains unverified.

The PostHog key has query permission, but retries of dashboard and insight access return 403 for missing dashboard:read and insight:read. Reporting SQL is prepared and verified but has not been saved to dashboard 664553. Saving charts needs dashboard/insight read-write scopes or the reporting owner.

Browser abandonment is best effort before server receipt; accepted events persist and can replay. OpenDots has no native installer or engine/model/harness chooser, so those OpenBot desktop events are not emitted. This associates signup accounts with template usage; it does not prove acquisition source. The shared telemetry event-map catalogue should record the new browser setup events under the existing oss.runtime.* namespace; no ingest gate change is needed.