feat: presence fix, voice ringing fix, user private notes + doc updates

- usePresenceUpdater: replace stale closure with readStatus() called at
  invocation time so changing custom status in Profile Settings is never
  silently overwritten by subsequent activity events
- CallEmbedProvider: fix m.space.parent state-key lookup by switching
  getStateEvent → getStateEvents (plural); space channel voice rooms no
  longer trigger the incoming-call ring/animation
- Add useUserNotes hook (io.lotus.user_notes account data, reactive via
  useAccountDataCallback, 500-char limit, cross-device sync)
- UserRoomProfile: add UserPrivateNotes textarea with 800ms debounced
  auto-save, saving indicator, char counter when <100 chars remain;
  shown only when viewing another user's profile
- LOTUS_FEATURES.md: add Private Notes section, Status Revert fix note,
  animation improvements subsection, Seasonal Themes section
- LOTUS_BUGS.md: mark presence revert + voice ringing bugs as resolved
- README.md + landing/index.html: document all new June 2026 features

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

LOTUS_BUGS.md

@@ -32,12 +32,11 @@ This document tracks identified bugs, edge cases, and architectural discrepancie
 
 ### 1. Presence Updater Reverts Status Updates
 **File:** `src/app/hooks/usePresenceUpdater.ts` (Line 20)
-**Status:** High Priority
+**Status:** ✅ RESOLVED (June 2026)
 
-*   **Issue:** The `storedStatus` variable is captured once when the `useEffect` starts.
-*   **Impact:** If a user updates their status message in the Profile settings, the presence updater hook continues to use the *old* status message from its closure. Every time the user moves their mouse/activity, the hook sends `setOnline` with the stale status, reverting the user's change.
-*   **Recommended Fix:** 
-    1. Read the status from `localStorage` inside the `setOnline`/`setUnavailable` functions rather than at the top of the effect.
+*   **Issue:** The `storedStatus` variable was captured once when the `useEffect` started.
+*   **Impact:** If a user updated their status message in Profile Settings, the hook would continue broadcasting the old message on every activity event, silently reverting the change.
+*   **Fix Applied:** Replaced the single `localStorage.getItem` read with a `readStatus()` function called inside every `setOnline` and `setUnavailable` invocation, ensuring the current value is always used.
 
 ### 2. Audio Playback Rate Reset
 **File:** `src/app/components/message/content/AudioContent.tsx` (Line 97)
@@ -57,11 +56,11 @@ This document tracks identified bugs, edge cases, and architectural discrepancie
 
 ### 4. Incorrect Ringing in Voice Rooms
 **File:** `src/app/components/CallEmbedProvider.tsx`
-**Status:** Logic Bug
+**Status:** ✅ RESOLVED (June 2026)
 
-*   **Issue:** Joining a static voice room (Public Space channel) triggers the "Incoming Call" ringing animation and sound. This should only occur for "StartedByUser" intents (DMs and Private Group Calls).
-*   **Root Cause:** The ringing logic does not distinguish between persistent voice rooms and user-initiated calls.
-*   **Recommended Fix:** Check `room.getJoinRule()` or check for the `m.space.parent` event. If the room is a public voice channel, suppress the ringing animation.
+*   **Issue:** Joining a static voice room (Public Space channel) triggered the "Incoming Call" ringing animation and sound.
+*   **Root Cause:** `getStateEvent(room, StateEvent.SpaceParent)` always returned `undefined` because `m.space.parent` events use the parent space's room ID as the state key, not an empty string. The ringing suppression check silently failed.
+*   **Fix Applied:** Replaced `getStateEvent` with `getStateEvents` (plural), which returns all events of a given type regardless of state key. A room with any `m.space.parent` event is correctly identified as a space channel and suppresses ringing.
 
 ---