Record the search-result and scaffolder fixes in the changelog

CHANGELOG.md

@@ -75,6 +75,27 @@ ADR-007 and ADR-002.
 
 ### Fixed
 
+- **A search result opened the list it sits in, not the record it found.** A
+  NOTICE linked to `/notifications`, so clicking the row search had already
+  identified sent the reader to the list page to find it again by hand. The id
+  was in the payload the whole time and only the URL ignored it. The subnet
+  searcher had the same defect: an IP search resolves which subnet an address
+  falls inside, then linked to the `/network` hub rather than that subnet.
+  Both now link to the record. Every other result type already carried its id.
+
+- **`flask plugin new` scaffolded a frontend that no lean build could prune.**
+  It wrote views to `frontend/src/views/<name>/` and a route file to
+  `frontend/src/router/routes/<name>.js`, while all 16 bundled plugins keep
+  their frontend in `plugins/<name>/frontend/`, staged by
+  `stage-frontend.mjs`. Nothing looked broken, which is why it lasted: the
+  router still globs `./routes/*.js` during the Phase 4 dual-location
+  transition, so the pages loaded. What a new plugin author silently lost was
+  ADR-013 lean builds, since pruning works off the staged tree, plus stranded
+  views on deleting the plugin. The templates for the right layout already
+  existed; only the output paths were wrong. Their core imports moved to the
+  `@` alias, which resolves the same before and after staging, where the
+  previous `../../api` was correct only in the old location.
+
 - **A zero bar height printed a barcode 176 wide and 0 high.** Nothing rejected
   it: the value went straight into a CSS length, `height: 0in` is perfectly
   valid, and an image at `height: 100%` of a zero-height box is zero pixels