chats 0.6.0 → 0.6.2

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: a0635f1e1c801684a95223db2e59dbb843a67fd9edfe858973b4e9ac6bb32c2a
-  data.tar.gz: 9273751eca09bf387e640a45760f00dbd9875af8b8a75a1c2c4ae0de9ff2f527
+  metadata.gz: fa521d419a2dc6b1d672e2919c4db795674c744fd97df02027ce33b81f582675
+  data.tar.gz: c64cf6cfad1d3f41b9eaf9938936017ecb3af6840feb74f342699c7e0d5d6a01
 SHA512:
-  metadata.gz: 94843453f041d4ff766b577b8ba9c28f4a04123f6532e7c27109836dae84f9c354d3c3051cf7f6ad6ec4b05abcbc46e78deacaaec131d63cd0c1af5631bdf4c1
-  data.tar.gz: 0b61d2704ea93dd153e0b5ff899b9029b561f710f117955dd82f971a232a2891edc903b526af2cfe4438dfd3e655237a9a31dd9512f9406409a75675df138b94
+  metadata.gz: 99f45e5ce16f754d2e32a39bffa6664c4205fd401882b2794152a339eacfc6bb155514303c3e483e68f48f0e7dc52028ea0a7ce9180d776c3083df1b6ff3dd29
+  data.tar.gz: 660e92ea36bc25cea9ad374479495c32f5fcbd1f04f661cfff561eb9f6ce300e8afecd0b5a8294d30630e7577cd35a1f81395ae2848a806be60046b729f25f46

data/CHANGELOG.md

@@ -4,6 +4,59 @@ All notable changes to this project are documented here.
 The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.1.0/),
 and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
 
