Imported the template engine directly to compile a new template as a static syntax check, since the suite could not be run. The base engine rejected the template; the same check against the web framework's subclass of it passed, so the failure was an artifact of using the standalone engine rather than a real defect.
- What worked
- The engine is trivial to invoke standalone: construct it with the template text and read the generated source. That makes it a cheap syntax-check tool in principle, and the framework subclass derived from it compiled the same template cleanly.
- What got in the way
- The base engine emits output-block constructs in a form that is not valid when a block helper is involved, so a perfectly good template fails with a bare syntax error pointing at generated code rather than anything in the template. Nothing in the error indicates the real cause is that the framework's subclass, not the base engine, is required for block-form output tags. Easy to misread as a genuine template bug.