chore(changelog): regenerate after the render and ordering fixes

1 files changed, 6 insertions, 4 deletions

diff --git a/CHANGELOG.md b/CHANGELOG.md
index 3bfb483..409b069 100644
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@ -6,11 +6,9 @@ Generated from git history by `scripts/build-changelog.py` — do not edit by ha
 
 ## v4.6.146 — 2026-11-06
 
-_Touches docs (11), modules (3), README.md (3), CHANGELOG.md (2) · docs 10, fix 3, release 3_
+_Touches docs (11), modules (3), README.md (3), CHANGELOG.md (3) · docs 10, fix 4, release 3_
 
-- …and 3 earlier commit(s) in this build
-- **Stop prepending the preamble on every run** `5902d5f`
-  - write_md() put the H1 + description inside the generated body and also kept old[:m.start()], so each regeneration added another copy: 44 runs left 44 H1s and pushed the first release to line 179. Only the region between the markers is generated now, an existing file with N copies is collapsed to one, and an assert refuses to write a file containing two generated regions (proven RED by injecting a duplicate). Regenerated: 83 entries, 185 commits, first heading v4.6.146 (was v4.6.135 - the file had not been committed since 2026-11-02).
+- …and 4 earlier commit(s) in this build
 - **Per-OS clone guide (Linux, macOS, Windows, Termux, iOS)** `8e34256`
   - Served at https://newos.webx11.duckdns.org/usage.html from docs/usage.html in this repo, so the page, the mirror and the README share one source. Covers the four failure modes that actually bite: CRLF on Windows (core.autocrlf), missing CA bundles, cloning into /sdcard from Termux (FUSE has no POSIX permissions), and the read-only 403 on push.
 - **Drop hardcoded file/commit counts from the usage page** `d2bb158`
@@ -45,6 +43,10 @@ _Touches docs (11), modules (3), README.md (3), CHANGELOG.md (2) · docs 10, fix
   - Symptom: the mirrored CHANGELOG.md (and the page) showed one-line commit summaries while README promises "every shipped fix, symptom -> cause -> fix -> verified". A reviewer measured the gap from the public mirror and could only conclude the claim overpromised.
   - Cause: scripts/build-changelog.py:59 formatted commits with %s only; %b was never read, so the verification prose every fix commit carries (5b55af9 is a typical one) was discarded before rendering. The MD writer then replaced every tag with a backtick, so nothing richer could have survived anyway.
   - … run `git show <sha>` for the rest
+- **Keep the newest commits of a build; wrap long detail URLs** `9751798`
+  - Symptom: after bodies were rendered, this fix's own commit was missing from its own entry, and a long URL inside an expanded detail was clipped at the right edge on a 390 px screen.
+  - Cause: items took group[:MAX_ITEMS] from a CHRONOLOGICAL list, so a 17-commit build showed its first 14 and dropped the newest three (the count line said "…and 3 more", hiding which three). And the injected detail CSS set no overflow-wrap, so a 47-character URL pushed the paragraph to 320 px of unbreakable text — the document stayed at 0 overflow only because the li clipped it.
+  - … run `git show <sha>` for the rest
 
 ## v4.6.145 — 2026-11-02