docs: add Asqav to external tracing processors list

[jagmarques]

Summary

Add Asqav to the external tracing processors list. Asqav now implements the TracingProcessor interface via AsqavTracingProcessor (added in commit 807e695), which signs trace and span lifecycle events as governance records.

This follows up on the feedback from #2858, where @seratch noted the page lists only integrations supporting the tracing interface. Asqav previously only had a guardrail integration - it now supports tracing as well.

• PyPI: https://pypi.org/project/asqav/
• Integration module: asqav.extras.openai_agents

Test plan

• Docs-only change (single line addition to docs/tracing.md)
• Link format matches existing entries

Issue number

Follow-up to #2858

Checks

• I've added new tests (if relevant)
• I've added/updated the relevant documentation
• I've run make lint and make format
• I've made sure tests pass

[seratch]

I am not sure if the module you just added works, plus the linked document does not mention tracing at all. So, we can't have this change yet.

[jagmarques]

Thanks for flagging both issues, @seratch. You're right that the docs page at asqav.com/docs/integrations doesn't currently cover tracing for the Agents SDK - it only documents the guardrail integration and general OpenTelemetry export separately. The AsqavTracingProcessor was just added in commit 807e695 and the documentation hasn't caught up yet, which is a fair gap to call out. I'd rather not leave a PR open that points to incomplete docs, so would it work if I come back once the tracing section is live and the integration can be verified end-to-end? Happy to update the PR at that point or open a fresh one, whichever you prefer.

[jagmarques]

Tracing docs are live at https://asqav.com/docs/integrations#openai-agents - covers AsqavTracingProcessor usage, all four signed events (trace:start/end, span:start/end), constructor params, and shutdown behavior. Let me know if anything else is needed.