Add flclashx app

[drode1]

---

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.

---

About this fork submission

This cask is for pluralplay/FlClashX, a fork of chen08209/FlClash. I am aware of Homebrew Cask's "Not a fork (usually)" policy and would like to explain why I believe this fork warrants
inclusion, and why it is submitted under the vendor-prefixed token pluralplay-flclash rather than replacing the upstream.

Why this fork exists and why it matters

FlClashX is a widely used proxy client in the Russian-speaking community, where it is one of the de-facto tools for bypassing network censorship and this tool is open source . It is actively promoted and documented as a
recommended client by the Remnawave project (https://docs.rw/), a popular open-source Xray/Remna panel used by many VPN providers. Remnawave lists FlClashX among its officially supported clients
for end users across platforms: https://docs.rw/docs/clients

The fork exists because the upstream chen08209/FlClash does not ship pre-built subscription/config presets and UX tailored to the Xray/Remnawave ecosystem that the Russian community depends on.
pluralplay/FlClashX adds these integrations and is the build that Remnawave's documentation points users to.

Notability

• 769 stars, 769 watchers on GitHub (well above the 225-star self-submission threshold, and I am not the author)

• Actively maintained with regular releases

• Publicly documented and recommended by a third-party project (Remnawave / docs.rw) with its own significant user base.
  Proff links:

  • https://docs.rw/docs/awesome-remnawave
  • https://docs.rw/docs/clients

• Has a clear public presence beyond "just brew install" - users can (and do) download it directly from GitHub Releases and from Remnawave's documentation

Naming

Per the "Forks and apps with conflicting names" rule, the token is prefixed with the vendor name: pluralplay-flclash. This avoids any conflict with a potential future upstream flclash cask and
makes the fork relationship explicit to users.

Not replacing upstream

I am not asking for this cask to replace a hypothetical upstream flclash cask. The upstream is still actively maintained and, if someone later submits it, both can coexist - the vendor prefix
exists exactly for this reason.

Validation

• brew style --cask pluralplay-flclash - no offenses
• brew audit --cask --online --new pluralplay-flclash - only the expected "GitHub fork" warning, which is the subject of this justification
• brew fetch succeeds for both arm64 and amd64 builds; sha256 verified
• Installed and launched locally on macOS 26.3+; zap paths manually verified