4 Commits

Include renames

Author	SHA1	Message	Date
Lotus CIandClaude Opus 5.5	657271163f	feat(lotus): soundboard works in voice channels with a call policy (#47) ... Clips publish as a separate Unknown-source track, which tokens limited to listed sources (any room with io.lotus.room_quality) refuse, so #52 could only answer not_permitted. Where the token allows the microphone, the clip is now mixed into the published mic for its duration: the track on the mic's RTCRtpSender (post-denoise) and the clip feed a MediaStreamAudioDestinationNode, the sender switches to the mix with replaceTrack, and the original goes back when the clip ends. Muting mid-clip stops it; a track LiveKit swapped in meanwhile is left alone. not_permitted remains for tokens without the microphone. Fixes #47 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_017PCb59uY3UKqDqt7B6hzd5	2026-10-19 23:23:06 -04:00
Lotus CIandClaude Opus 5.5	5f4844cad5	feat(lotus): report remote screenshare audio to the host (cinny #277) ... New fromWidget action io.lotus.screenshare_audio_state { present }: each LivekitRoomAudioRenderer reports whether a remote participant's ScreenShareAudio track is being received; the combined answer is sent to the host on change, and cleared when a renderer unmounts. cinny uses it to show "Mute Screenshare Audio" only when there is something to mute. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_017PCb59uY3UKqDqt7B6hzd5	2026-10-19 14:21:52 -04:00
Lotus CIandClaude Opus 5.5	2ef80cef2c	docs(lotus): LOTUS.md lists io.lotus.call_error and io.lotus.reconnect (#50) ... Regenerate the action table from lotusActions.ts: add the two actions from #50, and note which cinny PR handles each one still in flight. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_017PCb59uY3UKqDqt7B6hzd5	2026-10-19 00:01:18 -04:00
Lotus CIandClaude Opus 5.5	167ffc2440	docs(lotus): LOTUS.md: the io.lotus.* widget protocol, URL flags and release flow (#43) ... Everything the host relies on was documented only in src/lotus comments. Add a table of the 22 io.lotus.* actions (generated from lotusActions.ts, with direction, payload and whether cinny handles each), the URL flags, fork-only behaviour and the release/publish steps. Fixes #43 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_017PCb59uY3UKqDqt7B6hzd5	2026-10-18 01:24:22 -04:00