hibiki_rails 0.5.0 → 0.6.0

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 5c47d1cec132b52f2a741ca77596ca90e524b348f385b0db5d2d2992ae0dba0c
-  data.tar.gz: 44505ec6d36cb48589f8d924819d3d6ee02b2fb0092b67e0bd0c9b8af316da1b
+  metadata.gz: d708875aa67bf5d9b9137ac8d9bb05cf23604db936011706d068ec0b7116429c
+  data.tar.gz: 941b16f996127706d699e8812cf712b755c0f833f7a04c9e71912844421645ba
 SHA512:
-  metadata.gz: 85985021ba53ce7e11eb4b6713905e8abee6c9e0c6babd36a1fd8debb06887994827cce847ae82a20df822d53ff14398be3f4515f416354ad1058f7562151037
-  data.tar.gz: 031d605405895afed00c8119eabf62e7e545213a059f2d7e424f78fc08623939e550231168d829131f494d7bec3e9fa352f151cf41514700d1c8a90e3a68f6a0
+  metadata.gz: 74175d980c70f1b4ea1bb9ba593ef9940326eccfce6c783ceefdebfb2a0659706faa1040393759549366c5880ea23459740e0f3f280e64fb47a4bc32a371f69c
+  data.tar.gz: c88a903f15b13516310beb32a7ed741942c49ae65823a6422fb36823400a9fea420ae08bd2fe047bc1d2e6ff3e38cef8f86c0665eeee6014e0f495c880ad90a4

data/CHANGELOG.md

@@ -4,6 +4,123 @@ The gem and the npm package are released in lockstep and share these version
 numbers — `app/assets/javascripts/hibiki.js` is a single copy served both ways,
 so importmap and bundler apps always resolve identical client code.
 
