sulthan
0416354c06
Serves the userscript from the backend so Violentmonkey auto-updates it, plus two panel fixes.
## Backend: `GET /u/{token}/manga-bookmark.user.js`
The script is read off disk per request from `USERSCRIPT_PATH` and streamed back with its `@version` line rewritten.
- **Token in the path, not a header.** Violentmonkey's update poll sends no `Authorization` header, and the script embeds `API_TOKEN` in plain text — an open URL would hand that token to anyone who guessed it. Compare is constant-time.
- **404, never 401**, for both a wrong token and a missing file: a prober learns nothing about whether the route exists.
- Registered outside `withAuth` and outside the `WEB_PASSWORD` gate, so the script is installable on a deployment that never enabled the web UI.
- Stdlib only (`crypto/subtle`, `os`, `regexp`) — no new Go dependencies.
**The served `@version` is derived from the file's mtime** (`YYYY.MM.DD.HHMM`, UTC), discarding whatever the file body says. Violentmonkey only updates when the served version sorts higher than the installed one, so a body-derived version means one typo or accidental downgrade freezes updates forever. An mtime-derived version is monotonic by construction. A file with no `@version` line is served byte-identical. `os.Stat` runs before `os.ReadFile`, so a concurrent edit can only serve new content under an old stamp — which self-heals on the next poll — never the reverse.
## Bindmount
`./userscript` is bindmounted read-only at `/userscript`. The script is deliberately **not** copied into the image: the build context stays `./backend`, and widening it would churn every `COPY` path for a file the mount always supplies. Editing the file on the VPS is live on the next poll — no rebuild, no restart. `git pull` restores the committed version, so a redeploy always ships the repo's script; checkout sets mtime to now, so even a rollback serves a *higher* version and is adopted. Without the mount the endpoint 404s and logs it; bookmark sync is unaffected.
`@downloadURL` / `@updateURL` are literal URLs in the metadata block — it is parsed before any JS runs, so `API_BASE`/`API_TOKEN` cannot be interpolated. The token was already committed in this file, so this adds no new exposure.
## Userscript UI
- **Card actions moved under the subtitle.** Only the cover and the title continue reading now; the subtitle and the action row are inert siblings in the text column. A thumb that misses ★ lands on nothing, and Remove is never inside a link.
- **Loading spinner** while the first fetch is in flight — the panel used to read as frozen on the first open after a cold start. It draws only when there is nothing cached to draw instead, so a populated list never flaps.
## Verification
- `go test -count=1 ./...` — ok, 7.070s
- `node --check` clean; `node --test userscript/test/logic.test.js` — 14/14
- Live `docker compose` smoke: `/healthz` 200, wrong token 404, script served with a stamped `@version 2026.07.28.1057` and both metadata URLs present; `touch`ing the file advanced the served version to `2026.07.28.1100` with no restart.
Layout and spinner are verified on-device — there is deliberately no DOM test harness.
Reviewed-on: #8
Co-authored-by: Sulthan Zaki <sultankiki05@gmail.com>
Co-committed-by: Sulthan Zaki <sultankiki05@gmail.com>
156 lines
12 KiB
Markdown
156 lines
12 KiB
Markdown
# CLAUDE.md
|
|
|
|
This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.
|
|
|
|
## Status
|
|
|
|
Greenfield. Only `plans/mangaBookmark.md` exists — no code yet. That plan is the spec; read it before building. Two deliverables: a Go sync backend and a single Bromite-compatible userscript.
|
|
|
|
## What this is
|
|
|
|
A manga read-progress tracker for a user reading on **asurascans.com** (the current domain; asuracomic.net 301s here) and **demonicscans.org** from **Bromite** (mobile Chromium). A userscript injects on-page UI (floating button + slide-in panel) and syncs progress to a self-hosted Go backend so bookmarks unify across both sites and across devices.
|
|
|
|
## Hard constraints (these drive the design — do not violate)
|
|
|
|
Bromite uses Chromium's **native** userscript engine, not Tampermonkey:
|
|
- **No `GM_*` APIs anywhere.** No `GM_setValue`/`GM_getValue` (use page `localStorage`), no `GM_registerMenuCommand` (inject on-page UI), no `GM_xmlhttpRequest` for cross-origin (use plain `fetch()`). Keeping the script GM-free also lets it run in desktop Tampermonkey/Violentmonkey for faster iteration.
|
|
- Cross-origin `fetch()` works **only** against a CORS-enabled backend. Manga sites are `https://`, so backend **must be HTTPS** (mixed-content block otherwise).
|
|
- Asura and Demonic are **separate origins with separate `localStorage`** — a shared remote store is the only way to unify bookmarks. Cloud sync is required, not optional.
|
|
- Userscript runs in an **isolated world**, so the embedded API token is safe from the site's JS.
|
|
- Cloudflare's block on fetching the manga sites is **IP-reputation-based, not universal — and not reliably reproducible.** Verified 2026-07-26: plain `curl` from both the CGNAT dev machine *and* the deployed VPS got clean 200s with real HTML on both asurascans.com and demonicscans.org (homepage, series, chapter pages) — no interactive Turnstile challenge from either IP at test time. This contradicts an earlier, untested assumption that the CGNAT dev IP would be blocked; it was not, at least on this date. Treat "does curl work right now" as a live, time-varying fact to re-check, not a fixed property of a given machine — Cloudflare's bot scoring can flip a previously-clean IP without notice. Any backend fetcher still needs a graceful-degrade path for when it does get challenged, and adapters should be **verified against live pages** (Playwright MCP, on-device devtools, or a direct probe) before finalizing, not assumed from a single earlier test.
|
|
|
|
## Architecture
|
|
|
|
```
|
|
Bromite userscript (isolated world, per-site adapters, localStorage cache)
|
|
-- fetch() HTTPS --> reverse proxy (TLS + CORS) --> Go net/http --> SQLite (volume)
|
|
```
|
|
|
|
- **Backend** (`backend/`): stdlib `net/http` (a handful of routes, no framework) + `modernc.org/sqlite` (pure Go, `CGO_ENABLED=0` -> static binary -> distroless/scratch image). The reverse proxy terminates TLS; the Go service listens plain `:8080`.
|
|
- **Single-user store.** One `bookmarks` table keyed `<site>:<series_id>` (`asura`|`demonic`). Sync is **last-write-wins**. Schema and endpoint list are in the plan.
|
|
- **Endpoints:** `GET /bookmarks`, `PUT /bookmarks/{key}` (upsert; see `updated_at` rule below), `DELETE /bookmarks/{key}`, `GET /healthz` (no auth).
|
|
- **Web UI:** the same binary serves a password-gated browser UI on a second
|
|
hostname — `GET /` (list, or login page when there is no session),
|
|
`POST /login`, `POST /logout`, `GET /static/*`, and htmx fragment endpoints
|
|
under `/ui/*`. Templates and assets are `go:embed`-ed, so `backend/Dockerfile`
|
|
must copy `templates/` and `static/` as well as `*.go`. Sessions are stateless
|
|
HMAC cookies keyed off `API_TOKEN`; `WEB_PASSWORD` gates them and, when empty,
|
|
the web routes are not registered at all. UI mutations read-modify-write
|
|
through `Store.Get` + `Store.Upsert` so the `updated_at` rule stays in one
|
|
place. See `docs/superpowers/specs/2026-07-25-web-ui-design.md`.
|
|
- **Latest-chapter poller:** a ticker goroutine in the same binary re-checks
|
|
each bookmarked series' newest published chapter from the backend's own
|
|
network access, so `latest_chapter` stays fresh when the user is not
|
|
browsing. It is a *second, parallel* signal — the userscript keeps its own
|
|
`maybeCaptureLatestOnSeriesPage`/`backgroundRefreshLatest` logic unchanged.
|
|
Two independent clocks: a per-bookmark cooldown (`latest_checked_at` column,
|
|
enforced by `Store.DueForLatestCheck`'s WHERE clause) and a wake interval.
|
|
The row is stamped *before* the fetch so a broken series waits out a full
|
|
cooldown instead of retrying every tick, and writes go through
|
|
`Store.Get` + `Store.Upsert` so a new chapter never reorders the list.
|
|
Fetches use `bogdanfinn/tls-client` with a Chrome profile as defence in depth
|
|
against fingerprint-based blocking; any failure logs and skips. See
|
|
`docs/superpowers/specs/2026-07-26-server-latest-chapter-polling-design.md`.
|
|
The poller's `Store.Get` + `Store.Upsert` is not wrapped in a transaction, so
|
|
a userscript `PUT` that commits between the two can be overwritten by the
|
|
poller's stale re-read — reverting that read progress and, since the stored
|
|
value now differs, moving `updated_at` and reordering the list. This is a
|
|
known, accepted limitation for a single-user deployment, not a bug to fix.
|
|
- **`updated_at` drives list order, so it moves only on real reading progress:** the server applies its timestamp when the row is new or `last_chapter_num` changes, and otherwise keeps the stored value — favouriting a series or recording a newly published chapter must not reorder the list. `PUT` therefore returns the row **as stored**, and clients must adopt that response rather than their own payload. See `plans/2026-07-25-bookmark-list-favorites-design.md` §4.
|
|
- **Lifecycle buckets:** `status` on each bookmark is `reading` | `archived` |
|
|
`finished`, orthogonal to `favorite`. Archived and finished appear only in
|
|
their own tab — not in All, Updated, Favourites, or the recent strip. The
|
|
poller keeps checking archived series and skips finished ones. `finished` is
|
|
settable only from the web UI; `PUT /bookmarks/{key}` rejects it with 400.
|
|
**An empty incoming status means "keep the stored one"** — resolved on the
|
|
`VALUES` side of `Store.Upsert`, not in the conflict clause, because
|
|
`excluded.*` is the post-evaluation row and a default applied there would
|
|
wipe the bucket on every PUT from a client that predates the column. See
|
|
`docs/superpowers/specs/2026-07-27-status-buckets-design.md`.
|
|
- **Config via env:** `API_TOKEN`, `ALLOWED_ORIGINS` (comma list), `DB_PATH`
|
|
(default `/data/bookmarks.db`), `PORT` (default `8080`), `WEB_PASSWORD`
|
|
(gates the browser UI; unset disables it),
|
|
`LATEST_CHAPTER_POLL_ENABLED`/`_COOLDOWN`/`_INTERVAL`/`_BATCH`/`_STAGGER`
|
|
(background latest-chapter poller; defaults on, `1h`/`10m`/`14`/`20s`).
|
|
`USERSCRIPT_PATH` (file served at `/u/{token}/manga-bookmark.user.js`,
|
|
default `/userscript/manga-bookmark.user.js`, supplied by a bindmount).
|
|
|
|
### Userscript structure (single IIFE, `manga-bookmark.user.js`)
|
|
|
|
1. **Site adapters** — one per host, `detect(location, document)` returns page `type` + IDs. Identify type/IDs from **URL regex** (most stable); pull `title`/`cover` from **`og:title`/`og:image` meta tags**, not CSS classes.
|
|
2. **API client** — `apiGet/apiPut/apiDelete` with bearer header; `localStorage` key `mangabm:cache` for instant render + offline fallback.
|
|
3. **Progress logic** — auto-upsert `last_chapter` only when `chapterNum >= stored last_chapter_num` (re-reading old chapters must not regress progress; unparseable -> set current). Manual panel override forces any value.
|
|
4. **Retry queue** — every write goes through `pushBookmark`/`pushDelete`, so a
|
|
failed mutation is parked in `localStorage` (`mangabm:queue`) and replayed on
|
|
the next navigation, reconnect, or `refresh()`. Entries are markers
|
|
(`{key, op, sendStatus, attempts}`), never payloads — the body is read from
|
|
the cache at send time, so one entry per key gives ordering and coalescing for
|
|
free. `sendStatus` is **sticky**: while an archive is pending, later writes to
|
|
that key keep carrying the bucket, which is what stops a successful
|
|
in-between write from silently un-archiving the series. `refresh()` drains
|
|
before it fetches and overlays anything still pending, so the list never
|
|
flaps. A 400 drops the entry, a 401 aborts the pass and keeps the queue, and
|
|
transient failures retry to a cap of 10. Latest-chapter writes deliberately
|
|
stay out of the queue. See
|
|
`docs/superpowers/specs/2026-07-27-offline-retry-queue-design.md`.
|
|
5. **UI** — rendered inside a **Shadow DOM** root to isolate from site CSS
|
|
(critical on mobile). Three tabs (All / Favourites / Archived) and a row of
|
|
link chips to the web UI and both manga sites; `WEB_BASE` sits in the CONFIG
|
|
block next to `API_BASE`.
|
|
6. **SPA navigation** — Asura is Astro, client-routed on the comic/chapter pages: patch `history.pushState`/`replaceState` + listen `popstate`, re-run `detect()` on URL change so auto-update fires without reload. Demonic uses classic reloads (initial `document-idle` run suffices).
|
|
|
|
### Live URL shapes (verified 2026-07-26, may drift — re-check against live pages before trusting)
|
|
|
|
- **asurascans.com**: series `/comics/<slug>` (slug carries a trailing
|
|
site-wide build-hash suffix, e.g. `-059befe1`, that **rotates on every
|
|
redeploy**), chapter `/comics/<slug>/chapter/<n>`. `seriesId` must strip
|
|
the hash (`/-[0-9a-f]{8}$/`, `stripBuildHash` in the userscript,
|
|
`asuraBuildHash` in the backend); URLs keep the full slug — stale-hash
|
|
URLs 302 to current ones. Astro-rendered; chapter links present in raw
|
|
server HTML.
|
|
- **demonicscans.org**: series `/manga/<slug>` (slug may URL-encode punctuation, e.g. `%2527` for `'`), chapter `/title/<slug>/chapter/<n>/<page>` (older `chaptered.php?manga=<id>&chapter=<n>` form still exists as redirect, what series-page chapter-list anchors link through).
|
|
Encodings (incl. triple-encoded punctuation like `%25252D`) are identical
|
|
on /manga/ and /title/ pages, so decode-once seriesIds match — verified
|
|
2026-07-28.
|
|
|
|
## Commands (once code exists)
|
|
|
|
Backend (`cd backend`):
|
|
- Test all: `go test ./...`
|
|
- Single test: `go test -run TestName ./...`
|
|
- Build static binary: `CGO_ENABLED=0 go build`
|
|
|
|
Local stack: `docker compose up` (named volume mounted at `/data`, `restart: unless-stopped`).
|
|
|
|
Smoke test: `curl` the endpoints with `Authorization: Bearer <token>`; confirm `OPTIONS` preflight returns CORS headers and `/healthz` returns 200.
|
|
|
|
## Forge: Gitea, not GitHub
|
|
|
|
`origin` is a self-hosted Gitea instance (`gitea.violetcrown.my.id`), so **`gh` does not work here — use `tea` (Gitea CLI) for anything past plain git.** Common ones:
|
|
|
|
- Open a PR: `tea pr create --head <branch> --base main --title "..." --description "..."`
|
|
- List / view / check out: `tea pr list`, `tea pr <n>`, `tea pr checkout <n>`
|
|
- Issues: `tea issue create`, `tea issue list`
|
|
- Auth lives in `tea login`, not a `GH_TOKEN` env var.
|
|
|
|
`tea` prints its output as rendered boxes rather than plain text; the PR URL lands on the last line.
|
|
|
|
## Security invariants
|
|
|
|
- Auth on `/bookmarks*`: require `Authorization: Bearer <API_TOKEN>`, **constant-time compare**, 401 otherwise.
|
|
- CORS: reflect `Origin` only when in `ALLOWED_ORIGINS`; allow `GET,PUT,DELETE,OPTIONS` + headers `Authorization,Content-Type`; answer preflight `OPTIONS` with `204`.
|
|
|
|
## Relevant skills
|
|
|
|
`multi-stage-dockerfile` and `docker-compose-orchestration` for the container work (referenced in the plan).
|
|
|
|
## graphify
|
|
|
|
This project has a knowledge graph at graphify-out/ with god nodes, community structure, and cross-file relationships.
|
|
|
|
Rules:
|
|
- For codebase questions, first run `graphify query "<question>"` when graphify-out/graph.json exists. Use `graphify path "<A>" "<B>"` for relationships and `graphify explain "<concept>"` for focused concepts. These return a scoped subgraph, usually much smaller than GRAPH_REPORT.md or raw grep output.
|
|
- If graphify-out/wiki/index.md exists, use it for broad navigation instead of raw source browsing.
|
|
- Read graphify-out/GRAPH_REPORT.md only for broad architecture review or when query/path/explain do not surface enough context.
|
|
- After modifying code, run `graphify update .` to keep the graph current (AST-only, no API cost).
|