Daily use 31: User, member and DM context menus (#520) #585

Closed
charles wants to merge 0 commits from dailyuse-31-ui-user-dm-menus into dailyuse
Owner

What

Daily use 31: the user, member and DM context menus (spec §3.2 (e), (f)).

  • Right press on a member list row, a message author's avatar or name (the message rides along so "Report message" shows), a user mention pill (MentionRenderer.tsx: guild only, no channel/message) and a DM / group DM row opens the fluxer_core::menus::{user, dm} model at the cursor (screens/main/menus/{mod,user,dm}.rs). Escape / outside click close it; opening it closes the participant and stream menus.
  • Relationship rows go through the store confirm drawn by Task 33's generic confirm; Shift sends confirmed: true only where social::confirm_rule says ConfirmShiftSkips (block, unblock, remove, accept). Close DM, Open DM (blocked) and Leave group always ask.
  • "Change friend nickname" opens modals/friend_nickname.rs (BaseChangeNicknameModal.tsx: title "Change nickname", label "Nickname", display name as placeholder, X "Clear nickname" while non-empty, "Save"; >32 chars shows "Nickname must not exceed 32 characters"; trim() || null).
  • Participant menu gains a first group "Mention" / "Message" ("Open DM" when blocked) taken from the same core builder (#476; VoiceParticipantMenuData.tsx:576-603).
  • Row icons from ContextMenuIcons.tsx (new Phosphor fills: User, UserMinus, CheckCircle).

Tests

  • crates/fluxer-ui/tests/menus_user_dm.rs: author_right_press_carries_message_for_report, mention_right_press, shift_click_on_block_skips_confirm_but_not_on_close_dm, nickname_modal_validation, plus member/DM row opening, mention row, participant Mention/Message.
  • Goldens (lavapipe): member_menu, member_menu_moderator (own menu with read-only Roles open), dm_menu, group_dm_menu, block_confirm; participant_menu and participant_menu_entrance_submenu regenerated (new first group). References in docs/screenshots/ (dimensions from ContextMenu.module.css, BaseChangeNicknameModal.module.css); no Electron side-by-side available here.
  • FLUXER_SCREENSHOT_TESTS=1 cargo xtask ci green locally. No FLUXER_DESKTOP_TESTS tests apply.

Deviations / notes for the reviewer

  • File ownership: screens/main/menus/mod.rs is also created by the unmerged Task 29 (#571), which 31 does not depend on in the plan. I built it with the same API names (Target, Open, State, Message, items, action_at, update, over, trigger; Local::menus, main::Message::Menus) and verbatim items/row_item/action_at, so the later merge is a union of Target variants, State fields, icon arms and update arms. update takes a shift argument here.
  • Touched outside the Files list (minimal): widgets/inline_flow.rs (text runs take on_right_press, window offset tracked like row_input), rich_text/ast_to_spans.rs (SpanModel.user), app.rs (Local field, Escape), messages.rs (OpenUserMenu), no-op UserMenu arms in profile_popout.rs, forum/{guidelines,composer}.rs, message_content/embed.rs, modals/mod.rs. Paragraphs with a user mention are now drawn by InlineFlow (existing goldens unchanged).
  • Merge conflict of the stacked branches in dms/mod.rs (DM list X): resolved per useDMListItemHandlers.tsx:132-150: a group's X asks "Leave group", a 1:1 DM's X closes at once (confirmed: true); tests/friends.rs expectation fixed accordingly.
  • Not built: the "Copied to clipboard" toast after Copy user/channel ID, and the "Nickname updated" toast; the modal closes on Save without waiting for the server.
  • Participant menu's new rows have no icons, like its other rows.
  • Base CI hit the known #549/#304 SIGSEGV at exit of fluxer lib tests once; rerun green.

Stacked on: origin/dailyuse-18-core-user-dm-menus, origin/dailyuse-33-ui-confirm-friends-page

Closes #520
Closes #476

🤖 Generated with Claude Code

## What Daily use 31: the user, member and DM context menus (spec §3.2 (e), (f)). - Right press on a member list row, a message author's avatar or name (the message rides along so "Report message" shows), a user mention pill (`MentionRenderer.tsx`: guild only, no channel/message) and a DM / group DM row opens the `fluxer_core::menus::{user, dm}` model at the cursor (`screens/main/menus/{mod,user,dm}.rs`). Escape / outside click close it; opening it closes the participant and stream menus. - Relationship rows go through the store confirm drawn by Task 33's generic confirm; Shift sends `confirmed: true` only where `social::confirm_rule` says `ConfirmShiftSkips` (block, unblock, remove, accept). Close DM, Open DM (blocked) and Leave group always ask. - "Change friend nickname" opens `modals/friend_nickname.rs` (`BaseChangeNicknameModal.tsx`: title "Change nickname", label "Nickname", display name as placeholder, X "Clear nickname" while non-empty, "Save"; >32 chars shows "Nickname must not exceed 32 characters"; `trim() || null`). - Participant menu gains a first group "Mention" / "Message" ("Open DM" when blocked) taken from the same core builder (#476; `VoiceParticipantMenuData.tsx:576-603`). - Row icons from `ContextMenuIcons.tsx` (new Phosphor fills: User, UserMinus, CheckCircle). ## Tests - `crates/fluxer-ui/tests/menus_user_dm.rs`: `author_right_press_carries_message_for_report`, `mention_right_press`, `shift_click_on_block_skips_confirm_but_not_on_close_dm`, `nickname_modal_validation`, plus member/DM row opening, mention row, participant Mention/Message. - Goldens (lavapipe): `member_menu`, `member_menu_moderator` (own menu with read-only Roles open), `dm_menu`, `group_dm_menu`, `block_confirm`; `participant_menu` and `participant_menu_entrance_submenu` regenerated (new first group). References in `docs/screenshots/` (dimensions from `ContextMenu.module.css`, `BaseChangeNicknameModal.module.css`); no Electron side-by-side available here. - `FLUXER_SCREENSHOT_TESTS=1 cargo xtask ci` green locally. No FLUXER_DESKTOP_TESTS tests apply. ## Deviations / notes for the reviewer - **File ownership:** `screens/main/menus/mod.rs` is also created by the unmerged Task 29 (#571), which 31 does not depend on in the plan. I built it with the same API names (`Target`, `Open`, `State`, `Message`, `items`, `action_at`, `update`, `over`, `trigger`; `Local::menus`, `main::Message::Menus`) and verbatim `items`/`row_item`/`action_at`, so the later merge is a union of `Target` variants, `State` fields, icon arms and update arms. `update` takes a `shift` argument here. - Touched outside the Files list (minimal): `widgets/inline_flow.rs` (text runs take `on_right_press`, window offset tracked like `row_input`), `rich_text/ast_to_spans.rs` (`SpanModel.user`), `app.rs` (Local field, Escape), `messages.rs` (`OpenUserMenu`), no-op `UserMenu` arms in `profile_popout.rs`, `forum/{guidelines,composer}.rs`, `message_content/embed.rs`, `modals/mod.rs`. Paragraphs with a user mention are now drawn by `InlineFlow` (existing goldens unchanged). - Merge conflict of the stacked branches in `dms/mod.rs` (DM list X): resolved per `useDMListItemHandlers.tsx:132-150`: a group's X asks "Leave group", a 1:1 DM's X closes at once (`confirmed: true`); `tests/friends.rs` expectation fixed accordingly. - Not built: the "Copied to clipboard" toast after Copy user/channel ID, and the "Nickname updated" toast; the modal closes on Save without waiting for the server. - Participant menu's new rows have no icons, like its other rows. - Base CI hit the known #549/#304 SIGSEGV at exit of `fluxer` lib tests once; rerun green. Stacked on: origin/dailyuse-18-core-user-dm-menus, origin/dailyuse-33-ui-confirm-friends-page Closes #520 Closes #476 🤖 Generated with [Claude Code](https://claude.com/claude-code)
Refs #495

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Every UserAction, CoreEvent, Effect, ApiRequest/ApiResult and chat::Confirm
variant of the Daily use plan (Task 11a), plus the menu types (menus::MenuModel,
MenuItem, MenuItemKind, MenuItemId, MenuModel::flatten). New actions and events
do nothing yet; the runtime answers each new request with 501 CLIENT_NOT_WIRED
and logs Effect::Window until Daily use 28. MessageUser and CloseDm take a
confirmed flag and act as before; Notification gains icon (always None).

Refs #495

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Refs #496

Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
New domains notif_settings, social, invites, switcher, keynav and report with
their state, Default and stub reducers wired into App::apply; stub menu
builders (channel, category, guild, user, dm, mute::item); OwnPresence, profile
notes and modal state. Relationships move from chat::dms to app.social and are
read through social::relationship.

Refs #496

Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
Refs #497

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Fixtures used: fixtures/rest/invite_guild.json, invite_group_dm.json (shaped as
fork:packages/schema/src/domains/invite/InviteSchemas.ts:42-91, Daily use 2).

Refs #501

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Refs #501

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Settings from READY, USER_GUILD_SETTINGS_UPDATE and the patch answers;
immediate menu mutes (guild scalars, whole channel_overrides map for
channels, categories and DMs in @me), mute_config in ms, local expiry
timers, 3 s debounced modal changes, revert on failure, selectors
is_muted / muted_until / level / guild_settings_modal, and the shared
mute menu row (MuteTargetMenuItem.tsx, MuteOptions.ts,
UserGuildSettings.ts, UserGuildSettingsCommands.ts).

Refs #497

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
format_date_time shifted the end with to_offset, which panics when the
local date leaves year 9999 (a 9999-12-31T23:30Z end read east of UTC).
It now uses checked_to_offset and falls back to UTC. The
event_replaces_guild_settings test now checks the staff override is
really gone instead of an always-true assertion.

Refs #497

Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
Uses the existing server-shaped fixtures: rest/invite_metadata.json
(POST /channels/{id}/invites, S/invite/InviteSchemas.ts:42-91 plus the
metadata fields), rest/guild.json (POST /guilds, GuildResponse) and
gateway/guild_create.json.

Refs #502

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The invite modal (default invite at open, settings clamped to the
server's limits, link, expiry text, friends and group DMs with
Invite -> Sent through SendMessage), can_invite / invite_channel for the
menus, "Create or join a community" (name, static icon, create then
select the system channel once its GUILD_CREATE is in, join through the
accept flow), and "Leave community" (Confirm::LeaveGuild, no Shift
bypass, no delete_messages; hidden for the owner; on success the guild
goes as its GUILD_DELETE would, so a selected one leaves for the DMs).

Refs #502

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
dailyuse_ports listed them among the stubs that do nothing.

Refs #502

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Table tests for the notification decision (Notification.ts:187-256) and
tests for mute consumers: unread, guild pill, hide muted channels, DM
mentions. Stubs for SidebarSection.{category_muted,muted} and
notif_settings::hides_muted_channels so the tests compile.

Refs #498

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
- notif_settings::mentions_me as MessageUtils.isMentioned and
  Notification.isMessageMentionLike: blocked author no, user mention,
  @everyone unless suppressed or in an unjoined thread, own role unless
  suppressed, unmuted DM.
- notification_for follows Notification.ts:187-256: own, blocked, DND,
  SUPPRESS_NOTIFICATIONS, then thread levels (member level, parent level,
  forum new-post level, else only mentions) or mute at any level and the
  effective level.
- read_state::unread is false for a muted channel (mention counts kept);
  has_unread_messages keeps the raw answer for the new-messages bar and
  the thread menu's Mark as read.
- channel_tree: category_muted and muted rows; hide muted channels per
  guild (default_hide_muted_channels without an entry), unless selected,
  connected or with a mention; all-hidden categories hidden.
- DmRowModel.muted from the @me override; a thread is muted by its
  membership or its parent at any level.

Refs #498

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Refs #499

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Own presence from the user settings; SetStatus / SetCustomStatus write only
their fields (optimistic, reverted on failure); reset timer; idle and afk
from CoreEvent::Idle; op 3 whenever the computed presence changes; status
popout, custom status modal and custom status selectors.

Refs #499

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
A failed reset PATCH was re-sent at once by the same refresh, with no
limit (a request storm while offline or on 4xx/429). Remember the reset
whose write failed and skip it until READY, USER_SETTINGS_UPDATE or a
patch answer brings new settings, as StatusExpiry.handleExpiry does not
retry. The custom status test now asserts the profile popout exists.

Refs #499

Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
Relationship fixtures are shaped like RelationshipResponse
(packages/schema/src/domains/user/UserResponseSchemas.ts:492 of the
fork): id, type, user, nickname (nullable, always sent),
share_voice_activity, friend_shares_voice_activity.

Refs #500

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Refs #500

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
# Conflicts:
#	crates/fluxer-core/src/app.rs
# Conflicts:
#	crates/fluxer-core/src/app.rs
Refs #504

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Refs #522

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The generic confirm draws every daily-use confirm of the store; the
leave confirm (group with "Leave silently", community without); the
friends page with its tabs, search, rows, More menu, empty states and
Add friend form; Settings -> Blocked users; the DM welcome's friend
buttons; the DM list's Friends entry; the group X asks Leave group; the
group settings preview the picked icon (#383).

Refs #522

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Six new goldens from the dailyuse scenario's READY
(fixtures/gateway/dailyuse_ready.json): friends_online, friends_pending,
friends_add, friends_empty, blocked_users and leave_group_confirm, with
their reference images and README rows. dm_list, friend_picker,
group_dm_welcome, group_settings and personal_notes_welcome are redrawn:
the DM list now starts with the Friends entry. Rendered on lavapipe in
the fluxer-native-shots:u2204 (Ubuntu 22.04) image like the Linux
runner; the whole suite (129 tests) passes there.

Refs #522

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Refs #522

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Refs #522

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
menus::user and menus::dm with the rows of GuildMemberContextMenu,
UserContextMenu, DMContextMenu and GroupDMContextMenu that this client
builds; Mention into the composer; Pin DM; Close DM and Open DM (blocked)
confirms; Invite to community; Report message in the message menu.

Refs #504

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
# Conflicts:
#	crates/fluxer-ui/src/screens/main/dms/mod.rs
Refs #520

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
A right press on a member row, a message author's avatar or name, a
user mention or a DM row opens the user, member or DM menu that
fluxer_core::menus builds (spec 3.2 (e), (f)). Relationship rows ask
through the generic confirm; Shift sends them confirmed only where
social::confirm_rule lets it (block, unblock, remove, accept), never
for Close DM, Open DM or Leave group. "Change friend nickname" opens
its modal ("Change nickname", "Clear nickname", 32 characters). The
voice participant menu gains Mention and Message from the same builder
(#476).

Refs #520

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
member_menu, member_menu_moderator, dm_menu, group_dm_menu and
block_confirm; participant_menu and its entrance submenu redrawn with
Mention and Message first (#476).

Refs #520

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Author
Owner

Independent review: Daily use 31 (user, member and DM context menus)

I reviewed 6bd87ac..cd8c18e (this task's own changes), and also the 18/33 conflict resolution in the merge commit 6bd87ac.

Plan tests: author_right_press_carries_message_for_report, mention_right_press, shift_click_on_block_skips_confirm_but_not_on_close_dm and nickname_modal_validation all exist and assert what the plan describes. The 5 goldens exist: member_menu, member_menu_moderator, dm_menu, group_dm_menu and block_confirm. Each has a reference image in docs/screenshots/ and a README row.
Interfaces: These triggers open Task 18's menus at the cursor: member rows, author avatar and name (the message is passed so "Report message" can show), user mention pills and DM/group DM rows. Confirms go through the store confirm (Task 33). with_shift sets confirmed: true only when social::confirm_rule returns ConfirmShiftSkips, so Close DM, Open DM and Leave group still ask. The nickname modal has "Clear nickname" and the 32-char check. The participant menu now has Mention and Message / Open DM, built by the same builder (#476).
Invariants: No new I/O in fluxer-ui, no new dependencies, no fixtures, no secrets. Server data (unknown mention ids, a channel that is not cached) falls back to None and does not panic.

Parity spot-checks against the fork (all match):

  • MentionRenderer.tsx:143,173 passes only guildId (no channelId, no message), so a mention's menu has no Mention or Report row. Matches menus::user::mention.
  • BaseChangeNicknameModal.tsx: title "Change nickname", label "Nickname", the display name as placeholder, maxLength 32, data.nick.trim() || null, a Save-only footer. All match friend_nickname.rs.
  • VoiceParticipantMenuData.tsx:265-603: Mention appears only when the focused channel is text-based and allows SEND_MESSAGES; Message / Open DM appears when the user is not oneself. Both are the first group. This matches, because the native menu opens only from the participant list.
  • useDMListItemHandlers.tsx:132-150: the DM list's X leaves a group (through the leave confirm) and closes a 1:1 DM at once. Matches the merge resolution in dms/mod.rs.

Review Focus 5: Shift skips block, unblock, remove friend and accept in menus. It does not skip Close DM, Open DM (blocked user) or Leave group, and this is tested. The Close DM confirm shows no Shift tip.

Local gate: I ran FLUXER_SCREENSHOT_TESTS=1 cargo xtask ci in a fresh review worktree and every step passed. The 7 menus_user_dm tests passed, and all 5 new goldens plus the 2 regenerated participant_menu* goldens matched.

Findings

  1. minor (file ownership / merge coordination): The plan lists crates/fluxer-ui/src/screens/main/menus/mod.rs as a file Task 29 creates (#571, unmerged). 31 creates it too and does not depend on 29. The constraint says to stop and ask the orchestrator in this case. The API names match, but update() here takes an extra shift argument, and Target, State and Message are different. Whichever PR merges second has to combine both Target enums and both States, keep the shift parameter (29's call sites will need it), and keep 29's toast fields. The orchestrator should decide the merge order and tell the second PR.
  2. minor (parity, not built): After Save, the original waits for updateFriendNickname, shows the "Nickname updated" toast and then closes the modal. If the request fails, the modal stays open. Here the modal closes at once and shows no toast. The "Copied to clipboard" toast for Copy user ID / Copy channel ID is not built either. This is acknowledged in the PR notes; it needs a follow-up issue linked before merge.
  3. minor: A paragraph that contains right-to-left text is drawn without InlineFlow, so a user mention in it has no right-click menu (view_block's !is_rtl_paragraph guard). This is an acceptable limitation; it is worth a line in the follow-up.

Not this task's code, noted for reference: Task 18's core leaves out "Start voice call" when no DM exists with the user (grace's member_menu golden has no row for it). The original's StartVoiceCallMenuItem shows it whenever the user is not a bot and has no call in progress. If that divergence is not intended, it belongs in a Task 18 follow-up.

Verdict: APPROVED. There are no blocking findings and local CI is green. Merge coordination with #571 is needed (finding 1).

## Independent review: Daily use 31 (user, member and DM context menus) I reviewed `6bd87ac..cd8c18e` (this task's own changes), and also the 18/33 conflict resolution in the merge commit 6bd87ac. **Plan tests:** `author_right_press_carries_message_for_report`, `mention_right_press`, `shift_click_on_block_skips_confirm_but_not_on_close_dm` and `nickname_modal_validation` all exist and assert what the plan describes. The 5 goldens exist: `member_menu`, `member_menu_moderator`, `dm_menu`, `group_dm_menu` and `block_confirm`. Each has a reference image in `docs/screenshots/` and a README row. **Interfaces:** These triggers open Task 18's menus at the cursor: member rows, author avatar and name (the message is passed so "Report message" can show), user mention pills and DM/group DM rows. Confirms go through the store confirm (Task 33). `with_shift` sets `confirmed: true` only when `social::confirm_rule` returns `ConfirmShiftSkips`, so Close DM, Open DM and Leave group still ask. The nickname modal has "Clear nickname" and the 32-char check. The participant menu now has Mention and Message / Open DM, built by the same builder (#476). **Invariants:** No new I/O in fluxer-ui, no new dependencies, no fixtures, no secrets. Server data (unknown mention ids, a channel that is not cached) falls back to `None` and does not panic. **Parity spot-checks against the fork (all match):** - `MentionRenderer.tsx:143,173` passes only `guildId` (no `channelId`, no message), so a mention's menu has no Mention or Report row. Matches `menus::user::mention`. - `BaseChangeNicknameModal.tsx`: title "Change nickname", label "Nickname", the display name as placeholder, `maxLength 32`, `data.nick.trim() || null`, a Save-only footer. All match `friend_nickname.rs`. - `VoiceParticipantMenuData.tsx:265-603`: Mention appears only when the focused channel is text-based and allows SEND_MESSAGES; Message / Open DM appears when the user is not oneself. Both are the first group. This matches, because the native menu opens only from the participant list. - `useDMListItemHandlers.tsx:132-150`: the DM list's X leaves a group (through the leave confirm) and closes a 1:1 DM at once. Matches the merge resolution in `dms/mod.rs`. **Review Focus 5:** Shift skips block, unblock, remove friend and accept in menus. It does not skip Close DM, Open DM (blocked user) or Leave group, and this is tested. The Close DM confirm shows no Shift tip. **Local gate:** I ran `FLUXER_SCREENSHOT_TESTS=1 cargo xtask ci` in a fresh review worktree and every step passed. The 7 `menus_user_dm` tests passed, and all 5 new goldens plus the 2 regenerated `participant_menu*` goldens matched. ### Findings 1. **minor (file ownership / merge coordination):** The plan lists `crates/fluxer-ui/src/screens/main/menus/mod.rs` as a file Task 29 creates (#571, unmerged). 31 creates it too and does not depend on 29. The constraint says to stop and ask the orchestrator in this case. The API names match, but `update()` here takes an extra `shift` argument, and `Target`, `State` and `Message` are different. Whichever PR merges second has to combine both `Target` enums and both `State`s, keep the `shift` parameter (29's call sites will need it), and keep 29's toast fields. The orchestrator should decide the merge order and tell the second PR. 2. **minor (parity, not built):** After Save, the original waits for `updateFriendNickname`, shows the "Nickname updated" toast and then closes the modal. If the request fails, the modal stays open. Here the modal closes at once and shows no toast. The "Copied to clipboard" toast for Copy user ID / Copy channel ID is not built either. This is acknowledged in the PR notes; it needs a `follow-up` issue linked before merge. 3. **minor:** A paragraph that contains right-to-left text is drawn without `InlineFlow`, so a user mention in it has no right-click menu (`view_block`'s `!is_rtl_paragraph` guard). This is an acceptable limitation; it is worth a line in the follow-up. Not this task's code, noted for reference: Task 18's core leaves out "Start voice call" when no DM exists with the user (grace's `member_menu` golden has no row for it). The original's `StartVoiceCallMenuItem` shows it whenever the user is not a bot and has no call in progress. If that divergence is not intended, it belongs in a Task 18 follow-up. **Verdict: APPROVED.** There are no blocking findings and local CI is green. Merge coordination with #571 is needed (finding 1).
Author
Owner

Merged into dailyuse at f7972c3 (combined merge of 23 Daily use tasks plus textchat).

Merged into `dailyuse` at f7972c3 (combined merge of 23 Daily use tasks plus `textchat`).
charles closed this pull request 2026-11-15 06:08:28 +00:00

Pull request closed

Sign in to join this conversation.
No description provided.