An offboard's price stops hiding in one number: the miners' cut and the ASP's service charge (base + lifetime ppm) record separately and the history detail shows them on their own lines — settling the mystery of a ~350-sat chain fee inside a ~650-sat total. The community row's member count anchors to last session's settled figure instead of ticking upward through the guestbook replay, and a profile's Pay button reached from search actually reaches Send — the lingering search screen was winning the router

Co-Authored-By: Claude Fable 5 <[email protected]>
Claude-Session: https://claude.ai/code/session_01MrkLsNScXe9b6BviUSdmMr

1 files changed, 13 insertions, 3 deletions

diff --git a/src/features/messages.js b/src/features/messages.js
index ac43e40..803afc9 100644
--- a/src/features/messages.js
+++ b/src/features/messages.js
@@ -2029,7 +2029,13 @@ export function messagesFeature(ctx) {
                 } }, t('msgDmsTitle')),
                 h('button', { class: 'grow', onClick: () => {
                   const npubStr = npubOf(pk);
+                  // leave the whole messaging surface, not just the profile —
+                  // a lingering search or thread would win the screen router
+                  // and the Send tab would never appear
                   ui.profilePk = null;
+                  ui.profOverThread = false;
+                  ui.noteThread = null;
+                  ui.userSearch = null;
                   ui.chatOpen = false;
                   ui.tab = 'send';
                   render();
@@ -2418,10 +2424,14 @@ export function messagesFeature(ctx) {
     kids.push(h('div', { class: 'list' }, communities().map((jm) => {
       const room = rooms.get(jm.community_id);
       const name = room?.folded?.metadata?.name || jm.name;
-      // until the guestbook fold lands, last session's settled count beats
-      // a placeholder that flips a moment later
+      // Last session's settled count anchors the number: while the guestbook
+      // replay is still streaming in (multiple relays, bursts past the fold
+      // debounce), the live tally climbs through intermediate values — take
+      // the max so the count doesn't visibly tick upward on every refresh.
+      // Once the replay settles, the cache is rewritten to the live figure,
+      // so a genuine departure still shows (one quiet step down, not a climb).
       const live = room ? [...room.members.values()].filter((m) => m.state === 'join').length : 0;
-      const memberCount = live || (st().memberCounts || {})[jm.community_id] || 0;
+      const memberCount = Math.max(live, (st().memberCounts || {})[jm.community_id] || 0);
       const unread = room ? roomUnread(room) : false;
       return h('div', {
         class: 'item chat-thread-row' + (unread ? ' unread' : ''),