+## 0.6.0 — 2026-08-10
+
+### Added
+
+**`Hibiki::Rails.record_equals` — a per-signal comparator for ActiveRecord
+records.** `ActiveRecord#==` compares class and id only, so a stale record is
+`==` to its edited reload and a signal write carrying the fresh one is silently
+dropped. Pass the comparator per signal and the write goes through:
+
+```ruby
+state(:items, equals: Hibiki::Rails.record_equals) { fetch }
+```
+
+It compares class + `attributes`, recurses through arrays, and falls back to
+`==` for everything else. It needs hibiki 0.3.0's `equals:` (see the dependency
+change below), which is honored at both of the graph's equality gates — the
+write gate and the flush-time check — so a change that passes the comparator
+actually reaches the page. This is opt-in sugar that makes the snapshot pattern
+forgiving; "records stop at the boundary" stays the documented default, and a
+comparator still cannot see an in-place mutation that never enters the write
+path.
+
+**A development-mode warning for the write that pattern swallows.** When a
+`State` write is dropped by the default `==` but the old and new values'
+`attributes` differ — the classic silent-stale-UI debugging session — the log
+now says so and points at the docs. Development only (never test or
+production), zero semantic change: the write is still dropped.
+
+### Changed
+
+**The scaffold's row projection is gone — records now cross the boundary as
+frozen snapshots.** `app/models/book_row.rb` is no longer generated. The query
+object's `rows` returns real records, hardened at the boundary —
+
+```ruby
+def rows
+  @rows ||= window_scope.strict_loading.map { it.readonly!; it.freeze }
+end
+```
+
+— and the channels' `rows`/`row` deriveds compare them with
+`equals: Hibiki::Rails.record_equals`. What the `Data` projection's structural
+`==` used to provide, the comparator provides; what it could never provide, the
+freeze triple does: an attribute write raises `FrozenError`, `save` raises
+`ActiveRecord::ReadOnlyRecord`, and an unpreloaded association walk raises
+`ActiveRecord::StrictLoadingViolationError` instead of firing a lazy query off
+the graph thread. Views print a `belongs_to` label as `book.author&.name`
+directly, so **the scaffold no longer injects a `delegate` per `belongs_to`
+into the model** — the model injection is the `after_commit` ping alone. The
+member channel's fetch preloads its associations (`includes(...) +
+strict_loading`) for the same reason.
+
+Existing scaffolded apps keep working untouched: their `book_row.rb` and
+delegates are app code, and the runtime reads none of it. Re-running a scaffold
+with `--force` moves the resource over; the generator never deletes, so the
+orphaned `*_row.rb` stays on disk for you to remove.
+
+**The hibiki dependency floor is `~> 0.3`** (per-signal `equals:`, shipped in
+hibiki 0.3.0). Everything 0.2 provided still holds; generated channels now rely
+on the comparator being consulted at both equality gates.
+
+**The page control and the field-error line are shared partials now.** Each
+scaffold used to write its own copy per resource; both are presentation-only,
+so they are emitted once per app instead — `app/views/shared/_pagination.html.erb`
+and `_field_error.html.erb` (under `--phlex`: `Views::Shared::Pagination` and
+`Views::Shared::FieldError` in `app/views/shared/`). Everything resource-shaped
+reaches the page control as locals from the list partial. A second scaffold
+finds the files present and leaves them; if they were generated under a
+different `--css` style, a notice says so instead of silently restyling every
+other resource's control.
+
+**Pagination renders above the list as well as below**, so a long page starts
+with a control in reach. Both copies live inside the re-rendered fragment and
+carry distinct ids (`books_pagination_top` / `books_pagination`), so idiomorph
+updates them in place.
+
+Re-running a scaffold with `--force` moves the list over to the shared
+partials and prints a notice naming the now-dead per-resource copies — the
+generator never deletes them itself.
+
+**The form's error summary is a shared partial too** —
+`app/views/shared/_form_errors.html.erb` (under `--phlex`:
+`Views::Shared::FormErrors`), rendered by every scaffolded full-page form. The
+resource name comes off the record at render time, so one file serves every
+scaffold. Under `--css=tailwind` and `--css=daisyui` the block is styled as a
+red alert panel instead of the scaffold-stock `style="color: red"`, which
+`--css=none` keeps.
+
+### Fixed
+
+**The `hibiki_busy.css` import lands directly below `@import "tailwindcss";`**
+instead of at the end of the entry stylesheet — appending placed it after
+`@plugin` lines, and CSS requires every `@import` before any other statement.
+Also fixed: re-running a scaffold in a tailwindcss-rails app
+(`app/assets/tailwind/application.css`) duplicated the import on every run,
+because the idempotence probe checked the wrong path spelling.
+
+## 0.5.1 — 2026-08-08
+
+### Changed
+
+**Generator output and messages slimmed down.** The scaffold templates used to
+carry long design-rationale comments into every generated file; they are now
+one-to-three-line hints, with the docs holding the prose. The safety notes a
+user editing the file actually needs stayed: public channel methods are
+client-invocable actions, ActionCable's exact-arity rule, the untrusted
+subscribe param, Phlex omitting `false`-valued attributes, and the busy
+stylesheet's do-not-wrap-in-a-layer rule.
+
+The generators' status notices were shortened the same way — they still say
+what to do, just not why at essay length.
+
+No behavior change anywhere: no code inside any template moved, and neither
+the runtime nor the packaged client changed (the npm 0.5.1 exists only to keep
+the lockstep rule). Re-running a scaffold with `--force` rewrites the views
+with the shorter comments; that diff is the whole upgrade.
+
 ## 0.5.0 — 2026-08-05
 
 ### Added

data/lib/generators/hibiki/rails/css_variant.rb

@@ -87,10 +87,19 @@ module Hibiki
           spinner: "loading loading-spinner loading-xs",
           warning_text: "text-warning",
           error_text: "text-error text-sm mt-1",
+          # The full-form error summary. Plain Tailwind on purpose, so both
+          # styled variants share it via the merge — an addition (2026-08-09),
+          # not a transcription: the reference apps carried the scaffold-stock
+          # `style="color: red"` block, which --css=none still emits.
+          error_summary: "rounded-md border border-red-200 bg-red-50 p-4 mb-6",
+          error_summary_title: "text-sm font-semibold text-red-800",
+          error_summary_list: "mt-2 list-disc list-inside text-sm text-red-700",
           muted: "opacity-60 italic",
           muted_inline: "opacity-60",
           counts: "ml-auto text-sm opacity-70",
-          pagination_nav: "join mt-2 mx-auto flex justify-center w-fit"
+          # my-, not mt-: the control renders above the list as well as below,
+          # and the top copy needs the gap on its other side.
+          pagination_nav: "join my-2 mx-auto flex justify-center w-fit"
         }.freeze
 
         # DaisyUI is a plugin over Tailwind, and the merge says so literally:
@@ -135,7 +144,7 @@ module Hibiki
           muted: "text-gray-500 italic",
           muted_inline: "text-gray-400",
           counts: "ml-auto text-sm text-gray-500",
-          pagination_nav: "mt-2 mx-auto flex justify-center w-fit -space-x-px rounded-md shadow-sm"
+          pagination_nav: "my-2 mx-auto flex justify-center w-fit -space-x-px rounded-md shadow-sm"
         ).freeze
 
         # Every lookup misses, so every class argument is omitted entirely.

data/lib/generators/hibiki/rails/generator_helpers.rb

@@ -71,8 +71,7 @@ module Hibiki
         def wiring_hint
           return if hibiki_registered? && helpers_included?
 
-          say_status :hint, "the packaged client is not fully wired " \
-                            "(register line and/or Helpers include) — run: " \
+          say_status :hint, "the packaged client is not fully wired. Run: " \
                             "bin/rails g hibiki:rails:install", :yellow
         end
       end

data/lib/generators/hibiki/rails/install/install_generator.rb

@@ -103,8 +103,7 @@ module Hibiki
 
         def bundler_note
           say_status :skip, "#{IMPORTMAP} not found — with a JS bundler, " \
-                            "npm/yarn add hibiki-rails instead (it pulls in " \
-                            "@rails/actioncable)", :yellow
+                            "npm/yarn/bun add hibiki-rails instead", :yellow
         end
       end
     end

data/lib/generators/hibiki/rails/install/templates/hibiki_controller.js.tt

@@ -1,7 +1,4 @@
-// Registers the packaged hibiki client (the "hibiki-rails" module: the
-// engine's importmap pin, or the npm package in bundler apps) as the
-// "hibiki" Stimulus controller — the Ruby helpers hardcode that
-// identifier in data-controller. File-backed on purpose: `bin/rails
-// stimulus:manifest:update` re-derives this exact registration from the
-// filename, so it survives manifest rewrites.
+// Registers the packaged hibiki client as "hibiki" Stimulus controller.
+// `bin/rails stimulus:manifest:update` re-derives this,
+// so it survives manifest rewrites.
 export { default } from "hibiki-rails"

