Verify each finding against the current code and only fix it if needed.

Inline comments:
In `@admin/assets/js/slimstat-chart.js`:
- Around line 87-89: The guard clause that checks element, chartCanvas, inside,
and chartWrap currently emits a console.warn with chartId; remove that
console.warn so the function simply returns when the required DOM pieces are
missing (i.e., keep the if (!element || !chartCanvas || !inside || !chartWrap) {
return; } behavior) to avoid introducing production console output in
slimstat-chart.js.

In `@admin/config/index.php`:
- Around line 941-960: The GDPR banner string registration currently done in the
settings save flow (the $gdpr_translatable loop that calls
do_action('wpml_register_single_string', ...) and pll_register_string(...)) must
be made idempotent and invoked during plugin init/upgrade as well so
pre-existing custom banner text is registered for WPML/Polylang; extract that
loop into a reusable function (e.g., register_gdpr_translatable_strings) and
call it from your upgrade/init sequence (or hook into admin_init/plugin_loaded)
in addition to the save handler, ensuring it skips empty values and safely
re-registers the same keys without side effects.

In `@admin/index.php`:
- Around line 735-740: The migration currently forces
wp_slimstat::$settings['use_separate_menu'] = 'on' for all sites < 5.4.1; change
it to only modify legacy/unset values: read
wp_slimstat::$settings['use_separate_menu'] and if the key is not set, is empty,
or equals the legacy 'no' value, then set it to 'on'; otherwise leave the
existing value untouched so existing user preferences are preserved (keep the
version_compare check and update behavior confined to the migration block).

In `@languages/wp-slimstat.pot`:
- Around line 5489-5495: Unify the negative consent label to a single key (use
"Decline") so translations aren’t split; update the POT entries in
languages/wp-slimstat.pot to remove msgid "Deny" and keep only msgid "Decline",
and then update all code references that emit the button label (e.g., in
src/Services/GDPRService.php and wp-slimstat.php where __('Deny') or similar is
used) to use __('Decline') (or the chosen translation helper) so every banner
path uses the same translation key.

In `@src/Services/GDPRService.php`:
- Around line 210-223: The callback used in preg_replace_callback is too
restrictive: inside the anonymous function (the one handling $matches and
setting $href) replace the current preg_match('#^(https?://|/)#i', $href) check
with a pattern that accepts any valid URL scheme plus protocol-relative and
root-relative URLs so mailto:, tel:, ftp:, etc. are preserved; e.g. test for a
scheme per RFC (like '^[a-z][a-z0-9+.\-]*:'), protocol-relative ('//') or
root-relative ('/'), and return $matches[0] when that test passes, otherwise
return $matches[2].

---

Outside diff comments:
In `@admin/assets/js/slimstat-chart.js`:
- Around line 100-152: The AJAX handler hides chartWrap before sending but only
restores it on the successful branch; update xhr.onreadystatechange (and the
JSON parse) to ensure the loadingIndicator is removed and
chartWrap.style.display is set back to "block" on all failure paths (non-200
status, JSON.parse errors, and when result.success === false). Specifically,
wrap JSON.parse in try/catch inside xhr.onreadystatechange, handle xhr.status
!== 200 and result.success === false by cleaning up
(inside.removeChild(loadingIndicator) and chartWrap.style.display = "block"),
and consolidate final cleanup so both the happy path and any early-return error
cases restore the UI; reference chartWrap, loadingIndicator, inside,
xhr.onreadystatechange, and result in your changes.

Verify each finding against the current code and only fix it if needed.

Inline comments:
In `@admin/assets/js/admin.js`:
- Around line 1470-1477: The early return when timeSinceManualRefresh < 2000
prevents dispatching the minute pulse event and delays real-time updates; before
returning in that conditional (inside the block that checks
SlimStatAdmin._lastManualRefreshTime) ensure you still dispatch the minute pulse
(the same event emitted elsewhere, e.g. 'slimstat:minute_pulse' or by calling
the existing minute pulse emitter) and then reset lastTriggerMinute = -1 and
return; reference SlimStatAdmin._lastManualRefreshTime and lastTriggerMinute to
locate the block and add the dispatch so the minute pulse always fires even
after a manual refresh.
- Around line 1449-1451: Currently the code sets
SlimStatAdmin._lastManualRefreshTime inside the refresh path when id ==
"slim_p7_02", which makes auto-refreshes appear manual; remove that assignment
from refresh_report() and instead set SlimStatAdmin._lastManualRefreshTime at
the actual manual trigger site(s). Concretely, either (a) delete the block that
sets _lastManualRefreshTime in refresh_report()/where id=="slim_p7_02", and add
a line that sets SlimStatAdmin._lastManualRefreshTime = Date.now() in the manual
refresh handler(s) that call refresh_report("slim_p7_02"), or (b) change
refresh_report(id, {manual: true}) to accept a manual flag and only set
_lastManualRefreshTime when manual===true, updating manual callers to pass that
flag; reference: id "slim_p7_02", function refresh_report, and property
SlimStatAdmin._lastManualRefreshTime.