Summary

• Add optional lastAudioAt metadata to the shared realtime output activity tracker snapshot without adding a required SDK method.
• Reuse the shared tracker in Google Meet Chrome command-pair and paired-node realtime output paths for output byte/active health and recent-output local barge-in gating.
• Keep transport, Chrome/node process lifecycle, audio conversion, echo suppression, and Google Meet config ownership local.

Audit notes

• Gateway Talk already consumes shared forced-consult coordination and speakable tool-result extraction; it does not own browser playback, so no output tracker migration there.
• Google Meet is the useful non-Discord adapter proof because it owns local playback/buffer clearing and local human barge-in detection.
• Duplicate realtime error suppression still appears provider-specific to OpenAI; no second generic consumer found in this pass.
• Speakable-result extraction is already shared where Gateway Talk and Voice Call need it; Google Meet native consult submission does not need a separate extraction.

Verification

• pnpm exec oxfmt --check --threads=1 src/talk/output-activity-tracker.ts src/talk/output-activity-tracker.test.ts extensions/google-meet/src/realtime.ts extensions/google-meet/src/realtime-node.ts
• node scripts/run-vitest.mjs src/talk/output-activity-tracker.test.ts
• pnpm test extensions/google-meet/index.test.ts -- --reporter=dot -t "uses realtime transcription plus regular TTS in Chrome agent mode|pipes Chrome command-pair audio through the realtime provider|uses a local barge-in input command to clear active Chrome playback|pipes paired-node command-pair audio through the realtime provider"
• pnpm plugin-sdk:api:check
• pnpm build
• env -u OPENCLAW_TESTBOX pnpm check:changed
• /Users/steipete/Projects/agent-skills/skills/autoreview/scripts/autoreview --mode local

Behavior addressed: Google Meet command and node realtime audio bridges now consume the shared realtime output activity tracker while preserving existing playback ownership and local barge-in timing behavior.
Real environment tested: Local macOS source checkout, Node/pnpm repo toolchain, focused Google Meet realtime adapter tests.
Exact steps or command run after this patch: Tracker unit test, four focused Google Meet realtime adapter tests, SDK API check, full build, changed checks, and two autoreview runs after one accepted SDK-compat finding was fixed.
Evidence after fix: Tracker tests passed, Google Meet adapter tests passed, SDK API baseline check passed, build passed, check:changed passed, final autoreview reported no accepted/actionable findings.
Observed result after fix: Output byte/active health and recent-output barge-in checks are backed by shared tracker state; no live provider behavior change intended.
What was not tested: Live Google Meet, browser voice, or Discord sessions; this is a helper reuse/refactor with unit and adapter proof.