Fix Backend (Go) CI guard failure from forbidden ElevenLabs endpoint literal in tests

[Copilot]

The Backend (Go) GitHub Actions job failed before build/test execution because the CI guard that blocks live ElevenLabs endpoint usage in tests matched a literal endpoint string in a test comment. This PR removes that false-positive trigger without changing test behavior.

• Root cause (CI guard trip)

  • ci.yml enforces:

    grep -rn "api.elevenlabs.io" pkg/briefing/*_test.go

  • A comment in backend/pkg/briefing/tts_test.go contained that exact literal, causing the guard to fail the job.

• Change made (minimal/surgical)

  • Reworded the ttsServer helper comment in backend/pkg/briefing/tts_test.go to preserve intent (tests must not call live ElevenLabs) while removing the forbidden literal string.

• Behavioral impact

  • No production code changes.
  • No test logic changes.
  • Only comment text was updated to comply with the CI guard.

[Copilot]

Pull request overview

This PR fixes a false-positive failure in the “Backend (Go)” CI guard that blocks live ElevenLabs usage in tests by rewording a test helper comment to avoid the forbidden api.elevenlabs.io literal, without changing any test behavior.

Changes:

• Reworded the ttsServer helper comment in backend/pkg/briefing/tts_test.go to remove the literal endpoint string that CI greps for.
• Preserved the intent of the comment (tests must not make outbound calls to ElevenLabs).

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.