chats 0.1.1 → 0.3.1

data/app/views/chats/conversations/index.html.erb

@@ -1,16 +1,37 @@
 <%# The inbox. Subscribed to the viewer's inbox stream: new activity anywhere
     triggers a Turbo 8 page refresh (morphing, scroll-preserving), which
     re-renders this page per-viewer — see Chats::Broadcasts for why refreshes
-    beat surgical row patches here. %>
+    beat surgical row patches here.
+
+    Rows come from Chats::Inbox and are either a Chats::Conversation or a
+    Chats::InboxGroup (every direct thread with a `inbox: :grouped` messager,
+    stacked into one row).
+
+    The chats--refresh-inbox wrapper heals a MISSED refresh broadcast: Action
+    Cable has no replay, so a broadcast sent while the socket was down (tab
+    backgrounded, network blip) would leave the inbox stale until the user
+    navigated. The controller re-runs the same page refresh on cable reconnect
+    and on return-to-visible. It needs to wrap the <turbo-cable-stream-source>
+    that `turbo_stream_from` renders so it can observe its `connected`
+    attribute as the heartbeat. %>
 <%= chats_styles %>
-<%= turbo_stream_from chats_current_messager, :chats_inbox %>
+<div data-controller="chats--refresh-inbox">
+  <%= turbo_stream_from chats_current_messager, :chats_inbox %>
+</div>
 
 <div class="chats chats-inbox">
   <header class="chats-inbox__header">
     <h1 class="chats-inbox__title"><%= t("chats.inbox.title") %></h1>
   </header>
 
-  <% if Chats.config.search %>
+  <% if @inbox.filtered? %>
+    <p class="chats-inbox__filter">
+      <%= t("chats.inbox.filtered_by", name: Chats.display_name_for(@inbox.with)) %>
+      <%= link_to t("chats.inbox.clear_filter"), conversations_path, class: "chats-inbox__filter-clear" %>
+    </p>
+  <% end %>
+
+  <% if Chats.config.search && !@inbox.filtered? %>
     <%= form_with url: conversations_path,
           method: :get,
           class: "chats-search",
@@ -29,13 +50,21 @@
   <% end %>
 
   <%= turbo_frame_tag "chats_inbox_results", target: "_top" do %>
-    <% if @conversations.any? %>
+    <%# Slot: anything the host wants above the first row — a support door,
+        an announcement, a filter bar. Renders only when the partial exists. %>
+    <%= chats_slot :inbox_top, viewer: chats_current_messager, inbox: @inbox %>
+
+    <% if @rows.any? %>
       <ul class="chats-inbox__list">
-        <% @conversations.each do |conversation| %>
-          <%= render "chats/conversations/conversation_row",
-                conversation: conversation,
-                viewer: chats_current_messager,
-                unread_count: @unread_counts.fetch(conversation.id, 0) %>
+        <% @rows.each do |row| %>
+          <% if row.is_a?(Chats::InboxGroup) %>
+            <%= render "chats/conversations/group", group: row, viewer: chats_current_messager %>
+          <% else %>
+            <%= render "chats/conversations/conversation_row",
+                  conversation: row,
+                  viewer: chats_current_messager,
+                  unread_count: @unread_counts.fetch(row.id, 0) %>
+          <% end %>
         <% end %>
       </ul>
     <% elsif params[:q].present? %>
@@ -48,6 +77,7 @@
         <span class="chats-empty__icon" aria-hidden="true">💬</span>
         <p class="chats-empty__title"><%= t("chats.inbox.empty_title") %></p>
         <p class="chats-empty__hint"><%= t("chats.inbox.empty_hint") %></p>
+        <%= chats_slot :inbox_empty, viewer: chats_current_messager, inbox: @inbox %>
       </div>
     <% end %>
   <% end %>

data/app/views/chats/conversations/show.html.erb

