Are these meant to be programmatically enforced via CI? If so, I wonder if adding an Alpine-based build to the pipeline would cover all the unsupported commands automatically.
It would be better to ensure POSIX shell script compliance by running the scripts with dash shell instead.
Historically, the list of architectures that public github action runners make available has been quite limited. Having an alpine runner to surface unsupported commands would be a huge win.
That being said, it's very useful as a plugin dev to have this test suite while working on a WSL2/Ubuntu so that I don't need to run a full CI build every time