--- name: report-release description: Rebuild and verify a report's final export, including PDF layout, citations, links, figures, copied text, source/export consistency and accurate printed-page review queues. Use for final document checks or re-export after edits. --- # Report release Verify the actual deliverable produced from the latest authorised source. Use the available document/PDF skills and established build tools appropriate to the source format. This is a release check, not a substitute for substantive review. ## Recurring issues Whenever a user or reviewer identifies a complex or systematic issue that plausibly recurs, formulate or refine a contextual pattern and record the example. Apply the pattern across the draft when that broader check is already authorised; otherwise explicitly offer the wider pass alongside addressing the local request. Follow the [recurring-pattern procedure](../report-review/references/recurring-patterns.md) for scope, contextual matching, counterexamples and completion. This applies even when only one instance has been pointed out; a routine isolated typo does not automatically justify a broad audit. ## Build from the right source Identify the editable source, dependencies, canonical output and latest user edits. Preserve an appropriate baseline, inspect existing changes, and honour exclusions such as large data files. Re-export-only requests preserve wording and scope. Stage only when requested, using explicit inspected paths; do not infer commit, publication or submission authority. Record source/export identities using suitable metadata or hashes for permitted files. Build through the established workflow. Resolve material compilation, bibliography and cross-reference errors. A successful build establishes neither semantic correctness nor visual quality. Confirm that the canonical saved output is the one inspected, not an older preview. Check for source or dependency changes made during the build/verification window; if they changed, rebuild and repeat relevant checks before declaring the output current. ## Verify meaning and rendering Read [release checklist](references/release-checklist.md) when verifying a full release. For a small re-export, inspect changed content and layout dependencies; broaden if pagination, typography, references or figures changed. If a full visual audit is requested, inspect every rendered page and record coverage. Contact sheets help navigation but do not replace readable inspection of dense or suspect pages. Use text extraction for content, counts and copying checks; use rendered pages for spacing, clipping and layout. Verify important results, qualifications and approved changes in the export. Check visual meaning as well as aesthetics: units, population, denominators, legends, category distinctions and illustrative-versus-measured scope. Apply the actual presentation requirements. Colour and greyscale policy, caption position, font size and length constraints belong to the document's governing guidance and approved design. Use greyscale/pattern checks when printing or accessibility requires them. Keep code indentation and literal content intact unless an authorised technical correction requires change. When the deliverable has formal accessibility or format requirements, use the [standards guide](../report-drafting/references/report-standards.md#citation-language-and-accessibility) to locate the official sources for the applicable profile. Reuse the report's requirements record and capture what was verified in the exported file and what remains open. ## Page map and handoff For each justified review stop, verify the exact passage in the final export and record section/title, printed page label and physical PDF page separately. Use the visible printed label, not an assumed constant offset or an old section-start page. Check headings exist and account for examples split across pages. Reconcile required findings, deferred items, rubric constraints, source support and post-writing meaning checks. If rendering or link checking was unavailable, state the incomplete verification explicitly rather than calling the release fully verified. Deliver the source/export, concise changes, actual verification coverage and unresolved limits. Retain approved text without cosmetic churn and end the manual queue when no further consequential user judgement is needed. Submission readiness is a bounded judgement; distinguish presentation blockers from acknowledged research limitations and unresolved mandatory requirements.