data/lib/generators/hibiki/rails/island/templates/channel.rb.tt

@@ -1,9 +1,7 @@
 # frozen_string_literal: true
 
 # Generated by hibiki:rails:island — a working mini-example: one state,
-# one derived, one action, one broadcasting effect. The concern owns the
-# actor, the root, the per-action batch, and the [channel_name, cid]
-# stream convention; this class is just the graph and its actions.
+# one derived, one action, one broadcasting effect.
 class <%= class_name %>Channel < ApplicationCable::Channel
   include Hibiki::Rails::Channel
 

data/lib/generators/hibiki/rails/island/templates/display.html.erb.tt

@@ -1,5 +1,4 @@
-<%%# The root id is the broadcast replacement key — keep it in sync with the
-    channel effect's target. %>
+<%%# The root id is the replacement key. Keep in sync with channel effect's target. %>
 <p id="<%= display_dom_id %>">
   count: <strong><%%= count %></strong> &middot; doubled: <strong><%%= doubled %></strong>
 </p>

data/lib/generators/hibiki/rails/island/templates/island.html.erb.tt

@@ -1,13 +1,9 @@
-<%%# Stamped through Hibiki::Rails::Helpers (hibiki_island / on) — never
-    write the underlying data attributes by hand, they are private to the
-    gem and version with its packaged JS. %>
+<%%# Reactive island generated by hibiki_rails %>
 <%% cid = local_assigns.fetch(:cid) { SecureRandom.uuid } %>
 <%%= tag.div(**hibiki_island(<%= class_name %>Channel, cid:)) do %>
   <%%= turbo_stream_from "<%= stream_name %>", cid %>
 
