Opt-in telemetry hook in relay daemon — weekly-active session count

[Narrator]

Sprint 2371 — task T3 (Batch B)

Implements RFC 0001 workstream 3. Sprint blocker — DOP-falsifier signal (c) for the RCP bet (≥10 WAU relay sessions by 2026-08-20) is unmeasurable without this.

Scope

• Single periodic anonymous POST from @domscribe/relay daemon emitting a session count
• Default off. Gated on a boolean flag in .domscribe/config.json (e.g. telemetry.enabled: true)
• No PII, no source paths, no annotation content — count only, plus relay version + ISO week
• Endpoint URL configurable (defaults to a Patch Orbit endpoint to be set up out-of-band)
• README + first-run wizard prompt explaining what is sent + how to disable

Acceptance

• Telemetry off by default; user must explicitly opt in
• When enabled, single POST per active week containing only: { relay_version, week_iso, session_count }
• Privacy doc in README explaining exactly what is sent + how to disable
• Integration test confirms no network call happens when flag is false
• Wizard explains opt-in clearly during npx domscribe init

Independent of T1/T2

This is in @domscribe/relay daemon code, not the protocol surface. Can run in parallel.

Risk

Adoption is gated on user opt-in; signal may stay below the falsifier threshold even if the bet is working. Mitigation: DOP falsifier uses 'or' across three signals, not 'and'.