@@ -19,6 +19,10 @@
       "chats--thread-refresh-url-value": refresh_conversation_path(@conversation),
       "chats--thread-thread-url-value": conversation_path(@conversation),
       "chats--thread-copied-label-value": t("chats.message.copied"),
+      # A plain data attribute (not a Stimulus value): host CSS/JS keys its
+      # own block/report affordances off it. False for a messager declared
+      # `acts_as_messager blockable: false`.
+      "chats-blockable": chats_blockable?(chats_counterpart),
       action: "pointerdown->chats--thread#pressStart pointermove->chats--thread#pressMove " \
               "pointerup->chats--thread#pressEnd pointercancel->chats--thread#pressCancel " \
               "contextmenu->chats--thread#contextMenu"
@@ -31,13 +35,37 @@
       <span aria-hidden="true">‹</span>
     <% end %>
 
-    <%= chats_conversation_avatar(@conversation, chats_current_messager) %>
+    <%# The counterpart is already resolved for the title, the profile link
+        and the stack link — reuse it here instead of asking again. %>
+    <% if chats_counterpart %>
+      <%= chats_messager_avatar(chats_counterpart) %>
+    <% else %>
+      <%= chats_conversation_avatar(@conversation, chats_current_messager) %>
+    <% end %>
 
     <div class="chats-thread__identity">
-      <h1 class="chats-thread__title"><%= @conversation.title_for(chats_current_messager) %></h1>
+      <%# Both arms wrap the name in .chats-thread__name: the <h1> is a flex
+          row (the badge is its second child), and only a real element can
+          carry the ellipsis. %>
+      <h1 class="chats-thread__title">
+        <% if chats_counterpart %>
+          <%= chats_messager_name(chats_counterpart, css_class: "chats-thread__name") %>
+          <%= chats_verified_badge(chats_counterpart) %>
+        <% else %>
+          <span class="chats-thread__name"><%= @conversation.title_for(chats_current_messager) %></span>
+        <% end %>
+      </h1>
       <% if @conversation.subject_label %>
         <p class="chats-thread__subject"><%= @conversation.subject_label %></p>
       <% end %>
+      <%# A stacked counterpart's thread is one of many: offer the way back
+          to the whole stack (chats' filtered inbox, or the host's own
+          screen via `group_path:`). %>
+      <% if Chats.grouped_inbox?(chats_counterpart) %>
+        <p class="chats-thread__see-all">
+          <%= link_to t("chats.thread.see_all"), chats_group_path_for(chats_counterpart), class: "chats-thread__see-all-link" %>
+        </p>
+      <% end %>
     </div>
 
     <details class="chats-menu">
@@ -51,6 +79,15 @@
         <% if @conversation.group? %>
           <%= button_to t("chats.thread.leave"), leave_conversation_path(@conversation), method: :post, class: "chats-menu__item chats-menu__item--danger" %>
         <% end %>
+        <%# Slot: the host's own thread actions (block, report, archive…).
+            `blockable` is false for messagers declared
+            `acts_as_messager blockable: false`, so safety affordances
+            disappear against a support desk without any class check. %>
+        <%= chats_slot :conversation_header_actions,
+              conversation: @conversation,
+              viewer: chats_current_messager,
+              counterpart: chats_counterpart,
+              blockable: chats_blockable?(chats_counterpart) %>
       </div>
     </details>
   </header>
@@ -133,5 +170,13 @@
     </div>
   </div>
 
-  <%= render "chats/messages/composer", conversation: @conversation %>
+  <%# A locked conversation (its SUBJECT says so — Chats::ChatSubject#
+      chat_locked?) keeps its whole history readable and swaps the composer
+      for the reason it's closed. Never a hidden screen: gate the action,
+      explain it in place. %>
+  <% if @conversation.locked? %>
+    <%= render "chats/conversations/locked_composer", conversation: @conversation %>
+  <% else %>
+    <%= render "chats/messages/composer", conversation: @conversation %>
+  <% end %>
 <% end %>

