[eyevinn-developer]

Summary

• Make the admin-panel per-participant mute control functional: a mute/unmute toggle on each eligible participant row.
• Mute sends the existing SMB EndpointMessage directive { muteParticipant: 'mute' } to the target endpoint plus the global broadcast { muteState: 'mute', participantId }; unmute sends the 'unmute' variants (payloads per the Define admin-mute vs self-mute state model and unmute semantics #677 model).
• The button reads per-participant admin-mute state from callState.participantMuteState (the Record<endpointId, boolean> map from Propagate global mute state to all participants (state sync + enforcement model) #678/feat: propagate global mute state to all participants via data channel #749) so it reflects current state for every admin, showing the unmute affordance with aria-pressed when muted.
• Reuses the existing data-channel signalling path and the UPDATE_PARTICIPANT_MUTE_STATE reducer action from feat: propagate global mute state to all participants via data channel #749 — no new state model and no new dependencies.
• Kick control intentionally left a disabled placeholder (tracked separately in Feat: Control panel — Kick user from call #638).

Test plan

• Tests pass (npm test)
• TypeScript compiles (npm run typecheck)
• Lint clean (npm run lint)
• Join one SMB line from two+ browsers, open the admin panel, click a participant's mute button and confirm their input is silenced and the row shows the muted/unmute state in every connected client; click again to unmute and confirm it reverses.

What a human does next

Nothing to configure. To verify manually: join one SMB line from two+ browsers, open the admin panel, click a participant's mute button and confirm their input is silenced and the row shows the muted/unmute state in every connected client; click again to unmute and confirm it reverses (advisory — the target can still unmute locally, matching the merged self-mute model).

Closes #676

🤖 Generated with Claude Code

[eyevinn-pr-reviewer]

Code Review

Verdict: LGTM

Summary: A clean, well-scoped extension of the already-merged advisory mute model (#749) into a per-participant admin toggle. It correctly reuses the participantMuteState map, the UPDATE_PARTICIPANT_MUTE_STATE reducer action, and the existing data-channel send/broadcast pattern rather than reinventing them; the AdminPanel component is well tested. Two non-blocking warnings: the net-new setParticipantMute send-path logic is untested, and the panel toggle silently no-ops when the data channel is closed.

Blocking

None.

Warnings

• src/components/ui/production-line/production-line.tsx:642-685 — The net-new behavior for #676 lives in setParticipantMute (the "unmute" payload branch, the parameterized broadcast with participantId: endpointId, and the false/"data channel not open" return path) and has no unit or integration test. admin-panel.test.tsx only asserts that the AdminPanel invokes the onToggleMute callback with the right arguments; it does not exercise the actual directive/broadcast JSON construction or the closed-channel branch. Consider extracting the message-construction logic into a pure helper (like data-channel-parser.ts on the receive side) so it can be unit tested, or add coverage for the send path.
• src/components/ui/production-line/admin-panel.tsx:222 — The toggle calls onToggleMute(p.endpointId, !isMuted) and discards the boolean it returns. When the data channel is closed, setParticipantMute returns false, dispatches nothing, and logs internally — so an admin clicking mute/unmute in the panel gets a silent no-op with no UI feedback and no change to the button state. The sibling UserList/confirmation path surfaces this via setMuteError. The panel path should give equivalent feedback or at least not appear to succeed.

Suggestions

• src/components/ui/production-line/admin-panel.tsx:84,224 — The SVG fill is hardcoded to #f96c6c (error red) in both states, and an unmuted participant renders the MicMuted (crossed-mic) icon as the "click to mute" affordance. Combined with the always-red fill it can read as "this participant is muted" even when they are not. Consider differentiating the icon fill by state.

Domain Note

This change affects data channel parsing and the advisory mute directive/broadcast lifecycle. The send path is consistent with the receive side (data-channel-parser.ts maps "unmute" → muted: false), so both mute and unmute round-trip correctly. Advisory (non-server-enforced) mute semantics match the merged self-mute model.

---

Reviewed by eyevinn-pr-reviewer via daily-backlog-pr Phase 3.