scarletkc/seiso is a Markdown convention and linter for project documentation written by AI and read by humans and agents. The commit of October 13, 2026 (5bae44f, PR #91) separated the Rust build cache by build target in the package publishing pipeline. The only file touched is the publishing workflow .github/workflows/publish.yml, and the change adds 4 lines and deletes 0.
The reason for the separation was shared cache keys. This workflow prepares the Rust toolchain with dtolnay/rust-toolchain@stable and caches build artifacts with Swatinem/rust-cache@v2. When several build rows in one runner image share the default cache key, entries stored by an Alpine-family musl build container spill over into the manylinux2014 build, which targets multiple Linux distributions. As a result, the build broke in a host build script that requires a glibc newer than the glibc of the manylinux2014 container. This change specifies key: ${{ matrix.platform }} on the cache action, so that the gnu row and the musl row no longer restore each other's build scripts. In the same workflow, Rust tests run on Linux x64, and the wheels of the musl row are checked on Alpine.
That said, the scope of this commit stops at build cache isolation. There is nothing in this commit record about which rules the linter catches or how the Markdown convention is defined. Nor does this record contain any figures indicating the license or the linter's performance. It reads as a small but meaningful cleanup that makes publishing less sensitive to the state of a particular runner image. Judging what the linter catches is difficult from this commit record alone, and more evidence is needed.