Best possible solution:

Land the plugin-owned validation and canonical URL normalization after the branch and exact-head required checks satisfy the repository’s normal merge gates.

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

Yes. Current main forwards incomplete bridge-control parameter objects to node-host handlers that require those fields, providing a high-confidence source reproduction without a live meeting.

Is this the best way to solve the issue?

Yes. Validating caller-controlled fields in the dangerous plugin invoke policy is the narrowest maintainable fix, and the proposed checks match both node-host requirements and established internal callers.

AGENTS.md: found and applied where relevant.

Codex review notes: model internal, reasoning high; reviewed against 790cd2aff2d4.

Label justifications:

• P2: This fixes a bounded late-validation defect in the Google Meet plugin without evidence of widespread outage, data loss, or message loss.
• 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. Sufficient (live_output): Controlled after-fix output exercises the real policy and node-host handler, showing malformed calls denied before dispatch and valid URL-filter calls dispatched successfully.
• proof: sufficient: Contributor real behavior proof is sufficient. Controlled after-fix output exercises the real policy and node-host handler, showing malformed calls denied before dispatch and valid URL-filter calls dispatched successfully.

PR surface:

Source +33, Tests +42. Total +75 across 2 files.

What I checked:

• Current-main reproduction: The current policy forwards incomplete stopByUrl, pullAudio, pushAudio, and clearAudio parameter objects instead of rejecting them before node dispatch. (extensions/google-meet/src/node-invoke-policy.ts:94, 790cd2aff2d4)
• Node-host contract: The corresponding node-host handlers require stopByUrl.url, audio bridge IDs, and pushAudio.base64, confirming that malformed calls currently fail only after dispatch. (extensions/google-meet/src/node-host.ts:489, 790cd2aff2d4)
• Proposed policy fix: The PR returns closed policy decisions, denies missing handler-required fields, normalizes Meet URL filters, strips unrelated fields, and invokes the node only after approval. (extensions/google-meet/src/node-invoke-policy.ts:94, 0ff60bfb0c1b)
• Caller compatibility: Plugin-owned callers already supply the newly required URL, bridge ID, and audio data fields, so the stricter policy preserves established internal requests. (extensions/google-meet/src/realtime-node.ts:242, 790cd2aff2d4)
• Canonical URL behavior: The reused normalizer accepts explicit HTTPS Google Meet meeting-code URLs and preserves valid query strings, matching start-flow validation and node-host filtering semantics. (extensions/google-meet/src/runtime.ts:59, 790cd2aff2d4)
• Regression coverage: Focused tests assert that malformed control calls never invoke the node and that valid stopByUrl filters are normalized and reduced to approved fields. (extensions/google-meet/src/node-invoke-policy.test.ts:124, 0ff60bfb0c1b)

Likely related people:

• steipete: The present Google Meet policy and node-host files enter the available checkout history in his commit; grafted snapshot history limits finer attribution. (role: recent area contributor; confidence: medium; commits: 920b29bdd5d8; files: extensions/google-meet/src/node-invoke-policy.ts, extensions/google-meet/src/node-host.ts)
• Vincent Koc: The preceding available repository snapshot containing the Google Meet node-host surface is authored by Vincent Koc, though grafted history prevents precise feature-level attribution. (role: earlier area contributor; confidence: low; commits: e085fa1a3ffd; files: extensions/google-meet/src/node-host.ts, extensions/google-meet/src/realtime-node.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.

• reviewed 2026-07-10T15:18:41.235Z sha 9673edb :: needs real behavior proof before merge. :: none
• reviewed 2026-07-11T00:13:16.471Z sha 841b7eb :: needs maintainer review before merge. :: none
• reviewed 2026-07-11T00:44:08.383Z sha d32a965 :: needs maintainer review before merge. :: none