diff --git a/context-docs/14-template-releases.md b/context-docs/14-template-releases.md
index 5b99eb8..3918760 100644
--- a/context-docs/14-template-releases.md
+++ b/context-docs/14-template-releases.md
@@ -76,6 +76,18 @@ behind the marker:
 Without that discipline `v1.0.14` tells the receiving operator nothing about
 whether they need to act, which is most of the point of having a number.
 
+That discipline has slipped once. `v1.4.1` carried two `f13ldman.css` changes
+(the gram-button sizing and the flag-heading scoping) and was cut as a patch
+because the PR title had no marker — so its number said "stay as you are" about
+a payload the table above says must be re-transferred. It was re-issued as
+**`v1.5.0`** with the same template content, and that is the release to
+transfer; `v1.4.1` is left in place rather than deleted, because a published
+tag is a record. The check that prevents a repeat is mechanical: a PR that
+touches any file in the "full re-transfer" row of
+`12-template-transfer-air-gapped-network.md` gets `[minor]` in its title
+before merging. The rule is repeated at the top of the template's own README,
+where whoever edits the template will see it.
+
 ## Reading the version off a published output
 
 The tag is where the version is *decided*, but a tag is no use to someone
diff --git a/publications/pub-5/template-2026/README.md b/publications/pub-5/template-2026/README.md
index 7e5b0e7..b1b87dd 100644
--- a/publications/pub-5/template-2026/README.md
+++ b/publications/pub-5/template-2026/README.md
@@ -12,8 +12,14 @@ template already styled every class pub-10 uses.
 
 > **Releases.** Every push to `main` that changes this folder publishes a
 > versioned zip, tagged `pub-5-template-2026-v<major>.<minor>.<patch>`. Patch is
-> automatic; put `[minor]` or `[major]` in a commit message to bump further.
-> The release stamps the version into `resources/template-version.txt`, which
+> automatic; put `[minor]` or `[major]` in a commit message or PR title to bump
+> further. **Any edit to `f13ldman.css`, `notes.css`, the XSLT, the page layouts,
+> the fragments or `f13ldMan.opt` is at least `[minor]`** — the transfer
+> procedure calls every one of those a full re-transfer, and a patch number
+> tells the receiving operator the opposite. Forgetting the marker is easy
+> (v1.4.1 was a CSS change cut as a patch, and had to be re-issued as v1.5.0),
+> and cheap to check: if the PR touches one of those files, put `[minor]` in
+> its title before merging. The release stamps the version into `resources/template-version.txt`, which
 > Oxygen copies into every published output at
 > `oxygen-webhelp/template/resources/template-version.txt` — so a publication
 > can be traced back to the template that built it. That file is committed with