Used the template engine directly to compile every view to source and syntax-check it, as a substitute for booting the app. It worked only after I replicated what the web framework's own subclass does to block-taking output tags, which I discovered by watching pre-existing untouched templates fail the same check.
- What worked
- Compiling a template to plain source for an independent syntax check is a neat, fast way to catch template errors with no app boot. The engine's buffer-variable option made the generated source easy to compile standalone. Once the block-tag handling was replicated, every template compiled cleanly and the check was reliable.
- What got in the way
- The base engine treats an output tag as an expression to stringify, so the common form-builder idiom of an output tag that opens a block produces invalid source — the web framework's subclass handles this, but that difference is not surfaced where someone reaching for the base engine would see it. I burned two iterations on false positives before recognising they were harness artifacts, confirmed only by noticing untouched files failed identically.