From db1e75c3b13bb9aa7b665ff0abe1d52d3148c4df Mon Sep 17 00:00:00 2001
From: hoelee <me@hoelee.com>
Date: Fri, 16 Oct 2026 13:25:34 +0800
Subject: [PATCH] docs(project-state): B2l published (7b001dc) + B2n the
 backdated silent-JS post held for review

---
 docs/project-state.md | 38 +++++++++++++++++++++++++++++++-------
 1 file changed, 31 insertions(+), 7 deletions(-)

diff --git a/docs/project-state.md b/docs/project-state.md
index 80f48c6..83fab23 100644
--- a/docs/project-state.md
+++ b/docs/project-state.md
@@ -538,14 +538,14 @@ from a normal Chrome UA — so "0 pageviews after a headless test" is not a bug.
 - ⚠ **Reminder for the next session:** the assertion method matters — hrefs must be checked against **raw** HTML, not the
   tag-stripped text (a first pass reported the CTA and cross-links "missing" because tag-stripping removes `href`).
 
-**Step B2l — (unplanned) Two posts written from the 2026-10-09 → 10-16 sessions, held for the user's read.** 🔵
+**Step B2l — (unplanned) Two posts written from the 2026-10-09 → 10-16 sessions.** ✅ Published 2026-10-16 (`7b001dc`)
 
-Per the user's instruction of 2026-10-16 ("先写出来，我看了过后，确认后再发"), these two are **written, built and
-image-complete but deliberately not committed and not pushed** — they are untracked files in the working tree while
-they wait for a read. **A parallel session's `git add -A` would sweep them in — never stage blindly in this tree.**
-A third post written in the same batch (`the-dialog-opened-in-7-seconds-my-script-waited-5`, category `ai`) was
-**dropped by the user** — parked as `draft: true` in `18f2ed3` and **not to be published**; see the note under the
-table.
+Both were written, built and image-complete, then held for the user's read and **published the same day on his
+go-ahead**: 8 URLs (EN / ZH / og / banner × 2) verified **200**, `/posts/` order still monotonic, `lastmod` =
+2026-10-16 on both. A third post written in the same batch (`the-dialog-opened-in-7-seconds-my-script-waited-5`,
+category `ai`) was **dropped and deleted** — see the note under the table.
+⚠ The `7b001dc` message claims "build 159 pages"; the real count was **153** — both posts had `draft: false` from the
+start, so publishing added no pages. The number in that message is wrong; the deploy itself was verified by URL.
 
 | Slug | Category | Proposed `pubDate` | Source session (Hermes id) | What it argues |
 |---|---|---|---|---|
@@ -580,6 +580,30 @@ table.
 - **To publish one:** confirm the real `pubDate` (`date`, and the newest `<time>` on the live `/posts/`), then
   `git add` the four explicit paths (post EN/ZH + og + banner) and push `origin main`; verify the four URLs 200.
 
+**Step B2n — (unplanned) The silent-JavaScript-failure post, backdated into the 2025-02 gap.** 🔵 held for the read
+
+| Slug | Category | `pubDate` | `updatedDate` | Source |
+|---|---|---|---|---|
+| `two-ways-a-javascript-file-stops-working-and-looks-fine` | `engineering` | **2025-02-20** | 2026-10-16 | `hevc-transcode` `docs/OPERATIONS.md` §10.33 |
+
+- **What it argues:** a parameter named `t` shadowing the i18n `t()` function, and a `let LANG` declared *after* its
+  first call (TDZ) — two unrelated one-line causes that each aborted the whole script while the page kept rendering
+  the inline default-language text, so nothing looked wrong. The fix is asserting on **effects** in a real browser
+  (`typeof t === 'function'`, every inline handler resolves — 219 attributes / 217 named calls), plus a
+  **pseudo-locale** (`?lang=pseudo`, strings stretched 1.6×) that catches untranslated nodes and overflow.
+- **Why the 2025-02-20 date:** the prose carries no calendar date and no checkable version pin, which is the
+  condition for backdating (see B2m's note). It fills the empty stretch between `why-your-cdp-clicks-silently-fail`
+  (2025-03-19) and `chainlink-vrf-v2-lottery-contract` (2024-12-10) — verified in the built feed: the post lands at
+  position 64 of 67, monotonic, with `lastmod` = 2026-10-16 from `updatedDate`.
+- ⚠ **Consequence of the deep date: no internal links.** Every post it would naturally reference is dated later, and
+  a backdated post may only link *backwards* — so it ships as a stand-alone page. If the cross-links are worth more
+  than the gap (e.g. to `it-reported-success-nothing-had-changed`, 2026-10-08, the same "trust the signal, not the
+  intent" theme), move the date into the recent window instead; that is a one-line frontmatter change in two files.
+- **State:** EN + ZH written (`rewrap_post.py` → `wrap_lists.py` on EN only), og + banner generated and measured
+  (og `rows=1 overflow=0`; banner 8 rows `delta=2 overflow=0`), build clean at **155 pages**, both `dist/` pages
+  asserted locally (language switch both ways, content, date 2025-02-20, sitemap hreflang pair). Not committed, not
+  pushed — the working tree also carries the two generator entries for this slug (additive: 5 / 17 lines, deletions 0).
+
 **Step B2m — The next-session topic queue (user decision 2026-10-16).** ⬜
 
 From the same sweep, **explicitly not to be written**: the Photoshop "closes every five minutes" post (#6 in the