Fix harmonize:images thumb rebuild and allow oversized museum scans.

Co-authored-by: Cursor <cursoragent@cursor.com>

Documentation/FAC.md

@@ -143,7 +143,7 @@ Run `npm run dev:migrate` against prod DB after first deploy with auth vars set
 | `npm run devtoprod:db:restore -- --file <path>` | Restore into **prod** (requires confirmation) |
 | `npm run harmonize` | Bidirectional catalog DB + image merge by `updated_at` / file mtime — [harmonize-dev-prod.md](harmonize-dev-prod.md) |
 | `npm run harmonize:schema` | Apply dev migrations to prod schema only (dev → prod) |
-| `npm run harmonize:db` / `harmonize:images` | DB or image merge only |
+| `npm run harmonize:db` / `harmonize:images` | DB or image merge only (`harmonize:images` also regenerates painting + portrait thumbs on both sides) |
 | `npm run dev:backfill-updated-at` | Backfill catalog `updated_at` from image mtimes (dev) |
 
 **One-time split (recommended):** pgAdmin on dev PC → open [`db/split-dev-prod-pgadmin.sql`](../db/split-dev-prod-pgadmin.sql) → run each STEP on database `postgres`, then verify on `gallery_dev`.

Documentation/data-and-images.md

@@ -31,7 +31,7 @@ File names are sanitised `{Artist}_{Title}.{ext}`. The image service can redisco
 | **Development** | `./data/images/` in repo | Working copy on dev PC |
 | **Production** | `/mnt/BasePool/Applications/Gallery/data/images` on TrueNAS | SMB `\\192.168.10.122\Gallery\data\images` |
 
-**One-direction promote:** `npm run devtoprod:images` (dev → prod, skip older). **Refresh all images on dev from prod:** `npm run prodto:dev:images`. **One artist only:** map the SMB share, then `robocopy` that artist’s `ArtistName*` files under `paintings/` and `paintings/thumbs/` (see [FAC.md](FAC.md#dev--prod-image-sync-smb)). **Bidirectional merge** (newer file wins): `npm run harmonize:images` or full `npm run harmonize` — see [harmonize-dev-prod.md](harmonize-dev-prod.md). General sync reference: [environments.md](environments.md).
+**One-direction promote:** `npm run devtoprod:images` (dev → prod, skip older). **Refresh all images on dev from prod:** `npm run prodto:dev:images`. **One artist only:** map the SMB share, then `robocopy` that artist’s `ArtistName*` files under `paintings/` and `paintings/thumbs/` (see [FAC.md](FAC.md#dev--prod-image-sync-smb)). **Bidirectional merge** (newer file wins, then rebuild painting + portrait thumbs on both sides): `npm run harmonize:images` or full `npm run harmonize` — see [harmonize-dev-prod.md](harmonize-dev-prod.md). General sync reference: [environments.md](environments.md).
 
 ## Scripts overview
 
@@ -49,7 +49,7 @@ File names are sanitised `{Artist}_{Title}.{ext}`. The image service can redisco
 | `fetch-missing-images.js` | `npm run dev:fetch-images` | Downloads files for paintings missing on disk |
 | `image-fetcher.js` | *(library)* | Wikimedia / museum resolution used by fetch scripts and API |
 | `sync-images-to-prod.ps1` / `sync-images-from-prod.ps1` | `npm run devtoprod:images` / `npm run prodto:dev:images` | Robocopy via SMB `\\192.168.10.122\Gallery` |
-| `harmonize-db.js` / `harmonize-images.js` | `npm run harmonize:db` / `harmonize:images` | Bidirectional merge by `updated_at` / file mtime |
+| `harmonize-db.js` / `harmonize-images.js` | `npm run harmonize:db` / `harmonize:images` | Bidirectional merge by `updated_at` / file mtime; images step then rebuilds thumbs on both sides |
 | `harmonize.ps1` | `npm run harmonize` | Orchestrator: backups, optional schema, DB + image merge |
 | `regenerate-thumbnails.js` | `npm run dev:regenerate-thumbnails` | Rebuild painting thumbs from full images via `sharp` |
 | `regenerate-portrait-thumbs.js` | `npm run dev:regenerate-portrait-thumbs` | Rebuild timeline portrait thumbs (~256px) and set `portrait_thumb_path` |

Documentation/environments.md

@@ -341,7 +341,7 @@ For **incremental** dev ↔ prod merge (both sides edited), use [harmonize-dev-p
 | `npm run devtoprod:db:restore` | Dev PC PowerShell | Restore into prod |
 | `npm run harmonize` | Dev PC PowerShell | Bidirectional catalog + image merge — [harmonize-dev-prod.md](harmonize-dev-prod.md) |
 | `npm run harmonize:db` | Dev PC PowerShell | DB merge only |
-| `npm run harmonize:images` | Dev PC PowerShell | Image merge only |
+| `npm run harmonize:images` | Dev PC PowerShell | Image merge + regenerate thumbs on both sides |
 
 ## Image sync
 

Documentation/harmonize-dev-prod.md

@@ -83,7 +83,7 @@ npm run harmonize:dry-run
 | `backupProd` | `prod:db:backup` | Safety snapshot |
 | `schema` | `harmonize:schema` | Apply dev migrations to prod (when `schemaChanged: true`) |
 | `db` | `harmonize:db` | Row-level catalog merge |
-| `images` | `harmonize:images` | Bidirectional file merge |
+| `images` | `harmonize:images` | Bidirectional file merge, then regenerate painting + portrait thumbs on **dev and prod** |
 | `verify` | curl `/api/bounds` | Optional smoke check |
 
 Reports are written to `db/SyncReports/harmonize_db_*.json` and `harmonize_images_*.json` (gitignored).
@@ -98,7 +98,9 @@ Reports are written to `db/SyncReports/harmonize_db_*.json` and `harmonize_image
 | `npm run harmonize:db` | Merge catalog rows by `updated_at` |
 | `npm run harmonize:db -- --dry-run` | Preview DB changes |
 | `npm run harmonize:db -- --prefer=dev` | On equal `updated_at`, dev wins |
-| `npm run harmonize:images` | Merge image files by mtime |
+| `npm run harmonize:images` | Merge image files by mtime, then regenerate painting + portrait thumbnails on both sides |
+| `npm run harmonize:images -- --skip-thumbnails` | File merge only (no thumb rebuild) |
+| `npm run harmonize:images -- --dry-run` | Preview file copies only (skips thumbnails) |
 | `npm run dev:migrate:sync-timestamps` | Apply `updated_at` migration on dev only |
 | `npm run dev:backfill-updated-at` | Backfill dev `updated_at` from image mtimes |
 | `npm run harmonize:backfill-updated-at` | Same backfill on prod |