fix: prevent corestore corruption during graceful shutdown

- Reorder cleanup sequence to close HTTP/TLS/DNS servers BEFORE corestore operations
- Move dnsPass/main corestore closing after plugin cleanup to prevent race conditions
- Add explicit drive cleanup call to close all plugin drive stores
- Fix proxy-server cleanup to properly close state.store after dnsPass
- Add store.closed checks and improve error handling in cleanup functions
- Verify Autopass dnsPass.close() handles its internal corestore properly
- Remove duplicate DNS server closing code causing syntax errors

This resolves "Corestore is closed" errors during shutdown by ensuring no new
requests can access closed corestores, preventing corruption and ensuring clean
shutdown of all corestore instances (main, plugin databases, plugin drives, dnsPass).

includes/admin/admin-frontend/ui/info-modal.js

@@ -70,6 +70,32 @@ const infoContent = {
       }
     ]
   },
+  'p2p-domain-conflicts': {
+    title: 'P2P Domain Conflicts',
+    description: 'Manage conflicts between local and network-resolved domain hashes',
+    sections: [
+      {
+        title: 'Overview',
+        content: 'P2P Domain Conflicts occur when your local hash for a domain differs from the hash resolved by the P2P network consensus. This tab shows all domains where such conflicts exist.'
+      },
+      {
+        title: 'Local Hash',
+        content: 'The Local Hash is the hash you have stored locally for a domain. This represents your local claim or configuration for that domain.'
+      },
+      {
+        title: 'Resolved Hash',
+        content: 'The Resolved Hash is the hash determined by the P2P network consensus. This is what the majority of peers in the network have agreed upon for this domain.'
+      },
+      {
+        title: 'Hash Preference',
+        content: 'Use the toggle switch to choose which hash to use for resolution. "Local" uses your local hash, while "Resolved" uses the network consensus hash. Your preference is saved and will be used for future resolutions.'
+      },
+      {
+        title: 'When Conflicts Occur',
+        content: 'Conflicts typically occur when you have a local claim for a domain that differs from what the network consensus has resolved, or when network consensus changes after you\'ve set a local preference.'
+      }
+    ]
+  },
   'entries': {
     title: 'Autopass Entries',
     description: 'View the P2P network ledger',