hooks/ponytail-config.js: JSON.parse doesn't strip BOM — config silently fails on Windows

[nanaubusiness]

In hooks/ponytail-config.js line 86:

const config = JSON.parse(fs.readFileSync(configPath, 'utf8'));

Unlike ponytail-activate.js (which strips UTF-8 BOM at line 49) and check-versions.js (which strips BOM at line 34), this function does not strip the BOM before JSON parsing. Config files saved with a BOM (common on Windows) cause silent parse failures, making user config settings be ignored with no warning.

[nanaubusiness]

Already fixed in PR #384.

[nanaubusiness]

Reopening — corresponding PR is under review.

[DietrichGebert]

Fixed in #478. getDefaultMode() was parsing config.json without stripping a UTF-8 BOM, so a config saved with one (common on Windows) silently failed to parse and your defaultMode was ignored. It now strips the BOM the same way the other readers already do. Verified end to end: a BOM-prefixed config with defaultMode ultra is now honored. Thanks for the precise pointer to the line and the matching fixes elsewhere.