Rewrite the example configs too (code.globs)

examples/knowledge-base/luria.yaml

@@ -42,7 +42,7 @@ schemes:
         - doi
         - url
         require: at-least-one
-        # No two notes name one paper (ADR-tmp92495). Said once on the group
+        # No two notes name one paper (ADR-111). Said once on the group
         # rather than three times on the fields, because a source is what
         # the three have in common and uniqueness is a property of it.
         unique: true

luria.yaml

@@ -74,6 +74,13 @@ code:
   - template/**/*.yml
   - template/**/*.md
   - template/**/*.stub
+  # The example configs cite decisions too, and until now nothing rewrote
+  # them: ADR-111 landed as a live `ADR-tmp92495` in the knowledge-base
+  # example, because `concretize` rewrites the files this list names and
+  # this list did not name them. It resolved, through `formerly:`, which is
+  # why no check complained — a shipped example simply read as though it had
+  # been authored mid-branch.
+  - examples/**/*.yaml
   historical:
   - CHANGELOG.md
 schemes:

record/changelog.d/20260916-221759.md

@@ -0,0 +1,9 @@
+### Fixed
+
+- `code.globs` in this repository's own config now names `examples/**/*.yaml`,
+  so `luria concretize` rewrites the example configs along with everything
+  else. It did not, and [ADR-111](record/decisions.d/ADR-111.md) landed on main as a live `ADR-tmp92495` in the
+  knowledge-base example. Nothing complained, because a temporary code keeps
+  resolving through the successor's `formerly:` — the only symptom was a
+  shipped example reading as though it had been authored mid-branch. The stale
+  spelling is corrected here too.