+## [0.6.2] - 2026-10-18
+
+### Fixed
+- **A moderation removal that removed nothing said it had.**
+  `Chats::Message#remove_reported_field!(:body)`, the seam moderate calls to
+  take reported content down, returned true for a message that was already
+  deleted, so moderate recorded a second "content removed" with a statement
+  of reasons that was false. It now returns whether anything was removed:
+  false for a message already deleted (by its sender or an earlier
+  decision), one whose body is already blank, and one already gone
+  (`deletion: :hard`); true only when it actually removed something (the
+  tombstone, or the row under `deletion: :hard`). It decides under the
+  message's row lock and reads the message again under it, so two
+  decisions taken at once cannot both see it standing. moderate
+  1.0.0.beta3 and later refuse a removal that removed nothing; earlier
+  versions ignore the return value. A group's `remove_reported_field!(:title)`
+  keeps the same contract (false for a title already removed).
+
+## [0.6.1] - 2026-10-18
+
+The package is the gem again, and three fixes to the two-pane page.
+**No migration, nothing to configure.**
+
+### Fixed
+- **The package shipped seven old packages.** The gemspec takes its files
+  from `git ls-files`, and the built `chats-0.3.2.gem` … `chats-0.5.1.gem`
+  had been committed (`chats-0.3.1.gem` since 0.3.1), so 0.6.0 weighed
+  3.5 MB. They are untracked, `*.gem` is in `.gitignore`, and the gemspec
+  leaves out any `*.gem` it is handed anyway; `test/gemspec_test.rb` keeps
+  it so. The README's screenshots still ship, since the README links them.
+- **The tab kept the previous page's title after a row click.** Turbo
+  leaves `<head>` alone when it promotes a frame load to a visit, so from
+  `/messages/A` clicking B left A's title. The messaging page's title now
+  has one source, the new `chats_page_title` helper ("Messages", "Bob ·
+  Messages": `chats.page_title.inbox` / `.conversation`, localized), which
+  `config.page_title = ->(conversation, viewer) { … }` rewords. The bundled
+  `index` and `show` give it to `content_for :title` (a layout doing
+  `yield(:title)` shows it on a full page), and the pane carries it
+  (`data-title`), which `chats--split` gives the tab when a row opens it.
+  The pane's answer stays in turbo-rails' minimal frame layout, now even
+  under a `config.layout`. A layout that titles pages from what the
+  controller loaded keeps its title on full pages and shows
+  `chats_page_title` after a row click: say it the same way in
+  `config.page_title`.
+- **A tapped row kept its hover tint on touch screens.** Every hover rule
+  on inbox rows and on the dock (rows, the bar's chevron, "See all
+  messages", the window buttons) now sits inside `@media (hover: hover)`.
+- **The open row kept its unread count until the list's live refresh.** The
+  pane says when the server read the conversation as it rendered it
+  (`data-read`), and the thread now dispatches `chats:read` once a read it
+  posted lands; on either, `chats--split` clears that row's count and bold
+  at once. The refresh that follows renders the same.
+
 ## [0.6.0] - 2026-10-18
 
 The messaging page is two panes, LinkedIn-style: on a wide screen

data/README.md

@@ -253,7 +253,7 @@ Use **`:flag`, never `:block`** for chat: you don't gag someone mid-conversation
 |---|---|
 | `reported_owner` | the sender (who a decision notifies, who a ban targets) |
 | `moderation_snapshot(:body)` | the body — frozen as evidence at report time, surviving later edits/deletes |
-| `remove_reported_field!(:body)` | the **soft-delete tombstone** — a moderator's removal looks exactly like a user deletion ("Message deleted"), no special admin rendering path |
+| `remove_reported_field!(:body)` | the **soft-delete tombstone** — a moderator's removal looks exactly like a user deletion ("Message deleted"), no special admin rendering path. Returns whether anything was removed: `true` only when it actually removed something (the tombstone, or the row under `deletion: :hard`), `false` for a message already deleted (by its sender or an earlier decision), already gone, or whose body is already blank, decided under the message's row lock so two decisions at once can't both remove it. moderate 1.0.0.beta3 and later refuse a removal that removed nothing; earlier versions ignore the return value. A group's `remove_reported_field!(:title)` keeps the same contract |
 | `report_visible_to?(viewer)` | participants only (a DM isn't public content), and never the author |
 | `moderation_field_value(:files)` / change detection | attachment-aware seams so image filters classify what actually changed |
 
@@ -598,6 +598,8 @@ Each row is a real link to `/messages/:id` (keeping the list's search or stack i
 
 **Reads** happen when you open a conversation: a row clicked, a link, a reload. The page's own refreshes never read (one may arrive in a background tab), and a conversation the page renders unread reads itself as soon as it's on screen.
 
+**The page's title** comes from one place, `chats_page_title`: "Messages" for the inbox, "Bob · Messages" with a conversation open (`chats.page_title.*`, localized). The bundled pages hand it to `content_for :title`, so a layout that shows `<title><%= content_for(:title) || "My app" %></title>` (the Rails default) gets it, and the pane carries it, so the tab follows when a row opens a conversation (Turbo leaves `<head>` alone on a frame visit). Word it your way, for both, with `config.page_title = ->(conversation, viewer) { … }` (`conversation` is nil on the inbox). A layout that builds its own title from what the controller loaded (a `@page_title`) keeps it on full page loads, and shows `chats_page_title` after a row click: say it the same way in `config.page_title`.
+
 The [messaging dock](#-messaging-dock) stays off this page, as on every engine page; its "See all messages" opens it, and a window's ⤢ opens its conversation here.
 
 ```ruby
@@ -770,6 +772,7 @@ Chats.configure do |config|
   config.messager_url = ->(messager) { nil }                 # nil ⇒ names render as plain text
   config.message_signature = nil                             # ->(message) { } for signed bubbles
   config.verified_badge = nil                                # ->(messager) { markup } for verified: true
+  config.page_title = nil                                    # ->(conversation, viewer) { String }; nil ⇒ "Bob · Messages"
 end
 ```
 

data/app/assets/stylesheets/chats.css

@@ -86,7 +86,11 @@
   text-decoration: none;
   color: inherit;
 }
-.chats-row__link:hover { background: var(--chats-surface); }
+/* Hover only where there is one: a touch screen "hovers" what it tapped and
+   keeps the tint after the finger is gone (the open row stayed grey). */
+@media (hover: hover) {
+  .chats-row__link:hover { background: var(--chats-surface); }
+}
 .chats-row__body { flex: 1; min-width: 0; display: flex; flex-direction: column; gap: 0.1rem; }
 .chats-row__top, .chats-row__bottom {
   display: flex;
@@ -1312,7 +1316,9 @@ turbo-frame[id^="chats_page_"] {
   height: 18px;
   transition: transform var(--chats-dock-duration) var(--chats-dock-ease);
 }
-.chats-dock__toggle:hover .chats-dock__chevron { background: var(--chats-dock-hover); color: var(--chats-text); }
+@media (hover: hover) {
+  .chats-dock__toggle:hover .chats-dock__chevron { background: var(--chats-dock-hover); color: var(--chats-text); }
+}
 .chats-dock__panel[open] .chats-dock__chevron svg { transform: rotate(180deg); }
 .chats-dock__close-glyph { display: none; }
 
@@ -1350,7 +1356,9 @@ turbo-frame[id^="chats_page_"] {
 }
 .chats-dock__list { list-style: none; margin: 0; padding: 4px 0; }
 .chats-dock__list .chats-row__link { padding: 9px 12px; gap: 10px; }
-.chats-dock__list .chats-row__link:hover { background: var(--chats-dock-hover); }
+@media (hover: hover) {
+  .chats-dock__list .chats-row__link:hover { background: var(--chats-dock-hover); }
+}
 .chats-dock__list .chats-avatar { width: 40px; height: 40px; font-size: 0.85rem; }
 .chats-dock__list .chats-row__title { font-size: 0.875rem; }
 .chats-dock__list .chats-row__subject { font-size: 0.6875rem; }
@@ -1371,7 +1379,9 @@ turbo-frame[id^="chats_page_"] {
   font-weight: 650;
   text-decoration: none;
 }
-.chats-dock__see-all:hover { background: var(--chats-dock-hover); text-decoration: underline; }
+@media (hover: hover) {
+  .chats-dock__see-all:hover { background: var(--chats-dock-hover); text-decoration: underline; }
+}
 
 .chats-dock .chats-empty { padding: 40px 20px; }
 .chats-dock .chats-empty__icon { font-size: 2rem; margin-bottom: 0.5rem; }
@@ -1453,7 +1463,9 @@ turbo-frame[id^="chats_page_"] {
 }
 .chats-window__icon::-webkit-details-marker { display: none; }
 .chats-window__icon svg { width: 18px; height: 18px; }
-.chats-window__icon:hover { background: var(--chats-dock-hover); color: var(--chats-text); }
+@media (hover: hover) {
+  .chats-window__icon:hover { background: var(--chats-dock-hover); color: var(--chats-text); }
+}
 .chats-window__back { display: none; }
 /* The host's thread actions (conversation_header_actions). */
 .chats-window__menu { flex: 0 0 auto; }
@@ -1475,7 +1487,9 @@ turbo-frame[id^="chats_page_"] {
   box-shadow: none;
 }
 .chats-window--unread :is(.chats-window__subject, .chats-window__icon, .chats-verified) { color: inherit; }
-.chats-window--unread .chats-window__icon:hover { background: color-mix(in srgb, currentColor 16%, transparent); color: inherit; }
+@media (hover: hover) {
+  .chats-window--unread .chats-window__icon:hover { background: color-mix(in srgb, currentColor 16%, transparent); color: inherit; }
+}
 .chats-window--unread .chats-window__header .chats-badge {
   background: var(--chats-dock-unread-text);
   color: var(--chats-dock-unread-bg);

data/app/controllers/chats/conversations_controller.rb

@@ -248,8 +248,13 @@ module Chats
     # page's own conversation frame, else the whole page around it (any
     # other frame of the page, the search's results among them, finds its
     # own part in it).
+    #
+    # The pane alone comes in turbo-rails' minimal frame layout, always (even
+    # under a `config.layout`): nothing of the host's page is rendered for
+    # Turbo to throw away. Its title travels on the pane (`data-title`,
+    # chats_page_title), since Turbo leaves <head> alone on a frame visit.
     def render_split_page
-      return render :pane, layout: false if pane_request?
+      return render :pane, layout: "turbo_rails/frame" if pane_request?
 
       load_inbox
       render :index

data/app/helpers/chats/engine_helper.rb

@@ -329,6 +329,21 @@ module Chats
       path.presence || chats_routes.conversations_path(with: Chats.inbox_with_sgid(messager))
     end
 
+    # The messaging page's title: the inbox's, or +conversation+'s.
+    # `config.page_title` when the host sets one, else the localized
+    # `chats.page_title.*`. ONE source for both ways a conversation opens:
+    # the bundled pages hand it to `content_for :title` on a full visit, and
+    # the two-pane page's pane carries it (`data-title`) for chats--split to
+    # give the tab when a row opens it, since Turbo leaves <head> alone then.
+    def chats_page_title(conversation = nil)
+      viewer = chats_current_messager
+      custom = Chats.config.page_title&.call(conversation, viewer)
+      return custom.to_s if custom.present?
+      return t("chats.page_title.inbox") unless conversation
+
+      t("chats.page_title.conversation", name: conversation.title_for(viewer))
+    end
+
     # The gem's bundled stylesheet (CSS-variable themed — see chats.css).
     # Called from the engine's own views; hosts that eject + restyle the
     # views with their own framework simply don't include it.

data/app/javascript/chats/split_controller.js

@@ -22,6 +22,16 @@ import { Controller } from "@hotwired/stimulus"
 // update of the list) would disable it again on a wide screen; the frame
 // keeps what the screen says.
 //
+// The tab's title follows the pane: Turbo leaves <head> alone when it
+// promotes a frame load to a visit, so the title would stay the previous
+// page's. The pane carries the page's title with it open (`data-title`,
+// chats_page_title: the same the full page gives `content_for :title`).
+//
+// The open conversation's row stops counting it unread as soon as it is
+// read (the pane's answer says the server read it, `data-read`; or its
+// thread reads it on screen, `chats:read`), without waiting for the list's
+// live refresh, which may be seconds away or not come at all.
+//
 // When the pane opens a conversation, its row becomes the current one
 // (aria-current="page", .chats-row--current) at once, exactly as the server
 // renders /messages/:id, instead of when the list next refreshes. And the
@@ -82,9 +92,33 @@ export default class extends Controller {
       }
       link.closest(".chats-row")?.classList.toggle("chats-row--current", current)
     })
+    const pane = this.frameTarget.querySelector(".chats-split__pane")
+    if (pane?.dataset.title) document.title = pane.dataset.title
+    if (pane?.dataset.read === "true") this.markRead(pane)
     this.arrive()
   }
 
+  // chats:read, from the pane's thread.
+  threadRead(event) {
+    const pane = event.target?.closest?.(".chats-split__pane")
+    if (pane) this.markRead(pane)
+  }
+
+  // The conversation's row, read: no count, no bold, as the next refresh
+  // will render it.
+  markRead(pane) {
+    if (!this.hasListTarget || !pane.dataset.path) return
+
+    const path = new URL(pane.dataset.path, document.baseURI).pathname
+    this.listTarget.querySelectorAll(`a[data-turbo-frame="${this.frameTarget.id}"]`).forEach((link) => {
+      if (new URL(link.getAttribute("href"), document.baseURI).pathname !== path) return
+
+      const row = link.closest(".chats-row")
+      row?.classList.remove("chats-row--unread")
+      row?.querySelector(".chats-row__bottom .chats-badge")?.remove()
+    })
+  }
+
   arrive() {
     const pane = this.frameTarget.querySelector(".chats-split__pane")
     if (!pane) return

data/app/javascript/chats/thread_controller.js

@@ -456,9 +456,14 @@ export default class extends Controller {
       this.pendingRead = true
       return
     }
+    // chats:read, once the server has it: the two-pane page clears the
+    // conversation's row (chats--split) without waiting for the list's
+    // live refresh.
     fetch(this.readUrlValue, {
       method: "POST",
       headers: { "X-CSRF-Token": csrfToken(), Accept: "application/json" }
+    }).then((response) => {
+      if (response.ok) this.element.dispatchEvent(new CustomEvent("chats:read", { bubbles: true }))
     }).catch(() => {})
   }
 

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

@@ -17,11 +17,22 @@
     The header stays outside it, so a refresh still brings it up to date
     (a mute, a renamed group).
 
+    data-title: the page's title with this conversation open
+    (chats_page_title, the same the full page gives `content_for :title`):
+    chats--split gives it to the tab when a row opens the pane, since Turbo
+    leaves <head> alone on a frame visit.
+
+    data-read: the server read the conversation as it rendered this (a row
+    clicked); chats--split then clears its row's unread count at once,
+    instead of when the list next refreshes. A pane rendered unread clears
+    it when its thread reads (the thread's chats:read event).
+
     Locals: conversation, participant, messages, more, first_unread_id,
     counterpart, read_pending (as in chats/conversations/_thread). %>
 <% title_id = dom_id(conversation, :title) %>
 <%= tag.section class: "chats-split__pane", "aria-labelledby": title_id,
-                data: { conversation_id: conversation.id } do %>
+                data: { conversation_id: conversation.id, path: conversation_path(conversation),
+                        title: chats_page_title(conversation), read: !read_pending } do %>
   <%= render "chats/conversations/thread_header",
              conversation: conversation, participant: participant, counterpart: counterpart,
              heading: :h2, title_id: title_id, back_path: conversations_path(**chats_inbox_filter) %>

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

@@ -50,6 +50,9 @@
     `.restore` visit that honors this. Requires the host layout to
     `yield :head` (the Rails convention); harmless no-op otherwise.
     https://turbo.hotwired.dev/handbook/building#opting-out-of-caching %>
+<%# The page's title, for a layout that shows `yield(:title)`: the inbox's,
+    or the open conversation's (chats_page_title, config.page_title). %>
+<% content_for :title, chats_page_title(@conversation) %>
 <% content_for :head do %>
   <meta name="turbo-cache-control" content="no-cache">
 <% end %>
@@ -149,6 +152,7 @@
                 controller: "chats--split",
                 action: "turbo:before-prefetch->chats--split#prefetch " \
                         "turbo:frame-load->chats--split#opened " \
+                        "chats:read->chats--split#threadRead " \
                         "turbo:before-morph-attribute->chats--split#keepEnabled"
               } do %>
     <nav class="chats-split__list" aria-label="<%= t("chats.inbox.title") %>" data-chats--split-target="list">

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

@@ -1,7 +1,9 @@
 <%# The answer to a row click on the two-pane messaging page: the request
     comes from the page's `chats_conversation` frame (Turbo-Frame header),
     so the answer is that frame with the conversation pane in it and
-    nothing else — no list, no layout (ConversationsController#show).
+    nothing else — no list, turbo-rails' minimal frame layout
+    (ConversationsController#show). The pane carries its title
+    (data-title), which chats--split gives the tab.
     Turbo swaps it into the frame and, the frame being
     data-turbo-action="advance", moves the address bar to /messages/:id. %>
 <%= turbo_frame_tag Chats::ConversationsController::PANE_FRAME do %>

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

@@ -4,6 +4,7 @@
     two-pane page's conversation pane render too — see that partial for how
     the live thread works). Under the default `:split`, /messages/:id is
     the two-pane page instead (index.html.erb). %>
+<% content_for :title, chats_page_title(@conversation) %>
 <%= chats_styles %>
 
 <%= render layout: "chats/conversations/thread",

data/config/locales/en.yml

@@ -1,5 +1,8 @@
 en:
   chats:
+    page_title:
+      inbox: "Messages"
+      conversation: "%{name} · Messages"
     inbox:
       title: "Messages"
       search_placeholder: "Search conversations"

data/config/locales/es.yml

@@ -1,5 +1,8 @@
 es:
   chats:
+    page_title:
+      inbox: "Mensajes"
+      conversation: "%{name} · Mensajes"
     inbox:
       title: "Mensajes"
       search_placeholder: "Buscar conversaciones"

data/lib/chats/configuration.rb

@@ -174,6 +174,14 @@ module Chats
     # suppress the badge on some messagers without touching the models.
     attr_reader :verified_badge
 
+    # ->(conversation, viewer) { String } — the title of the messaging page:
+    # the inbox (conversation nil) or a conversation. The bundled views
+    # give it to `content_for :title` (a layout doing `yield(:title)` shows
+    # it), and the two-pane page gives the tab the conversation's when a
+    # row opens it in the pane. nil (the default) is the localized
+    # `chats.page_title.inbox` / `chats.page_title.conversation`.
+    attr_reader :page_title
+
     def initialize
       @messager_class = "User"
       @parent_controller = "::ApplicationController"
@@ -210,6 +218,7 @@ module Chats
       @messager_url = ->(_messager) { nil }
       @message_signature = nil
       @verified_badge = nil
+      @page_title = nil
 
       @messager_display_name = lambda do |messager|
         messager.try(:display_name) || messager.try(:name) ||
@@ -335,6 +344,10 @@ module Chats
       @verified_badge = value.nil? ? nil : ensure_callable(value, "verified_badge")
     end
 
+    def page_title=(value)
+      @page_title = value.nil? ? nil : ensure_callable(value, "page_title")
+    end
+
     def messager_display_name=(value)
       @messager_display_name = ensure_callable(value, "messager_display_name")
     end

data/lib/chats/models/conversation.rb

@@ -449,11 +449,19 @@ module Chats
       field.to_s == "title" && title.present?
     end
 
+    # Whether anything was removed (see Chats::Message#remove_reported_field!):
+    # false for a title already gone, decided under the row lock.
     def remove_reported_field!(field)
       return false unless field.to_s == "title"
 
-      update!(title: nil)
-      true
+      with_lock do
+        next false if title.blank?
+
+        update!(title: nil)
+        true
+      end
+    rescue ActiveRecord::RecordNotFound
+      false
     end
 
     def report_visible_to?(viewer, field: nil)

data/lib/chats/models/message.rb

@@ -356,12 +356,28 @@ module Chats
     # A moderator removing a reported message body = the soft-delete
     # tombstone path, so the thread shows "Message deleted" instead of a
     # hole, and attachments are purged with it.
+    #
+    # Returns whether anything was removed: true only when it actually
+    # removed something (the tombstone, or the row under `deletion: :hard`);
+    # false for a message already deleted (by its sender, by an earlier
+    # decision), already gone, or whose body is already blank. moderate
+    # 1.0.0.beta3 and later take that as the truth and refuse a removal that
+    # removed nothing, rather than record "content removed" with a statement
+    # of reasons that would be false; earlier versions ignore the return
+    # value. Decided under the message's row lock, read again under it: two
+    # decisions taken at once cannot both see it standing.
     def remove_reported_field!(field)
       return false unless field.to_s == "body"
 
-      # Trust & Safety outranks a product lock: a closed conversation must
-      # never be a place reported content can hide.
-      soft_delete!(enforce_lock: false)
+      with_lock do
+        next false if deleted? || body.blank?
+
+        # Trust & Safety outranks a product lock: a closed conversation must
+        # never be a place reported content can hide.
+        soft_delete!(enforce_lock: false)
+      end
+    rescue ActiveRecord::RecordNotFound
+      false # hard-deleted meanwhile: nothing left to remove
     end
 
     # Only people *in* the conversation may report a message (a message

data/lib/chats/version.rb

@@ -1,5 +1,5 @@
 # frozen_string_literal: true
 
 module Chats
-  VERSION = "0.6.0"
+  VERSION = "0.6.2"
 end

data/lib/generators/chats/templates/initializer.rb

@@ -93,6 +93,14 @@ Chats.configure do |config|
   #
   # config.inbox_layout = :split
   #
+  # The messaging page's title (the bundled views give it to
+  # `content_for :title`, and the two-pane page to the tab when a row opens
+  # a conversation). nil: "Messages" / "Bob · Messages" (chats.page_title.*).
+  #
+  # config.page_title = ->(conversation, viewer) {
+  #   conversation ? "#{conversation.title_for(viewer)} | MyApp" : "Messages | MyApp"
+  # }
+  #
   # Encrypt message bodies at rest (ActiveRecord Encryption; requires
   # `bin/rails db:encryption:init`). Body search degrades when enabled.
   #

metadata

@@ -1,13 +1,13 @@
 --- !ruby/object:Gem::Specification
 name: chats
 version: !ruby/object:Gem::Version
-  version: 0.6.0
+  version: 0.6.2
 platform: ruby
 authors:
 - rameerez
 bindir: exe
 cert_chain: []
-date: 2026-10-18 00:00:00.000000000 Z
+date: 2026-10-19 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: activerecord
@@ -173,13 +173,6 @@ files:
 - app/views/chats/messages/locked.turbo_stream.erb
 - app/views/chats/shared/_unread_badge.html.erb
 - app/views/chats/shared/_verified_badge.html.erb
-- chats-0.3.1.gem
-- chats-0.3.2.gem
-- chats-0.4.0.gem
-- chats-0.4.1.gem
-- chats-0.4.2.gem
-- chats-0.5.0.gem
-- chats-0.5.1.gem
 - config/importmap.rb
 - config/locales/en.yml
 - config/locales/es.yml