chore(changelog): regenerate for v4.6.150

1 files changed, 11 insertions, 4 deletions

diff --git a/CHANGELOG.md b/CHANGELOG.md
index 409b069..b5dbd5f 100644
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@ -4,13 +4,19 @@ Generated from git history by `scripts/build-changelog.py` — do not edit by ha
 
 <!-- generated:start -->
 
+## v4.6.150 — 2026-11-06
+
+_Touches modules (7), main.html (1) · project 1_
+
+- **Commit the module work that has been live but uncommitted** `6bea062`
+  - Operator commit-approve, 2026-11-06. These changes have been served since 2026-11-02/03 while git HEAD still stamped v4.6.146, so the mirror published a tree four builds behind the running instance and the release tag named the wrong build.
+  - … run `git show <sha>` for the rest
+
 ## v4.6.146 — 2026-11-06
 
-_Touches docs (11), modules (3), README.md (3), CHANGELOG.md (3) · docs 10, fix 4, release 3_
+_Touches docs (11), CHANGELOG.md (4), modules (3), README.md (3) · docs 10, fix 4, release 3_
 
-- …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.
+- …and 5 earlier commit(s) in this build
 - **Drop hardcoded file/commit counts from the usage page** `d2bb158`
   - 310 files / 182 commits were already wrong at publish time (184). A count that changes on every publish is a rot vector; the page now says what the tree is and lets the reader run the commands.
 - **No byte count either — it grows with every publish** `a24ec6b`
@@ -47,6 +53,7 @@ _Touches docs (11), modules (3), README.md (3), CHANGELOG.md (3) · docs 10, fix
   - 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
+- **Regenerate after the render and ordering fixes** `2feefc0`
 
 ## v4.6.145 — 2026-11-02