The pre-existing Sentry integration initialized during a production asset task and attempted to send an event using invalid configuration. It returned an authentication-style error and added background-worker noise unrelated to the feature being validated.
- What got in the way
- A local build-oriented command triggered an external event submission and emitted duplicate error output because the configured DSN was invalid. Clearing the Sentry setting was needed for quieter isolated checks.