sulthan/mangaBookmark
1
0
Fork 0
Code Issues 4 Pull Requests Actions Packages Projects Releases Wiki Activity

lightnovelworld a-will-eternal: chapter list max (1317) disagrees with the Site's own newest-chapter indicators (1298) #79

New Issue
Open
opened 2026-08-11 09:20:47 +07:00 by sulthan · 2 comments
sulthan commented 2026-08-11 09:20:47 +07:00
Owner
Copy Link
Copy Source

Symptom

The Poll reports Latest Chapter 1317 for lightnovelworld:a-will-eternal, while every
newest-chapter indicator the Site renders on that page says 1298. A Reader whose
Progress is 1298 therefore sees a New Chapter ember for a chapter dated 19 days older
than the one they last read.

Measurement (live, 2026-08-11, headless browser DOM pass, HTTP 200, no Cloudflare challenge)

https://lightnovelworld.net/novel/a-will-eternal/ renders 1317 chapter entries,
newest-first: top entry is Ch. 1298, bottom is Ch. 1. A 19-entry block, Ch. 1299 to
Ch. 1317, is wedged mid-list between Ch. 274 and Ch. 273, in ascending order.

Indicator Value
Numeric maximum of the chapter list 1317
First (top) entry of the chapter list 1298
"New Chapter" widget Vol. 1 Ch. 1298
Date on Ch. 1298 26 Apr 2026
Date on Ch. 1299-1317 7-8 Apr 2026
prev/next reading order ends at 1298 (no next link)

The misplaced chapters are real and belong to this Series: Ch. 1300 and Ch. 1317 both
return 200, carry <h1>A Will Eternal Chapter N</h1>, and their "All Chapter" anchor
points at /novel/a-will-eternal/. Ch. 1317 is titled "A will eternal epilogue"; the
Series status is Completed.

The Site's own prev/next chain, built from list order, reads:
... -> 273 -> 1317 -> 1316 -> ... -> 1299 -> 274 -> 275 -> ... -> 1298.

Prevalence: 0 of 5 other Series pages sampled the same day show any disagreement
between list maximum and top entry (reverend-insanity 2334, immortality-simulator
1232, dreadful-radio-game 209, evil-god-average 82,
surviving-in-a-romance-fantasy-novel 176). The earlier 41-novel survey in
docs/research/lightnovelworld-chapter-vs-series-slug.md also found no second example.

[INFERENCE] The Site imported the final volume late and inserted it at the wrong list
position; the block's dates match Ch. 274's neighbourhood. Not proven.

Decision: Latest Chapter follows the largest chapter number

Settled 2026-08-11. Latest Chapter is the highest chapter number the Site lists for a
Series. It is not the Site's own newest-chapter widget, and it is not the most recent
date.

Same root shape as #78: a derived summary disagrees with the underlying record, and the
record wins. In #78 the stale summary is the userscript's own cached row, adopted from a
PUT response and never re-read. Here the stale summary is the Site's "New Chapter"
widget, which disagrees with the chapter list it sits above. Trust the record.

By that rule the current behaviour is correct. Chapters 1299-1317 exist, are
reachable, and belong to this Series; a Reader at 1298 genuinely has 19 unread chapters,
so the New Chapter ember is earned. No code changes.

Do not "fix" this later

This issue exists so the next reader does not add a plausible-looking guard. Specifically,
rejected here:

  • Cross-checking the numeric maximum against the "New Chapter" widget or the top list
    entry, and preferring the widget on disagreement.
  • Rejecting a chapter whose date is older than the current Latest Chapter's date.
  • Capping the maximum at the first list entry.

Each of these would report 1298 for a Series that has 1317 published chapters, and each
adds a second, weaker source of truth for a value that already has a strong one.

Relation to #77

#77 rewrites lnwSeriesFixture in backend/internal/latest/sites_test.go and moves the
lightnovelworld scan window. a-will-eternal is a poor fixture for that work for two
independent reasons - the divergent-slug case it was meant to cover does not apply to it
(its Chapter Slug and series slug coincide), and its chapter numbering is the anomaly
described here. #77 replaces it with immortality-simulator. Nothing in this issue blocks
#77.

