ManYue pre-chapter recap cards: retain only what is needed to resume a serial

An update list can identify a new chapter without restoring your memory of where the serial stopped. Make a short personal recap connecting the last-read chapter to the next one. This task concerns narrative continuity, not update configuration, download queues or automatically generated summaries.

Identify the chapter actually completed

Use history or your record to locate the last genuinely completed chapter and verify its ending. Record source, number and title, distinguishing previews and extras. If you stopped midway, record that scene rather than marking the chapter complete. Update and download counts describe different states and cannot establish completed reading. A truthful content boundary determines which evidence belongs in the recap.

Use three continuity fields

Write one or two sentences for the last confirmed event, unresolved question and next starting point. Keep predictions labelled and avoid retelling the chapter. Link an existing character note instead of copying a roster. Use external text or supported remarks: “card” describes your record, not a dedicated template or newly generated app interface.

Anchor the last event to its evidence

Save and test a supported bookmark to the decisive ending page, with chapter and panel description. A lone suspense keyword may become meaningless, so identify people, objects and situation. Minimal locators are sufficient without copying many images. Separate advertisements and author notices from the final story event. If access later fails, keep the dated description and state that its source is temporarily uncheckable rather than turning memory into verified quotation.

Verify the new catalogue item

When an update appears, identify continuation, preview, repost or extra before treating it as the next story chapter. New dates can belong to pinned notices or reuploads. Inspect the opening against the recap’s unresolved thread and record source/check date. For numbering gaps, examine explanations and neighbours rather than assuming missed reading or renumbering old notes to create continuity.

Keep the pre-read record separate

Read the old card before the new chapter and revisit only necessary context. Do not backfill later revelations into an undated old record. Date any new prediction separately and retain its hypothetical status. Shorten repetition while preserving event, question and evidence. The aim is understanding the new opening, not spending maximal time rereading everything.

Record how the new chapter responds

After reading, mark questions answered, still open or based on a rejected assumption, with new chapter evidence. Absence of mention does not prove abandonment, and an unmet prediction is not a plot error. Preserve old dated questions and create the next recap separately. Identify whether an extra adds background or advances present action. These are narrative judgements supported by pages, not statistics or favourite flags.

Keep the recap useful during a hiatus

During a hiatus retain the latest useful recap and essential history without rewriting it on every list visit. Re-establish anchors after source/edition changes through chapter and scene, not copied percentages. Preserve files and reading records separately; the recap is not a comic backup. You can pause a to-read entry while retaining the card. It should remain understandable later without relying on today’s memory of aliases.

Acceptance and mistaken inferences

Finish when the card identifies the actual last event, unresolved question and correct next chapter, with dated boundaries between old interpretation and new evidence. Downloads are not completed reading, and previews are not necessarily story events. Correct contradictions against checkable pages rather than rationalising every old guess as foreshadowing. The workflow requires no daily update, new reminder or message to the source; reuse the same three fields when the serial continues.

Related guides and sources

Follow updates in ManYue: build a list for ongoing reading; ManYue reading history: find the last title and position.

Checked on November 3, 2026: Apple public version information lists ManYue 2.0.4, requiring iOS / iPadOS 15.0 or later. Feature scope follows the official App Store description and the installed version. This article describes actions and content checks you can perform; it does not claim step-by-step physical-device or private-server testing. Manual records, external tools and application controls are identified separately, and code observations or personal inferences are not presented as verified automatic capabilities.