Skip to content

feat: ebook - Align manuscript loading with validated sources #380

Open

Description

@ashleyshaw

Outcome

Connect verified manuscript files to the existing reader pipeline with explicit missing-source diagnostics.

Verified context

bookContentLoader.ts targets absent src/content; root content/book/ includes reference material. The inspected inventory does not prove all expected manuscript assets exist.

Scope

Discover approved sources, exclude the brief and reconcile existing eBook validation; do not migrate imaginary chapters.

Acceptance criteria

  • Canonical files and missing assets are recorded; this-one-time-on-acid-brief.md cannot enter reader content.
  • Type, chapter/part, page/order, title/subtitle and appendix mappings have explicit requiredness decisions.
  • Ordering, page breaks and contents are deterministic for supplied fixtures.
  • Invalid/unsupported/empty sources produce diagnostics; approved representative fixtures prove discovery and mapping.

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.

Branch instructions

  • Repository: lightspeedwp/ThisOneTimeOnAcidCom
  • Proposed branch: feat/ebook-source-loading
  • Base: develop
  • Naming policy: local guide, validator, organisation strategy.
  • Pull request template: Organisation .github/PULL_REQUEST_TEMPLATE/pr_feature.md, per inspected local routing; recheck before opening a PR.
  • Constraints: Preserve unrelated changes; do not force-push, merge or deploy. Complete applicable Spec Kit requirements before implementation.
  • Conflicts or missing evidence: Proposed branch, not an existing branch; collision freedom is unverified. Recheck current branch routing and open governance changes, including PR automation: repo-governance - Add governance automation and validation #346. Older instructions claim branch rules are absent; the inspected local guide and executable validator establish the current convention. This draft creates no branch or pull request.

Unanswered clarification questions

These questions clarify the existing source-loading outcome without inventing manuscript content or new implementation requirements.

  1. Which discovered files are approved canonical manuscript sources, and which expected assets are confirmed missing?
  2. Which type, chapter/part, page/order, title/subtitle and appendix fields are required or optional?
  3. What ordering, page-break and contents rules should the approved fixtures demonstrate?
  4. Which representative valid, invalid, unsupported and empty fixtures should provide acceptance evidence?
  5. Which existing validation rules remain authoritative, and how should conflicting source or metadata rules be resolved?

Continuation handover — manuscript sources and reader reliability

pasted.md

This issue owns the source-loading portion of the combined handover: canonical source selection, discovery, frontmatter/schema handling, deterministic ordering, explicit page breaks, contents mapping and diagnostics for invalid, unsupported or empty sources.

The complementary source-anchored continuity work belongs to #381. Neither issue is a duplicate of the other. Keep their requirements and acceptance evidence distinct, even where assessment or tests overlap.

Before implementation, reconcile current source, plans, issue requirements and existing branches/PRs. Treat the attachment’s PR #482 account and revision-specific observations as historical evidence requiring verification.

Do not infer manuscript approval from existing prose. Missing canonical-source or editorial-metadata decisions must be presented explicitly; do not rewrite, delete, renumber or publish manuscript prose.

The attachment proposes a combined implementation branch and draft PR. Those proposals do not establish current approval for a combined delivery scope. Adding this handover does not start implementation, create a branch or authorise publication.

Related project document: Source alignment and inventory — approved review package

Metadata

Metadata

Assignees

Type

No type

Fields

Priority

None yet

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions