diff --git a/docs/prs/2026-09-04-PR#23-follow-up-builds.md b/docs/prs/2026-09-04-PR#23-follow-up-builds.md
index 00617ee..f845d52 100644
--- a/docs/prs/2026-09-04-PR#23-follow-up-builds.md
+++ b/docs/prs/2026-09-04-PR#23-follow-up-builds.md
@@ -185,6 +185,13 @@ Three places stay in sync with the new key, as the invariant demands: the data c
   (verified by [ConfigLoaderTest — "a branch whose layer lacks the predecessor loses only its follow-up"](../../src/test/kotlin/de/hoennig/werkator/config/ConfigLoaderTest.kt)).
   An instance fragment checked by `init --apply` is not checked for its predecessor at all: the build it names may well live in the project config it is merged with, and the merged configuration is checked on every load anyway.
 
+## Additional Changes
+
+- `BuildStatusChangedEvent` now carries the `RepoContext` the result belongs to: a `BuildResult` does not know its repository, and the listener has to enqueue into the right one.
+- `ConfigLoader.loadWithBranchLayer` and `loadForWorktree` take an optional branch name, used only to name the branch in the pinning warnings; the watcher passes it.
+- The follow-up check distinguishes three loads: the primary configuration refuses a missing predecessor, a branch layer warns, and an instance fragment (`init --apply`) skips the check — its predecessor may live in the project config it is merged with.
+- The "no build triggered" warning now names `afterSuccessOf` as the third trigger.
+
 ## Follow-up PRs
 
 - Werkbaum: commit the `deploy` definition to its `.werkator.yml`, add the host part on mih09, and retire the manual `deploy-prod.sh` invocation from the README.