Remove the client latest-chapter scan for lightnovelworld (#91) #93

Merged
sulthan merged 5 commits from ticket/91-client-lnw-scan-removed into main 2026-08-11 20:58:20 +07:00

5 Commits

Author SHA1 Message Date
sulthan 1e830f188c chore: refresh graphify map for the lnw client-scan removal 2026-08-11 20:28:28 +07:00
sulthan 48cd6e8d60 Address review: match the sibling adapter guard in the lnw skip (#91)
The manga script's refresh guards both the adapter and its method; the
novel guard skipped the adapter null-check. Provably non-null today, but
the sibling shape is the convention to match.
2026-08-11 20:27:11 +07:00
sulthan fb65c78e15 Document the Poll-only latest-chapter contract for lightnovelworld (#91) 2026-08-11 20:23:51 +07:00
sulthan 1bf571736f Pin the lnw scan removal with computeLatestChapter tests (#91)
The new export is the seam the suite addresses behaviour through: for
lightnovelworld no anchor set yields a Latest Chapter, comment-shaped
anchors included, and for novelfull the scan still returns the maximum and
ignores other series. The old lnw scan test asserted the deleted behaviour.
2026-08-11 20:23:51 +07:00
sulthan 3f897b6a65 Remove the client latest-chapter scan for lightnovelworld (#91)
The scan was scoped to the stored series_id, which since #89 is the Series
slug while chapter addresses carry a Chapter Slug, so on divergent novels it
matched zero anchors. The Poll refreshes lnw Series on a one-hour cooldown,
four times faster than the client throttle, so the scan optimised nothing
while its unscoped alternative would have let a public wpdiscuz comment
anchor write a Latest Chapter every Reader of the row shares. Delete the
adapter method; the shared computation yields null for an adapter without a
scanner, and the background refresh skips the Site before the due filter so
no Series page is fetched and no freshness timestamp is recorded.
2026-08-11 20:23:51 +07:00