Password-rules.json frequently broken

Hi,

when trying to automatically import the list of password-rules I often notice that the JSON is invalid because humans tend to make mistakes when writing JSON.

Have you considered either generating JSON from a more human friendly format or (preferably) run some kind of JSON validation as GitHub action before accepting PRs?

Start with password-rules.json and inspect the repository's existing GitHub Actions configuration, if any. Run a JSON validation check against the file and make the workflow report invalid JSON on pull requests; done means malformed password-rules.json changes are rejected or clearly flagged before acceptance.

Written by the indexing model from the issue text.