feat: the camera's own colour, a reading that keeps its place, and cloud links in Settings

- RAW opens at the colour the camera wrote into it: the develop carries the
  difference against the file's own preview (previewResidual) instead of the
  per-channel cubic fit, dE00 6.04 -> 0.54; previewMatch.ts keeps only the grid.
- Immich reading: keyset position kept across visits, one reading per node,
  a page in flight retried, timeline buckets for the years on offer.
- The wall draws a server frame at the address the proxy serves it (no blob
  minted for it), and the 80-thumbnail pre-cache on open is gone.
- Settings lists the cloud links, flags two that answer at the same address,
  and forgets one.
- Custom frames imported from a file (engine/customFrame.ts, IndexedDB).
- Upload an edited frame from Studio to Immich Cloud.

docker/backend/src/server.ts

@@ -150,9 +150,13 @@ app.addContentTypeParser('application/json', { parseAs: 'string' }, (_req, body,
 
 // Photo uploads are the raw image bytes, not multipart: one file per request
 // needs no boundary parsing, so no dependency and no parser attack surface.
-app.addContentTypeParser(['image/jpeg', 'image/png', 'image/webp'], { parseAs: 'buffer' }, (_req, body, done) => {
-  done(null, body);
-});
+app.addContentTypeParser(
+  ['image/jpeg', 'image/png', 'image/webp', 'application/octet-stream'],
+  { parseAs: 'buffer', bodyLimit: 50 * 1024 * 1024 },
+  (_req, body, done) => {
+    done(null, body);
+  }
+);
 
 // A restore body is a whole data dir, so it is the one body far past the
 // instance limit. Buffered, not streamed: `tar` needs the archive to be