## Symptom The Poll reports Latest Chapter **1317** for `lightnovelworld:a-will-eternal`, while every newest-chapter indicator the Site renders on that page says **1298**. A Reader whose Progress is 1298 therefore sees a New Chapter ember for a chapter dated 19 days *older* than the one they last read. ## Measurement (live, 2026-08-11, headless browser DOM pass, HTTP 200, no Cloudflare challenge) `https://lightnovelworld.net/novel/a-will-eternal/` renders 1317 chapter entries, newest-first: top entry is Ch. 1298, bottom is Ch. 1. A 19-entry block, **Ch. 1299 to Ch. 1317**, is wedged mid-list between Ch. 274 and Ch. 273, in ascending order. | Indicator | Value | | --- | --- | | Numeric maximum of the chapter list | 1317 | | First (top) entry of the chapter list | 1298 | | "New Chapter" widget | Vol. 1 Ch. 1298 | | Date on Ch. 1298 | 26 Apr 2026 | | Date on Ch. 1299-1317 | 7-8 Apr 2026 | | prev/next reading order | ends at 1298 (no `next` link) | The misplaced chapters are real and belong to this Series: Ch. 1300 and Ch. 1317 both return 200, carry `<h1>A Will Eternal Chapter N</h1>`, and their "All Chapter" anchor points at `/novel/a-will-eternal/`. Ch. 1317 is titled "A will eternal epilogue"; the Series status is Completed. The Site's own prev/next chain, built from list order, reads: `... -> 273 -> 1317 -> 1316 -> ... -> 1299 -> 274 -> 275 -> ... -> 1298`. **Prevalence:** 0 of 5 other Series pages sampled the same day show any disagreement between list maximum and top entry (`reverend-insanity` 2334, `immortality-simulator` 1232, `dreadful-radio-game` 209, `evil-god-average` 82, `surviving-in-a-romance-fantasy-novel` 176). The earlier 41-novel survey in `docs/research/lightnovelworld-chapter-vs-series-slug.md` also found no second example. `[INFERENCE]` The Site imported the final volume late and inserted it at the wrong list position; the block's dates match Ch. 274's neighbourhood. Not proven. ## Decision: Latest Chapter follows the largest chapter number Settled 2026-08-11. **Latest Chapter is the highest chapter number the Site lists for a Series. It is not the Site's own newest-chapter widget, and it is not the most recent date.** Same root shape as #78: a derived summary disagrees with the underlying record, and the record wins. In #78 the stale summary is the userscript's own cached row, adopted from a PUT response and never re-read. Here the stale summary is the Site's "New Chapter" widget, which disagrees with the chapter list it sits above. Trust the record. By that rule the current behaviour is **correct**. Chapters 1299-1317 exist, are reachable, and belong to this Series; a Reader at 1298 genuinely has 19 unread chapters, so the New Chapter ember is earned. No code changes. ## Do not "fix" this later This issue exists so the next reader does not add a plausible-looking guard. Specifically, rejected here: - Cross-checking the numeric maximum against the "New Chapter" widget or the top list entry, and preferring the widget on disagreement. - Rejecting a chapter whose date is older than the current Latest Chapter's date. - Capping the maximum at the first list entry. Each of these would report 1298 for a Series that has 1317 published chapters, and each adds a second, weaker source of truth for a value that already has a strong one. ## Relation to #77 #77 rewrites `lnwSeriesFixture` in `backend/internal/latest/sites_test.go` and moves the lightnovelworld scan window. `a-will-eternal` is a poor fixture for that work for two independent reasons - the divergent-slug case it was meant to cover does not apply to it (its Chapter Slug and series slug coincide), and its chapter numbering is the anomaly described here. #77 replaces it with `immortality-simulator`. Nothing in this issue blocks #77.
sulthan added the wontfix label 2026-08-11 09:20:47 +07:00
sulthan commented 2026-08-17 15:23:06 +07:00
Author
Owner
Copy Link
Copy Source

Referenced by wayfinder ticket #121 (Data-correction actions), on map #114 — this is the motivating case for an owner-side Latest Chapter correction, since the wrong number is visible to every Reader of the Series. That ticket decides whether a hand-set value is authoritative and what stops the next poll overwriting it; it does not replace fixing the adapter's chapter-list read.

Referenced by wayfinder ticket #121 (Data-correction actions), on map #114 — this is the motivating case for an owner-side Latest Chapter correction, since the wrong number is visible to every Reader of the Series. That ticket decides whether a hand-set value is authoritative and what stops the next poll overwriting it; it does not replace fixing the adapter's chapter-list read.
sulthan commented 2026-08-18 09:33:12 +07:00
Author
Owner
Copy Link
Copy Source

Follow-up to the 2026-08-17 note above: #121 is closed, and it resolved without relying on this
issue. The decision recorded here — Latest Chapter is the highest chapter number the Site lists —
stands unqualified, so 1317 is correct for a-will-eternal and there is nothing here for an owner to
correct. #121's opening premise (that every Reader sees a wrong number) was stale when written; the
map's "fixes the class of #79" line is struck.

What #121 did settle, for the class that does exist — a Reader-raised Latest Chapter on a Series
whose page the Poll cannot read — is that a hand-set value is not authoritative: no pin, no
floor, and the next successful Poll or any Reader's page visit overwrites it. A floor in particular
would have made this Series' downward direction unrepairable, which is the direction this issue
says is wrong.

Follow-up to the 2026-08-17 note above: #121 is closed, and it resolved **without** relying on this issue. The decision recorded here — Latest Chapter is the highest chapter number the Site lists — stands unqualified, so 1317 is correct for a-will-eternal and there is nothing here for an owner to correct. #121's opening premise (that every Reader sees a wrong number) was stale when written; the map's "fixes the class of #79" line is struck. What #121 did settle, for the class that *does* exist — a Reader-raised Latest Chapter on a Series whose page the Poll cannot read — is that a hand-set value is **not** authoritative: no pin, no floor, and the next successful Poll or any Reader's page visit overwrites it. A floor in particular would have made this Series' *downward* direction unrepairable, which is the direction this issue says is wrong.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
Something is broken
 enhancement
New feature or improvement
 needs-info
Waiting on reporter for more information
 needs-triage
Maintainer needs to evaluate
 ready-for-agent
Fully specified, ready for an AFK agent
 ready-for-human
Needs human implementation
 wayfinder:grilling
wayfinder:map
wayfinder:prototype
wayfinder:research
wontfix
Will not be actioned
No Label wontfix
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
sulthan
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: sulthan/mangaBookmark#79
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?