Describe this repository's build with a build definition

Its own `.werkator.yml` still used the deprecated `branches` section
with an `autoBuild` schedule that was switched off. That section is read
only while nothing defines a build at all, and step 18 rejects it by
name — so this repository would have blocked the precondition of that
step, which asks that no configuration still in play carries it.

Nothing about the build changes: `builds.default` with `trigger.onPush`
is a build of every new commit on every branch, which is what the branch
section said. `config:print --full` resolves the definition completely
and logs no deprecation warning any more.

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

.werkator.yml

@@ -19,10 +19,14 @@ watcher:
   # max commit age for new origin branches to be pulled automatically
   newBranchMaxAge: 5d
 
-# Per-branch build configuration.
+# Named build definitions. "default" is the base every other one inherits its
-# Use "default" as the fallback for all branches not listed explicitly.
+# settings from — never its trigger.
-branches:
+builds:
   default:
+    # When this build runs and for which branches. The only part a build does
+    # NOT inherit from the default — everything below it does.
+    trigger:
+      onPush: true          # build every new commit of the selected branches
     # run before each build
     cleanCommand: rm -rf build
     # shell command for each build
@@ -32,6 +36,3 @@ branches:
       - build/reports
     stdoutLog: build.stdout.log   # filename for captured stdout
     stderrLog: build.stderr.log   # filename for captured stderr
-    autoBuild:
-      enabled: false        # whether to rebuild on schedule
-      times: ["01:00"]      # UTC times HH:MM for scheduled builds

docs/prs/2026-08-31-PR#1-rename-gittally-to-werkator.md

@@ -148,6 +148,8 @@ The rollback section names the asymmetry: the new version reads both names, the
   The conversion has served its purpose with the vm2176 → vm4006 migration; what remains is the setup of a new instance: the preconditions, the credential prompt, and the machine configuration written mode 600.
   It also stops emitting a legacy `branches:` section, which [plan step 18](../plan/18-remove-branches-section.md) is about to reject outright.
 - Restored the real `GITTALLY_*` spelling in `docs/plan/00-legacy-analysis.md` and `docs/plan/13-nginx-tls.md`, which record what the old script read.
+- Migrated this repository's own `.werkator.yml` from the deprecated `branches` section to a `builds.default` definition with a `trigger` block.
+  Nothing about its build changes; it stops being the blocker for the precondition of [plan step 18](../plan/18-remove-branches-section.md), which requires that no configuration still in play carries the section, and which rejects it by name afterwards.
 
 ## Follow-up PRs