[Slai.life (huong8373tt-beep)]

Description

Implements the remaining service-shutdown investigation for P311-08 from #3166.

When close_services_async collects failures from cached backend service closure and analytics service closure, the original exceptions now receive safe operation-name notes before they are re-raised or grouped. This preserves exception identity, type, traceback, cancellation behavior, ordering, and the existing single-error/BaseExceptionGroup contract.

Tests and Documentation

• uv run --frozen --no-sync pytest -q --basetemp=D:\oss_contrib\pyrit-p311-08\.pytest-tmp-service-shutdown tests/unit/backend/test_analytics_lifecycle.py — 12 passed.
• uv run --frozen --no-sync pre-commit run --files pyrit/backend/services/service_lifecycle.py tests/unit/backend/test_analytics_lifecycle.py — passed, including Ruff and ty checks.
• git diff --check — passed.
• No documentation changes were needed.

Slai Agent Runtime assisted with investigation, implementation, and tests. The account owner reviewed and authorized this contribution.

[Manohar Paturi (ManoharPaturi)]

Using error.add_note here fits Python 3.11 exception handling nicely. It attaches the specific service closure context without wrapping or altering the underlying exception type, so single error raises keep their exact identity and tracebacks intact while multi failure scenarios retain the existing BaseExceptionGroup structure. The lifecycle tests in test_analytics_lifecycle verify both the single failure and grouped failure cases cleanly.