Merge branch 'feat/wire-error-plane'

# Conflicts:
#	package.json

Author: Hanzo AI

components/providers/analytics.tsx

@@ -8,12 +8,24 @@ import { createAnalytics } from '@hanzo/event';
 import { AnalyticsProvider, ErrorBoundary, useAnalytics, usePageview } from '@hanzo/event/react';
 import { setErrorReporter, type ErrorContext } from '@/lib/error-handling/error-logger';
 
-/** The ONE Hanzo Cloud telemetry front door — POST api.hanzo.ai/v1/event. Cloud
- *  fans the one batched stream out to the web (analytics), product (insights), and
- *  error (sentry) lenses; the client never sends the org — Cloud resolves the
- *  tenant server-side from the validated bearer (or the publishable key). */
+/** The Hanzo Cloud event-stream door — POST api.hanzo.ai/v1/event. The client
+ *  never sends the org; Cloud resolves the tenant server-side from the validated
+ *  bearer (or the publishable key).
+ *
+ *  NOTE: this door does NOT fan out to sentry. An earlier comment here claimed
+ *  Cloud fanned the one stream into the error (sentry) lens — it does not, and
+ *  that mistaken belief is why this app reported zero errors to sentry.hanzo.ai.
+ *  A `type:'error'` event lands in the cloud event warehouse (readable via
+ *  GET /v1/errors); reaching sentry requires the DSN below. */
 const HOST = 'https://api.hanzo.ai';
 
+/** Hanzo-minted Sentry DSN for the `hanzo-app` project — the ERROR plane.
+ *  "https://<version>:<hmac>@<host>/v1/sentry/<projectId>". Publishable and
+ *  write-only, so it is safe in the bundle. Unset => the error plane is inert
+ *  (fail-safe: analytics keeps working, nothing throws). Set in the build env;
+ *  never committed. Mint: POST /v1/sentry/projects */
+const EVENT_DSN = process.env.NEXT_PUBLIC_HANZO_EVENT_DSN || undefined;
+
 /** Optional publishable ingest key (pk_…) that lets LOGGED-OUT marketing/public
  *  views emit accepted telemetry (pageviews + errors + unload beacons) — the key
  *  HMAC-verifies to the org server-side, so anonymous events light up all three
@@ -53,7 +65,8 @@ function Identity() {
  * the bearer the @hanzo/iam SDK already holds — it emits pageviews, a stable-id
  * identify() once auth resolves, AND captures errors (auto: window.onerror +
  * unhandledrejection; React: the ErrorBoundary below; manual: errorLogger, wired
- * through setErrorReporter). One client, one stream — errors are just events.
+ * through setErrorReporter). One client, two planes: every captured error goes to
+ * sentry.hanzo.ai as a Sentry envelope AND stays correlated on the event stream.
  * The token is read through a live ref so a single stable client survives token
  * refresh without re-initializing.
  */
@@ -71,6 +84,9 @@ export function AnalyticsRoot({ children }: { children: ReactNode }) {
         host: HOST,
         getToken: () => tokenRef.current ?? undefined,
         ingestKey: INGEST_KEY,
+        // Error plane -> sentry.hanzo.ai. Inert (fail-safe) when the DSN is unset.
+        dsn: EVENT_DSN,
+        environment: process.env.NODE_ENV,
         // Consent gate: honor the browser Do-Not-Track signal.
         enabled: !doNotTrack(),
       }),

package.json

@@ -29,7 +29,7 @@
     "@hanzo/ai": "^0.2.1",
     "@hanzo/base": "^0.2.1",
     "@hanzo/brand": "^1.4.4",
-    "@hanzo/event": "^0.3.1",
+    "@hanzo/event": "^0.3.2",
     "@hanzo/gui": "7.3.0",
     "@hanzo/iam": "^0.13.8",
     "@hanzo/logo": "^1.0.13",