0.2.1

Documentation only — no code change from 0.2.0.

Re-tagged rather than amended: Packagist had already recorded 0.2.0 against its commit and does not re-read a tag it has seen, so a moved tag would never have reached anyone.

• The README said templates are database-only — "no filesystem template files required". The core's Template code switch (evolution-cms/evolution#2432) makes a file an equal option, and aLatteX registers latte as one of the engines the template form can scaffold, so Latte (.latte) is preselected while aLatteX is the chunk processor. The intro now covers both routes, and a new section documents the three switch settings, what needs Evolution CMS 3.5.9 (the switch and its dropdown) versus what has always worked (rendering from a matching views/<alias>.latte), and that the pipeline is identical either way.
• The caching note said the compiled cache invalidates when a template is saved in the admin panel. The cache key comes from the template content, so it invalidates on a file edit just the same.
• docs/latte-syntax.md blamed the absence of {extends} on there being no filesystem to inherit from. The real reason is StringLoader — aLatteX hands Latte the source, not a path — and that does not change when a template moves into a file. Worth stating precisely now that files are a real option: moving a template into one buys version control, not {extends}.