-  <%%# Paint-avoidance placeholder only: the controller subscribes AFTER the
-      Turbo stream above confirms, so the graph's first broadcast replaces
-      this. %>
+  <%%# Placeholder only: the graph's first broadcast replaces this. %>
   <%%= render "<%= view_dir %>/<%= file_name %>_display", count: 0, doubled: 0 %>
 
   <p><%%= tag.button("+1", **on(:increment)) %></p>

data/lib/generators/hibiki/rails/phlex/phlex_generator.rb

@@ -27,9 +27,8 @@ module Hibiki
         def warn_without_hibiki_phlex
           require "hibiki/phlex"
         rescue LoadError
-          say_status :warn, "hibiki_phlex is not in this bundle — the generated channel " \
-                            "calls Hibiki::Phlex.render_effect. Add `gem \"hibiki_phlex\"` " \
-                            "(and `gem \"phlex-rails\"` to render components from views).", :yellow
+          say_status :warn, "hibiki_phlex is not in this bundle. " \
+                            "Add `gem \"hibiki_phlex\"`.", :yellow
         end
 
         def create_channel
@@ -64,7 +63,7 @@ module Hibiki
         def register_hint
           return if hibiki_registered?
 
-          say_status :hint, "the packaged client is not registered — run: " \
+          say_status :hint, "the packaged client is not registered. Run: " \
                             "bin/rails g hibiki:rails:install", :yellow
         end
       end

data/lib/generators/hibiki/rails/phlex/templates/channel.rb.tt

@@ -1,9 +1,6 @@
 # frozen_string_literal: true
 
-# Generated by hibiki:rails:phlex — the component owns the state
-# (Hibiki::Reactive); the channel owns the transport. One render effect,
-# re-rendering THE SAME INSTANCE, its HTML transmitted over the channel's
-# own subscription and swapped in by the fragment's root DOM id.
+# Generated by hibiki:rails:phlex
 class <%= class_name %>Channel < ApplicationCable::Channel
   include Hibiki::Rails::Channel
 

data/lib/generators/hibiki/rails/phlex/templates/component.rb.tt

@@ -1,10 +1,6 @@
 # frozen_string_literal: true
 
-# Generated by hibiki:rails:phlex — a working mini-example. The component
-# is a plain Ruby object: Hibiki::Reactive gives it per-instance signals
-# read as ordinary method calls (no .value anywhere), Rerenderable lets
-# the channel's render effect re-render this same instance, and Helpers
-# stamps the client's wire protocol.
+# Generated by hibiki:rails:phlex
 class Components::<%= class_name %> < Phlex::HTML
   include Hibiki::Reactive
   include Hibiki::Phlex::Rerenderable
@@ -14,11 +10,10 @@ class Components::<%= class_name %> < Phlex::HTML
   derived(:doubled) { count * 2 }
 
   def view_template
-    # The root id is the swap key for transmitted fragments — page-unique.
+    # The root id is the swap key for transmitted fragments; keep page-unique.
     div(id: "<%= component_dom_id %>") do
       p { "count: #{count} · doubled: #{doubled}" }
-      # Inside the swapped fragment on purpose: the island's root-scoped
-      # delegation keeps the button working across replacements.
+      # The island's delegation keeps the button working across replacements.
       button(**on(:increment)) { "+1" }
     end
   end

data/lib/generators/hibiki/rails/phlex/templates/island_component.rb.tt

@@ -1,16 +1,14 @@
 # frozen_string_literal: true
 
-# The island wrapper: one channel subscription per render, identified by
-# a per-page-load cid. Render from any page:
-#
+# Generated by hibiki:rails:phlex
+# Render from any page:
 #   <%%= render Components::<%= class_name %>Island.new %>
 class Components::<%= class_name %>Island < Phlex::HTML
   include Hibiki::Rails::Helpers
 
   def view_template
     div(**hibiki_island(<%= class_name %>Channel, cid: SecureRandom.uuid)) do
