audit-generated-config-integrity

Validate design-docs configuration by running a post-generation gate that enforces TypeScript compilation, contentBlock union coverage, and block order alignment. This ensures the config is type-safe, properly ordered, and unique before brand sync.

ContentBlock union coverage validation ensures every block type defined in the union has a corresponding renderer. This prevents rendering failures by verifying the generated config fully covers all block types before processing.

Check contentBlock order by verifying the generated config aligns with the source HTML document order, such as ensuring the header appears before the byline. This maintains structural consistency between the source and rendered output.

Design-docs config fails TypeScript compilation when required fields like url, fonts, or contentBlocks are missing or incorrectly typed. A validation gate applies TypeScript compilation checks to catch these errors and provide remediation guidance.

Yes, design-docs config validation checks for chart data presence in any birdkit or datawrapper blocks. It verifies that corresponding constants are exported and used in the rendering pipeline to prevent empty visualizations.

Yes, you can enforce per-article fonts and colors uniqueness by running a post-generation validation policy. This prevents accidental content duplication across articles and ensures background color consistency with the brand rendering context.