data/app/views/chats/messages/_composer.html.erb

@@ -2,8 +2,12 @@
     the response — instant, no cable round-trip needed); the chats--composer
     controller adds autosize, desktop Enter-to-send, throttled typing pings,
     and reset-on-success. Plain form POST still works with JS disabled. %>
+<%# id: the swap target — a conversation that locks while this form is open
+    gets the locked notice rendered straight over it (see
+    chats/messages/locked.turbo_stream.erb). %>
 <%= form_with model: Chats::Message.new,
       url: conversation_messages_path(conversation),
+      id: dom_id(conversation, :composer),
       class: "chats-composer",
       data: {
         controller: "chats--composer",

data/app/views/chats/messages/_message.html.erb

@@ -27,7 +27,7 @@
   <% else %>
     <div class="chats-message__content">
       <% if message.conversation.group? && message.sender %>
-        <span class="chats-message__sender"><%= Chats.display_name_for(message.sender) %></span>
+        <%= chats_messager_name(message.sender, css_class: "chats-message__sender") %>
       <% end %>
 
       <div class="chats-message__bubble-row">
@@ -76,11 +76,20 @@
             <% end %>
           <% end %>
 
+          <%# Signature: who WROTE this, when that isn't who it was sent
+              from — an agent answering from a shared desk seat. The sender
+              stays the conversation identity; this line keeps the human
+              visible. See Chats::Message#signed?. %>
+          <% if (signature = chats_message_signature(message)) %>
+            <div class="chats-message__signature" data-chats-message-signature><%= signature %></div>
+          <% end %>
+
           <span class="chats-message__meta">
             <% if message.edited? && !message.deleted? %>
               <span class="chats-message__edited"><%= t("chats.message.edited") %></span>
             <% end %>
             <time datetime="<%= message.created_at.iso8601 %>"><%= message.created_at.in_time_zone.strftime("%H:%M") %></time>
+            <%= chats_slot :message_meta, message: message %>
             <% if Chats.config.read_receipts %>
               <span class="chats-message__receipt"
                     data-chats-message-receipt
@@ -95,6 +104,12 @@
       </div>
 
       <% unless message.deleted? %>
+        <%# A locked conversation (its SUBJECT says so) refuses every write —
+            new messages, edits, deletes and reactions alike. The server
+            enforces it; here we stop OFFERING what would only 422: existing
+            reactions still render, as plain counts instead of toggles, and
+            the long-press menu keeps only Copy. %>
+        <% locked = message.conversation.locked? %>
         <% reactions = Chats.config.reactions ? Chats::Reaction.summary_for(message) : [] %>
         <% if reactions.any? %>
           <div class="chats-message__reactions">
@@ -103,10 +118,16 @@
                 through the HOST's renderer where engine helpers don't exist
                 unqualified. See EngineHelper#chats_routes. %>
             <% reactions.each do |emoji, count| %>
-              <%= button_to chats_routes.conversation_message_reactions_path(message.conversation, message),
-                    method: :post, params: { emoji: emoji },
-                    class: "chats-reaction", "aria-label": t("chats.message.toggle_reaction", emoji: emoji) do %>
-                <%= emoji %><% if count > 1 %><span class="chats-reaction__count"><%= count %></span><% end %>
+              <% if locked %>
+                <span class="chats-reaction chats-reaction--locked">
+                  <%= emoji %><% if count > 1 %><span class="chats-reaction__count"><%= count %></span><% end %>
+                </span>
+              <% else %>
+                <%= button_to chats_routes.conversation_message_reactions_path(message.conversation, message),
+                      method: :post, params: { emoji: emoji },
+                      class: "chats-reaction", "aria-label": t("chats.message.toggle_reaction", emoji: emoji) do %>
+                  <%= emoji %><% if count > 1 %><span class="chats-reaction__count"><%= count %></span><% end %>
+                <% end %>
               <% end %>
             <% end %>
           </div>
@@ -122,7 +143,7 @@
             button_to forms keep working when cloned: the CSRF token is
             baked in at render time. %>
         <template data-chats-message-menu>
-          <% if Chats.config.reactions %>
+          <% if Chats.config.reactions && !locked %>
             <div class="chats-popup__reactions" role="group" aria-label="<%= t("chats.message.react") %>">
               <% %w[👍 ❤️ 😂 😮 😢 🙏].each do |emoji| %>
                 <%= button_to emoji, chats_routes.conversation_message_reactions_path(message.conversation, message),
@@ -137,12 +158,12 @@
                 <%= t("chats.message.copy") %>
               </button>
             <% end %>
-            <% if Chats.config.editing && message.body.present? %>
+            <% if Chats.config.editing && message.body.present? && !locked %>
               <button type="button" class="chats-popup__item" role="menuitem" data-chats-action="edit" data-chats-own-only>
                 <%= t("chats.message.edit") %>
               </button>
             <% end %>
-            <% if Chats.config.deletion %>
+            <% if Chats.config.deletion && !locked %>
               <%= button_to t("chats.message.delete"),
                     chats_routes.conversation_message_path(message.conversation, message),
                     method: :delete,

data/app/views/chats/messages/locked.turbo_stream.erb

@@ -0,0 +1,6 @@
+<%# The send landed on a conversation whose subject has since locked it.
+    Replace the composer with the locked notice (422) so the screen stops
+    lying to whoever had it open, and clear any stale error text. %>
+<%= turbo_stream.replace dom_id(@conversation, :composer) do %>
+  <%= render "chats/conversations/locked_composer", conversation: @conversation %>
+<% end %>

data/app/views/chats/shared/_verified_badge.html.erb

@@ -0,0 +1,32 @@
+<%# The "official account" mark. Rendered next to a verified messager's name
+    (`acts_as_messager verified: true`) in every bundled view that shows one:
+    the inbox row, the stacked row and the thread header.
+
+    It is an IMAGE with a name, not decoration: the wrapper carries
+    role="img" plus the localized label, so a screen reader announces
+    "Cuenta oficial" / "Official account" where a sighted person sees the
+    badge, and the glyph itself is aria-hidden so it is never read twice.
+
+    The glyph is heroicons `check-badge` (24/solid): a scalloped rosette
+    with a TICK knocked out of it, which is the mark people already read as
+    "verified". It is deliberately not a plain star — a star says "favourite"
+    or "rated", and at 14px a solid star and a solid rosette are the same
+    blob, so the tick is the whole point. `fill-rule: evenodd` is what knocks
+    the tick out; without it the rosette fills solid and the mark is a blob.
+
+    Colour comes from the --chats-verified CSS variable (see chats.css) via
+    `fill: currentColor` — override that variable, or swap this whole partial
+    with `config.verified_badge`. %>
+<span class="chats-verified"
+      role="img"
+      title="<%= t("chats.verified.label") %>"
+      aria-label="<%= t("chats.verified.label") %>">
+  <svg xmlns="http://www.w3.org/2000/svg"
+       viewBox="0 0 24 24"
+       fill="currentColor"
+       class="chats-verified__glyph"
+       aria-hidden="true"
+       focusable="false">
+    <path fill-rule="evenodd" clip-rule="evenodd" d="M8.603 3.799A4.49 4.49 0 0 1 12 2.25c1.357 0 2.573.6 3.397 1.549a4.49 4.49 0 0 1 3.498 1.307 4.491 4.491 0 0 1 1.307 3.497A4.49 4.49 0 0 1 21.75 12a4.49 4.49 0 0 1-1.549 3.397 4.491 4.491 0 0 1-1.307 3.497 4.491 4.491 0 0 1-3.497 1.307A4.49 4.49 0 0 1 12 21.75a4.49 4.49 0 0 1-3.397-1.549 4.49 4.49 0 0 1-3.498-1.306 4.491 4.491 0 0 1-1.307-3.498A4.49 4.49 0 0 1 2.25 12c0-1.357.6-2.573 1.549-3.397a4.49 4.49 0 0 1 1.307-3.497 4.49 4.49 0 0 1 3.497-1.307Zm7.007 6.387a.75.75 0 1 0-1.22-.872l-3.236 4.53L9.53 12.22a.75.75 0 0 0-1.06 1.06l2.25 2.25a.75.75 0 0 0 1.14-.094l3.75-5.25Z" />
+  </svg>
+</span>

data/config/importmap.rb

@@ -8,9 +8,10 @@
 # "chats--composer", etc. with ZERO host JavaScript changes. (stimulus-rails,
 # app/assets/javascripts/stimulus-loading.js, registerControllerFromPath.)
 #
-# Hosts can override either controller by pinning the same key themselves —
+# Hosts can override any controller by pinning the same key themselves —
 # the engine's importmap is drawn FIRST (unshifted in Chats::Engine), and
 # importmap-rails resolves duplicate pins last-wins.
 pin "controllers/chats/thread_controller", to: "chats/thread_controller.js"
 pin "controllers/chats/composer_controller", to: "chats/composer_controller.js"
 pin "controllers/chats/debounced_submit_controller", to: "chats/debounced_submit_controller.js"
+pin "controllers/chats/refresh_inbox_controller", to: "chats/refresh_inbox_controller.js"

data/config/locales/en.yml

@@ -8,6 +8,11 @@ en:
       no_results_title: "No results"
       no_results_hint: "Nothing matched “%{query}”."
       no_messages: "No messages yet"
+      filtered_by: "Conversations with %{name}"
+      clear_filter: "Show all conversations"
+      group_count:
+        one: "1 conversation"
+        other: "%{count} conversations"
       you_prefix: "You:"
     thread:
       back: "Back"
@@ -22,14 +27,18 @@ en:
       yesterday: "Yesterday"
       typing_suffix: "is typing…"
       new_messages: "New messages"
+      see_all: "See all"
     conversation:
       empty_title: "Conversation"
+    verified:
+      label: "Official account"
     message:
       deleted: "Message deleted"
       edited: "edited"
       copy: "Copy"
       copied: "Copied!"
       attachment: "Photo"
+      signature: "— %{name}"
       close_attachment: "Close photo"
       edit: "Edit"
       delete: "Delete"
@@ -44,6 +53,7 @@ en:
       placeholder: "Write a message…"
       send: "Send"
       attach: "Attach images"
+      locked: "This conversation is closed."
     buttons:
       chat: "Message"
     flashes:
@@ -67,7 +77,10 @@ en:
         chats/message:
           attributes:
             base:
+              locked: "This conversation is closed."
               blocked: "You can't message this person."
+            author:
+              not_a_messager: "must be a messager (acts_as_messager)"
             sender:
               blank: "is required"
               not_a_participant: "is not a participant of this conversation"

data/config/locales/es.yml

@@ -8,6 +8,11 @@ es:
       no_results_title: "Sin resultados"
       no_results_hint: "No hay nada que coincida con «%{query}»."
       no_messages: "Sin mensajes todavía"
+      filtered_by: "Conversaciones con %{name}"
+      clear_filter: "Ver todas las conversaciones"
+      group_count:
+        one: "1 conversación"
+        other: "%{count} conversaciones"
       you_prefix: "Tú:"
     thread:
       back: "Atrás"
@@ -22,14 +27,18 @@ es:
       yesterday: "Ayer"
       typing_suffix: "está escribiendo…"
       new_messages: "Mensajes nuevos"
+      see_all: "Ver todas"
     conversation:
       empty_title: "Conversación"
+    verified:
+      label: "Cuenta oficial"
     message:
       deleted: "Mensaje eliminado"
       edited: "editado"
       copy: "Copiar"
       copied: "¡Copiado!"
       attachment: "Foto"
+      signature: "— %{name}"
       close_attachment: "Cerrar foto"
       edit: "Editar"
       delete: "Eliminar"
@@ -44,6 +53,7 @@ es:
       placeholder: "Escribe un mensaje…"
       send: "Enviar"
       attach: "Adjuntar imágenes"
+      locked: "Esta conversación está cerrada."
     buttons:
       chat: "Mensaje"
     flashes:
@@ -67,7 +77,10 @@ es:
         chats/message:
           attributes:
             base:
+              locked: "Esta conversación está cerrada."
               blocked: "No puedes enviar mensajes a esta persona."
+            author:
+              not_a_messager: "debe ser un mensajero (acts_as_messager)"
             sender:
               blank: "es obligatorio"
               not_a_participant: "no participa en esta conversación"

data/context7.json

@@ -0,0 +1,4 @@
+{
+  "url": "https://context7.com/rameerez/chats",
+  "public_key": "pk_HibNJE5rTFvy1txHHXUot"
+}

data/docs/PRD.md

@@ -18,7 +18,7 @@ Direct messages, group chats, reactions, attachments, read receipts — Hotwire-
 
 A gem you add to a Rails app to get **Instagram/X-DM-class** user-to-user messaging without building it again. The happy path is one generator + one `acts_as_messager` line + a mounted engine; the result is a working, real-time, polished inbox. Power users override views, policies, and adapters.
 
-It is **not** a chatbot/LLM framework, not a Slack-clone with workspaces, and not a support-ticketing tool. It is peer-to-peer (and group) human messaging.
+It is **not** a chatbot/LLM framework, not a Slack-clone with workspaces, and not a support-ticketing tool (that is `support_desk`, a separate product gem built on this one — see README). It is peer-to-peer (and group) human messaging.
 
 **Why it exists:** every consumer app eventually needs DMs, and everyone rebuilds the same Conversation/Message/Participant/Receipt model, the same Action Cable + Turbo plumbing, and the same "report this message / block this user / filter this text" surface. We already built the moderation half for CarHey; `chats` is the messaging half, and the two snap together.
 

data/docs/campfire_review.md

@@ -11,7 +11,7 @@ with the same facts.
 
 | Campfire pattern | Where it landed here | Notes |
 | --- | --- | --- |
-| **Stale-room refresh** (`Rooms::RefreshesController` + `refresh_room_controller.js`): on tab-visible-after-sleep or cable reconnect, fetch `?since=` and append new / replace updated | `ConversationsController#refresh`, `Message.created_since/.updated_since`, thread controller `refreshThread()` | The single biggest reliability pattern in their codebase — mobile WebViews reap WebSockets constantly. We improved the trigger: instead of their dedicated `HeartbeatChannel`, we observe the `connected` attribute turbo-rails already toggles on `<turbo-cable-stream-source>`. Zero new channels. We also added a deep-backlog escape hatch: > 1 page missed answers with a Turbo 8 `refresh` stream action (full morph) instead of splicing arbitrary history. |
+| **Stale-room refresh** (`Rooms::RefreshesController` + `refresh_room_controller.js`): on tab-visible-after-sleep or cable reconnect, fetch `?since=` and append new / replace updated | `ConversationsController#refresh`, `Message.created_since/.updated_since`, thread controller `refreshThread()`; **and the inbox** via `refresh_inbox_controller.js` (same reconnect/visibility triggers, but the recovery action is a Turbo 8 page `refresh` since inbox broadcasts already are page refreshes) | The single biggest reliability pattern in their codebase — mobile WebViews reap WebSockets constantly. We improved the trigger: instead of their dedicated `HeartbeatChannel`, we observe the `connected` attribute turbo-rails already toggles on `<turbo-cable-stream-source>`. Zero new channels. We also added a deep-backlog escape hatch: > 1 page missed answers with a Turbo 8 `refresh` stream action (full morph) instead of splicing arbitrary history. The inbox got the same doctrine (missed inbox refreshes had no recovery before). |
 | **DOM cap** (`message_paginator.js` `maxMessages: 300`) | Thread controller `trimExcessMessages()` (300 + 20 leeway) | Only trims while the viewer is parked at the bottom. Our pagination is a server-rendered lazy-frame chain (theirs is JS-driven), so trimming also re-plants the keyset anchor frame (`rebuildPaginationAnchor()`) — trimmed history stays reachable on scroll-up with no gaps. |
 | **Out-of-order arrival handling** (their `messages_controller.js` re-sorts on insert) | Thread controller `ensureChronological()` | Broadcast appends from concurrent host job workers can land out of order. ISO8601 lexicographic compare; equal timestamps keep arrival order. |
 | **First-unread anchoring** (they page around the first unread; membership unread marker) | The «new messages» divider: `@first_unread_id` computed in `#show` *before* `read!` advances the horizon | We render a divider rather than re-anchoring the page — the thread still opens at the bottom (coordination chats are short; jumping deep into history on open would feel broken at our scale). Backlogs deeper than a page pin the divider to the top of the page. |

data/gemfiles/rails_7.1.gemfile

@@ -14,6 +14,7 @@ group :development do
 end
 
 group :test do
+  gem "json", "~> 2.7"
   gem "minitest", "~> 6.0"
   gem "minitest-mock"
   gem "mocha", "~> 2.0"

data/gemfiles/rails_7.2.gemfile

@@ -14,6 +14,7 @@ group :development do
 end
 
 group :test do
+  gem "json", "~> 2.7"
   gem "minitest", "~> 6.0"
   gem "minitest-mock"
   gem "mocha", "~> 2.0"

data/gemfiles/rails_8.1.gemfile

@@ -14,6 +14,7 @@ group :development do
 end
 
 group :test do
+  gem "json", "~> 2.7"
   gem "minitest", "~> 6.0"
   gem "minitest-mock"
   gem "mocha", "~> 2.0"

data/lib/chats/configuration.rb

@@ -86,6 +86,12 @@ module Chats
     attr_accessor :messages_per_page, :max_message_length, :max_group_size, :max_attachment_size,
                   :max_attachments_per_message
 
+    # How many conversations the inbox loads (and therefore how deep search
+    # and grouping see). The inbox is a "recent activity" surface, not an
+    # archive — raise it only if your users really keep hundreds of live
+    # threads.
+    attr_accessor :inbox_limit
+
     # Per-sender send throttle, enforced with Rails 8's built-in controller
     # `rate_limit` when available (feature-detected; on Rails 7.1 it's a
     # no-op). Shape: `{ to: Integer, within: ActiveSupport::Duration }`.
@@ -109,6 +115,12 @@ module Chats
     # May +creator+ create a group conversation?
     attr_reader :can_create_group
 
+    # ->(relation, viewer) { relation } — composed into the inbox query
+    # before the limit, so a host can hide or re-scope rows without
+    # overriding the controller:
+    #   config.inbox_scope = ->(relation, viewer) { relation.where.not(kind: "group") }
+    attr_reader :inbox_scope
+
     # --- Ecosystem seams (procs, no-op defaults) ------------------------------
 
     # ->(messager) { ids } — every messager id that can't talk with the given
@@ -130,6 +142,28 @@ module Chats
     # or variant), or nil to render an initials placeholder.
     attr_reader :messager_avatar
 
+    # ->(messager) { path_or_url_or_nil } — where a messager's profile lives.
+    # The bundled views link names and avatars to it; nil (the default) means
+    # no anchor at all, so the gem never assumes a `user_path` exists.
+    attr_reader :messager_url
+
+    # ->(message) { String } — the signature line under a SIGNED message
+    # (one written by an author on the sender's behalf — see
+    # Chats::Message#signed?). nil (the default) renders the localized
+    # "— Author Name".
+    attr_reader :message_signature
+
+    # ->(messager) { markup } — the badge shown next to an OFFICIAL
+    # account's name (`acts_as_messager verified: true`). nil (the default)
+    # renders the gem's own rosette, `chats/shared/_verified_badge`, coloured
+    # by the `--chats-verified` CSS variable.
+    #
+    # Return an html_safe value (anything `render`, `tag` or `image_tag`
+    # gives you) — a bare String is escaped, exactly as it would be anywhere
+    # else in a Rails view. Returning nil renders nothing, so a host can
+    # suppress the badge on some messagers without touching the models.
+    attr_reader :verified_badge
+
     def initialize
       @messager_class = "User"
       @parent_controller = "::ApplicationController"
@@ -152,14 +186,19 @@ module Chats
       @max_attachment_size = 10 * 1024 * 1024 # 10 MB
       @max_attachments_per_message = 4
       @send_rate_limit = { to: 60, within: 60 } # 60 messages per minute per sender
+      @inbox_limit = 200
 
       @encrypt_messages = false
 
       @can_message = ->(_sender, _recipient) { true }
       @can_create_group = ->(_creator) { true }
+      @inbox_scope = ->(relation, _viewer) { relation }
 
       @blocked_messager_ids = ->(_messager) { [] }
       @notifier = ->(_event, **_payload) {}
+      @messager_url = ->(_messager) { nil }
+      @message_signature = nil
+      @verified_badge = nil
 
       @messager_display_name = lambda do |messager|
         messager.try(:display_name) || messager.try(:name) ||
@@ -232,8 +271,45 @@ module Chats
       @blocked_messager_ids = ensure_callable(value, "blocked_messager_ids")
     end
 
+    # DEPRECATED (removed in 1.0): sugar that subscribes one `(event,
+    # **payload)` proc to the two events that existed in 0.1.1
+    # (:message_created, :conversation_read) — and ONLY those, so an old
+    # keyword-specific hook can't start raising on events it was never
+    # written for. `Chats.on` supersedes it: many subscribers, per-event
+    # payloads, reload-safe keys, and every event.
     def notifier=(value)
-      @notifier = ensure_callable(value, "notifier")
+      hook = ensure_callable(value, "notifier")
+      Chats.deprecator.warn(
+        "config.notifier is deprecated and will be removed in chats 1.0. " \
+        "It receives #{Chats::Subscribers::LEGACY_NOTIFIER_EVENTS.map(&:inspect).join(" and ")} only; " \
+        "the events added in 0.2.0 are Chats.on-only. " \
+        "Subscribe with Chats.on(:message_created) { |message| … } instead " \
+        "(see the README's \"Events\" section)."
+      )
+
+      Chats::Subscribers::LEGACY_NOTIFIER_EVENTS.each do |event|
+        Chats::Subscribers.on(event, key: Chats::Subscribers::NOTIFIER_KEY, style: :event) do |fired, **payload|
+          hook.call(fired, **payload)
+        end
+      end
+
+      @notifier = hook
+    end
+
+    def inbox_scope=(value)
+      @inbox_scope = ensure_callable(value, "inbox_scope")
+    end
+
+    def messager_url=(value)
+      @messager_url = ensure_callable(value, "messager_url")
+    end
+
+    def message_signature=(value)
+      @message_signature = value.nil? ? nil : ensure_callable(value, "message_signature")
+    end
+
+    def verified_badge=(value)
+      @verified_badge = value.nil? ? nil : ensure_callable(value, "verified_badge")
     end
 
     def messager_display_name=(value)
@@ -259,6 +335,8 @@ module Chats
         raise ConfigurationError, "messages_per_page must be positive (got #{messages_per_page.inspect})"
       end
 
+      raise ConfigurationError, "inbox_limit must be positive (got #{inbox_limit.inspect})" if inbox_limit.to_i < 1
+
       true
     end