For a final chapter-name correction, trace only the representations that should change. Rename C03 from “Practice” to “Practical Examples,” then verify the authoritative heading, EPUB body heading, and third navigation label all use the new name while the destination still resolves to C03.
The first build from no accepted baseline—three chapters, three navigation items, one cover, and their acceptance conditions—is a separate exercise. This article owns the later one-change rebuild and C03 label synchronization. Keep cover-guide.png as a separate unchanged setting, but do not claim that a cover-inclusive package passed its package check: the current cover-result discrepancy remains unresolved.
Decision: make C03 label synchronization the finish line
Use three required results:
- the authoritative C03 heading is Practical Examples;
- the generated C03 body heading and third navigation label are Practical Examples;
- the third navigation destination remains C03 or
ch03.xhtml.
Chapter order, other prose, and cover setting are unchanged conditions. Do not combine another correction with this run.
Freeze the baseline C03 relationships
Identify before.epub and the editable authority. Record the old third navigation label, C03 body heading, and destination in one row. Add the cover-setting name in a separate field.
Use four columns: old package, expected authority value, new package, and judgment. Do not prefill the new-package column merely because the authority now says “Practical Examples.” Keep the body heading, navigation label, and destination on separate rows, and leave an unavailable value unverified.
Keep chapter ID C03 and its position unchanged. This is a label correction, not a chapter move.
Change only the authoritative C03 heading
Edit the C03 heading line in the source. Do not patch generated XHTML or nav files, and do not replace ordinary prose uses of “practice.”
Compare source before and after. If more than the intended heading line changed, stop before regeneration.
Check body heading and navigation label separately
Generate under a new artifact identity. Check the C03 body heading and the third navigation label as separate rows. A new body heading with a stale navigation label is not synchronized.
If both a visible contents page and nav exist, record each third label. Check only resources that actually exist in the package.
Preserve the C03 destination
The new label must still target C03 or ch03.xhtml. Record the href and the chapter reached. A correct-looking label linked to C02 or C04 fails the correction.
This article checks only the changed third entry and its propagation. Establish the first package’s nav, NCX, spine, and cover-reference acceptance conditions before beginning this one-change rebuild. Preserve those baseline conditions while tracing the changed C03 label.
Keep the cover as a separate unchanged condition
Compare the recorded cover setting with cover-guide.png. This prevents an unrelated cover change from being mixed into the C03 correction.
An unchanged setting name does not prove that a cover-inclusive package passed its package check. In the current evidence, the cover image existed inside the ZIP while the checking result reported it as missing. This article leaves that discrepancy unresolved.
What the Rune Studio checks support
Product documentation covers chapter order, per-chapter navigation inclusion, cover selection, confirmation, distinct output identity, and EPUB 3 generation.
In an image-free common sample, one text item was corrected, the old value reached zero and the new value one, a distinct package was generated, and the changed XHTML was confirmed in a passing, nonidentical result. That supports part of a regeneration route. It does not prove this article’s C03 heading-navigation synchronization or a cover-inclusive pass.
Keep the result pending until the three C03 representations and the required cover-inclusive package check are completed on the article-specific case.
Conclusion: hold until all three C03 representations agree
For this final EPUB correction, synchronize the authoritative C03 heading, generated body heading, and third navigation label, then verify that the destination remains C03. Record the cover setting separately and preserve the unresolved cover result.
If the generated body says “Practical Example” but the third navigation label still says “Practice,” reject that package and keep the accepted baseline untouched. Return to the authoritative C03 heading, correct the navigation source rather than editing the packaged XHTML, and generate again under a third identity. Recheck old-name count zero, new-name count one in the source, the generated body heading, the third navigation label, and the C03 destination. Also compare C01, C02, C04, and the unchanged cover setting with the baseline. Pass only when the three changed representations agree, the destination remains C03, and every declared unchanged item still matches. This recovery route shows that a fresh filename alone is not evidence of a correct rebuild and prevents a partially corrected package from replacing the accepted baseline.
Keep the baseline name, rebuilt name, changed source location, three C03 representations, and unchanged-item comparison on one result card. Another editor should be able to identify the accepted package without opening a file chosen only by its modification time. Preserve the rejected package until the comparison is recorded, then continue from the authoritative source rather than from that partial output.
Start with one C03 relationship row. If Rune Studio is a candidate, review the current Mac scope on the Rune Studio product page without promoting the partial common-sample check into an article-specific pass.
