fix(posts): correct the 3 video posts after consultant review, with fresh artwork

Reviewer's five "highest priority" items, each checked against the source before acting:

* 38% speedup -> 38.1% less render time (352s -> 218s, 1.61x throughput); says it was
  a single run each, same clip, same machine, same encoder settings.
* "microsecond-accurate" -> frame-accurate: at 30 fps one frame is 33.3 ms, and the text
  now states that word-level timestamps are not microsecond-accurate.
* "Three minutes later" -> "a few minutes later", plus the one measured number (218 s
  render for the 4-minute track) so the claim is checkable.
* Zero Jitter / Zero Light Flashing -> "no visible jitter" / "no dark flash at the cut",
  scoped to the clip that was measured.
* ti.mode 0o666 -> 0o644. Hygiene, not the syntax error he reported: source and live HTML
  both read 0o666 (the live page splits it across two highlight spans and his text
  extraction inserted a space), and 0o666 is legal Python.
* "0 MB RAM spike in Chrome" now scopes itself to the Chrome container and says the
  Python client still buffers the whole tar. New "What this pattern does not solve"
  block: client buffering, target directory must already exist, tar member names become
  container paths, Portainer key / CDP 9222 are root-equivalent.

All three posts get a TL;DR and inline cross-links (the trio had zero internal links
before); the ZH links use the real /posts/zh/<slug>/ path.

Not done, because it needs the owner's data rather than invention: end-to-end timing
table, benchmark conditions, whether 1.89 s was a single run, before/after jitter clips,
the "what still needs a human" list. Task list:
docs/consultant-review-2026-10-22-3-video-posts.md.

Artwork for the three slugs regenerated (1600x900 banner, 1200x630 share cards EN+ZH,
400/800 list thumbs); the ZH pipeline card already carries the corrected description.

docs/project-state.md

@@ -387,6 +387,23 @@ and a DOM probe for the regenerated card. Spot values: `/zh/posts/` 200 · `/tag
 - **Not enabled** (still owner-gated, re-measured today): Cloudflare Web Analytics — `grep -c cloudflareinsights` on the homepage returns **0**. `sitemap-index.xml`, `llms.txt` and `robots.txt` all serve 200.
 - **Remotes**: Gitea and GitHub both at `5ec321a`, 0 divergence.
 
+---
+## 4d. Consultant review of the three video posts — 2026-10-22
+
+A paid reviewer read `how-i-built-an-automated-music-video-pipeline`, `uploading-large-videos-to-youtube-via-cdp` and
+`debugging-remotion-video-jitter` (EN + ZH). Full verdict and task list: **`docs/consultant-review-2026-10-22-3-video-posts.md`**.
+
+- **Shipped (content-only, nothing invented):** "Three minutes later" → "a few minutes later" plus the measured **218 s** render
+  figure; "microsecond-accurate" → frame-accurate (33.3 ms at 30 fps); "38% speedup" → **38.1% less render time, 1.61× throughput**;
+  `Zero Jitter` / `Zero Light Flashing` → "no visible jitter" / "no dark flash at the cut"; `ti.mode` `0o666` → `0o644`; the
+  "0 MB RAM spike" line now scopes itself to the Chrome container and admits the client buffers the whole tar; new
+  **"What this pattern does not solve"** block; **TL;DR + inline cross-links on all three** (the trio had **zero** internal links before).
+- **He was wrong about one thing:** the "`ti.mode = 0o 666` syntax error" does not exist — source and live HTML both read
+  `0o666` (the live page splits it across two highlight spans and his text extraction inserted a space), and `0o666` is legal
+  Python. The permission fix landed anyway, as hygiene rather than as a bug fix.
+- **Still needs the owner** (no data to invent): end-to-end timing table, benchmark conditions (Remotion version / encoder
+  settings / number of runs), whether 1.89 s was a single run, before/after jitter clips, and the "what still needs a human" list.
+
 ---
 ## 5. Conventions (non-negotiable)