Chore/add support info on suppressed exceptions

[jp-agenta]

Description

Add top-level support metadata to API-layer read/query responses and propagate it from the exception wrappers.

What changed

• Added a shared Support model in application/api/oss/src/utils/exceptions.py with:
  • support_id
  • support_ts in UTC
• Updated suppress_exceptions() so suppressed API responses get populated with support metadata instead of returning an unmarked empty object.
• Updated intercept_exceptions() so unexpected failures include support metadata in the error payload and logs.
• Made the API response DTOs used by suppressed read/query routes inherit Support directly, so the response shape now includes top-level support_id and support_ts.
• Added unit tests covering:
  • UTC support timestamp generation
  • support fields on API response models
  • support attachment on suppressed responses
  • support metadata in intercepted exceptions

Notes

This change is limited to API-layer read/query response models that use suppress_exceptions().
DAO-layer suppression behavior remains unchanged.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
agenta-documentation	Ready	Preview, Comment	Apr 22, 2026 0:36am

[github-actions]

Railway Preview Environment

Preview URL	https://gateway-production-906ea.up.railway.app/w
Project	agenta-oss-pr-4212
Image tag	pr-4212-7aba3b9
Status	Deployed
Railway logs	Open logs
Workflow logs	View workflow run
Updated at 2026-04-22T12:41:29.169Z