[Feedback] :pencil2: correction — Scope WAU using cloud events

Nobody has claimed this yet.

## Feedback (correction)

**Question:** Scope WAU using cloud events
**Tool:** `query`
**Dataset:** `scope_cloud_events`

### Corrected SQL
```sql
SELECT toStartOfWeek(activity_date) AS week_start, uniqIf(person_id, has_scope_streaming = 1) AS scope_wau FROM semantic.user_daily_engagement WHERE activity_date >= toDate('2026-01-12') AND is_active = 1 GROUP BY week_start ORDER BY week_start
```

### Corrected answer
Canonical Scope WAU query uses user_daily_engagement with has_scope_streaming flag. Do NOT use scope_cloud_events for WAU — it includes internal users and unresolved identities. External filter is already baked into user_daily_engagement (model-level). No additional WHERE clause needed to exclude internals.

### Notes
Original query used scope_cloud_events uniq(user_id) which (1) included internal @livepeer.org users inflating numbers, (2) included unresolved person identities not present in user_daily_engagement, (3) was inconsistent with all other platform WAU metrics. Correct query is user_daily_engagement with has_scope_streaming flag.

---
_Feedback ID: `a8aeab8f-0f66-40a2-8db7-a08d73fd4c4a` | Recorded at 2026-03-11T00:43:54.863Z_

The issue names the `query` tool, `scope_cloud_events` dataset, and `semantic.user_daily_engagement` table, but no implementation file. Start by tracing how the query tool defines Scope WAU and compare it with the corrected SQL. Done means the canonical query uses `has_scope_streaming` and matches the stated external-user behavior.

Written by the indexing model from the issue text.