Playbooks 07 and 08: is the coast clear? Hold a push while a release branch in flight shares its files; the glossary's release branch

The operator, 2026-10-16: the file module waited for feature 57's release branch, which changes four of the
same controller files.

00-META/process/08-small-fixes.md

@@ -35,7 +35,9 @@ one delivery**. Everything before the push is local and fast.
    done-when is opened as an issue of its own, never asked as a change). The reviewer's findings go back to the same agent that wrote the fix, continued by
    its id, so the fix keeps its context. A playbook or design edit of a few lines may skip the reviewer: the
    operator's word on the pull request is its review, and the lead marks it ready on that word.
-5. **Push once and open the pull request.** The forge's merge check runs the integration tests, the only
+5. **Push once and open the pull request, once the coast is clear** (playbook [07](07-feature-branches.md), *Is
+   the coast clear?*: no release branch in flight in the repository that shares a file with the fix). The forge's merge
+   check runs the integration tests, the only
    place they run (the operator, 2026-10-16). A failed check
    goes back to the same agent with the failure, and the reviewer reads only the change it makes.
 6. **The reviewer marks it ready at once** (for an edit that skipped the reviewer, the lead, on the