Many older photos (especially pre-EXIF-orientation cameras) are off
by a multiple of 90 degrees with no metadata to auto-correct. Each
image row in the admin file table now has rotate buttons that
physically rotate the file (auto-orienting first to normalize any
existing EXIF tag), swap the stored width/height, and clear the
cached thumbnail so it regenerates from the corrected image.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

Browsers only decode H.264 4:2:0 (Baseline/Main/High). Files reported
as codec_name=h264 could still be High 4:2:2/4:4:4 profile if an
earlier transcode pass (or the source) used non-standard chroma —
ffprobe/ffmpeg read these fine, but real browsers reject them as
unsupported. update.rb now also checks pix_fmt and re-transcodes if
it isn't yuv420p/yuvj420p, and forces -pix_fmt yuv420p on output so
this can't recur.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

Photo search was returning every individual matching photo, which
was overkill for what's meant to be a quick way to find an album.
/search now groups matches by album (cover thumbnail + match count)
instead of listing each photo, and is relabeled "Album Search"
throughout the UI.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

The HEVC-to-H.264 transcode kept the original file as a hidden
(non-admin) entry with transcoded_to set, but the lightbox <video>
element and the slideshow always pointed at the original file's URL.
Opening a transcoded video (e.g. via a direct ?photo= link) tried to
play the unsupported original codec instead of the browser-compatible
copy.

- album.erb/album.js: lightbox video now plays the transcoded file
  when present, while the "Download Original" link still serves the
  true original.
- all_media_entries: slideshow skips transcoded originals entirely
  since it has no separate download path.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

People bulk-move previously required moving members into an existing
person, the pool, or the blacklist; this adds a "new person" target
that creates a fresh cluster from the selected faces.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

Mirrors the browse page filter: files with transcoded_to set are hidden
from unprivileged users, so the album video badge now matches what they
actually see.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

Replace media_count helper with media_counts returning {photos, videos}.
Album overview shows photo count as before, plus a coloured ▶ N badge
only when an album (or its sub-albums) contains videos.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

Firefox has no HEVC support. Pixel 9a (and newer phones) record video
in HEVC by default. update.rb now probes the codec of every .mp4/.m4v
file via ffprobe and transcodes non-web-friendly codecs (anything not
h264/vp8/vp9/av1) to H.264 MP4 with a .h264.mp4 suffix, same as the
existing MOV→MP4 flow. The original is kept and hidden from non-admins.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

When ?photo= is in the URL, @og_use_media was forcing the full-res
image (2-3MB) as the og:image. WhatsApp fetched it but showed no
preview, likely due to size or timeout. Now uses the thumbnail.

Also removed hardcoded og:image:width/height (1200x630) from individual
photo/album pages — those dimensions only apply to the default fallback
image and were causing WhatsApp to reject previews when the actual image
dimensions didn't match the declared ones.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

nginx was sending X-Forwarded-Proto: http (its own scheme) rather than
https (the edge scheme), so og:url and og:image were http:// URLs.
Fixed by hardcoding https in the nginx proxy_set_header since HTTPS is
always terminated at the upstream Apache router.

Added a 1200x630 landscape og-default.png (WhatsApp requires ~1.91:1
ratio) and explicit og:image:width/height meta tags. Also tracks the
nginx site config in the repo.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>