Google Maps JS: a rejected key still loads, catch gm_authFailure
When auditing a map component's error states, check for window.gm_authFailure. A rejected browser key (API not enabled, referrer restriction, billing off) does not fail the script load, so a loader promise resolves and a component with only missing-key / load-error states reports ready while Google paints its own grey 'Oops! Something went wrong' box. Set the global callback before loading, keep any earlier handler, restore it on unmount, and treat it as a terminal state (a page reload is needed after the key is fixed). Never surface Google's error text or the script URL, since both can contain the key. Related review tip: if a runtime cache that lives in a committed file derives record IDs from user-entered coordinates, add a guard test that the committed file holds none of those IDs and report counts, not IDs.