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/Admin.tsx

@@ -227,6 +227,11 @@ export function Admin() {
                       <img src={api.photoUrl(p.id)} alt="" loading="lazy" />
                       <div className="adm-meta">
                         <b>#{p.id}</b>
+                        {/* The labels the uploader's studio stored, when it
+                            sent any — the same ones the reel draws. */}
+                        {p.tag ? <span>{p.tag}</span> : null}
+                        {p.title ? <span>{p.title}</span> : null}
+                        {p.meta ? <span>{p.meta}</span> : null}
                         <span>{t('adm.owner')}: {p.email}</span>
                         <span>{t('adm.uploaded')}: {new Date(p.createdAt).toLocaleString()}</span>
                         <span>{t('adm.size')}: {Math.round(p.bytes / 1024)} KB · {p.mime}</span>