R1: mark done in PRERELEASE.md (post-merge close-out)

scrabble-game #31 + scrabble-dictionary #2 merged, v1.0.1 cut, contour DB wiped
and re-migrated to the baseline (verified).

PRERELEASE.md

@@ -17,7 +17,7 @@ the edge before prod. Each phase maps back to the owner's raw pre-release TODO l
 
 | # | Phase | Raw TODOs | Status |
 |---|-------|-----------|--------|
-| R1 | Schema & naming reset | 1 + 10 | **in review** |
+| R1 | Schema & naming reset | 1 + 10 | **done** |
 | R2 | Stress harness + contour observability + early run | 9a | todo |
 | R3 | Edge hardening | 2 + 8 + 3 | todo |
 | R4 | Push enrichment + kill the last poll | 4 + 5 | todo |
@@ -214,6 +214,9 @@ Then Stage 18.
   - **Migrations squashed** 12 → one hand-written `00001_baseline.sql`. Verified by a
     `pg_dump --schema-only` diff (the chain vs the baseline are **identical** but for the two intended
     variant-CHECK values) plus the green integration suite. **No data migration** (no production data).
-  - **Follow-ups:** post-merge, drop the contour `postgres-data` volume on the runner host so the next
-    deploy provisions a clean DB on the new baseline; the **`scrabble-dictionary` tidy** ships as its own
-    PR in that repo (sources consolidated to a single build point; byte-identical artifact).
+  - **Done (cross-repo + contour):** the **`scrabble-dictionary` tidy** merged (PR #2) and was re-cut as
+    the **byte-identical `v1.0.1`** release for clean provenance (the backend stays on `v1.0.0` — same
+    bytes, no rewire; the backend pulls a version-pinned release artifact, not master). Post-merge the
+    contour `backend` schema was wiped (`DROP SCHEMA backend CASCADE` + restart, not a volume drop) and
+    re-migrated to the baseline — verified the new variant CHECK (`scrabble_en/scrabble_ru/erudit_ru`),
+    `games`=0 and a clean boot.