Prepare the repository for a public release

- docs/deployment.md: step-by-step Docker deployment for anyone (setup,
  configuration, LAN/HTTPS/VPN access, adding manga, operation, prebuilt
  images, backups, peering, troubleshooting, rules for agents).
- deploy/circus.sh: host helper without Node (status, up/down with queue
  pause, logs, pause/resume, update, rescan, restore-test); deploy/compose.https.yml
  + Caddyfile for automatic HTTPS.
- README rewritten for public readers (Docker first, sources/copyright note,
  docs index); AGENTS.md + CLAUDE.md for contributors and coding agents.
- Removed notes about one particular installation (Windows host, handoffs,
  audits of a private library, benchmarks with local paths, wishlist, reading
  map) and the unused ops/proxmox templates; generalized remaining mentions of
  hosts, VPN and Windows-only commands.
- Defaults: TZ and reading time zone UTC; .gitattributes keeps shell/YAML LF.
- Personal agent coordination files are git-ignored (CLAUDE.local.md,
  .claude/skills/manga-org/).

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

scraper/README.md

@@ -4,9 +4,8 @@ The scraper uses small host adapters to create a common manifest, followed by on
 
 Start with [AGENT_RUNBOOK.md](AGENT_RUNBOOK.md). It contains the host-specific procedures, safety limits, and stop conditions. `manifest.example.json` documents the interchange format.
 
-The historical human-readable wishlist is [WISHLIST.md](WISHLIST.md). Once the
-managed daemon has started, `data/scraper/queue.json` is the authoritative queue and
-is edited through the admin UI.
+Once the managed daemon has started, `data/scraper/queue.json` is the authoritative
+queue and is edited through the admin UI.
 
 ## Managed service
 
@@ -32,9 +31,8 @@ Queue schema version 3 supports scoped jobs, multiple jobs for the same upstream
 series, one sequential worker per source, incremental chapter publication, library
 duplicate/version checks, and configurable nightly update discovery. See
 [`docs/scraper-service.md`](../docs/scraper-service.md) for the service contract and
-[`docs/local-deployment.md`](../docs/local-deployment.md) for the currently running
-Windows Scheduled Task deployment. On that machine the scheduled task owns the single
-supervisor; do not run `npm run start:all` beside it.
+[`docs/deployment.md`](../docs/deployment.md) for running it in Docker. Run only one
+supervisor or container against the same library and data.
 
 ```bash
 npm run test:scraper