Files

T

CI / Build & Quality Checks (push) Failing after 5m43s

Details

docs: add blocked features section, upstream improvements, TDS design law

- Blocked section: MSC3892 (reaction redaction), MSC3266 (room preview),
  MSC4306 (thread subscriptions), MSC4260 (report user) — all noted with
  unblock conditions and next steps
- 5 new [IMPROVE] tasks for upstream features: Jump to Latest (#104),
  spoiler transition (#105), report category (#106), speaking ring (#107),
  typing dots TDS (#108)
- TDS design law banner added at top of file and repeated in Implementation Notes
- Pinned messages count badge confirmed upstream (no action needed)
- Audits 1, 2, 4 marked complete; audit 3 (profile banner) remains open
- Upstream features table updated with improvement task cross-references

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

2026-06-01 13:21:39 -04:00

66 KiB

Raw Blame History

Lotus Chat — Master Feature TODO

Location: /root/code/cinny/LOTUS_TODO.md
Repo: lotus branch at https://code.lotusguild.org/LotusGuild/cinny
Deploy: push to lotus → CI → auto-deploy to chat.lotusguild.org (~11 min)

This file is the single source of truth for all planned, in-progress, and backlog features. Update it as features are completed or reprioritized.

⚠️ TDS DESIGN LAW — READ BEFORE TOUCHING ANY UI

ALL Lotus Terminal Design System (TDS) styling — colors, animations, glows, borders, fonts, spacing — MUST come exclusively from /root/code/web_template/base.css CSS variables. Do NOT hardcode hex values. Do NOT invent new variable names. Do NOT deviate from the design tokens defined in that file. The canonical variable reference: --lt-accent-orange, --lt-accent-cyan, --lt-accent-green, --lt-glow-orange, --lt-box-glow-*, --lt-border-color, etc. Reference implementation for code patterns: /root/code/tinker_tickets/ (markdown.js, base.js, ticket.css) This rule applies to EVERY task in this file without exception.

Legend:

[AUDIT REQUIRED] — at least one assumption needs code/server verification before implementing
[SERVER CHECK] — depends on a Synapse feature or MSC; verify on matrix.lotusguild.org
[LOW PRIORITY] — implement after all higher-priority items
[EXTREME COMPLEXITY] — multi-sprint, plan separately before touching
[BLOCKED] — cannot build until a server upgrade, upstream MSC, or dependency resolves
[IMPROVE] — feature exists in upstream Cinny; this task enhances it for Lotus Chat

Status: [ ] pending · [~] in progress · [x] completed

AUDIT RESULTS — completed June 2026

Server Status

Synapse version: 1.153.0 (released 2026-05-19) — FULLY UP TO DATE, no upgrade needed
Matrix spec reported: up to v1.12 formally, but newer MSC features available via unstable_features
MSC feature flags confirmed ON: msc4140 (delayed messages) · msc3771 (thread receipts) · msc3440.stable (threading) · msc4133.stable (extended profiles) · simplified_msc3575 (sliding sync)
MSC feature flags confirmed OFF: msc4306 (thread subscriptions — BLOCKED) · msc3882 · msc3912 · msc4155
MSC3266 (room summary, v1.15): endpoint returned 404 — NOT available on this server
MSC3765 (rich room topics, v1.15): NOT available as stable, but client-side rendering is still worth doing
MSC3892 (relation redaction): not listed in flags — NOT supported, feature BLOCKED
MSC4260 (report user, v1.14): server at v1.12 formally — NOT available as spec endpoint; however report user already exists upstream in Cinny (message reporting via reportEvent)
MSC4151 (report room, v1.12): merged at exactly v1.12 — should be available ✅

Upstream Cinny Features Confirmed (exist in upstream — only improve, don't re-implement)

Feature	Location in upstream	Lotus improvement task
"Jump to Latest" button	`RoomTimeline.tsx:2180-2192`	#104 — add unread count + animation
Mark rooms as read (per section)	`Home.tsx:73-102`, `DirectTab.tsx:29-61`	None needed
Room upgrade / tombstone banner	`RoomTombstone.tsx`, `RoomUpgrade.tsx`	None needed
Visual speaking indicator	`useCallSpeakers.ts:8-60`, `MemberSpeaking.tsx:1-78`	#107 — TDS animated ring
Image + video spoilers (blur/reveal)	`ImageContent.tsx`, `VideoContent.tsx`	#105 — smooth CSS transition
Report message per event	`Message.tsx:588-709` — `mx.reportEvent()`	#106 — add category selector
Drag-and-drop file upload	`useFileDrop.ts` — works but overlay bug	#73 — fix overlay dismiss
Typing indicator (animated dots)	`TypingIndicator.tsx`, `TypingIndicator.css.ts`	#108 — TDS orange dots
Pinned messages count badge	Confirmed in upstream header icon	None needed

Upstream Cinny Features Confirmed MISSING (we should build these)

Quick Switcher, Sidebar filter, Favorite rooms, Invite link generator, Edit history modal,
Export history, Room preview before joining, Suggested rooms display, Server notices styling,
DM last-message preview, Media gallery, Knock-to-join full UX

Code Architecture Facts (relevant to implementation)

Finding	Impact
`folds AvatarImage` does NOT accept children	Avatar overlays/frames must wrap the Avatar component externally, not nest inside it
Sidebar `SidebarItem` has `translateX` on hover	CSS `backdrop-filter` won't work on sidebar items directly — apply to parent wrapper instead
Element Call bridge has NO join/leave participant events	Join/leave sounds (#89) must use `m.call.member` Matrix room state events instead
Element Call bridge has NO audio level events	Speaking indicator uses CSS polling of EC iframe DOM — no direct event bridge
No in-app toast system exists anywhere	Toast redesign (#80) must build a full `ToastProvider` + queue system from scratch
Voice message player: `AudioContent.tsx:44-223`	Speed control (#8): add `playbackRate` on the hidden `<audio>` element at line 217
Notification sounds: 2 hardcoded `.ogg` files	Custom sounds (#22): replace file path with settingsAtom value
Chat backgrounds: `chatBackground.ts`, applied to `<Page>` in `RoomView.tsx`	Animated wallpapers (#77): add new entries returning CSS animation keyframe strings
Push rule UI: mode switcher only, no custom rule creation	Full push rule editor (#61) is a significant build from scratch
URL preview: `urlPreview: true` default, `encUrlPreview: false` default	Task #49: only need to change `encUrlPreview` default to `true` + add warning text
Private read receipts: `ReceiptType.ReadPrivate` already in SDK	Task #34: very simple — `markAsRead()` in `notifications.ts` already has `privateReceipt` param
Right-click room menu: 6 items (Mark read, Notifications, Invite, Copy Link, Settings, Leave)	Task #102: add Mute-with-duration submenu and consolidate
Glassmorphism: sidebar uses `translateX` transform	Must apply `backdrop-filter` to a parent div, not the sidebar element itself
JetBrains Mono: NOT bundled, relies on system fonts	Font selector (#98): must bundle fonts as `public/font/*.woff2` files
GIF links (Giphy/Tenor): render as generic OG preview cards, NOT auto-embedded	Task #42: inline GIF embed needs to be built
Composer toolbar buttons (in order): Formatting, Emoji/Sticker, GIF, Location, Voice, Send	Task #43: configurable toolbar is straightforward — buttons are a sequential array
Message hover toolbar: quick reactions row already exists inside Menu component	Task #92: quick reaction bar is already partially there via `MessageQuickReactions`

COMPLETED

Audit & document: who reacted hover tooltip — README + landing page
Audit & document: sticker/emoji panel — README + landing page
Audit & document: custom status messages — added to README Presence section
Audit & document: pinned messages — confirmed upstream, not added to README

PRIORITY 0 — Quick wins: low complexity, high daily value

These are the easiest items to ship and immediately improve the daily experience. Attack these first; most are single-file changes or simple new components.

[ ] P0-1 · Report Room (MSC4151)

Spec: MSC4151, merged ~Matrix spec v1.12. Synapse supports it.
Confirmed: NOT present in upstream Cinny mainline.
What: Add a "Report Room" option in the room header context menu (⋮ or room settings). Opens a modal with a reason text field (required) and a Submit button. Calls:

POST /_matrix/client/v3/rooms/{roomId}/report
Body: { "reason": "string" }

The homeserver forwards the report to server admins.
Where: src/app/features/room/RoomViewHeader.tsx (add menu item), new ReportRoomModal.tsx component.
Complexity: Low — one API call, one modal.

[ ] P0-2 · Server support contact display (MSC1929)

Spec: MSC1929, stable in Matrix spec.
What: On load (or when Settings → Help & About is opened), fetch:

GET /.well-known/matrix/support

Parse the contacts array and support_page URL. Display in Settings → Help & About:

"Homeserver admin: @jared:matrix.lotusguild.org"
Link to support page if present Cache the response in component state; no repeated fetches.
Where: src/app/features/settings/ Help/About panel.
Complexity: Low — one fetch, display result.

[ ] P0-3 · Server notices distinct rendering (m.server_notice)

Spec: CS-API §13.17, stable.
Audit result: CONFIRMED MISSING. Only M_CANNOT_LEAVE_SERVER_NOTICE_ROOM error code exists in src/app/cs-errorcode.ts — no rendering differentiation. Server notices currently arrive as plain DMs.
What: The m.server_notice room type is set in m.room.create content (type: 'm.server_notice'). Detect it via room.getType() === 'm.server_notice'. Render with:

A distinct "Server Notice" header badge (server icon + label) in RoomViewHeader.tsx
Slightly different background color (use color.Warning or neutral surface)
Composer hidden/disabled in server notice rooms (check room type in RoomInput.tsx)
Where: src/app/features/room/RoomViewHeader.tsx (badge), src/app/features/room/RoomInput.tsx (hide composer when room.getType() === 'm.server_notice').
Complexity: Low.

[BLOCKED] P0-4 · Reaction / relation redaction (MSC3892)

Spec: MSC3892, in Final Comment Period.
Server check result: org.matrix.msc3892 is NOT in the server's unstable_features list — NOT supported. Current full-event redaction behavior is correct and should not be changed. This task is BLOCKED until the homeserver adds MSC3892 support. No action needed now.
Complexity: N/A — blocked.

[ ] P0-5 · Rich room topic rendering (MSC3765)

Spec: MSC3765, merged Matrix spec v1.15.
What: Room topics can now include formatted text via the m.topic content block (bold, links, italic). Currently topics render as plain text in the room header. Pipe the formatted_body of the m.room.topic state event through the existing HTML/Markdown renderer (same renderer used for message bodies).
[AUDIT REQUIRED] — Check if matrix.lotusguild.org Synapse version supports sending m.topic content blocks. Also check if existing room topics on the server have formatted_body set. The rendering improvement is worthwhile even if new formatted topics aren't being set yet.
Where: Wherever the room topic is displayed in src/app/features/room/RoomViewHeader.tsx or similar.
Complexity: Low — reuse existing HTML renderer.

[ ] P0-6 · Edit history viewer

Spec: CS-API §11.8.2 (stable). Edit history is stored as m.replace relation events.
What: When a message shows the "edited" label, clicking it opens a popover or small modal listing every prior version of the message with timestamps:

Original:  "Hello world"        — 3:41 PM
Edit 1:    "Hello world!"       — 3:42 PM  
Edit 2:    "Hello everyone!"    — 3:45 PM  (current)

Fetch edit history via:

GET /_matrix/client/v1/rooms/{roomId}/relations/{eventId}/m.replace

[AUDIT REQUIRED] — Confirm upstream Cinny does NOT already show edit history on click. If it does, this is upstream and should not be added to our README.
Where: src/app/features/room/message/Message.tsx — find where "edited" label renders and add click handler.
Complexity: Low — one API call, display list.

[ ] P0-7 · Room preview before joining (MSC3266)

Spec: MSC3266, merged Matrix spec v1.15. Synapse supports it.
What: When a user follows a matrix.to link or is invited to a room they haven't joined, show a preview card:

Room avatar, name, topic, member count, join rule
"Join Room" / "Request to Join" (if knock) / "Accept Invite" button
"Back" option without joining Uses: GET /_matrix/client/v1/rooms/{roomId}/summary
[AUDIT REQUIRED] — Check if upstream Cinny already has a room preview screen before joining. Many Matrix clients have this. If Cinny has it, this is upstream and only Lotus-specific styling/improvements are needed.
[SERVER CHECK] — Verify matrix.lotusguild.org Synapse version supports the /summary endpoint.
Where: Likely in the routing/navigation layer when a room is selected but not joined.
Complexity: Low-medium.

[ ] P0-8 · Personal room name overrides (MSC4431)

Spec: MSC4431, in review.
What: Let a user rename a room locally — visible only to them. Stored in Matrix account data:

PUT /_matrix/client/v3/user/{userId}/account_data/m.room_names
Body: { "rooms": { "!roomId:server": "My Custom Name" } }

Access via right-click on room in sidebar → "Rename for me…". Show a small edit icon next to locally-renamed rooms. The original room name remains unchanged for all other members.
[SERVER CHECK] — MSC4431 is still in review; it uses account data which is universally supported even if the MSC isn't finalized. The account data key name may change when merged.
Where: Room nav item context menu, sidebar room list rendering.
Complexity: Low.

[ ] P0-9 · "Back to Latest" button

What: A floating pill button that appears at the bottom of the room timeline when the user has scrolled up (away from the live timeline). Displays "↓ Jump to latest" (and shows unread count if applicable, e.g. "↓ 12 new messages"). Clicking scrolls to the live timeline bottom and hides the pill.
[AUDIT REQUIRED] — Confirm this does NOT already exist in upstream Cinny. Check RoomTimeline.tsx for any existing "scroll to bottom" UI — there is already a "Jump to Unread" chip (confirmed in code exploration); verify this is distinct.
Where: src/app/features/room/RoomTimeline.tsx — add a TimelineFloat element at the bottom, shown conditionally based on scroll position.
Complexity: Low.

[ ] P0-10 · Mark all rooms as read

What: A single action that sends read receipts for all rooms with unread counts, clearing every unread badge at once. Accessible via:

Right-click on the "Home" icon in the sidebar → "Mark all as read"
Or a button in the Home view header
Iterates all rooms with room.getUnreadNotificationCount() > 0 and calls mx.sendReadReceipt(room.getLastActiveTimestamp()) for each.
[AUDIT REQUIRED] — Confirm upstream Cinny does NOT already have this. Check sidebar context menus and Home view for any existing "mark all read" action.
Where: src/app/pages/client/sidebar/HomeTab.tsx context menu or src/app/pages/client/home/Home.tsx header.
Complexity: Low.

[ ] P0-11 · Spoiler text audit and fix if broken

What: The message composer toolbar has a spoiler mark (||spoiler text||). Verify the end-to-end flow:

Composer correctly wraps text in <span data-mx-spoiler> in formatted_body
Timeline renderer displays spoiler as blurred/hidden text with a "Reveal" click
Mobile touch works for reveal
If any step is broken, fix it. If all working correctly, close this task with no changes.
[AUDIT REQUIRED] — Full code audit of spoiler mark in toolbar → event content → timeline renderer.
Complexity: Low (audit) — fix complexity TBD.

[ ] P0-12 · URL Preview default settings + security warning

Audit result: settings.ts line 103: urlPreview: true (already on by default) · line 104: encUrlPreview: false (encrypted rooms OFF by default).
What: Change encUrlPreview default to true in src/app/state/settings.ts. Add a one-sentence security note next to the encrypted-room toggle in the settings UI:

"URL previews in encrypted rooms are fetched by your homeserver, which sees the URL but not the message content."
Where: src/app/state/settings.ts line 104 (change default), settings UI file for URL preview toggles (find via grep for encUrlPreview).
Complexity: Very Low — one default value change + one sentence of UI text.

PRIORITY 1 — High value, moderate effort

Core features that meaningfully expand what users can do every day.

[ ] P1-1 · Quick Room Switcher (Ctrl+K / Cmd+K)

What: Global keyboard shortcut opens a floating search modal above all content. Features:

Fuzzy-search across ALL rooms and DMs by display name in real time
Keyboard navigable: ↑/↓ to move, Enter to open room, Esc to close
Shows unread badge count inline next to each result
Pressing Ctrl+K again while open closes it
Recent rooms shown immediately before typing
Architecture:
New component: src/app/components/QuickSwitcher.tsx
Register global hotkey via useEffect + window.addEventListener('keydown') in src/app/pages/client/ClientRoot.tsx
Use the existing OverlayContainerProvider portal (from App.tsx) so the modal floats above everything
Room data: allRoomsAtom + mDirectAtom from src/app/state/roomList.ts
Style with folds Menu, Box, Input components matching existing patterns
Use is-hotkey library (already in the project) for the keybind
[AUDIT REQUIRED] — Confirm upstream Cinny does NOT already have a quick switcher. Check for any existing Ctrl+K handler in ClientRoot.tsx or App.tsx.
Complexity: Medium.

[ ] P1-2 · Media Gallery

What: A scrollable grid of all shared images, videos, and files in a room. Accessible via a new icon in the room header (picture/grid icon). Features:

Tab bar: Images | Videos | Files
Infinite scroll / paginated load via GET /rooms/{roomId}/messages filtering for m.image, m.video, m.file msgtypes
Click image → full-screen lightbox (upstream Cinny lightbox)
Click file → download
Shows sender + timestamp tooltip on hover
TDS-aware grid styling
Architecture:
New component: src/app/features/room/media-gallery/MediaGallery.tsx
Renders as a right-side drawer (similar to the members drawer pattern)
Add icon button to src/app/features/room/RoomViewHeader.tsx
Paginate backwards from latest event using /messages?dir=b
[AUDIT REQUIRED] — Confirm upstream Cinny has no existing media gallery or file browser. Check room header icons and room settings panels.
Complexity: Medium.

[ ] P1-3 · Sidebar Room Filter / Search

What: A text input at the top of each room list tab (Home, DMs, Spaces) that filters visible rooms in real time by display name. Ephemeral — clears when you switch tabs. No server calls — pure client-side filter over the loaded room list.
Architecture:

Add filter useState<string>('') to each tab component
Filter the room array before rendering: rooms.filter(id => displayName(id).toLowerCase().includes(filter))
Show a small × clear button when filter is non-empty
TDS: mono font, dim border input matching the design system
Where: src/app/pages/client/home/Home.tsx (Home tab), DMs equivalent, Space room list.
[AUDIT REQUIRED] — Confirm upstream Cinny does NOT already have a filter input in room lists.
Complexity: Low-Medium.

[ ] P1-4 · Enhanced DM List (last message preview + timestamp)

What: Show the last message text and relative timestamp ("2 min ago", "Yesterday") next to each DM in the sidebar, like iMessage or WhatsApp. Currently only the room name and unread badge are shown.
Architecture:

For each DM room: get room.getLastActiveTimestamp() and room.timeline[room.timeline.length - 1] for the last event
Render the event body (truncated to ~60 chars), stripping any HTML
Format timestamp: "just now" / "X min ago" / "Yesterday" / date
Falls back gracefully if the room has no messages yet
[AUDIT REQUIRED] — Check if upstream Cinny already shows message previews in DM list. Check src/app/pages/client/direct-messages/ or DirectTab.tsx for existing DM list item rendering.
Complexity: Medium — need to extract last event body safely across encrypted/non-encrypted rooms.

[ ] P1-5 · Voice Message Playback Speed Control

What: Add a speed toggle to the voice message audio player in the room timeline: 0.75× → 1× → 1.5× → 2×. Clicking the current speed label cycles to the next. Uses the HTML <audio> element's playbackRate property.
Architecture:

const [speed, setSpeed] = useState(1)
On click: audioRef.current.playbackRate = nextSpeed
Render a small clickable pill: 1× etc., next to the audio controls
Persist speed preference in settingsAtom so it carries across messages
[AUDIT REQUIRED] — Locate exactly where voice messages render in the timeline. Search for m.audio / MSC3245 / VoiceMessage in src/app/features/room/. The recorder is in VoiceMessageRecorder.tsx but the player for received voice messages is elsewhere.
Complexity: Low-Medium.

[ ] P1-6 · Poll Creation

What: Users can create polls from the message composer. Features:

"Create Poll" toolbar button (poll icon) in RoomInput.tsx
Modal: question field (required) + 2–10 answer options (add/remove dynamically) + single vs. multiple choice toggle
Sends m.poll.start event (Matrix 1.7 stable format — same JSON we already render):

{
  "type": "m.poll.start",
  "content": {
    "m.poll": {
      "question": { "m.text": "..." },
      "answers": [{ "m.id": "uuid", "m.text": "Option 1" }, ...],
      "max_selections": 1
    }
  }
}

mx.sendEvent(roomId, 'm.poll.start', content)
Architecture:
New component: src/app/features/room/PollCreator.tsx
Wire toolbar button into src/app/features/room/RoomInput.tsx (follow GIF picker pattern)
Complexity: Medium.

[ ] P1-7 · Code Syntax Highlighting in Messages

What: Color-code fenced code blocks in rendered messages. Language auto-detected from the code fence hint (```python, ```js, etc.).
⚠️ MUST match /root/code/web_template/base.css exactly. The web_template defines the canonical token structure for all Lotus apps:

.lt-code-block — container: bg-secondary, border-dim border
.lt-code-header — header bar with language label + copy button
- .lt-code-lang — mono font, accent-orange, uppercase, 0.1em letter-spacing
- .lt-code-copy — dim border/color; hover → cyan; .copied state → green
.lt-code-block pre — mono font, 0.8rem, 1.6 line-height, max-height 400px, scrollable
Syntax token classes (custom tokenizer, NOT highlight.js/Prism):
- .tok-kw → var(--accent-cyan) (keywords)
- .tok-str → var(--accent-green) (strings)
- .tok-num → var(--accent-orange) (numbers)
- .tok-cmt → var(--color-tok-cmt) italic (comments)
- .tok-fn → var(--accent-purple) (function names) See /root/code/tinker_tickets/assets/js/markdown.js for the reference tokenizer implementation.
  [AUDIT REQUIRED] — Check the TDS CSS variables (--accent-cyan, --accent-green, etc.) are available in Cinny's lotus-terminal.css.ts vanilla-extract theme. Map var(--accent-*) to the correct folds/vanilla-extract tokens. Also verify the tokenizer approach from tinker_tickets is language-agnostic enough for chat (it may need extension for more languages).
  Where: Code block renderer in src/app/components/message/ or wherever <pre><code> is rendered.
  Complexity: Medium.

[ ] P1-8 · Favorite / Starred Rooms

What: Star any room from its context menu. Starred rooms appear in a dedicated "Favorites" section at the top of the sidebar room list. Uses Matrix's built-in m.favourite room tag (account data), so favorites sync across devices and clients automatically.

PUT /_matrix/client/v3/user/{userId}/rooms/{roomId}/tags/m.favourite
Body: { "order": 0.5 }

Right-click room → "Add to Favorites" / "Remove from Favorites"
Favorites section appears above the regular room list in the Home tab
Star icon shown on favorited rooms in the list
[AUDIT REQUIRED] — Confirm upstream Cinny does NOT already render m.favourite tagged rooms in a special section. Check src/app/pages/client/home/ for any tag-based room grouping. Some versions of Cinny may already do this.
Complexity: Medium.

[ ] P1-9 · Invite Link Generator (with QR code)

What: In room settings (or via right-click on room), a "Copy Invite Link" button that:

Generates a matrix.to URL: https://matrix.to/#/!roomId:server?via=matrix.lotusguild.org
Copies it to clipboard via navigator.clipboard.writeText()
Shows a QR code of the link (use a lightweight QR library e.g. qrcode npm package)
"Share" button that opens the native Web Share API if supported
[AUDIT REQUIRED] — Check if upstream Cinny already has a "copy invite link" button in room settings. Also check if the room settings panel already shows the room address/alias.
Where: Room settings panel src/app/features/room-settings/ or room header context menu.
Complexity: Low-Medium.

[ ] P1-10 · Private Read Receipts toggle

Spec: CS-API stable — m.read.private vs m.read.
What: Add a toggle in Settings → Privacy: "Send private read receipts" — when enabled, read receipts are sent as m.read.private (only you and the server see them) instead of m.read (everyone in the room sees when you read). Default: public (current behavior, unchanged).
Architecture:

New settingsAtom field: privateReadReceipts: boolean (default false)
When sending a read receipt, check the setting and use the appropriate type
Find mx.sendReadReceipt(...) call sites and add the receiptType parameter
[AUDIT REQUIRED] — Verify the matrix-js-sdk version in use supports the receiptType parameter on sendReadReceipt. Check the SDK's type definitions for this method.
Complexity: Low.

[ ] P1-11 · Knock-to-join UX (Room version 7)

Spec: Room version 7 (stable Matrix spec). Join rule: knock.
What: Full knock UX for both sides:

Knocking: When a room's join rule is knock, show a "Request to Join" button instead of "Join Room". Sends POST /join which triggers a knock state event. Show pending state ("Request sent") while waiting.
Approving knocks: Room admins/mods see a notification of pending knocks. In the members drawer or room settings, show a "Pending Requests" section listing knockers with "Approve" (/invite) and "Deny" (/kick) buttons.
[SERVER CHECK] — Verify matrix.lotusguild.org Synapse supports room version 7 and the knock join rule.
[AUDIT REQUIRED] — Check if upstream Cinny handles the knock join rule at all. If it does, only the approvals UI on the admin side may be missing.
Complexity: Medium.

PRIORITY 2 — Good value, medium effort or lower daily frequency

[ ] P2-1 · Jump to Date

What: A calendar date picker accessible from the room header (small calendar icon). Selecting a date navigates the timeline to the first message on or after that date.
API: GET /_matrix/client/v1/rooms/{roomId}/timestamp_to_event?ts={epochMs}&dir=f
Returns { event_id, origin_server_ts }. Then scroll the timeline to that event ID using the existing scrollToEventId / virtual paginator logic.
[SERVER CHECK] — Verify matrix.lotusguild.org Synapse supports the /timestamp_to_event endpoint (added in Synapse 1.73 / Matrix spec v1.6).
[AUDIT REQUIRED] — Understand how RoomTimeline.tsx handles navigating to an arbitrary event ID that may not be in the current timeline window. The virtual paginator may need to fetch backwards to that event.
Where: src/app/features/room/RoomViewHeader.tsx (button), new JumpToDate.tsx component.
Complexity: Medium.

[ ] P2-2 · Custom Notification Sounds

What: Let users pick from a set of built-in notification sounds for mentions, messages, and DMs. Features:

Settings → Notifications: sound selector per category (Mention / Message / DM)
Each option has a preview "▶ Play" button
"None" option to disable sound for that category
4–6 built-in sounds shipped as audio files in public/sounds/
Stored in settingsAtom
Architecture:
Add notificationSounds: { mention: string, message: string, dm: string } to settingsAtom
In ClientNonUIFeatures.tsx (where notification sounds are currently played), swap out the hardcoded sound URL for the settings value
[AUDIT REQUIRED] — Find exactly where notification sounds play in the codebase. Search for new Audio( or .play() in src/app/. Confirm how many distinct notification categories currently exist.
Complexity: Medium.

[ ] P2-3 · Sort Non-Space Rooms on Home Page

What: A sort control on the Home tab for orphan rooms (rooms not in any space). Options:

Unread first — rooms with unread messages appear at top
Recent activity — sort by room.getLastActiveTimestamp()
Alphabetical — sort by display name A→Z Persisted in settingsAtom as homeRoomSortOrder: 'unread' | 'recent' | 'alpha'. Default: 'recent'.
Note: Space rooms are reordered by space admins via the Space Lobby — this only affects non-space orphan rooms on the Home tab.
[AUDIT REQUIRED] — Find where orphan rooms are listed on the Home tab. Confirm which hook/atom provides the room list (useOrphanRooms() in roomList.ts). Verify the sort is applied purely client-side with no server calls needed.
Complexity: Medium.

[ ] P2-4 · Export Room History

What: Export a room's messages to plain text, JSON, or HTML. Accessible from room settings (gear icon → "Export Room History"). Features:

Format selector: Plain Text / JSON / HTML
Date range filter (optional: all time or custom range)
Only exports messages where E2EE decryption keys are available locally
Shows progress bar for large rooms (batched /messages calls)
Downloads as a file via URL.createObjectURL(blob) + <a download>
Note: Element already has this feature — mention in the landing page comparison table once implemented.
Landing page update: Add "Export room history" row to /root/code/matrix/landing/index.html comparison table.
[AUDIT REQUIRED] — Confirm upstream Cinny does NOT have an export feature. Check room settings panels.
Complexity: Medium.

[ ] P2-5 · Notification Quiet Hours

What: Set a daily time window when browser notifications are suppressed (e.g., 11:00 PM – 8:00 AM). Toggle + start/end time pickers in Settings → Notifications.
Architecture:

New settingsAtom field: quietHours: { enabled: boolean, start: string, end: string } (times as "HH:MM" 24h strings)
In ClientNonUIFeatures.tsx or SystemNotification.tsx, before dispatching a browser Notification, check:

function isQuietHours(settings): boolean {
  if (!settings.quietHours.enabled) return false;
  const now = new Date();
  const [sh, sm] = settings.quietHours.start.split(':').map(Number);
  const [eh, em] = settings.quietHours.end.split(':').map(Number);
  // handle overnight ranges (e.g. 23:00 – 07:00)
  ...
}

Client-side only — does not touch Synapse push rules
[AUDIT REQUIRED] — Find the exact location in the codebase where browser Notification objects are created. Confirm no other code paths trigger sounds/notifications that also need to be suppressed.
Complexity: Medium.

[ ] P2-6 · Room Activity / Moderation Log

What: A filterable log of room state changes, accessible from room settings. Shows:

Member joins, leaves, kicks, bans, unbans
Power level changes ("@alice promoted to Moderator by @bob")
Room name / topic / avatar changes
Server ACL changes Filter controls: event type, date range, user. Sorted newest-first.
Fetches via /rooms/{roomId}/messages?filter={"types":["m.room.member","m.room.power_levels",...]} paginated backwards.
[AUDIT REQUIRED] — Check if upstream Cinny already has a room audit log. Also check if Synapse's admin API provides a richer audit log that could be used instead (admin only).
Complexity: Medium.

[ ] P2-7 · Richer Link Preview Cards

What: Expand URL preview cards beyond generic title/description/image:

YouTube: Show video thumbnail with a ▶ play overlay, channel name, duration
GitHub: Show repo name, description, star count, language badge, last updated
Twitter/X: Show avatar, handle, tweet text, likes/retweets (if metadata available)
Generic improvement: Better fallback when OG tags are missing
Architecture:
URL preview data comes from GET /_matrix/media/v3/preview_url?url=... (or the client-side oEmbed if homeserver doesn't provide enough data)
Detect URL domain/pattern and render a domain-specific card component
[AUDIT REQUIRED] — Check what data /_matrix/media/v3/preview_url returns for YouTube/GitHub links on matrix.lotusguild.org. The homeserver proxies this call — the richness depends on what metadata the target site exposes and what Synapse extracts. Test with real URLs before building domain-specific card logic.
Complexity: Medium.

[ ] P2-8 · Extended Profile Fields (MSC4133 + MSC4175)

Spec: MSC4133 + MSC4175, merged Matrix spec v1.16.
What: Support arbitrary profile fields. Specifically:

m.tz — IANA timezone string (e.g. "America/New_York")
m.pronouns — user's pronouns (e.g. "they/them")
Custom fields: job title, website
Display: Show set fields in the user profile panel/card.
Set: In Settings → Account → Profile, add input fields for each.
API: PUT /_matrix/client/v3/profile/{userId}/{field_name} / GET /_matrix/client/v3/profile/{userId}
[SERVER CHECK] — Verify matrix.lotusguild.org Synapse version supports MSC4133. This was merged in spec v1.16 (late 2025). May require a Synapse update if the server is running an older version.
[AUDIT REQUIRED] — Check if the matrix-js-sdk version in use exposes methods for getting/setting arbitrary profile fields beyond displayname and avatar_url. If not, use mx.http.authedRequest() directly.
Complexity: Medium.

[ ] P2-9 · Show User Local Time in Profile (MSC4175)

Depends on: P2-8 (Extended Profile Fields) — needs m.tz to be fetchable.
What: In user profile cards and the member list sidebar, when a user has m.tz set, display their current local time:

"Local time: 3:42 PM (UTC-5)"
Updates every minute via setInterval
Shows a small clock icon before the time
[AUDIT REQUIRED] — Depends on #P2-8 being implemented first. The m.tz field must be readable from the profile API.
Complexity: Low (once P2-8 is done).

[ ] P2-10 · Unverified Device Warning on Send (off by default)

What: Show a subtle warning in the composer area when a message will be sent to a room containing unverified devices. Features:

Off by default — toggled in Settings → Security ("Warn before sending to unverified devices")
When enabled: a small shield icon + "X unverified devices in this room" warning appears above the send button
User can click to see which devices, or dismiss and send anyway
Architecture:
Add warnOnUnverifiedDevices: boolean (default false) to settingsAtom
When setting is on, before rendering the composer, check room members' device trust via mx.getCrypto()?.getUserDeviceInfo() or equivalent
Do NOT block sending — just warn
[AUDIT REQUIRED] — Verify what the matrix-js-sdk (version in use) exposes for checking device verification status per room. The Crypto API varies significantly between SDK versions. This is the riskiest part of this feature.
Complexity: Medium.

[ ] P2-11 · Full Push Rule Editor

Spec: CS-API §13.13 (stable).
What: A dedicated page in Settings → Notifications showing the full push rule tree:

Override rules (highest priority)
Content rules (keyword matching)
Room rules (per-room overrides)
Sender rules (per-user overrides)
Underride rules (lowest priority) User can: create custom keyword rules, enable/disable any rule, set highlight/notify/silent action, delete custom rules.
API: GET /_matrix/client/v3/pushrules/ / PUT / DELETE per rule.
[AUDIT REQUIRED] — Audit the existing notification settings UI in src/app/features/settings/. Confirm exactly which push rules are already exposed and which are missing. The per-room and global mute controls likely use push rules under the hood.
Complexity: Medium-High.

[ ] P2-12 · Server ACL Viewer/Editor (m.room.server_acl)

Spec: CS-API §13.8 (stable), m.room.server_acl state event.
What: In room settings (visible to admins/mods with sufficient power level), show the current server ACL:

List of allowed servers (wildcard patterns supported: *.example.com)
List of denied servers
Toggle: "Allow IP literal addresses" (default: false)
Add/remove server entries
Save sends mx.sendStateEvent(roomId, 'm.room.server_acl', content)
[AUDIT REQUIRED] — Confirm the required power level to change m.room.server_acl (typically 50 or 100). The UI should only render for users with sufficient power. Check if upstream Cinny exposes any ACL UI.
Complexity: Medium.

PRIORITY 3 — Valuable but higher complexity or lower daily frequency

[ ] P3-1 · Message Bookmarks / Saved Messages

What: Save any message for later reference. Features:

"Bookmark" action in the message context menu
Saved to Matrix account data: PUT /_matrix/client/v3/user/{userId}/account_data/io.lotus.bookmarks
Structure: { bookmarks: [{ roomId, eventId, savedAt, previewText }] }
Dedicated sidebar panel (new icon in sidebar nav): list of bookmarks with room name, message preview, timestamp, and "Jump to message" button
Remove bookmark from the panel or from the message context menu
Architecture:
New hook: useBookmarks() for read/write account data
New panel: src/app/features/bookmarks/BookmarksPanel.tsx
Add sidebar icon
[AUDIT REQUIRED] — Confirm upstream Cinny has no bookmark/saved messages feature.
Complexity: Medium-High.

[ ] P3-2 · Message Scheduling / Send Later (MSC4140)

Spec: MSC4140 (Delayed Events). Status: Synapse-stable, not yet in formal spec.
First: SSH to compute-storage-01 → pct exec 151 -- bash (LXC 151 = Synapse) and check:

grep -i "delayed\|msc4140" /etc/matrix-synapse/homeserver.yaml
# Also check:
curl -s https://matrix.lotusguild.org/_matrix/client/unstable/org.matrix.msc4140/delayed_events

If supported: Implement send-later UI:

Hold send button (or right-click → "Schedule…") to open a date/time picker
On confirm: POST /_matrix/client/unstable/org.matrix.msc4140/rooms/{roomId}/send/{eventType}?delay={ms}
Scheduled messages appear in a "Scheduled" tray in the composer area
Can be cancelled before they fire via the MSC4140 cancel endpoint
If not supported: Either enable it in Synapse homeserver.yaml, or implement client-side localStorage queue as a fallback.
[SERVER CHECK] — The Synapse audit above is REQUIRED before any implementation work.
Complexity: Medium (if server supports) / High (if needs server config change + client fallback).

[ ] P3-3 · File Upload Compression (opt-in)

What: Before uploading images, present the user with an explicit choice:

Checkbox: "Compress image before uploading"
Detail text: "Reduces file size and loads faster for everyone. May slightly reduce quality."
Show: Original size (e.g. "4.2 MB") → Compressed size estimate (e.g. "~380 KB")
Show: Original dimensions if downsizing
User must explicitly check the box — compression is NEVER automatic.
Architecture:
Use browser Canvas API: canvas.toBlob(cb, 'image/jpeg', 0.82) for compression
Show before/after sizes in the upload preview UI
Only applies to JPEG and PNG; skip for GIF, SVG, WebP
[AUDIT REQUIRED] — Find where image upload preview currently shows in RoomInput.tsx. The compression step needs to insert between "file selected" and "upload confirmed".
Complexity: Medium.

[ ] P3-4 · Accessibility Improvements (WCAG 2.1 AA)

What: Comprehensive audit and fix pass targeting the critical user paths:

Room list navigation (keyboard-only)
Reading messages in the timeline (screen reader announces new messages)
Composing and sending a reply
Opening and closing modals (focus trap, return focus)
ARIA labels on all icon-only buttons
Scope: Do NOT attempt to make every corner of the app AA-compliant in one pass — focus on the golden path (open app → find room → read → reply → send).
[AUDIT REQUIRED] — Run an automated audit first: npx axe-core or browser DevTools accessibility tree. Document every violation before writing a single line of code. Prioritize by severity (critical > serious > moderate).
Complexity: Medium-High (audit is the main work).

[ ] P3-5 · Inline GIF Preview for Giphy/Tenor Links

[AUDIT REQUIRED — DO THIS FIRST] — Before any implementation, verify the current behavior:

Paste a Giphy URL (e.g. https://giphy.com/gifs/...) into the Lotus Chat composer and send it
Does it auto-embed as an animated GIF, or render as a plain URL preview card?
Repeat for Tenor URLs
If already auto-embedding: Close this task — it's handled by the existing URL preview pipeline.
If not: Detect Giphy/Tenor URL patterns in the URL preview renderer and fetch the GIF via the homeserver's /_matrix/media/v3/preview_url proxy. If the proxy returns a direct media URL, render it as an <img> tag with loading="lazy".
Complexity: Low-Medium (after audit).

What: Let users rearrange or hide individual composer toolbar buttons (GIF, Sticker, Emoji, File, Voice, Location). Changes stored in settingsAtom. Access via a small "⚙ Customize toolbar" option in toolbar overflow.
[AUDIT REQUIRED] — Audit the current toolbar button rendering in RoomInput.tsx. Understand the layout system (is it a fixed array or already mapped from config?). Drag-to-reorder may require a DnD library; consider whether reorder is worth the complexity vs just toggle-visibility.
Complexity: Medium-High (drag reorder adds significant complexity).

[ ] P3-7 · Room Stats / Insights Panel (opt-in)

What: An opt-in statistics panel in room settings ("Room Insights" tab). Shows:

Total cached message count
Top 5 most active members (by message count in local cache)
Top 5 most used reactions
Media files shared (count by type)
Activity heatmap (messages per hour of day)
Important: This panel must be explicitly opened — not shown by default. Do not make it the first tab or visible on room settings open.
Derived entirely from locally cached events — no server queries beyond what's already loaded.
[AUDIT REQUIRED] — Confirm the local Matrix SDK cache exposes enough event history to make the stats meaningful (depends on how many events are cached). Very small caches will show misleading data.
Complexity: Medium.

[ ] P3-8 · Thread Panel (full side drawer)

⚠️ LARGEST FEATURE — requires its own planning session before implementation.
What: A right-side drawer for threaded conversations. Currently "Reply in Thread" exists but there is no panel to read or write thread replies.
Features:

Click "Reply in Thread" → opens thread drawer on the right
Thread root event shown at the top of the panel
Full message rendering for all in-thread replies (reuse timeline components)
Reply input at the bottom (full composer with formatting, emoji, etc.)
Unread count badge on the thread button in the main timeline
Keyboard shortcut to close thread panel
Architecture:
New Jotai atom: activeThreadEventId: string | null
New component: src/app/features/room/thread/ThreadPanel.tsx
Rendered alongside RoomView as a conditional right panel (mirror the members drawer pattern)
Filter events in timeline to m.thread relation for the active root event ID
Shares the same mx client and room reference as the main timeline
[AUDIT REQUIRED] — Deeply audit how m.thread relation events are currently stored and retrieved in the matrix-js-sdk. Understand the thread aggregation API: GET /rooms/{roomId}/relations/{eventId}/m.thread. Check if RoomTimeline.tsx currently filters out thread replies from the main timeline (it should — confirm).
Complexity: High.

[ ] P3-9 · Policy List / Ban List Subscription UI

Spec: CS-API §13.16 (stable), m.policy.* events.
Note: User already has Draupnir bot running in all space rooms — this UI complements rather than replaces it.
What: A panel in room/space settings (admin-only) showing:

Currently subscribed policy list rooms
Contents of each list: banned users, banned rooms, banned servers (with reason)
"Subscribe" / "Unsubscribe" actions
Does NOT implement enforcement — Draupnir handles that
[AUDIT REQUIRED] — Understand how Draupnir reads policy lists on this homeserver. Confirm whether a client-side subscription UI would conflict with or duplicate Draupnir's configuration. May be more useful as a read-only viewer than a write UI.
Complexity: High.

PRIORITY 4 — Specialized, high complexity, or very low priority

[ ] P4-1 · Thread Notification Mode Per-Thread (MSC3771)

Spec: MSC3771 (stable). Depends on Thread Panel (#P3-8).
What: Per-thread notification toggle: "All messages" vs "Mentions only". Accessible from the thread panel header. Tracks unread counts separately per thread.
[AUDIT REQUIRED] — Implement after Thread Panel. Requires understanding how the SDK tracks per-thread unread counts.
Complexity: Medium (after thread panel exists).

[ ] P4-2 · Thread Subscriptions (MSC4306)

Spec: MSC4306 (Synapse experimental). Depends on Thread Panel (#P3-8).
What: "Follow thread" button to receive notifications for a thread you haven't posted in. Uses MSC4306 subscription endpoint.
[SERVER CHECK] — Verify matrix.lotusguild.org supports MSC4306. It is Synapse-experimental and may not be enabled.
Complexity: Medium (after thread panel exists).

[ ] P4-3 · Knock-to-join Notifications for Admins

Note: The basic knock-to-join UX is covered in P1-11. This task adds the admin notification side.
What: Space/room admins see a notification badge when there are pending knock requests. A "Pending Join Requests" section in the members drawer or room settings. Approve (invite) or deny (kick) each knock.
Complexity: Medium.

[ ] P4-4 · Math / LaTeX Rendering in Messages (LOW PRIORITY)

Spec: CS-API §11.5 (stable) — formatted_body can contain LaTeX.
What: Render $...$ or $$...$$ LaTeX expressions in message bodies. Use KaTeX (lightweight, ~100KB, renders server-side-compatible CSS). Must gracefully fall back to raw LaTeX text if KaTeX fails.
Note: This is LOW PRIORITY — only useful for academic/technical communities. Implement last.
[AUDIT REQUIRED] — Confirm KaTeX bundle size impact on the Vite bundle. Check if matrix-js-sdk's HTML sanitizer strips LaTeX before it reaches the renderer. The formatted_body sanitization pipeline is the main risk here.
Complexity: Low-Medium.

Spec: MSC3489 + MSC3672. Implemented in Element Web.
Note: Static location sharing is already implemented. This adds live/real-time GPS beacons. Very low priority per user preference.
What: Start sharing live location → creates m.beacon_info state event → client posts m.beacon events on a timer → other users see your position update live on a map.
[SERVER CHECK] — Verify MSC3489 support on matrix.lotusguild.org.
Complexity: High. Requires background geolocation API + live map rendering.

[ ] P4-6 · OIDC / SSO Next-Gen Auth (MSC3861) (EXTREME COMPLEXITY, LOW PRIORITY)

Spec: MSC3861, merged Matrix spec v1.15. Uses Matrix Authentication Service (MAS).
Context: ~80% of homeserver users have LLDAP/Authelia/SSO accounts. SSO is currently enabled on matrix.lotusguild.org but accounts are not yet linked. This would allow users to log in via their SSO credentials.
What: OAuth 2.0 / OIDC login flow, token refresh, account management page linking Matrix identity to SSO identity.
EXTREME COMPLEXITY — requires: MAS deployment/configuration on the homeserver, significant auth flow changes in the client, token refresh handling, session management overhaul.
[SERVER CHECK] — Before any client work, audit whether MAS is already deployed on compute-storage-01. Check: pct exec 151 -- systemctl status matrix-authentication-service or similar.
Complexity: Extreme. Multi-sprint project. Plan separately.

PRIORITY 5 — Gamer / Aesthetic / Customization features

[!] BUG · Drag-and-drop file overlay doesn't dismiss on hover-away

Confirmed bug — drag a file over the window without dropping: the drop overlay persists.
Fix: Ensure dragleave fires correctly at the window/document level. Child element boundaries can cause spurious dragleave — use a counter or relatedTarget check.
[AUDIT REQUIRED] Find the drag-and-drop overlay component in RoomInput.tsx or the room view. Confirm the exact event listener structure.
Complexity: Low (bug fix).

[ ] P5-1 · Custom Accent Color Picker (non-TDS mode only)

What: A hex/HSL color picker in Settings → Appearance. Chosen color replaces the primary accent throughout the UI: buttons, badges, active states, highlights, presence dot, links. Applied via a CSS custom property override injected into <head>.
IMPORTANT: This feature is completely inactive when TDS is enabled — TDS has its own fixed palette. Add this setting under a "Non-TDS Themes" section that is hidden when TDS is active.
[AUDIT REQUIRED] Identify all CSS custom properties that constitute the "accent color" in non-TDS mode. Map them to the folds/vanilla-extract token names.
Complexity: Medium.

[ ] P5-2 · Additional Color Theme Presets

What: 5 new one-click theme presets alongside TDS. Each must be a complete, polished system with proper contrast ratios (WCAG AA). All implemented as vanilla-extract themes matching the existing TDS pattern.
Themes:

Cyberpunk — deep navy bg (#0a0015), electric purple (#bf5fff) + hot pink (#ff2d9b) accents, neon glow
Ocean — deep sea blue bg (#020b18), teal (#00c9b1) + aqua (#0096d6) accents, soft feel
Blood Red — near-black bg (#0d0203), deep crimson (#7a0010) + bright red (#ff2233) accents
Classic Matrix — pure black bg (#000000), phosphor green (#00ff41) text + accents
Midnight — dark charcoal (#111827), cool blue-grey (#6b7ca8) accents, clean minimal
[AUDIT REQUIRED] Study src/lotus-terminal.css.ts for the full token list before designing themes. All tokens must be covered.
Complexity: Medium (design effort is the main cost).

[ ] P5-3 · Glassmorphism Sidebar Toggle

What: Semi-transparent sidebar + panels with backdrop-filter: blur(12px). Toggled in Settings → Appearance. Off by default. Best combined with animated wallpapers.
[AUDIT REQUIRED] Check whether backdrop-filter works on sidebar elements given the current z-index stack and CSS transforms. Some browsers require will-change or specific stacking context to allow blur through.
Complexity: Low-Medium.

[ ] P5-4 · Animated Chat Backgrounds (CSS-animated wallpapers)

What: 5 new animated wallpaper options in the chat background picker:

Matrix Digital Rain — falling character columns (green characters, CSS animation)
Drifting Stars — slow-moving particle field (CSS dots)
Aurora Borealis — slow shifting gradient waves (purple/green/cyan)
Grid Pulse — expanding ring pulses on a dark grid
Fireflies — slow drifting glowing dots
All pure CSS animations (keyframes + transforms) — no canvas, GPU-accelerated. Include a "Pause animations" toggle for accessibility. Colors adapt to active theme accent variables.
[AUDIT REQUIRED] Study how existing wallpapers are applied in lotus-terminal.css.ts to extend the system correctly.
Complexity: Medium.

[ ] P5-5 · Night Light / Blue Light Filter

What: Warm orange overlay rgba(255, 140, 0, 0.12) on the full UI. position:fixed; inset:0; pointer-events:none; z-index:9999. Intensity slider (0–30%) in Settings → Appearance. Optional: auto-activate after a set hour. Stored in settingsAtom.
Complexity: Low.

[ ] P5-6 · Channel / Room Emoji Prefix Support

What: Render a leading emoji in a room name slightly larger in the sidebar for visual impact (e.g. 🎮 general). Optional: right-click room → "Set channel emoji" shortcut for admins.
Note: Matrix room names already support Unicode — this is purely a rendering enhancement.
[AUDIT REQUIRED] Confirm upstream Cinny doesn't strip or truncate leading emoji in sidebar room name display. Also confirm emoji in room names works end-to-end on matrix.lotusguild.org.
Complexity: Low.

[ ] P5-7 · In-App Notification Toast Redesign (TDS mode only)

What: Slim dark card sliding in from bottom-right: user avatar, display name (orange), truncated message preview, room name (dim), × dismiss. 4-second auto-dismiss. TDS variables only — non-TDS keeps existing behavior.
[AUDIT REQUIRED] Find where in-app notification toasts are currently rendered in src/app/. May be in ClientNonUIFeatures.tsx.
Complexity: Medium.

[ ] P5-8 · Mention Highlight Animation

What: Brief pulse/glow animation (0.4–0.6s ease-out) on incoming @mention messages. CSS keyframe: scale 1.0 → 1.005 → 1.0 + background glow pulse. Only fires on new incoming messages, not on page load. Respects prefers-reduced-motion.
[AUDIT REQUIRED] Find where mentioned messages receive their highlight class in the timeline. Verify animation doesn't affect scroll position.
Complexity: Low.

[ ] P5-9 · LFG (Looking for Group) Slash Command

What: /lfg generates a formatted LFG post visible on ALL Matrix clients using standard m.room.message HTML. Fields: Game, Players Needed, Platform, Skill Level, Description, DM link. Other clients see clean formatted HTML; Lotus Chat renders an enhanced styled card.
[AUDIT REQUIRED] Test which HTML tags survive Matrix HTML sanitization on Element/FluffyChat before designing the card structure. Test with minimal HTML.
Complexity: Medium.

[ ] P5-10 · Voice Channel User Limit

What: Admins set max participants via custom state event io.lotus.voice_limit: { max_users: N }. Show "Channel Full (5/5)" to users over the limit. Local enforcement only.
[AUDIT REQUIRED] Check if Element Call has its own participant limit that should be integrated with rather than duplicated.
Complexity: Medium.

[ ] P5-11 · AFK / Idle Auto-Mute in Voice

What: Auto-mute mic after X minutes of silence (detected via Web Audio AnalyserNode). Show "You were auto-muted due to inactivity" toast with click-to-unmute. Admin-configurable via io.lotus.afk_timeout state event. Disableable in Settings → Calls.
[AUDIT REQUIRED] Verify auto-mute must go through the same CallControl bridge as manual mute.
Complexity: Medium.

[ ] P5-12 · Seasonal / Event Themes

What: Automatic + manually toggleable seasonal overlays with CSS particle effects and accent color variants:

Halloween (Oct 15–Nov 1): purple particles, orange accents, spider web pattern
Christmas (Dec 10–Jan 2): snow fall, red/green accents, snowflake pattern
New Year (Dec 31–Jan 1): firework burst animation, gold accents
Pride (June): rainbow gradient accent cycle
All toggleable manually in Settings → Appearance regardless of date. Respects prefers-reduced-motion.
[AUDIT REQUIRED] Design against existing CSS animation system in lotus-terminal.css.ts.
Complexity: Medium.

[ ] P5-13 · Avatar Frame / Border Decorations

What: Decorative CSS rings/frames rendered around user avatars. Built-in options: TDS Glow (animated orange pulsing), Cyberpunk (rotating gradient), Minimal (thin ring), Gold (supporter cosmetic). Stored in Matrix account data io.lotus.avatar_frame. Only visible in Lotus Chat.
[AUDIT REQUIRED] Verify folds Avatar component allows overlay decoration without breaking child-type constraints (see previous white-circle avatar bug).
Complexity: Medium.

[ ] P5-14 · Animated Avatar Overlay Decorations (Discord-style)

What: Animated WebM/GIF overlays that float around avatars (transparent center showing avatar). Curated built-in set OR user-uploaded mxc:// overlay. Stored in account data. Only Lotus Chat users see them.
[AUDIT REQUIRED] See #P5-13 audit. Also decide: curated set only vs user-uploadable.
Complexity: Medium.

[ ] P5-15 · In-Call Soundboard

What: Grid of short audio clips playable into the call audio stream via Web Audio API (AudioBufferSourceNode → MediaStreamDestinationNode → mixed with mic). Built-in clips + user-uploadable custom clips (stored as mxc://). Accessible from call controls bar.
[AUDIT REQUIRED] Verify the Element Call integration exposes the mic MediaStream for mixing. This is the highest-risk part of this feature.
Complexity: High.

[ ] P5-16 · Custom Join / Leave Sound Effects

What: Local-only sounds when participants join/leave a call you're in. Built-in options + per-user settable. Detect via Element Call participant list change events.
[AUDIT REQUIRED] Find how Element Call exposes join/leave participant events to the parent window via postMessage bridge.
Complexity: Medium.

[ ] P5-17 · Quick Emoji Reaction Bar (Hover Shortcut)

What: Floating mini-bar of 5 most recent reactions above the hover toolbar. One-click react. 6th button opens full emoji board.
[AUDIT REQUIRED] Find the message hover toolbar in Message.tsx and confirm how to inject an additional row without breaking layout. Confirm recent emoji tracking mechanism in EmojiBoard.
Complexity: Medium.

[ ] P5-18 · Status-Based Avatar Border Color

What: Colored ring on avatars matching presence: green (online), yellow (idle), red (DND), grey (offline). Subtle 2px CSS box-shadow/border. Applied across all avatar sizes.
[AUDIT REQUIRED] Check existing PresenceBadge component — this extends that concept to the avatar border. Verify folds Avatar allows border/shadow styling.
Complexity: Low-Medium.

[ ] P5-19 · Collapsible Long Messages ('Read more')

What: Messages >~20 lines auto-collapsed with "Read more ↓" button. Click to expand inline. Collapse threshold configurable in settings.
[AUDIT REQUIRED] Determine whether CSS max-height + overflow:hidden or a line-count approach is more appropriate for the current message renderer. Check edge cases with code blocks and media embeds.
Complexity: Medium.

[ ] P5-20 · Quick Reply from Browser Notification

What: Inline reply field in browser notification toasts via Notification Actions API. Reply sends as threaded reply to the triggering message.
[AUDIT REQUIRED] (1) Verify browser Notification Actions API support in target browsers. (2) This requires a Service Worker to handle the reply event — confirm if Lotus Chat has one or needs one.
Complexity: Medium-High.

[ ] P5-21 · Custom @Mention Highlight Color

What: Each user sets their own mention highlight color in Settings → Appearance. Applied as --user-mention-color CSS property override on mention-highlighted message rows.
Complexity: Low.

[ ] P5-22 · Font Selector for the UI

What: Font picker in Settings → Appearance. Options: JetBrains Mono, Inter, Geist, Fira Code, OpenDyslexic, System Default. Applied via CSS custom property overrides.
[AUDIT REQUIRED] Check if any fonts are already globally loaded to avoid double-loading.
Complexity: Low-Medium.

[ ] P5-23 · Message Send Animation

What: Own sent messages fade+scale into the timeline (0.15s ease-out: scale 0.97→1.0, opacity 0.4→1.0). Incoming messages unaffected. Respects prefers-reduced-motion.
Complexity: Low.

[ ] P5-24 · Hotkey Push-to-Deafen

What: Configurable hotkey (default Ctrl+Shift+D) to toggle deafen. Shows "DEAFENED" badge in call bar. Configurable in Settings → Calls alongside PTT keybind.
[AUDIT REQUIRED] Confirm Element Call widget bridge exposes speaker/audio-output control separately from microphone control.
Complexity: Medium.

[ ] P5-25 · Message Length Counter in Composer

What: Character counter near send button. Hidden <500 chars. Shows at 500+ (neutral), orange at 2000+, red at 3500+. TDS mono font styling.
Complexity: Low.

What: Consolidated right-click menu: Mute with duration submenu (15min/1hr/8hr/24hr/Indefinite), Copy room link, Mark as read, Leave room, Room settings.
[AUDIT REQUIRED] Audit current right-click menu to avoid duplicating existing actions.
Complexity: Low-Medium.

[ ] P5-27 · Notification Profile Presets (Gaming / Work / Sleep)

What: Saved presets that change all notification settings atomically. Gaming (mentions only), Work (DMs + mentions), Sleep (all off). Quick-switch from sidebar or settings.
Complexity: Medium.

BLOCKED FEATURES (waiting on server/MSC support)

These features are confirmed desirable but cannot be built until the listed dependency is resolved. Check back after each Synapse upgrade — re-run /matrix/client/versions and unstable_features to see if they've become available.

[BLOCKED] · Reaction / Relation Redaction (MSC3892)

Blocked by: org.matrix.msc3892 = false on matrix.lotusguild.org
What it would do: Cleanly remove a reaction without redacting the parent message.
Current behavior: Full event redaction — acceptable fallback, no user-facing issue.
Action when unblocked: Find onReactionToggle redaction call site; swap in MSC3892 endpoint with fallback.

[BLOCKED] · Room Preview Before Joining (MSC3266)

Blocked by: GET /v1/rooms/{id}/summary returns 404 — endpoint not available on this server
What it would do: Show room name, topic, avatar, member count before joining.
Action when unblocked: Build pre-join preview card; trigger on unjoined room navigation.

[BLOCKED] · Thread Subscriptions (MSC4306)

Blocked by: org.matrix.msc4306 = false on matrix.lotusguild.org
What it would do: Follow a thread without posting; get notifications for replies.
Action when unblocked: Add "Follow thread" button in the thread panel header (depends on #11 Thread Panel).

[BLOCKED] · Report User (MSC4260)

Blocked by: Server declares only spec v1.12; MSC4260 merged in v1.14 — endpoint may not exist
What it would do: Report a specific user to homeserver admins (separate from reporting a message).
Note: Report Message already exists in upstream Cinny. This would add Report User to the profile panel.
Action when unblocked: Test POST /_matrix/client/v3/users/{userId}/report; if 200, add button to user profile.

AUDITS PENDING

[x] Audit-1 · Suggested rooms in Space Lobby — CONFIRMED MISSING (build task #51 created)

[x] Audit-2 · Room upgrade / tombstone UX — CONFIRMED EXISTS in upstream (RoomTombstone.tsx, RoomUpgrade.tsx)

[ ] Audit-3 · Profile banner image — Matrix protocol support

Research whether Matrix spec or MSC4133 (v1.16) defines a standard profile banner field. uk.tcpip.msc4133.stable = true on our server — check if a banner_url or similar field is defined. If no cross-client standard exists, do not implement.

[x] Audit-4 · Visual speaking indicator — CONFIRMED EXISTS (useCallSpeakers.ts, MemberSpeaking.tsx). TDS improvement task #107 created.

IMPLEMENTATION NOTES

⚠️ TDS DESIGN LAW (repeated here for emphasis)

Every TDS color, animation, glow, border, shadow, and font value MUST come from /root/code/web_template/base.css.
Never hardcode hex values. Never invent CSS variable names.
Key variables: --lt-accent-orange · --lt-accent-cyan · --lt-accent-green · --lt-glow-* · --lt-box-glow-* · --lt-border-color · --lt-font-mono
Reference implementation: /root/code/tinker_tickets/ (markdown.js, base.js, ticket.css)
This applies without exception to every task marked [IMPROVE], [Build], or any UI change.

Design Rules

All new components must respect both TDS dark (LotusTerminalTheme) and TDS light (LotusTerminalLightTheme) modes
Non-TDS theme work (custom accent color, theme presets) uses vanilla-extract theme files — match the pattern in src/lotus-terminal.css.ts
Code syntax highlighting token classes: .tok-kw .tok-str .tok-num .tok-cmt .tok-fn (defined in web_template/base.css)
folds AvatarImage does NOT accept children — wrap Avatar components externally for overlays/frames/borders

CI/CD Pipeline

edit → commit → git push origin lotus
→ Gitea Actions: tsc --noEmit, eslint, prettier (~3 min)
→ Webhook: lotus_deploy.sh on LXC 106 polls CI, then npm ci && npm run build → rsync
→ Live at chat.lotusguild.org (~11 min total)

Per-Feature Checklist (before marking complete)

npx tsc --noEmit — zero TypeScript errors
npx eslint src/ — zero new errors (warnings OK if pre-existing)
npx prettier --check src/ — formatting passes
README.md updated (Lotus-custom features only — not upstream Cinny features)
landing/index.html updated if the feature appears in the comparison table
Visually tested at chat.lotusguild.org after CI deploys

Homeserver Access (for server audits)

Synapse (Matrix): LXC 151 on compute-storage-01 — pct exec 151 -- bash
Config: /etc/matrix-synapse/homeserver.yaml
Version check: curl -s https://matrix.lotusguild.org/_matrix/client/versions

66 KiB Raw Blame History Unescape Escape