← EGRA Test Build Review · Live state on staging

Live state on staging (verified 2026-09-27)

Check Result How verified
Which bot Main Rumi bot, repo hyasin270/whatsapp-ai-bot, branch staging. Nothing EGRA-related from this author in NIETE-Rumi. git log origin/staging and NIETE sandbox/staging/main logs
On production? No. All 8 commits (783116cc..e81dbc03, 16–18 Sep) are staging-only. git merge-base --is-ancestor <sha> origin/main for each
Changed since? No later commit by anyone touches these 42 files. Staging head 554c6a8d. git log e81dbc03..origin/staging -- <files>
Deploy Staging web service deploy 6547108a SUCCESS 2026-09-27 07:23 (+02:00). railway deployment list --service digital-coach-staging
Feature flag EGRA_EGMA_ICT_TEST_ENABLED=true on digital-coach-staging; not set on sqs-worker-staging. railway variables --kv (values masked)
Listening Flow EGRA_EGMA_LISTENING_FLOW_ID set; Meta reports "EGRA-EGMA ICT Test — Listening Comprehension (Staging)", PUBLISHED, JSON 6.3, no validation errors, updated 18 Sep. Graph API GET on the flow id
Results table egra_egma_ict_test_attempts EXISTS in the shared Supabase (the DB prod and staging share). The audio_* columns from the second migration do NOT exist. information_schema via analyst2
Rows saved 1 row, 1 session, 18 Sep. count(*)
Usage (Axiom) 9 sessions started by 3 accounts, 18–24 Sep; 8 children drawn from rosters; 4 listening Flows completed; 1 subtest recorded; 0 voice notes logged; 0 EGRA error/warn lines. APL on digital-coach-logs, service digital-coach-staging