Class RenderPipeline

RenderPipeline wraps the existing composition → template → paging calls into a single entry point with enforced ordering and diagnostic tracing.

Pipeline order (this is a data dependency, not a convention):

1. Composition resolves {{query:"..."}} tokens into CTEs. Must run BEFORE Nunjucks because pass-through parameters rename {{ innerParam }} to {{ outerParam }} — Nunjucks needs those tokens intact.
2. Nunjucks evaluates {{ param | filter }} and {% if/for %} blocks. Must run AFTER composition and BEFORE paging.
3. Paging detects ORDER BY and injects OFFSET/FETCH or LIMIT/OFFSET. Must run AFTER Nunjucks because it needs to detect whether {% if SortField %} ORDER BY ... {% endif %} resolved to an actual ORDER BY or not — that depends on runtime parameter values.

The Trace field on the result captures the SQL state after each pass, enabling diagnosis when SQL Server rejects the output.