A crowd you can find, and a phone 65px too narrow

Two reports against 1.6.0 and 1.7.0, both correct.

The crowd worked end to end and was, in practice, not there: the picker was
behind the ⋯ menu of a chat that already existed, and the switch was a card on
the Agents page, which made it read as an agent-chat feature. The picker is now
a button in the composer toolbar on both screens that include it, and on the
new-chat screen the choice rides along with the first message, so a chat can
start as a crowd instead of having to be converted into one. The instance
switch has its own page.

The width bug was the suggestion cards, exactly as reported. `.suggestions`
rendered 455px inside a 366px column, and the tree's standing rule applied on
its own made it worse -- 428px to 455px. A grid item carries `min-width: auto`,
which is a min-content floor, and a floor beats `width: 100%`; the floor is
measured while the percentage is indefinite, so `min(100%, …)` alone sends the
track to a card's max-content. Both halves now go on all four auto-fit grids,
and a test refuses either alone.

It survived four releases of narrow-width checking because the harness never
rendered that screen: `TestClient(app)` runs no lifespan outside a `with` block,
so the startup-seeded cards were missing from every shot ever taken of it. And
its overflow check skipped anything inside a scroller -- right for a table in
its own scroller, blind to the scroller itself, which `overflow-y: auto` makes
scroll sideways too. Both fixed; it now names the box and the child to blame.

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

src/lembas/api/admin_agents.py

@@ -66,10 +66,6 @@ async def agents_page(request: Request, db: Db, user: AdminUser, saved: bool = F
             # reply is allowed to set going on its own, and a nav entry for one
             # card would be worse than the near-miss.
             "subagents": settings_store.subagents(db),
-            # And a third group on the same page, for the same reason: a crowd is
-            # not an agent-chat feature either, but this is where somebody comes to
-            # find out what one turn is allowed to set going.
-            "crowd": settings_store.crowd(db),
             "saved": saved,
         },
     )
@@ -115,35 +111,6 @@ async def save_subagents(
     return RedirectResponse("/admin/agents?saved=1", status_code=status.HTTP_303_SEE_OTHER)
 
 
-@router.post("/crowd")
-async def save_crowd(
-    db: Db,
-    user: AdminUser,
-    enabled: bool = Form(False),
-    max_models: int = Form(4),
-    max_rounds: int = Form(2),
-    wall_seconds: int = Form(900),
-    collapse_agreement: bool = Form(False),
-) -> Response:
-    """Its own route, for the reason `save_subagents` gives above."""
-    settings_store.update(
-        db,
-        {
-            "enabled": enabled,
-            # Clamped here as well as on read. Every floor is one: a zero would be
-            # the feature switched off wearing the switch's clothes, and that is a
-            # thing to answer in one place.
-            "max_models": min(max(max_models, 1), 8),
-            "max_rounds": min(max(max_rounds, 1), 5),
-            "wall_seconds": min(max(wall_seconds, 60), 7200),
-            "collapse_agreement": collapse_agreement,
-        },
-        key=settings_store.CROWD,
-    )
-    log.info("crowd %s by %s", "enabled" if enabled else "disabled", user.email)
-    return RedirectResponse("/admin/agents?saved=1", status_code=status.HTTP_303_SEE_OTHER)
-
-
 @router.post("")
 async def save_agents(
     db: Db,