-      # A throwaway instance as a paint-avoidance placeholder; the
-      # channel's long-lived instance takes over from its first transmit.
+      # Placeholder; the channel takes over from the first transmit.
       render Components::<%= class_name %>.new
     end
   end

data/lib/generators/hibiki/rails/scaffold/USAGE

@@ -8,9 +8,9 @@ Description:
     Everything is derived from the field list you pass, exactly as Rails'
     scaffold derives its own output. Stock `rails g scaffold` is untouched.
 
-    The generated index is live: search, filter, sort and pagination are signal
-    state, edits happen in place, and a write from anywhere — another tab,
-    another user, the plain controller, a console — repaints every open list.
+    The generated index is live: search, filter, sort, and pagination are all
+    reactive, edits happen in place, and changes from anywhere update every open
+    list.
 
 Example:
     bin/rails generate hibiki:rails:scaffold Book title:string author:references
@@ -19,7 +19,6 @@ Example:
         db/migrate/XXXXXXXXXXXX_create_books.rb
         app/models/book.rb
         app/models/book_query.rb
-        app/models/book_row.rb
         app/channels/books_channel.rb
         app/channels/book_channel.rb
         app/forms/book_form.rb
@@ -29,8 +28,7 @@ Example:
     And add to config/routes.rb:
         resources :books
 
