Important: Do not tick a checkbox if you haven’t performed its action. Honesty is indispensable for a smooth review process.

In the following questions <cask> is the token of the cask you're submitting.

After making any changes to a cask, existing or new, verify:

• The submission is for a stable version or documented exception.
• brew audit --cask --online <cask> is error-free.
• brew style --fix <cask> reports no offenses.
• AI was used to generate or assist with generating this PR. Please specify below how you used AI to help you, and what steps you have taken to manually verify the changes.

Additionally, if adding a new cask:

• Named the cask according to the token reference.
• Checked the cask was not already refused (add your cask's name to the end of the search field).
• brew audit --cask --new <cask> worked successfully.
• HOMEBREW_NO_INSTALL_FROM_API=1 brew install --cask <cask> worked successfully.
• brew uninstall --cask <cask> worked successfully.

This cask is for the beta releases of the existing cask "Mos" from https://github.com/Caldis/Mos. Mos's release has stayed on version 3.5.0 for more than a year now and has since been pushing updates via 4.0.0-beta versions. Having discussed the prospect of adding a beta version cask in Caldis/Mos#824 I was advised by @Syrupdesu to create a PR to add the beta version cask myself.

AI was used to create this cask in the form of ChatGPT Codex. It wrote the ruby file for the cask, ran checks for conflicts and compliance in accordance to homebrew acceptable casks documentation. I ensured brew audit and brew style checks are all correct.