web: give each member a photo folder and burn the strip into the export

Every member gets /photos — their own uploads, counted against a 12-photo
cap, each card showing the tagline and the technical line the studio would
print. The studio gains SAVE PHOTO n/12 in the top bar: it renders the full
resolution look, stores the strip (tag/title/meta) with the upload so the
landing reel frames it the same way, and refuses past the cap.

EXPORT now burns that strip into the file: the amber #TAG over the photo's
top-left plus a dark caption band below carrying the recipe name and the
ISO / grain / warmth line. The live preview stays clean, and the saved
upload stays clean too — the reel draws its own frame from the stored
labels, so a burned band would tag the tag twice.

Admins manage any photo through DELETE /api/photos/:id; members only their
own. The users table's photo counts stay in step with the folder.

docker/frontend/src/Landing.tsx

@@ -170,10 +170,13 @@ export function Landing() {
   const reel = useMemo<Look[]>(
     () => [
       ...REEL,
+      // The labels the uploader's studio stored — the tagline, the title and
+      // the ISO/grain line. A contribution from before those existed keeps the
+      // plain community defaults.
       ...photos.filter((p) => p.slot === 'strip').map((p) => ({
-        tag: '#COMMUNITY',
-        title: { en: 'Community Frame', vi: 'Khung cộng đồng' },
-        meta: `#${p.id}`,
+        tag: p.tag ?? '#COMMUNITY',
+        title: { en: p.title ?? 'Community Frame', vi: p.title ?? 'Khung cộng đồng' },
+        meta: p.meta ?? `#${p.id}`,
         photo: api.photoUrl(p.id),
         filter: 'none',
       })),