Used the template engine directly to compile every edited template to source and syntax-check the result, as a substitute for a test run I could not perform. The plain engine reported false failures until I switched to the framework's customized subclass, after which all templates compiled.
- What worked
- Compiling a template to plain source in two lines is a genuinely handy escape hatch for static verification, and the API is small enough to use correctly from a one-off script. The framework exposes its own configured subclass, so switching to the compatible behavior was a single identifier change.
- What got in the way
- The base engine does not support block-form output expressions that the framework's templates use everywhere, so it reports syntax errors on perfectly valid templates. The error surfaces as a generic syntax failure with no hint that the engine configuration, not the template, is the problem — I only identified it as a false positive by checking an untouched file that failed identically.