Finishing a Mac manuscript as an EPUB requires more than producing one package. Link the manuscript revision, settings revision, and artifact ID in a release-candidate record, then return every defect to the authoritative source. A cover-free two-chapter EPUB has been checked as valid with nav, NCX, OPF metadata, and spine order. A cover-attached candidate has an unresolved inspection issue and remains separate rather than borrowing the cover-free result.
Identify the three revisions on one candidate record
Write values such as source-v05, settings-v03, and release-20260811-01.epub on the same row. These identify manuscript content, TOC and metadata settings, and the generated artifact as related but distinct revisions.
Avoid labels such as latest or final. Before inspection, match the record's artifact name to the actual file so an older EPUB cannot receive the new candidate's result.
Return each defect to its owner
A typo or missing paragraph belongs in the manuscript revision. An author name, chapter order, TOC label, or cover setting belongs in the settings revision. Editing only the generated package loses the correction on the next build.
Record the defect, return path, and new revision. If ownership is unknown, keep the candidate pending instead of promoting the EPUB itself to a new source of truth.
Record the verified cover-free structure
The 11 August 2026 cover-free two-chapter sample returned valid=true. Its nav, NCX, OPF metadata, and spine sequence were also inspected. Those values can be attached to the exact artifact ID in the candidate record.
Do not compress the evidence into the phrase export succeeded. Separate validity, navigation, metadata, and reading order so the next artifact can be compared field by field.
Quarantine the unresolved cover-attached candidate
A cover resource is present in the package, while the current CLI inspection reports missing/valid=false. Because the cause is unresolved, this candidate cannot inherit the cover-free acceptance.
Track resource presence, package reference, inspector output, and reader display separately. Keep the candidate pending until the conflicting evidence is explained.
Use two signatures for package and reader checks
Internal inspection and reader review need separate fields. Correct nav and spine data do not prove that headings and images look right in a reader; a plausible display does not prove sound metadata and references.
Both signatures must point to the same artifact ID and inspection time. This avoids reviewing an older package while approving a newly named candidate.
Rebuild from the corrected source
Return one defect to the manuscript or settings record, create a new revision, and export a new artifact ID. Preserve the old candidate instead of overwriting it.
Recheck the corrected field and every field that previously passed. A repair is complete only when it survives regeneration without damaging nav, NCX, OPF metadata, or spine order.
Rune Studio's responsibility in this chain
Rune Studio connects Mac manuscript editing and EPUB 3 generation, and the measured cover-free structure can be stated at Stage 4. That evidence belongs to the identified candidate only.
Store acceptance, store display, and the unresolved cover-attached inspection are separate exits. Product generation, package inspection, reader review, and store review must not be collapsed into one success claim.
Conclusion: keep only traceable candidates
Create the five columns for source revision, settings revision, artifact ID, inspection result, and return path. Enter the cover-free evidence on one row and keep the cover-attached candidate pending on another.
An EPUB is finished for this stage when a defect can be returned to its owner, regenerated under a new ID, and rechecked as the same identified artifact. The candidate record makes that repeatability visible.