tracing: add organization_id + message_id filters to ListSpans

[rowan-stein]

User request

Tracing needs to align with the architecture/product spec. In particular, we need routing/navigation refactor in the tracing UI and a way to open a run from the chat app by message id. The architecture spec requires the Tracing query API to support organization-scoped queries and message-id lookup.

Spec (from architecture + research)

References:

• https://github.com/agynio/architecture/blob/main/architecture/tracing.md#query-authorization
• https://github.com/agynio/architecture/blob/main/architecture/tracing.md#listspans

Changes

Update proto/agynio/api/tracing/v1/tracing.proto:

1. Add organization_id to ListSpansRequest (required)

message ListSpansRequest {
  SpanFilter filter = 1;
  int32 page_size = 2;
  string page_token = 3;
  ListSpansOrderBy order_by = 4;
  string organization_id = 5; // Required. UUID of the organization. Gateway enforces caller membership.
}

2. Add message_id to SpanFilter (optional)

message SpanFilter {
  // existing fields 1-9 unchanged
  string message_id = 10; // Optional. UUID of the thread message; matches resource attr agyn.thread.message.id
}

Notes

• agynio/api/gateway/v1/tracing.proto should not need explicit changes since it already proxies ListSpansRequest.

Validation

• buf lint
• buf build
• buf breaking --against '.git#branch=main'

Dependencies

Downstream repos that will need regeneration/updates after merge:

• agynio/tracing (implement filters)
• agynio/tracing-app (pass orgId; use messageId deep-link)