report-composer

Automating report generation from markdown templates involves parsing template definitions and run results to materialize final composed MD files. This process applies AST-based parsing to extract structure and recursively handle SUB-* templates for consistent project delivery.

The best way to parse setup.md driven workflows is through AST-based template parsing that extracts structure and regions. This enables scenario expansion and recursive handling of SUB-* templates to materialize final reports from run results.

Yes, automated report creation supports template-driven generation from both standards and client overrides. By applying AST-based parsing to extract structure and regions, it materializes final reports while accommodating project-specific requirements.

To resolve REG and CUSTOM cards when expanding report scenarios, use AST-based parsing of template definitions. This approach recursively handles SUB-* templates and materializes final composed MD files from run results.

Yes, automated report materialization works with md-writer for polishing output. The tool generates delivery/composed-*.md files from template definitions and run results, then delegates final polishing to md-writer to ensure consistent delivery.

AST-based parsing is needed for template-driven report generation to accurately extract template structure and regions. This mechanism enables scenario expansion, recursive handling of SUB-* templates, and consistent materialization of final reports.