docs: move project status out of the sync script into the docs

Script comments should describe the script. Where a run has got to is
project state, so it belongs in docs/gallery-dl.md, which now records the
live withaseul publish, the file-ownership caveat and where the profile
list lives.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

docs/gallery-dl.md

@@ -262,10 +262,25 @@ which are rewritten every run and would otherwise churn the synced share.
 Publishing happens once at the end of a run, so a profile that fails midway
 never reaches the archive half-written.
 
+## Status
+
+In use. `withaseul` has been fetched and published to the live archive — 322
+files added (74 media, 241 `.json`, 7 `.txt`), nothing overwritten or deleted.
+Of the 74 new media files, **zero** duplicated media already held under a
+different name, which is the check that says JD2 and gallery-dl naming really
+do converge.
+
+Published files land owned by the SSH user rather than `rslsync`. The viewer
+reads them fine (world-readable), but Resilio does not own what it syncs; worth
+a `chown` if that ever matters.
+
+The profiles to fetch live in `artms_account_links.txt` at the archive root,
+passed with `--urls-file`.
+
 ## Verified run
 
 `withaseul`, all four surfaces, staged locally and published to a scratch
-directory (never the live archive):
+directory before the live publish above:
 
 ```
 ==> withaseul / posts      seeded 915 of 984 live items

scripts/gdl-sync.py

@@ -6,9 +6,6 @@ The CLI replacement for the JDownloader2 workflow. See docs/gallery-dl.md for
 the measurements behind every choice here — especially the safety model, which
 is the reason this script exists in this shape rather than a simpler one.
 
-STATUS: in use. `withaseul` was fetched and published to the live archive
-(322 files added, nothing overwritten or deleted).
-
 The fetch host needs no copy of the archive. It stages locally and rsyncs
 afterwards; what it already holds is learned from a *file listing* alone
 (`--index`), which the viewer's own API serves.