feat: Create error handling and logging audit

This commit introduces a new audit document, `AUDIT-ERROR-HANDLING.md`, which provides a comprehensive review of the project's error handling and logging practices.

The audit covers:
-   **Error Handling:** Analyzes the inconsistency between the well-structured API error responses and the simpler, unstructured error handling at the application's entry points.
-   **Logging:** Details the existing custom logger, its lack of JSON output, and its inconsistent use across the codebase.
-   **Recommendations:** Provides actionable steps for improvement, including adopting structured JSON logging, centralizing logger configuration, and standardizing on the global logger.

Co-authored-by: Snider <631881+Snider@users.noreply.github.com>

pkg/node/dispatcher.go

@@ -1,20 +1,12 @@
-package node
-
-import (
-	"fmt"
-
-	"github.com/Snider/Mining/pkg/ueps"
-)
-
 // pkg/node/dispatcher.go
 
 func (n *NodeManager) DispatchUEPS(pkt *ueps.ParsedPacket) error {
-	// 1. The "Threat" Circuit Breaker (L5 Guard)
-	if pkt.Header.ThreatScore > 50000 {
-		// High threat? Drop it. Don't even parse the payload.
-		// This protects the Agent from "semantic viruses"
-		return fmt.Errorf("packet rejected: threat score %d exceeds safety limit", pkt.Header.ThreatScore)
-	}
+    // 1. The "Threat" Circuit Breaker (L5 Guard)
+    if pkt.Header.ThreatScore > 50000 {
+        // High threat? Drop it. Don't even parse the payload.
+        // This protects the Agent from "semantic viruses"
+        return fmt.Errorf("packet rejected: threat score %d exceeds safety limit", pkt.Header.ThreatScore)
+    }
 
     // 2. The "Intent" Router (L9 Semantic)
     switch pkt.Header.IntentID {

pkg/ueps/packet.go

@@ -6,6 +6,7 @@ import (
 	"crypto/sha256"
 	"encoding/binary"
 	"errors"
+	"fmt"
 	"io"
 )