Clients must recognise the same time-lapse filed under another id on the server, and an
integrated pair must get a photo into the server sequence even when another sequence there
already holds it. The server now answers both, authorised and scoped by itself.
- POST /api/v1/photos/lookup (Read right): per probe, the sequences of the served archive
that hold its hashes in a frame, tombstoned them (deleted or replaced by a conversion),
match its unhashed photos by size and capture millisecond, or carry its session key; only
ids and counts, batched raw SQL, 413 too_many beyond 200 probes or 20,000 items, a 4 MB
body limit so a full request fits.
- Uploads with IntoTarget: sequenceId required, never with Restore, the target must be the
served archive's and the caller its owner, an admin or an editor. Only a copy in the target
stands in; a tombstone keeps the photo deleted. Otherwise the server copies an intact file
of another sequence of the served archive (never another archive of the index) into the
target: quota and room checked, verified copy, hash compared (a damaged source falls back
to a normal upload), committed refusing removed photos, used bytes charged only for a new
frame, frames event published, answered copied.
- server/info announces photo-lookup and upload-into (the desktop's hosted share too).
Refs #73
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>