docs: record v0.2.0 release and production deploy

.opencode/progress.txt

@@ -312,3 +312,11 @@ Not verified locally:
 - Context: three review rounds hardened replay attempts, compaction-vs-append locking, exhausted-retry handling, and reclaim-guard identity. Residual fs-lock scheduling windows are documented and accepted.
 - Outcome: accepted. F12 passes=true came from the user's own host verification (2,836 null rows backfilled, column default set) and was committed unchanged. Extension repo still owns no DB code for F12.
 - Learning: journal locking is the hard part, not the retry logic — plan the lock protocol before writing the journal. Browser + live-cluster checks remain the only gaps; deploy requires a human.
+
+## 2026-10-30 — release v0.2.0 + production deploy (F11)
+
+- Merged `goal/image-previews` into master (`ed1b625`), bumped package to 0.2.0 (`73da969`), tagged `v0.2.0`; pushed master + tag to origin.
+- Built locally (prod has no Node), packaged `dist/ package.json README.md LICENSE` (`sha256 094c31f0…`), SCP'd to `land-nest:apps/directus/`.
+- Backed up previous `dist` + `package.json` as `*.bak-20261030-072734`; installed 0.2.0; `pm2 reload directus` clean (all 4 workers online, restart count 1).
+- Verified: `/server/health` 200, `/image-previews/status` and `/image-previews/failures` 403 (mounted + admin guard), empty PM2 error logs. Rollback = restore `dist.bak-20261030-072734` + `pm2 reload directus`.
+- Still unverified: browser render of the Failed previews table and a live scheduler retry tick (user waived; code/test evidence only).