@ai-matrx/meet 0.7.2 → 0.7.5

package/CHANGELOG.md

@@ -1,8 +1,96 @@
 # Changelog — `@ai-matrx/meet`
 
+## 0.7.5
+### Unreleased
+
+### Meet wave 2 — in-meeting parity with Zoom and Google Meet
+
+- **Host moderation now actually happens — through the server.** Through 0.7.x "Mute" and
+  "Remove" were published on the room's data plane (`mx.host`) and nothing in the platform
+  listened: the buttons did nothing. Every host power is now `POST /api/v1/meet/moderate`
+  (`MEET_ROUTES.moderate`), decided by aidream from the meeting itself and performed by the SFU:
+  mute, stop video, stop screen share, mute everyone, ask to unmute (one / everyone), spotlight
+  for everyone, lower a hand / all hands, make or remove a co-host, make someone the host
+  (host only; the previous host stays a co-host), rename (self, or a host renaming others),
+  remove (cannot rejoin), report. New `core/in-room.ts` (`createInRoomClient`,
+  `ModerationAction`, `MODERATION_ACTIONS`), exposed as `MeetHost.inRoom`.
+  `useHostControls()` gains `run(request)`, `isOwner`, `busy`, and a shared `notice` (the
+  server's sentence, kept in the snapshot as `actionNotice`).
+- **In-meeting chat is SAVED.** A message to everyone goes through `POST /api/v1/meet/chat`,
+  is stored in `communication.meet_chat_messages`, and reaches the room as the server's
+  `matrx.meet.chat`; every join reads the history (`GET ?meeting_id=`), so a late joiner sees
+  what was said. It shows at once as pending, then saved; a refusal stays visible with the
+  server's reason. **Private messages** to one person: `engine.sendPrivateChat(to, text)` /
+  `useRoom().sendPrivateChat` — data plane only, addressed to that identity, never saved.
+- **Spotlight for everyone** rides the room's metadata (server-set, delivered on join);
+  `snapshot.spotlight`, `computeStage({ spotlight })` — a local pin outranks it, a screen share
+  outranks both.
+- **Raise hand queue** — hands carry when they went up (`MeetParticipant.handRaisedAt`),
+  `useHandQueue()` orders them, a raised hand is re-announced (with its original time) to a late
+  joiner, and a host lowers one or all.
+- **Reactions** — a reaction picker in the control bar (Meet's nine), and the overlay is finally
+  mounted (`<MeetingOverlays>` inside `<ControlBar>`).
+- **What a host did to me** — `matrx.meet.moderation` packets become `snapshot.moderationNotice`
+  ("Ana is asking you to unmute" with an Unmute button; muted; removed). A demotion re-grants
+  the local role, so an old host loses host controls at once.
+- **Noise suppression and background blur / picture** — `engine.setEffects()` /
+  `useMediaEffects()`, applied live and remembered per browser (`createWebEffectsStorage`);
+  background effects via `@livekit/track-processors` (new dependency, imported lazily), absent
+  on a browser without WebGL2.
+- **Devices** — the chosen microphone / camera / speaker are now APPLIED on join (the pickers
+  used to store a choice nothing read); `<SettingsPanel>` switches them live with a microphone
+  level meter and a speaker test; the pre-join screen has a live camera preview (with the chosen
+  background), a mic level meter, a speaker picker + test, and the effects.
+- **Connection quality** — `<QualityBars>` on every tile and People row.
+- **People panel** — search, the hand queue with Lower all, Mute all / Ask all to unmute, and a
+  per-person menu (`<PersonMenu>`, also on every tile) with every action the actor may take.
+- **Keyboard shortcuts** (Meet's chords): ⌘/Ctrl+D mic, ⌘/Ctrl+E camera, ⌘/Ctrl+Alt+H hand,
+  ⌘/Ctrl+Alt+C chat, ⌘/Ctrl+Alt+P people, Shift+? the sheet (`useMeetShortcuts`,
+  `MEET_SHORTCUTS`, `<ShortcutsSheet>`).
+- **Exported for host layouts**: `HostMenu` (lock / end — the Board layout can now render it),
+  `MeetingOverlays`, `PersonMenu`, `SettingsPanel`, `ShortcutsSheet`, `QualityBars`,
+  `MEET_REACTIONS`, new icons.
+
+### Removed
+
+- `RoomEngine.publishHostAction`, `HostAction`, `DATA_TOPICS.hostAction` — a control plane
+  nobody listened to (see above). `RoomEngine.sendChat` → `MeetHost.inRoom.sendChat` (saved).
+
+### Consumer action
+
+matrx-frontend: bump `@ai-matrx/meet`; the Board header renders `<HostMenu>` beside its host
+controls. Everything else arrives through `<ControlBar>`, which both layouts already render.
+Requires the aidream routes `/v1/meet/moderate` and `/v1/meet/chat`.
+
+## 0.7.4
+
+Automatic changed-only republish (docs/metadata drift since the last tag — see
+`git diff npm/meet/v0.7.3..npm/meet/v0.7.4 -- apps/shared/meet`).
+No source changes intended and no consumer action required.
+
+## 0.7.3
+
+Automatic changed-only republish (docs/metadata drift since the last tag — see
+`git diff npm/meet/v0.7.2..npm/meet/v0.7.3 -- apps/shared/meet`).
+No source changes intended and no consumer action required.
+
 ## 0.7.2
 ### Unreleased
 
+- **Meet wave 1 — meetings you can manage day to day.** New `MeetRepository` methods over the
+  new database doors: `scheduleMeeting`, `updateMeeting` (JSON patch, version compare-and-swap),
+  `cancelMeeting`, `archiveMeeting`, `restoreMeeting`, `setOccurrence` (cancel / move / restore one
+  occurrence of a series), `meetingOccurrences`, `occurrencesBetween` (the Upcoming list),
+  `invitees`, `addInvitees`, `setInviteeRole`, `removeInvitee`, `respond`, and the account-less
+  `invitationByToken` / `respondByToken`. New server calls `announceMeeting` (send invitations /
+  updates / cancellations with `.ics`, re-queue reminders — call after every save) and
+  `pushMeetingToGoogleCalendar` (gated by the server). `MeetingRecord` gains `timeZone`, `agenda`,
+  `recurrenceRule`, `joinBeforeHost`, `cancelledAt`, `cancellationReason`, `deletedAt`,
+  `calendarSequence`, `version` (optional in the type). New `MeetErrorCode` `cancelled` (a join to
+  a cancelled meeting, 410, with the server's sentence); `40001` / `55000` now map to `conflict`.
+  `MEET_ROUTES.meetingAnnounce` / `meetingGoogleCalendar` + `meetingPath()`. Consumer action: none
+  required; the management screens (matrx-frontend, wave 1 UI) adopt the new methods.
+
 - **A meeting link works for people from any organization.** The server now admits a
   signed-in person from another organization who holds the link (guest rules: lobby,
   host admission). The durable feed's meeting re-read fell over for them, because RLS