Templetry Desktop v1.8.0

Engine v1.10.0 gave every template a taxonomy — three axes describing what a form is, what it is written in and what it is built on (ADR-0017). This release makes the app read it.

Build: the catalog is navigable

Every form shows its axes as chips — kinds in brass, languages and frameworks quieter — and the catalog filters on them:

• Kind chips, OR within the axis, the same semantics as templetry list --kind a --kind b. Only the kinds the loaded catalogs actually use appear; a chip that can never match anything is noise.
• A text box matching name, description and every axis at once.

Parents with no matches disappear rather than leaving an empty heading, and when nothing matches the message says why it might be: a form that declares no taxonomy never matches a kind.

The catalog reached 25 forms across 10 parents this week. One flat list was already awkward.

Cloud: a template repo now says what it is

A repository carrying a template.yml was flagged as engine-readable and nothing more. That was not a display decision — the tree walk kept only the directory the manifest lived in, so there was nothing else to show.

It now keeps the manifest path, reads each one (bounded and concurrent) and parses it with the engine. Each detected form reports its name, description and taxonomy. A manifest that will not parse still appears with its path, labelled unreadable: the file is there, it simply says nothing the engine understands.

This works on GitHub, GitLab and Gitea alike, because it reuses the per-forge file reader that landed in v1.7.0.

Also

Runs on engine v1.10.0, which compiled unchanged — the fifth time a minor engine bump has cost the app nothing.

---

Windows SmartScreen still warns on the installer: these builds are not code-signed. Choose More info → Run anyway, or use the portable exe.