switchy 1.1.4 (new cask)

[benhursenabathi]

---

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.

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.

---

• 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, including zap stanza paths.

AI assisted with the cask draft, release preparation, and PR text. I manually verified: the published first-party DMG checksum (sha256 matches the cask), brew style --fix with no offenses, brew audit --cask --new --online error-free, brew livecheck resolving 1.1.4,70 from the Sparkle appcast, and a full brew install --cask / brew uninstall --cask cycle. For the zap stanza: I mounted the v1.1.4 build 70 DMG and confirmed the app's bundle identifier is com.mangobuns.Switchy, matching the zap paths (~/Library/HTTPStorages/com.mangobuns.Switchy, ~/Library/Preferences/com.mangobuns.Switchy.plist), which are the files the app actually creates on a real install.

---

[github-actions]

Thanks for your pull request. This has been closed because it appears to use an incomplete or outdated pull request template.

Please edit this pull request to fill in the current pull request template. This workflow will reopen this pull request automatically once the template is complete. Do not open a new pull request for this.