Six things that looked like they worked

None of these fails loudly and two of them correct themselves if you reload,
which is why five were found by reading rather than by anybody reporting them.

The reply that lost its author is the one worth knowing about: the frame that
replaces a bubble when a reply lands was looking the models up as nobody, and
"no user" answers "no models" rather than "all models" -- so every finished
reply swapped the model's avatar for the plain mark and put the instance's name
where the model's should be, until the next page load put it back.

Beside it: a concurrency quota enforced on two of the six paths that start a
reply, including neither of the two most used; a custom theme whose success and
warning colours moved the text and left the background behind; a phone shell
sized to one viewport inside a document sized to another, which is the reported
scroll past the bottom of Settings; a whole conversation's Markdown rendered on
every page load and read by nothing; a skip guard inert since it was written;
and an endpoint nothing has ever called.

The scroll fix folded five near-identical scroller rules into one, which is
also where the containment they were all missing now lives.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

src/lembas/web/static/css/admin.css

@@ -15,14 +15,10 @@
    that one, silently, while the reader was lost in the other. Under
    `.admin-scroll` the body is now an ordinary block and the page scrolls as one.
 */
-.admin-scroll,
-.main > .tabs > .tabs__body {
-  flex: 1;
-  min-height: 0;
-  overflow-y: auto;
-  scrollbar-width: thin;
-  scrollbar-color: var(--border-strong) transparent;
-}
+/* What makes one of these scroll is `.scroll-region` in app.css, which both of
+   these selectors are listed in. Named there so the four declarations exist
+   once; named *here* is the reasoning above, which is about which element is
+   the scroller on which screen rather than about how a scroller behaves. */
 
 .page,
 .admin-page {