release: record verified 1.9.0 production migrations

backend/migrations/applied.txt

@@ -18,3 +18,8 @@
 0008_backlog_claimed_at.sql
 0009_like_count_index.sql
 0010_generation_daily_usage.sql
+0011_content_supply.sql
+0012_curriculum_publication.sql
+0013_daily_reviews.sql
+0014_content_operations.sql
+0015_revision_generation_claims.sql

docs/CODEBASE_MAP.md

@@ -239,10 +239,10 @@ enforce one daily assignment and no concept repeats per user. RLS adds isolation
 | `0014_content_operations.sql` | Worker heartbeat and deduplicated condition state. |
 | `0015_revision_generation_claims.sql` | Durable claims for correction drafting. |
 
-Only migrations 0001–0010 are recorded in `migrations/applied.txt`; new migrations
-0011–0015 are unapplied in production at this PR handoff. Migration 0010 was
-applied and independently verified in production during the 1.8.0 release
-follow-up. The ledger is repository evidence, not a live check of production.
+Migrations 0001–0015 are recorded in `migrations/applied.txt`. The owner applied
+0011–0015 during 1.9.0 release preparation, and a separate read-only production
+connection verified their tables, RLS, columns, indexes, constraints and backfill.
+The backend/worker rollout remains pending; the ledger does not prove deployment.
 Application connections use the transaction pooler; migration DDL uses `DIRECT_URL`
 and the session pooler. Applied migrations must not be rewritten.
 

docs/WORK_LOG.md

@@ -7,6 +7,23 @@ claims as completed work.
 
 ## Current status
 
+### Version 1.9.0 production migration verification
+
+- Owner reported generation paused and manually applied migrations 0011–0015
+  in order through SQL Editor, each reporting success.
+- Independently verified the original production project through a read-only
+  session-pooler transaction: six new tables, RLS enabled with no client policies,
+  four added columns, five indexes, foreign keys/checks, daily-review uniqueness,
+  final revision-status constraint and published-lesson timestamp backfill.
+- Record all five migrations only after that verification. No production writes
+  were performed by this verification; migration files remain immutable.
+- Local pre-release dump exists and its archive index is readable. Full restore
+  remains untested; owner explicitly deferred the separate cloud Backup project.
+- Backend/worker rollout and ordering before OTA remain outstanding. Keep
+  generation paused and release #200 draft; do not merge main yet.
+- Validation: migration file/ledger comparison and whitespace checks passed.
+  No application code changed; application tests were not rerun for this entry.
+
 ### Version 1.9.0 release preparation
 
 - Preparing the merged #197/#198 work for a `develop` to `main` release.