chore: keep CLAUDE.md and package.json identical to main

A superset branch only stays cheap if the files it shares with main are
untouched. Both diverged: package.json carried a jd2 script and CLAUDE.md
described the tooling, so every merge from main would have conflicted on them
forever, and main's removal commit would have kept trying to delete the
tooling entries here.

The tooling files themselves do not exist on main, so they can hold whatever
they like. The jd2 invocation moves into docs/jdownloader.md as a direct npx
call instead of an npm script.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01UXfdJu7QhSJLr47K7koTDF

CLAUDE.md

@@ -15,14 +15,6 @@ InstaArchive Viewer is a React 19 + Vite 6 PWA for browsing archived Instagram d
 - `npm run lint` — type-check only (`tsc --noEmit`)
 - `npm test` / `npm run test:watch` — vitest
 - `npx vitest run src/lib/archive-patterns.test.ts` — a single test file
-- `npm run jd2 -- --archives <dir> --dry-run` — generate JDownloader `.crawljob`
-  files for every profile on disk (see `scripts/jd2-sync.ts` and
-  `docs/jdownloader.md`)
-- `scripts/gdl-sync.py` — the gallery-dl fetcher that replaced JD2 for the
-  ARTMS profiles (see `docs/gallery-dl.md`)
-
-**This branch is not published to GitHub.** `main` is; keep fetching tooling,
-host details and account lists on this branch only.
 
 Local development usually needs both `npm run dev` and `npm run server`. Local-folder mode works without the backend; server-mode archives do not.
 

docs/jdownloader.md

@@ -1,4 +1,16 @@
-# JDownloader2 — archive fetching quick reference
+# JDownloader2 — archive fetching
+
+> **This file lives only on the `tooling` branch.** `main` is published to
+> GitHub and deliberately carries none of this. Keep host details, IPs and
+> account names here.
+>
+> There is no `npm run jd2` script — `package.json` and `CLAUDE.md` are kept
+> byte-identical to `main` so that merging `main` into `tooling` never
+> conflicts. Run the crawljob generator directly:
+>
+> ```sh
+> npx tsx scripts/jd2-sync.ts --archives <dir> --dry-run
+> ```
 
 How content gets into this archive, and why the setup is shaped the way it is.
 

package.json

@@ -12,8 +12,7 @@
     "clean": "rm -rf dist",
     "lint": "tsc --noEmit",
     "test": "vitest run",
-    "test:watch": "vitest",
+    "test:watch": "vitest"
-    "jd2": "tsx scripts/jd2-sync.ts"
   },
   "dependencies": {
     "@tailwindcss/vite": "^4.1.14",