[Zac-Kyoti]

• What was wrong or hard: Mute Modes 0.2.2 (Mute Modes 0.2.2-experimental: SHADOW out of the stock timestretch task's SRAM (owner review) #1007) ran into three things the guides didn't say. A Mute Modes source change also moves its table-owner declaration and the beta base, so the update needs owner review. A change to the module's own qualification/probe.cpp moves its source fingerprint. And the probe container needs mc68k and an exec-enabled /tmp.
• What this changes:
  • docs/MODULE_QUALIFICATION.md: the source-fingerprint paragraph now names a module's own probe (qualification/probe.cpp, its runner). After the cycle-report paragraph, one paragraph covers the probe container: the vendor directory with mc68k mounted (the image lacks it), and --tmpfs /tmp:rw,exec,nosuid,nodev,size=128m, because Docker mounts a tmpfs noexec and the compiled probe can't start.
  • docs/MODULE_AUTHOR_UPDATES.md: one sentence, as you asked: until Octatrack base: PERSONALIZE rows as a base table (ot_personalize_rows), so table owners no longer pin package hashes #1023 lands, a Mute Modes source change also changes its table-owner declaration and the beta base, so every Mute Modes update is owner-reviewed.
• How I checked it: the fingerprint exclusions against moduleNativeSourceSha256 (scripts/module-qualification.mjs); the container flags against Mute Modes' TESTING.md command. npm run pr:ready says Ready (documentation path). Both files stay under the 40 KB limit.
• What the guides lacked or got wrong, and where I fixed it: the three points above, in these two files.

Related to #1007.

🤖 Generated with Claude Code