docs(state): record the consultant-review round as it actually shipped

§4d now carries the real commit chain (f32ae90 → 04a1082 → cf4504e), the
verification that matters (Actions 292/293/295, six pages 200, artwork md5 vs
live, check-assets 162/162) and an owner queue with three items.

The task doc is rewritten around that queue: (1) confirm whether the four stage
timings (14.2 / 2.1 / 32.4 / 48.6 s) were measured — they have no trail in the
repo and the reviewer's complaint was exactly about unmeasured numbers;
(2) supply the before/after jitter clips; (3) decide which session owns edits to
these three posts, since two sessions on the same files put one session's
paragraphs into the other's commit.

Also drops a claim inherited from the parallel session's completion block: the
reviewer's meta descriptions were never adopted, the frontmatter keeps the
originals.

docs/project-state.md

@@ -391,18 +391,27 @@ and a DOM probe for the regenerated card. Spot values: `/zh/posts/` 200 · `/tag
 ## 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`**.
+`debugging-remotion-video-jitter` (EN + ZH). Verdict, receipts, number audit and the open items:
+**`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.
+- **Live (Gitea Actions 292 / 293 / 295 success, six pages 200, artwork md5 matches, `check-assets.mjs` 162/162 OK):**
+  `f32ae90` did the fact corrections — "three minutes" → "a few minutes" + the 218 s scale, microsecond-accurate →
+  frame-accurate (33.3 ms at 30 fps), "38% speedup" → 38.0 % less render time / 1.61× throughput, the absolute
+  "Zero Jitter" / "Zero Light Flashing" claims scoped to the clip, `0o666` → `0o644`, the memory claim scoped to the
+  Chrome container, **TL;DR + inline cross-links on all three** (the trio had zero internal links), regenerated artwork.
+  `04a1082` (parallel session) added the end-to-end timing table, the benchmark table, the layer-compositing maths and the
+  upload-method comparison. `cf4504e` unified the render figure to **38.0 %** everywhere — the table derives it from 218.3 s.
+- **The reviewer got one item wrong:** the "`ti.mode = 0o 666` syntax error" does not exist. Source and live HTML both read
+  `0o666`; the live page splits the token across two highlight spans and his text extraction inserted a space. `0o666` is
+  legal Python, so the `0o644` change is permission hygiene, not a bug fix.
+- **Owner queue (nothing else blocks):**
+  - [ ] Confirm the provenance of the four stage timings in the pipeline post's timing table (14.2 / 2.1 / 32.4 / 48.6 s).
+    They have **no measurement trail in this repo** and the reviewer's whole complaint is about unmeasured numbers — either
+    confirm them as measured or relabel them as estimates. The render (218.3 s) and staging (1.89 s) figures do have a base.
+  - [ ] Provide the before/after jitter + dark-flash source clips so the comparison GIF can be cut and embedded (the one
+    reviewer item that needs an asset only the owner has).
+  - [ ] Decide which session owns edits to these three posts. On 2026-10-22 two sessions edited the same files and one
+    session's paragraphs rode into the other's commit — content survived, but the history stopped attributing correctly.
 
 ---
 ## 5. Conventions (non-negotiable)