v1.39.0

A release ends at its tag, and only the owner starts the family resync that moves its takers.

What changed for a member. WORKING.md says, under Releases and pins, that a release ends at its tag: the family resync moves the pins of the repositories that take it, only the owner starts a resync, and an agent that releases names in its report the members that will move at the next resync and neither re-pins them by hand nor starts one. Two resyncs side by side open the same branches and move the same pins twice, and a resync after every release makes many small ones that overlap where one would carry them all. REPOSITORIES.md's section on re-syncing after a release keeps no order of its own; it points at the family resync, which computes the order from the pins. PINS.md says the family report names a check in verify whose writer no step of the member's pins runs, so a missing step shows before the owner chooses chains. GLOSSARY.md fixes the gender of core, keeps Besitzer for the entity another is nested under and Bereich for a pane of the Obsidian window.

What breaks. Nothing a member runs. An agent working in a member now stops at its tag instead of re-pinning the repositories that take its release.

How to take it. Set the tag in conventions.json and the check.yml@ line to v1.39.0 and run sh conventions/conventions-sync sync once.