Templetry Desktop v1.7.1

A patch for the forge code v1.7.0 shipped with a stated caveat: it was written against GitLab's and Gitea's published APIs and had never run against a real server. It was wrong, in the way untested code is wrong.

What was broken

GitLab caps a recursive tree at 100 entries and walks it depth-first. For any repository of size, the first page comes back as nothing but directories. So a project full of markdown showed no documentation in the Cloud preview.

The quieter half is worse: template detection read the same truncated page, so a repository carrying a template.yml could be reported as not having one — a wrong answer indistinguishable from a right one.

Gitea had the same problem from the other side: it returned 1000 entries of a 10,004-entry tree and admitted it only in a truncated field nothing was reading.

Neither is exotic. Both are what happens when an API is modelled from its documentation rather than its behaviour — the docs describe the fields, not what a large repository does to them.

The fix

GitLab trees are now paged. Both forges share one named limit, stated in the code instead of inherited by accident, and ample for what the tree is used for: finding template manifests, which live near the root, and the first 40 markdown files.

How it was found

Live tests against public repositories on gitlab.com and codeberg.org. They use no token, so they need no account, and they assert only what the Cloud panel actually renders. They ship in this release:

go test -tags liveapi -run Live -v ./...

They are behind a build tag because they reach servers nobody here controls — a red result may mean the API changed, or merely that Codeberg is down.

Making them run unauthenticated exposed one more fix: an empty token was travelling as an empty auth header, which forges reject where they would otherwise have served a public repository.

Still not covered

The authenticated half — private repositories, and creating and pushing to a repo on GitLab or Gitea — genuinely needs an account and remains unexercised. The caveat shrank; it did not disappear.

---

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