Fixed

• /kyo notify off (and editing config.yml directly) could fail to actually stop broadcasts. OreFindNotifyListener and /kyo notify <on|off> both went through plugin.config (Bukkit YamlConfiguration) independently. Consolidated into a single @Volatile var notifyOnOreFind on KyokalithPlugin: /kyo notify writes it (and still persists to config.yml), the listener reads it directly instead of touching the config map on every mining event. This closes a real class of latent bug — OreVeinResolver's cache already needed Collections.synchronizedMap for the same non-thread-safe-config-object reason — but an earlier draft of this note incorrectly asserted a Folia cross-region-thread race as the confirmed production root cause. That assertion was wrong and unverified: production runs plain Paper, not Folia, so that specific race cannot be what's happening there. The true root cause of the reported production failure is still being investigated; see docs/HANDOFF.md in the main Lycohinya repo for the current state of that investigation. This 1.4.1 change stands on its own as a correctness improvement regardless of that outcome.