What is deliberately not here

No LTS branch. One maintainer, one line of development, and every installation on main: a maintenance branch would be a second tree to keep honest, and the honest state of it would be "untested". If a release ever needs fixing without the release after it, that is the moment to make one -- not before.

No release-notes generator. See point 8.

No CI badge on the public repository. The suite is not public, so a badge would either be a link to something nobody can open or a claim about a run nobody can see. The suite runs on every push in the private repository that holds it, and the verdict that matters is the one in point 1: a full green run, read properly, on the machine cutting the tag.