jam-cloud/agent-tasks/client-simulator/progress.md

Client Simulator Progress

Goal

Build a web-client-backed jamClient compatibility path plus a simulator/test harness that verifies frontend bridge calls, backend/frontend events, REST API usage, websocket traffic, and DB state behave equivalently for core session flows.

Plan

• Create task tracking and record the initial plan
• Complete async bridge contract spike (await context.jamClient.method() viability and blast radius)
• Complete async bridge contract spike (await context.jamClient.method() viability and blast radius) (dual-bundle parser split + SessionStore legacy/modern split in progress)
• Map protocol surface for join/mute/volume flows using native 2-party recordings
• Add instrumentation/tape-recording hooks (frontend/backend)
• Define comparison assertions for compatibility tests
• Implement web jamClient shim compatibility layer
• Replace VOL_JS_OBJECT dependency with explicit bridge methods
• Build MVP web-to-web session flow
• Build simulator/replay harness and automated specs

2026-03-01 WebRTC Planning Update

• Captured native reference logs for 2-party mute/volume scenario in:
  • web/ai/native-client-2p-recording/20260228-210957-seth-native-2p-mute-volume.log
  • web/ai/native-client-2p-recording/20260228-211006-david-native-2p-mute-volume.log
• Confirmed these are sufficient as baseline artifacts for bridge-call and REST/websocket pattern parity while implementing web-client media with selective behavioral divergence.
• Added execution plan in agent-tasks/client-simulator/webrtc-web-client-plan/progress.md.
• Added Tier A/B/C contract matrix from the captured logs in:
  • web/ai/native-client-2p-recording/contract-matrix.md

Notes

• Native recording execution is intentionally out of scope for this effort (native path is being deprecated).
• Recording/comparison scope must include REST API requests/responses in addition to bridge/events/websocket/DB behavior.