-    Restart the server afterwards: Rails computes autoload paths from the
-    app/* glob at boot, and app/forms is new.
+    Restart the server afterwards if it is running — app/forms is new.
 
     Pass --phlex to emit Phlex components under app/views/books/*.rb instead of
     ERB templates. The view layer is the only thing it changes; it needs the

data/lib/generators/hibiki/rails/scaffold_controller/USAGE

@@ -1,28 +1,23 @@
 Description:
-    Generates a reactive CRUD resource for a model that ALREADY exists — the
-    overlay half of hibiki:rails:scaffold.
+    Generates a reactive CRUD resource for a model that already exists.
 
-    With no field list the model's own schema is read: columns and types,
-    belongs_to reflections, and the validators behind per-field live errors.
-    Pass fields explicitly to override that, or when the table has not been
-    migrated yet.
+    With no field list, the model's schema is used to determine columns, types,
+    associations, and validators. Pass fields explicitly to override this or
+    when the table hasn't been migrated yet.
 
-    The generated index is live: search, filter, sort and pagination are signal
-    state, edits happen in place, and a write from anywhere repaints every open
+    The generated index is live: search, filter, sort, and pagination are all
+    reactive, edits happen in place, and changes from anywhere update every open
     list.
 
-    Two models are MODIFIED. This one gets a delegate per belongs_to plus the
-    after_commit broadcast the whole thing hangs off; each model a belongs_to
-    POINTS AT gets the has_many half Rails' scaffold never writes, and a ping,
-    because a row prints the parent's label rather than its id. Both are
-    idempotent, both are announced, and anything already declared is left alone.
+    Two models are MODIFIED. This one gets an after_commit broadcast. The
+    related models get the missing has_many association and a ping so changes
+    are reflected here. Existing declarations are left alone.
 
 Example:
     bin/rails generate hibiki:rails:scaffold_controller Book
 
     This will create:
         app/models/book_query.rb
-        app/models/book_row.rb
         app/channels/books_channel.rb
         app/channels/book_channel.rb
         app/forms/book_form.rb

data/lib/generators/hibiki/rails/scaffold_controller/scaffold_controller_generator.rb

@@ -10,6 +10,7 @@ require_relative "../scaffold_parent_injection"
 require_relative "../scaffold_parent_notices"
 require_relative "../scaffold_phlex_helpers"
 require_relative "../scaffold_post_install"
+require_relative "../scaffold_shared_views"
 require_relative "../scaffold_transport_stylesheet"
 require_relative "../scaffold_schema"
 require_relative "../css_variant"
@@ -36,6 +37,7 @@ module Hibiki
         include ScaffoldParentInjection
         include ScaffoldParentNotices
         include ScaffoldPostInstall
+        include ScaffoldSharedViews
         include ScaffoldTransportStylesheet
 
         TEMPLATE_ROOT = File.expand_path("templates", __dir__)
@@ -100,7 +102,6 @@ module Hibiki
 
         def create_models
           template "query.rb.tt", query_path
-          template "row.rb.tt", row_path
         end
 
         def create_form
@@ -112,27 +113,26 @@ module Hibiki
         end
 
         def create_views
-          return create_phlex_views if phlex?
-
-          %w[index show new edit _form _list _controls _field_error].each do |view|
-            template "views/#{view}.html.erb.tt", view_path("#{view}.html.erb")
+          if phlex?
+            create_phlex_views
+          else
+            %w[index show new edit _form _list _controls].each do |view|
+              template "views/#{view}.html.erb.tt", view_path("#{view}.html.erb")
+            end
+
+            template "views/_row.html.erb.tt", view_path("_#{row_partial}.html.erb")
+            template "views/_row_form.html.erb.tt", view_path("_#{row_form_partial}.html.erb")
           end
 
-          template "views/_row.html.erb.tt", view_path("_#{row_partial}.html.erb")
-          template "views/_row_form.html.erb.tt", view_path("_#{row_form_partial}.html.erb")
-
-          # Under --infinite-scroll the sentinel is inlined in _list and there
-          # is no page control at all — not an empty one.
-          template "views/_pagination.html.erb.tt", view_path("_pagination.html.erb") unless infinite?
+          # The page control and the field-error line, once per app — see
+          # ScaffoldSharedViews.
+          create_shared_views
         end
 
         # The model being scaffolded — one of two files this generator modifies
-        # that the app already owned.
-        #
-        # It is not optional, and not only about the ping: the row partial
-        # prints an association's LABEL, and the show page hands that partial a
-        # live record — so without the delegate the show page raises on arrival.
-        # Once we are editing the model anyway, the ping belongs here too.
+        # that the app already owned. It gets the after_commit ping, which is
+        # what makes another tab, another user, the plain controller and a
+        # console write all reach an open list.
         #
         # The alternative — printing it and hoping — fails SILENTLY: everything
         # works in one tab, and cross-tab plus out-of-band writes simply never
@@ -181,11 +181,9 @@ module Hibiki
         #
         # Private, because a public method on a Thor generator is a command.
         def create_phlex_views
-          %w[index show new edit form list row row_form controls field_error].each do |view|
+          %w[index show new edit form list row row_form controls].each do |view|
             template "views/#{view}.rb.tt", view_path("#{view}.rb")
           end
-
-          template "views/pagination.rb.tt", view_path("pagination.rb") unless infinite?
         end
 
         # Ordered so an app's own lib/templates/... override wins first, then

data/lib/generators/hibiki/rails/scaffold_controller/templates/daisyui/views/_pagination.html.erb.tt

@@ -1,62 +1,40 @@
 <%#- The ONE component with a per-variant template. DaisyUI expresses a page
      item as two tokens (`join-item btn`), so each of the six variants below can
-     repeat them inline — which is exactly what plain Tailwind cannot do. -%>
-<%%# locals: (page: 1, page_count: 1) -%>
-<%%# The numbered page control. It lives INSIDE the replaced fragment, like
-    every other control in there: page_count is a server number, so a
-    single-page list simply stops rendering this element. Placed outside the
-    fragment it would never be re-rendered and could only ever change its TEXT
-    (reactive values are textContent-only), leaving a control whose links point
-    at pages that no longer exist.
+     repeat them inline — which is exactly what plain Tailwind cannot do.
 
-    SCROLL. The links are anchors to the list, not buttons, and that IS the
-    scroll answer — the client only preventDefaults `submit`, so the click both
-    performs the action and does the browser's own fragment jump, which puts the
-    top of the list back in view exactly as a full page load would. No client
-    capability needed. data-turbo="false" keeps Turbo Drive out of it: a
-    same-page hash with Turbo off is a plain scroll, not a navigation.
-
-    No generation token — a page number is idempotent, so a double fire is one
-    write and one render.
-
-    `on` returns a { data: } hash, so an element needing its OWN data attributes
-    has to MERGE rather than splat: a bare ** after `data: { turbo: false }`
-    would silently replace it and the anchor would stop scrolling. %>
-<%%# PENDING. Nothing here asks for it: the client stamps data-hibiki-busy on
-    the control that fired, so the clicked page link dims itself while the trip
-    is out, and the swap that answers it destroys the attribute along with the
-    link. The bar above the list is the other half — the anchor jump has
-    already put it in view by then. %>
+     Emitted ONCE per app into app/views/shared/, so nothing here may name the
+     resource: everything resource-shaped (the wrapper id, the anchor target,
+     the page-number window) arrives as a local from the list partial. The
+     `--css=` marker below is how a later scaffold run detects a variant
+     mismatch — keep it. -%>
+<%%# locals: (page: 1, page_count: 1, pages: [], anchor:, id:) -%>
+<%%# Shared page control (--css=<%= css_variant %>), rendered above and below
+    every scaffolded list. The links are anchors to the list, so a click also
+    does the browser's own fragment jump; data-turbo="false" keeps Turbo Drive
+    out. `on` returns a { data: } hash — merge, don't splat, or the anchor
+    stops scrolling. %>
 <%% page_data = ->(n) { { turbo: false }.merge(on(:go_to_page, with: { page: n })[:data]) } %>
-<%%# The id-carrying wrapper stays put and stays BARE. It always renders, so
-    idiomorph always has a node to pair with, and it holds no layout classes of
-    its own — with no page control it is empty, and padding here would leave
-    dead vertical space on a list that has none. %>
-<div id="<%= pagination_dom_id %>">
+<%%# The wrapper always renders (so idiomorph has a node to pair with) and
+    stays bare — layout classes here would leave dead space when empty. %>
+<div id="<%%= id %>">
   <%% if page_count > 1 %>
     <nav<%= css_attr(:pagination_nav) %> aria-label="Pagination">
-      <%%# Prev/next stay rendered and go inert at the ends rather than
-          disappearing, so the control keeps its width across a page change —
-          one that reflows under the pointer is how you mis-click a list that
-          just repainted. A span, not a disabled link: there is no page to
-          name, so there is no action to stamp. %>
+      <%%# Prev/next go inert at the ends rather than disappearing, so the
+          control keeps its width across a page change. %>
       <%% if page == 1 %>
         <span class="join-item btn btn-disabled" aria-disabled="true">«</span>
       <%% else %>
-        <%%= link_to "«", "#<%= list_dom_id %>", class: "join-item btn", rel: "prev",
+        <%%= link_to "«", anchor, class: "join-item btn", rel: "prev",
                     "aria-label": "Previous page", data: page_data.(page - 1) %>
       <%% end %>
 
-      <%% <%= query_class_name %>.page_numbers(page: page, page_count: page_count).each do |n| %>
+      <%% pages.each do |n| %>
         <%% if n.nil? %>
           <span class="join-item btn btn-disabled" aria-hidden="true">…</span>
         <%% elsif n == page %>
-          <%%# aria-current is the only thing that tells a screen reader which
-              page it is on: the visual cue is a class, and the link text is
-              just a number either way. %>
           <span class="join-item btn btn-active" aria-current="page"><%%= n %></span>
         <%% else %>
-          <%%= link_to n, "#<%= list_dom_id %>", class: "join-item btn",
+          <%%= link_to n, anchor, class: "join-item btn",
                       "aria-label": "Page #{n}", data: page_data.(n) %>
         <%% end %>
       <%% end %>
@@ -64,7 +42,7 @@
       <%% if page == page_count %>
         <span class="join-item btn btn-disabled" aria-disabled="true">»</span>
       <%% else %>
-        <%%= link_to "»", "#<%= list_dom_id %>", class: "join-item btn", rel: "next",
+        <%%= link_to "»", anchor, class: "join-item btn", rel: "next",
                     "aria-label": "Next page", data: page_data.(page + 1) %>
       <%% end %>
     </nav>