Best possible solution:

Keep the PR open for maintainer review and merge once the current-head required checks finish, preserving the executable QA canaries in test/QA-owned surfaces.

Do we have a high-confidence way to reproduce the issue?

Not applicable: this PR adds executable QA coverage rather than fixing a reported runtime bug. The relevant verification path is the added canary tests and current-head CI/Testbox evidence.

Is this the best way to solve the issue?

Yes: the coverage is placed at existing owner seams for Voice Call, Gateway/WebChat media, browser Talk, heartbeat scheduling, and QA OTEL evidence without adding production APIs or config.

AGENTS.md: found and applied where relevant.

Codex review notes: model internal, reasoning high; reviewed against 0f1fbbe8779d.

Label changes:

• add rating: 🦞 diamond lobster: Overall readiness is 🦞 diamond lobster; proof is 🦞 diamond lobster and patch quality is 🦞 diamond lobster.
• add status: 👀 ready for maintainer look: ClawSweeper has no concrete contributor-facing blocker left for this PR. Not applicable: The contributor proof gate does not apply to this maintainer-labeled PR; the PR body still lists targeted runtime tests, Playwright proof, direct OTEL producer execution, Testbox check:changed, and autoreview evidence.

Label justifications:

• P3: This is low-risk test and QA evidence coverage with no production behavior change.
• rating: 🦞 diamond lobster: Overall readiness is 🦞 diamond lobster; proof is 🦞 diamond lobster and patch quality is 🦞 diamond lobster.
• status: 👀 ready for maintainer look: ClawSweeper has no concrete contributor-facing blocker left for this PR. Not applicable: The contributor proof gate does not apply to this maintainer-labeled PR; the PR body still lists targeted runtime tests, Playwright proof, direct OTEL producer execution, Testbox check:changed, and autoreview evidence.

PR surface:

Source +44, Tests +672, Other +72. Total +788 across 14 files.

What I checked:

• Live PR metadata: Live PR view shows this is an open, maintainer-labeled PR at head c807de8 with 14 changed files, all in QA scenarios, tests, or test helpers. (c807de8b4e00)
• PR diff scope: GitHub PR diff stat shows the branch adds runtime fixture canaries across 14 QA/test files and does not change production runtime files. (c807de8b4e00)
• Voice Call runtime canary: The new Voice Call E2E fixture registers the plugin, routes CLI, Gateway RPC, and agent tool calls through the existing mock-provider runtime, checks active status, and tears down runtime/global state. (extensions/voice-call/src/voice-call-cli-rpc-agent-tool.e2e.test.ts:53, c807de8b4e00)
• WebChat media-ticket canary: The WebChat test now exercises the real Gateway assistant-media route by minting a scoped ticket, rejecting unticketed access, and serving the synthesized local audio with the ticket. (test/e2e/qa-lab/media/webchat-auto-tts.e2e.test.ts:152, c807de8b4e00)
• Browser Talk canary: The new browser Talk E2E uses a real Playwright page, mock Gateway WebSocket, media-device/audio fixtures, and verifies start, live state, stop, and resource cleanup behavior. (ui/src/ui/e2e/browser-talk-start-stop.e2e.test.ts:72, c807de8b4e00)
• OTEL script evidence integration: The OTEL smoke runtime now wraps stdout/stderr through the shared QA script evidence writer and records pass/fail summaries plus bounded artifacts. (test/e2e/qa-lab/runtime/qa-otel-smoke-runtime.ts:1817, c807de8b4e00)

Likely related people:

• RomneyDa: Current-main history shows Dallin Romney recently touched the central QA/runtime, Voice Call, UI helper, and heartbeat files, and the PR head is in the same area. (role: recent area contributor; confidence: high; commits: e6dec69403f0, ab9e233d02a8, e1338bb2fa98; files: extensions/voice-call/src/manager.test-harness.ts, extensions/voice-call/index.ts, test/e2e/qa-lab/runtime/qa-otel-smoke-runtime.ts)
• Wynne668: Recent current-main history includes a Control UI helper/chat-flow change adjacent to the browser E2E helper touched by this PR. (role: recent UI adjacent contributor; confidence: medium; commits: 61564f2d2e83; files: ui/src/test-helpers/control-ui-e2e.ts, ui/src/ui/e2e/chat-flow.e2e.test.ts)

• 🦀 challenger crab: rare, exceptional readiness with strong proof, clean implementation, and convincing validation.
• 🦞 diamond lobster: very strong readiness with only minor maintainer review expected.
• 🐚 platinum hermit: good normal PR, likely mergeable with ordinary maintainer review.
• 🦐 gold shrimp: useful signal, but proof or patch confidence is still limited.
• 🦪 silver shellfish: thin signal; proof, validation, or implementation needs work.
• 🧂 unranked krab: not merge-ready because proof is missing/unusable or there are serious correctness or safety concerns.
• 🌊 off-meta tidepool: rating does not apply to this item.

Shiny media proof means a screenshot, video, or linked artifact directly shows the changed behavior. Runtime, network, CSP, and security claims still need visible diagnostics.

• ClawSweeper keeps one durable marker-backed review comment per issue or PR.
• Re-runs edit this comment so the latest verdict, findings, and automation markers stay together instead of adding duplicate bot comments.
• A fresh review can be triggered by eligible @clawsweeper re-review comments, exact-item GitHub events, scheduled/background review runs, or manual workflow dispatch.
• PR/issue authors and users with repository write access can comment @clawsweeper re-review or @clawsweeper re-run on an open PR or issue to request a fresh review only.
• Maintainers can also comment @clawsweeper review to request a fresh review only.
• Fresh-review commands do not start repair, autofix, rebase, CI repair, or automerge.
• Maintainer-only repair and merge flows require explicit commands such as @clawsweeper autofix, @clawsweeper automerge, @clawsweeper fix ci, or @clawsweeper address review.
• Maintainers can comment @clawsweeper explain to ask for more context, or @clawsweeper stop to stop active automation.