Consider is assigning `$contact` to template is required/ maintainable when rendering contact tokens with smarty enabled
We have a bunch of code that loads the
$contact and assigns it to the template for pdfs & emails when smarty is enabled (via the CIVICRM_Mail_Smarty or whatever it is define).
We could either
a) assign 'whatever we have for 'contact' to the template in tokenCompatSubscriber, just before processing smarty or b) create a new extension (outside core) that people can install if they want ^^ as a behaviour which does basically the same.
I'm leaning towards b since I think we are better off keeping any decisions about blanket assigning for later since
a) we don't know if anyone even uses it and b) we would be locked into a query object style array