scripts/uninstall.js: malformed settings.json crashes script mid-cleanup, leaving state partially deleted

[nanaubusiness]

In scripts/uninstall.js lines 38-40:

} catch (e) {
  if (e.code !== 'ENOENT') throw e;
}

If settings.json contains malformed JSON, JSON.parse throws a SyntaxError. SyntaxError has no .code property, so e.code !== 'ENOENT' is true and the error is re-thrown — crashing the script mid-cleanup.

At that point, .ponytail-active and config.json have already been deleted by removeIfExists() calls on lines 21-22, but settings.json may have been partially modified (if the crash happened after the delete settings.statusLine write on line 35 but before the script crashed).

Fix: catch SyntaxError specifically, or check e.code === undefined && !(e instanceof SyntaxError — actually the cleanest fix is to wrap the JSON.parse in its own try/catch.

[DietrichGebert]

Fixed in #481. A malformed settings.json made JSON.parse throw a SyntaxError, which has no .code, so the catch rethrew it and crashed after the mode flag and config were already removed. It now catches SyntaxError specifically: warns that the statusLine entry could not be removed, leaves the file untouched, and exits cleanly. Verified with a regression test and an end-to-end run. Thanks for the precise diagnosis.