server: own WebSocket handler tasks

[yisding]

Problem

VoiceServer tracked listener-created WebSocket handler tasks in a manual set. Shutdown cancelled and gathered those tasks but discarded every result, so expected cancellation and a handler cleanup failure were indistinguishable and failures lacked task identity.

Changes

• adopt each listener-created handler into a named RuntimeTaskScope
• assign a stable easycat-raw-ws-handler-<connection-id> task name
• cancel handlers through the scope snapshot during shutdown
• inspect completed gather results, suppressing only cancellation explicitly requested by stop
• log genuine handler cleanup failures with the exact task name
• update drain assertions to check the named scope is empty
• document handler ownership and result policy

Why / impact

WebSocket handlers now remain discoverable under one lifecycle owner until they exit. Normal stop cancellation stays quiet, while a cleanup exception raised after cancellation becomes attributable and observable.

Root cause

The listener owns creation of handler tasks, so VoiceServer historically kept a parallel set. That set had not been replaced by adoption into WS2.5's task-scope model, and its return_exceptions=True results were never classified.

Checks

• focused handler result-policy and source-inventory tests — 11 passed
• full VoiceServer lifecycle file outside the sandbox — 24 passed / 4 skipped
• local-socket drain selection — 15 skipped because localhost sockets are unavailable in this environment
• Ruff on changed Python files — passed
• mypy on voice_server.py — passed
• pre-commit hooks — passed

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Pro Plus

Run ID: a1882a2c-64f2-4b69-ab72-44247565efcf

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: d3a9af4eba

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".