Fix release migration check after verified production application

[Muawiya-contact]

Fix release #191's required migration check by recording 0010_generation_daily_usage.sql after its verified application to production.

The owner approved applying the exact pending SQL. It creates public.generation_daily_usage with a date primary key and nonnegative counter, enables row-level security, and has no client policies. No existing table or row was changed.

Validation:

• Verified the committed production schema through a new read-only connection: column types/nullability, zero counter default, primary key, nonnegative check, RLS, and no client policies.
• Ran the unchanged migration workflow's shell check locally: all ten migrations are recorded.
• Verified the migration SQL and CI workflow are unchanged; whitespace checks passed.
• The release's 145 backend tests previously passed with this same SQL on disposable PostgreSQL 16. No application code changed in this follow-up.

Merge into develop to update the existing develop-to-main release PR. The first-day generation rollout steps remain in the release checklist. This does not merge or deploy main.