Devin FoleyandPaperclip af846cfd8e Keep Sentry run failure context on its own event ...

Run failure reporting mutates a Sentry scope while the application skips
Sentry's OpenTelemetry setup. Without an async context manager, that scope
can remain active and attach old run IDs and fingerprints to later errors.

Pass the existing run metadata directly to captureException. Keep ordinary
exception capture unchanged. Add a real-SDK regression with an in-memory
transport and update the call-contract tests and monitoring documentation.

The regression failed before the fix. All 67 focused tests passed with the
optional Sentry SDK installed. Server typecheck and module boundaries passed.

Co-Authored-By: Paperclip <noreply@paperclip.ing>

2026-09-22 12:17:58 -07:00

..

scripts

fix: attribute Sentry errors to the loaded source release (#13719)

2026-09-20 08:08:33 -07:00

src

Keep Sentry run failure context on its own event

2026-09-22 12:17:58 -07:00

CHANGELOG.md

…

package.json

fix: preserve runner recovery, warm sessions, and task outcomes (#13338)

2026-09-12 19:41:15 -05:00

tsconfig.json

…

vitest.config.ts

fix(server): bundle the vendored paperclip-runner instead of hand-mirroring its deps (#13121)

2026-09-09 16:38:17 -07:00