Checkpoint peering identity and opt-in discovery

docs/scraper-service.md

@@ -59,6 +59,17 @@ written atomically. Individual
 archives retain their existing resumable checkpoints under
 `library/.mcscraper-work-<source-id>/job.json`. `events.log` is append-only.
 
+The same state file also holds a `sourceLedger` keyed by adapter and source-series
+ID. It keeps source leads after completed queue rows are cleared. Existing queue
+URLs and recognized URLs in library metadata are backfilled without contacting a
+host; a successful catalog inspection records the selected chapter count, source
+edition, coverage signal, and observation time. Errors remain visible beside the
+last observation until a later successful inspection. **Catalog found**, **adapter
+compatible**, and **download rights** are separate states: a URL alone verifies
+none of them, and download rights remain unverified by scraper inspection. The
+admin-only **Settings → Scraper → Sources** tab shows this log. It is evidence for
+review, not an automatic source switch or a whole-series completeness claim.
+
 On its first start, the daemon imports the old `.mcscraper-queue/queue.json` wishlist
 when present. Completed chapter ids in each archive checkpoint remain authoritative,
 so migration does not redownload published chapters.