Skip to main content
The verified Admin and Engine package manifests declare Sentry SDK dependencies. A dependency alone does not prove initialization, DSN configuration, event delivery, alerting, retention, or current provider health.

​
Source evidence

As of the exact Admin and Engine commits named in the frontmatter:
  • Admin declares the Sentry React SDK.
  • Engine declares the Sentry Node SDK.
  • Engine also contains structured logging and sensitive-telemetry redaction seams owned by its source.
This page does not claim that either deployed process initialized Sentry or sent an event on 2026-08-12.

​
Dated incident observations

An older canonical snapshot recorded Sentry observations involving oversized request bodies and webhook parsing limits. That snapshot was present when the Library canon was captured by 2026-06-23. Treat those entries as historical debugging evidence only. No event identifier, project, environment, issue state, recurrence, or resolution was reverified in the Sentry provider on 2026-08-12.

​
Observability doctrine

Lucia’s operational surfaces need evidence for:
  • whether a request arrived;
  • which environment and exact build handled it;
  • the returned status and duration;
  • the typed application failure;
  • the redacted diagnostic context; and
  • whether a provider or downstream side effect completed.
Render/application logs and Sentry answer different questions. Logs can prove a request path and runtime output; a Sentry event can add grouped exception and trace context. Neither substitutes for provider-delivery, datastore, or user-visible proof.

​
Current-proof requirement

Before describing Sentry as active for a surface, verify:
  1. exact owning source and deployed commit;
  2. runtime initialization without exposing the DSN;
  3. environment/release tagging;
  4. a safe test or naturally occurring event;
  5. provider receipt and searchable event;
  6. sensitive-data redaction; and
  7. alert/ownership state when operational response is claimed.
Provider project identifiers, DSNs, auth tokens, user details, payload secrets, and private event links must not be published.

​
See also