CSV_TO_PDF_REPORT/templates/definition_of_done.md

Definition of Done

Project-specific baseline seeded from Envelope_Report_Generator_Requirements.md on 2026-09-04. This should be tightened further once the implementation stack, automated test framework, and CI pipeline are finalized.

An item is only Done when ALL of the following are true:

• The story's acceptance criteria are met and the behavior matches the operator workflow described in the requirements.
• The change is implemented in working software under code/ and is runnable in the current local development setup.
• If the story changes how the product is launched, packaged, or resolves runtime configuration (e.g., a new desktop entry point, a new child-process launch, a new license/config resolution path), verification includes running the actual built artifact the way the target user would run it — not only an in-process test harness or a dev-shell invocation such as dotnet run.
• The change is self-reviewed against the story, nearby code, and likely regressions because no separate reviewer process is defined yet.
• Relevant validation has been performed using representative sample CSV/template data for the feature being changed.
• If the story affects rendering, validation covers expected PDF output, progress reporting, and failure handling for the touched scenario.
• If the story affects layout or preview behavior, the GUI behavior has been checked visually for usability by a print-operator workflow.
• Missing-font behavior remains blocking, and missing-image behavior remains warning/placeholder-based, unless the story explicitly changes that rule.
• No new known defect, blocker, or technical debt is introduced without being captured in logs/impediment_log.md or logs/technical_debt_log.md.
• Documentation or backlog notes are updated when the change affects workflow, configuration, constraints, or future planning.

Additional release-quality checks apply when relevant:

• High-volume rendering work demonstrates no material regression against the target of 100,000 records at 300 DPI in under 10 minutes.
• Output remains within the product constraints for PDF format, RGB color space, and sub-2 GB file size where applicable.
• The GUI remains responsive while background CLI rendering is in progress.