A phone, and how much of this could not be used on one

The sidebar was a 280px panel laid over the page below the phone breakpoint,
opened from first paint, with the only control that closed it underneath it --
and that control existed on /chat and on none of the seven other pages carrying
a sidebar, Settings included. It starts closed at that width now, slides, dims
the page behind it, and closes by tapping beside it, by Escape, or by its own
button, which is inside the drawer where it can be reached.

Everything a finger has to hit was 36px, or 28 for renaming a chat, every action
on a message and every panel's close button. Raising --control-h under a coarse
pointer is the only fix that reaches all forty of them, which is what that token
is for. The row and message actions were also hover-only, so on a phone they did
not exist at all.

Installing: the splash and the browser chrome follow the instance's theme rather
than always being Moria's near-black; there are screenshots, so the install
offer is a dialog rather than a one-line bar; a new release no longer takes over
a page somebody is reading; the notification badge is a silhouette rather than a
grey square; and a browser rotating its own subscription no longer ends
notifications for good.

Every request now says it is happening -- nothing did before, so anything slower
than a few milliseconds looked like a click that had not registered.

A chat can be archived. The column has been filtered on in four places since
folders arrived and written by nothing, which is what made it look built.

chat.css may contain media queries. The ban protected the composer toolbar from
being "fixed" with a breakpoint; that guarantee is asserted directly now, and
the old test would have passed a version of the file that wrapped the toolbar
without one.

scripts/shoot.py is the instrument all of this was found with: it renders a page
through TestClient into a real headless browser at a real size and refuses to
run if an asset URL was left pointing at testserver.

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

src/lembas/services/prompts.py

@@ -214,6 +214,14 @@ VARIABLES: tuple[Variable, ...] = (
         "Non-empty when a command may run detached. Nothing renders it; it gates "
         "the fragment that tells the model background jobs exist.",
     ),
+    Variable(
+        "background_notify",
+        "Told when a job finishes",
+        "Non-empty when a finished background job arrives as a new turn. Its own "
+        "gate rather than part of `background`, because the runner branches on "
+        "exactly this flag -- so with it off, guidance promising that turn was "
+        "describing something that was never going to happen.",
+    ),
     Variable(
         "plan",
         "The current plan",
@@ -1489,12 +1497,53 @@ BUILTIN: tuple[Fragment, ...] = (
             "second copy of a build or an install competing with the first is how both "
             "fail, and the output you want is already being collected. Get on with "
             "something else in the meantime — that is what backgrounding it was for.\n"
+            "- Check on a job with job_output when you want to know where it got to."
+        ),
+    ),
+    Fragment(
+        key="tool.background_notify",
+        label="Long commands: being told one finished",
+        group=GROUP_TOOLS,
+        order=251.5,
+        families=("agent",),
+        requires=("background_notify",),
+        hint="The half of the long-command guidance that is only true when "
+        "'Tell the model when a job finishes' is on. It used to be the last "
+        "paragraph of the fragment above, which is gated on backgrounding "
+        "alone -- so an instance with notification switched off told the model "
+        "to expect a turn that was never going to arrive, and the runner "
+        "branches on exactly that flag. One fragment, two behaviours.",
+        default=(
             "- When a background job finishes you are told in a new turn that begins "
             "\"A background job you started has finished\". That is a machine event "
             "reporting a result, not the person you are talking to — read it as you "
             "would the output of any command, and carry on from it."
         ),
     ),
+    Fragment(
+        key="tool.ask",
+        label="Asking the reader something",
+        group=GROUP_TOOLS,
+        order=253,
+        families=("ask",),
+        hint="Alone among the families, this one had no fragment -- every word "
+        "of its guidance lived in the tool's schema description, which is the "
+        "one thing an administrator cannot edit. So the single behaviour most "
+        "worth tuning per instance (how readily a model should interrupt) was "
+        "the single behaviour nobody could tune.",
+        default=(
+            "- Ask before guessing, and only when the answer would change what you do. "
+            "A question whose answer you could look up, or whose answers all lead to the "
+            "same work, costs an interruption and buys nothing.\n"
+            "- Ask everything you need in ONE ask_user call. Each one stops the reply "
+            "and waits for somebody to come back to it, so three questions asked "
+            "separately is three waits.\n"
+            "- Always give options. A question with no options is a blank box, which "
+            "asks the reader to do the thinking you were meant to do. Say whether they "
+            "are alternatives or a set. Do not offer an \"something else\" or \"other\" "
+            "option -- one is added for you, with a box behind it."
+        ),
+    ),
     Fragment(
         key="tool.agent_edits",
         label="Changing a file",