Thesis

Col 3 — Test no. I rhymed the format with 2026t / 4/12. The t looks like talk no. 4 of 12 from the Pentagram talk. So 2026l reads as light-mode test, 2026 series and 1/n signals an ongoing series with no fixed total — honest about the fact that mode-testing isn't a one-off. If you'd rather lock the count, 1/3 (light, dark, high-contrast) works.
‍
Col 4 — Surface, not Client address. This is HUX's own work, not a client deliverable. "Client address" doesn't translate. "Surface" both names the URL location and echoes the test's vocabulary — the system can swap surfaces without losing itself. The actual URL becomes the address.

Col 5 — Subject, kept. Two-line subject keeps the rhythm. Token swap; surface coherence mirrors the cadence of Think as a team; Speak machine — two phrases joined by a semicolon. The semicolon is doing real work: it says these are the two halves of the test.

Col 6 — Author and date, kept. Standard.
Two alternative col 3 framings to consider

Test no. / 2026l / 1/n — open series (my pick)
Version: / v0.1 / 2026.05.09 — software-build framing, ties to the v0.1 in your eyebrow
Slug: / light-mode-test / 2026.05.09 — pure machine address

The first reads most like a talk dossier and matches the reference. The second is most honest about it being a working test. The third is the most CEL-pure but loses the editorial feel.
Layout breakdown (column grid)
Reading the screenshot's proportions:
| col 1 | col 2 |    col 3    |    col 4    |    col 5    |    col 6    | bleed |
|  ~5%  |  ~13% |    ~14%     |    ~20%     |    ~16%     |    ~18%     |  ~14% |
Roughly. The right-hand bleed (the plant photo) suggests the metadata grid actually runs 6 columns within a 7-column overall layout, with the seventh reserved for a hero image / bleed area. On the test page the bleed could be left as negative space or carry a token-swap chip (a small visual that flips on mode change).
If you're working in Lumos or Webflow's grid: a 12-col container with 1-1-2-3-2-2-1 spans matches it cleanly, or 6 equal cols if you drop the bleed.
Recommended next move

Confirm Read 1 vs Read 2 (page-level vs component-level dossier).
Confirm col 3 framing — Test no., Version, or Slug.
I draft this as a CEL-named component spec (page-header__col, page-header__rule, page-header__label, page-header__value) ready for you to build in Webflow.

Once those two judgements are made, the rest is mechanical and I can produce the spec, the class stack, and the data attributes in one pass.