Add PostHog error tracking

README.md

@@ -38,7 +38,7 @@ Hogflare is not a full PostHog clone. It does not try to ship PostHog's complete
 - [PostHog Compatibility](docs/posthog-compatibility.md): SDK setup, endpoint behavior, persons, groups, feature flags, signing, and enrichment.
 - [Import Existing PostHog Data](docs/import-posthog.md): host-side backfill importer for existing PostHog projects.
 - [Data Model](docs/data-model.md): event and person row shapes plus DuckDB/R2 SQL query examples.
-- [`models/`](models): semantic model definitions for events, sessions, pageviews, persons, identity, groups, attribution, retention, and shared metrics.
+- [`models/`](models): semantic model definitions for events, sessions, pageviews, persons, identity, groups, attribution, retention, error tracking, and shared metrics.
 
 ## Architecture
 

docs/deployment.md

@@ -130,7 +130,7 @@ new_sqlite_classes = ["PersonIdCounterDurableObject", "GroupDurableObject"]
 | `HOGFLARE_REPLAY_EVENTS_TABLE` | No | Iceberg events table queried by replay APIs. Defaults to `default.hogflare_events`. |
 | `HOGFLARE_REPLAY_QUERY_LIMIT` | No | Maximum snapshot rows a replay API request can read. Defaults to `5000`. |
 | `POSTHOG_SIGNING_SECRET` | No | Enables HMAC request signature checks. |
-| `PERSON_DEBUG_TOKEN` | No | Enables `/__debug/person/:id` for deployment verification. |
+| `PERSON_DEBUG_TOKEN` | No | Enables authenticated administrative endpoints: `/__debug/person/:id` and error issue status updates. |
 | `HOGFLARE_FEATURE_FLAGS` | No | JSON flag config used by `/decide` and `/flags`. |
 
 ## Secrets

docs/posthog-compatibility.md

@@ -42,10 +42,24 @@ Set the SDK host/base URL to your Worker (`https://<your-worker>.workers.dev`) a
 - `/alias` creates aliases.
 - `/batch` accepts mixed event payloads.
 - `/e` accepts browser event payloads.
+- `/i/v0/e` accepts PostHog error tracking event payloads.
 - `/engage` accepts people updates.
 - `/groups` accepts `$groupidentify` payloads.
 - `/s` accepts session replay payloads.
 
+## Error Tracking
+
+PostHog SDK error tracking is supported through normal capture ingestion. `posthog.captureException(error, properties)` sends a `$exception` event with `$exception_list`, stack frames, mechanism metadata, optional `$exception_steps`, and any custom properties; Hogflare forwards those fields unchanged to the pipeline.
+
+The documented PostHog manual ingestion endpoint `/i/v0/e/` is also available and uses the same browser event normalization as `/e/`. SDK remote config advertises exception autocapture support and serves the `exception-autocapture.js` helper expected by `posthog-js`.
+
+Error tracking semantic models:
+
+- `error_events` normalizes `$exception` rows into exception type, value, stack frame, fingerprint, user, session, URL, SDK, and grouping fields.
+- `error_issues` groups exception events into issue rollups with first/last seen, event count, affected users, affected sessions, latest sample, and status.
+
+Issue status is append-only. `PATCH /errors/api/issues/:fingerprint/status` writes a trusted `$error_issue_status` event with `status` set to `active`, `resolved`, or `ignored`; `error_issues` derives the latest trusted status for that project. The request must include an `api_key` identifying the project and an `x-hogflare-debug-token` header matching `PERSON_DEBUG_TOKEN`. Status updates are disabled when that token is not configured. Client-captured events named `$error_issue_status` are retained as ordinary events but cannot change issue state.
+
 ## Persons
 
 Identify, capture `$set` / `$set_once` / `$unset`, and alias events update a person record stored in a Durable Object. The record tracks distinct ID aliases, person properties, and a sequential `id` plus a UUID.