Release v1.0.0: Werkator

The release after 0.9.21 is 1.0.0, because a product that changes its
name is better off counting from one under it. The release note says as
much, so the jump is not read as a claim about maturity — plan steps 14,
17 and 18 are still open.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

build.gradle.kts

@@ -12,7 +12,7 @@ group = "de.hoennig"
 // bump at least the patch version for every deployment — and only then, not per commit —
 // so the UI footer (BuildProperties), --version and the release notes identify what is
 // actually running; a deployment bundles whatever was committed since the last one
-version = "0.9.21"
+version = "1.0.0"
 
 java {
     toolchain {

src/main/resources/templates/releases.html

@@ -7,13 +7,15 @@
     <div th:replace="~{fragments :: nav(${view})}"></div>
     <div class="panel release-notes">
 
-        <h2>v0.9.22 <span class="muted">— unreleased</span></h2>
+        <h2>v1.0.0 <span class="muted">— 2026-08-31</span></h2>
         <ul>
             <li>GitTally is now <strong>Werkator</strong>. The old name already belongs to another
                 product in the git space, so the rename is a precaution and nothing more: what the
                 build system does, how it is configured, and how it reports to Gitea are unchanged.
                 In prose it is Werkator, everywhere a machine reads the name it is
-                <code>werkator</code>.</li>
+                <code>werkator</code>. The version marks the new name rather than a claim about
+                maturity: the release after <code>0.9.21</code> is <code>1.0.0</code>, because a
+                product that changes its name is better off counting from one under it.</li>
             <li>The rename reaches the file names an installation depends on. The committed
                 configuration is <code>.werkator.yml</code>, the machine-specific one
                 <code>.git/werkator/.werkator.yml</code>, and all state — build results, artifacts,