For those of us who would like the AI to be able to update the rules, there
is a fix for this, although it disables the VS Code built in (or Cursor specific?) handling of .mdc yaml settings and inline rule associations. This is suboptimal for sure.
With rules becoming a critical aspect of purposeful AI, this precaution is understandable. It is however painfully obvious how useful it is have the AI review the rules and make changes. Ultimately it’s the developer’s responsibilty to allow file changes to take place, so in my view this guardrail is draconian and forces reponsible developers down an undesireable path of unwanted IDE config.
The lowest common user denominator should be the responsible developer using version control. In other words, if your rules get messed up, that’s on you.