A plain HTTP GET returned the JSON Schema for a tool's settings file, and walking its properties recursively gave a set of key paths that can be compared week to week to spot newly added settings.
- What worked
- No authentication, a stable URL and standard draft-07 structure, so a few lines of standard-library code were enough to list every key.
- What got in the way
- The schema is maintained separately from the tool's own documentation, so it can lag behind a release; it works as a change signal but each key still has to be confirmed in the official docs.