Hey @user; that gate is repo-wide right now, prolly not specific to you (@user is hitting the same wall above). For a fix that's already scoped against #3511 & addresses iskhakov's #3726 feedback, your fork and a Slack note (like the one you just posted) pointing to the diff is probably the right path under the current posture. Worth a careful read of [contributing.md](https://github.com/archestra-ai/archestra/blob/main/docs/pages/contributing.md) before posting anything substantive ... the "Contribute Responsibly" section is actively enforced. Short/specific should probably land better than long/structured, as the latter gets read as slop regardless of your effort in the matter. I'm a friendly community member without any skin in the game, but I'm happy to welcome you, and I genuinely wish you good luck! (FWIW @user same spam-filtering gate affecting you too it seems.)

This is me... There's nothing remotely exciting about the changes. Of late, when I file "issues" before making PRs like this, people tend to use AIs to write PRs to fix my issues...