epic: ebook - Connect manuscript sources and harden reader behaviour #359

Outcome

Reliably connect approved manuscript sources to the existing responsive reader and retain reading continuity.

Verified context

The reader already offers spread/single modes, settings and navigation. Its loader targets absent /src/content/book/. Inspected evidence does not establish a complete canonical manuscript; missing chapters must not be invented. Editorial work is #37.

Scope

Coordinate K1–K3, discovering actual approved sources before integration.

Acceptance criteria

• Canonical manuscript availability and exclusions are verified explicitly.
• Ordering, page variants and contents follow validated contracts.
• Empty input and repagination cannot crash or silently misplace readers.
• Focused tests extend test: book-site - add Playwright frontend regression coverage #14 without duplicating rewriting or infrastructure.

Boundaries and sources

Creation defines work only; it does not start implementation. Preserve unrelated code, protected assets, editorial wording and existing records. Do not fabricate content, identity, media, manuscript chapters, dates or engagement data. Use approved repository-native authoring, validation, preview and publication decisions; do not provision an external CMS or database. Existing editorial verification remains with its current issues. All acceptance criteria remain unchecked until evidenced.

Repository evidence was inspected on develop at 4ecdb26d9655a48bf000a7c89da2f70383edce87. Recheck before implementation; no build or browser tests were run for this draft. Follow repository instructions and applicable Spec Kit requirements. Paths below refer to this repository.

Sources: repository instructions, application, editorial content.

Unanswered clarification questions

These questions clarify existing reader coordination; they do not approve publication scope or authorise implementation.

1. Which manuscript sources and versions are approved for reader integration, and which are explicitly excluded?
2. Who confirms source availability and editorial approval before integration begins?
3. Which ordering, page-variant and contents contracts must the child issues share?
4. Which child evidence is required to accept source loading, reading continuity and regression coverage?
5. How should unresolved launch-reading decisions in decision: website - Define launch reading requirements #411 affect sequencing without assuming full manuscript publication is required?