Core error reporting functions and utilities.

This namespace provides pure functions and higher-level abstractions over
the error reporting protocols, making it easier for feature modules to
report errors without dealing with protocol details directly.

Port definitions for error reporting infrastructure.

This namespace defines the protocols that error reporting adapters must implement,
providing a clean abstraction over different error reporting backends (Sentry,
Rollbar, custom webhooks, etc.).

Core protocols:
- IErrorReporter: Exception and error message reporting
- IErrorContext: Error context management and enrichment

Error Context Structure:
{:correlation-id string - Request correlation ID
 :request-id    string - HTTP request ID  
 :tenant-id     string - Multi-tenant context
 :user-id       string - User context (if authenticated)
 :span-id       string - Distributed tracing span ID
 :trace-id      string - Distributed tracing trace ID
 :tags          map    - Additional structured tags
 :extra         map    - Additional context data
 :breadcrumbs   vector - Sequence of events leading to error}

Configuration schemas for error reporting infrastructure.

This namespace defines Malli schemas for validating error reporting configuration,
ensuring proper structure and constraints for different error reporting providers.

No-op error reporting adapter that safely ignores all error reporting operations.

This adapter implements all error reporting protocols but performs no actual
error reporting, making it safe for feature modules to use error reporting
protocols even when error reporting is disabled or not configured.

Sentry error reporting adapter implementation.

This adapter integrates with Sentry (https://sentry.io) for production error tracking
and monitoring. It implements all error reporting protocols to provide comprehensive
exception tracking, context management, and alerting capabilities.

Features:
- Exception capture with stack traces
- Message-level reporting (debug, info, warning, error, fatal)
- Context management (user, tags, extra data, breadcrumbs)
- Environment and release tracking
- Sampling and filtering capabilities
- Runtime configuration management

Configuration:
The adapter requires a Sentry DSN (Data Source Name) and optionally accepts:
- Environment name (dev, staging, prod)
- Release identifier
- Sample rate (0.0 to 1.0)
- Debug mode flag
- Server name

Example:
(def sentry-reporter
  (create-sentry-error-reporter
    {:dsn "https://your-dsn@sentry.io/project-id"
     :environment "production"
     :release "1.0.0"
     :sample-rate 1.0
     :debug false}))