Our JSON data is produced using JavaScript, which follows the standard RFC-compliant JSON format. Chromium 142 changed its default behavior to require explicit parsing options, so we’re updating our code to use JSON_PARSE_RFC instead of the Chromium-specific extensions. This ensures our JSON is parsed consistently and correctly according to the standard JS/RFC rules