Check first six client testers' recent Discord channel activity

Read-only assessment of the FIRST six selected testers (response IDs 26,41,25,28,15,49), not the proposed next ten. Scan the last 30 days of Discord general channel 816749335672913920 in guild 631914882731606025. Match handles conservatively to stable user IDs; separate exact username/legacy matches from uncertain display-name/nickname matches and distinguish unmatched from inactive. Summarize counts, active UTC days, recency and replies; activity is not proof of tester/reporting quality. No contact values, bot credentials or raw conversations in output; avoid persisting raw messages. Completed a full 30-day channel-history scan: 2026-09-19 10:58 UTC to 2026-10-19 10:58 UTC; 9,316 messages across 94 pages, reaching beyond the start boundary. Exact case-insensitive username matches: response 26 has 1 message/1 UTC day, last Oct 9; response 28 has 2 messages/2 days, last Oct 3. Possible display/nickname matches only, not confirmed attribution: response 25 has 95 messages/19 days, last Oct 19, 10 messages in last 7 days and 21 replies; response 15 has 3 messages/1 day, last Oct 15, 1 reply and 1 attachment message. Responses 41 and 49 were unmatched in this channel/window; do not label them inactive or absent from the server. Three new identity/aggregation tests pass alongside the five existing adapter tests (8 total). Aggregate-only owner-readable report: .dev-data/tester-selection/first-six-discord-activity.json; reusable scanner discord_activity.py. No raw messages, unrelated author names, emails or credentials printed/persisted. Other channels, threads, deleted messages and lurkers are excluded. No qualitative helpfulness assessment was performed and self-reported handle ownership is not verified. No invitations or selection changes.