[Muawiya-contact]

Scope

• Port Railway reminders, weekly quiz notices, reviewer Gmail, curated refill, editorial correction, legacy enrichment, and demand-driven prefetch to bounded Supabase Edge jobs.
• Add durable SQL claims, quotas, one-use signed Cron dispatch, run and HTTP-result ledgers, and eight named schedules installed inactive.
• Provide owner and operator status, bounded run retention, staging verification, and a cutover runbook. Prepare mobile version 1.10.15 with a matching What's New card; native runtime stays 1.10.8.

Verified

• The protected staging batch applied migrations 0119–0127, deployed only the staging worker, installed eight inactive Cron jobs, and completed a signed provider-disabled dispatch. A later staging batch verified migrations 0128–0129, the candidate worker, inactive jobs, and signed dispatch.
• The controlled provider batch accepted one daily and one weekly Expo push and staged one private Gemini revision. The owner confirmed phone delivery. Staging gates were closed and temporary Edge credentials removed afterward.
• The no-send Gmail OAuth check passed token exchange after the staging client ID was corrected. The guarded email retry recorded exactly one batch as sent on attempt 3 and a worker result of sent=1. The owner found the controlled test email in the reviewer mailbox's Spam folder. Its job failed because the canary stopped before the separate HTTP receipt appeared; a focused regression fix now waits for that receipt. The read-only check found http=0 before reconciliation. The sent batch will not be retried.
• Railway screenshots confirm the reminders 15-minute and pool-topup 22:00 UTC schedules and recent successful no-op runs. The PR branch now incorporates current develop without rewriting its focused commits.

Before ready to merge

• Run the protected staging HTTP reconciliation, which records the existing pg_net receipt without dispatching or sending again. It is waiting at GitHub's supabase-staging approval gate.
• Verify remaining effective Railway non-secret flags/caps and deployed revision, or record a safe explicit cutover check for values Railway cannot expose.
• Final review of the current head. All three hosted PR quality jobs passed on 9ba416b; 16 focused local canary/receipt tests passed.

Production Supabase schedules remain disabled. Railway continues production work until issue #418's cutover. This draft references #417 and will add Closes #417 only after staged acceptance passes.