A personality belongs to a person

Owner's correction to 1.4.0: a model's character is per (model, person), and only
the description and the notes stay instance-wide. Two people talking to one model
are not talking to the same personality, and neither can see the other's.

The administrator's box becomes the DEFAULT, resolved by `personas.effective` as
a fallback and never as a layer -- two personalities at once contradict each
other with nothing to say which is losing, which is the reasoning behind "system
prompts replace, never stack". `persona_write` takes no argument naming a model
or a person; both come from the ToolContext, so it can only write the character
it has with whoever it is talking to, and it never touches the default.

Impressions move to their own table. Not a `kind` column: 1.4.0 shipped
`UNIQUE(model_key, owner_id)`, SQLite cannot alter a constraint and this schema
is additive-only, so a discriminator would leave an upgraded instance unable to
hold both rows for one pair. That leaves the first MANUAL_STEPS entry this
project has had -- the two shapes are indistinguishable, so nothing rewrites
them: a repair would be guessing at text that is read back in the first person.

TWO BUGS FROM A PHONE

`min-width` beats both `width` and `max-width` -- CSS clamps width to max-width
and then raises the result to min-width -- so `.canvas` and `.terminal` were
384px wide on every screen narrower than that, their `min(…, 100vw)` cap
overruled, and `.inspector` had no cap at all on a width that is a preference
draggable to 2400px. None of it scrolled sideways, because all three are
`position: fixed` and fixed overflow does not extend the scrollable area -- which
is exactly why the 1.1.0 narrow pass reported these pages clean. `min-width: 0`
in the overlay query, full width below the phone breakpoint, tablet column kept.

And the install button now says why it is absent. Measured against the live
instance: the manifest meets every Chrome criterion and the blocker is a
certificate from a private CA, so the origin is not trustworthy, the service
worker is refused and no install is offered. `base.html` had been swallowing that
with an empty catch -- which kept the page working, the reason it was there, and
threw away the only evidence. It now records the outcome and `app.js` turns it
into a sentence naming the certificate, which is the cause the old hint did not
mention.

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

src/lembas/web/static/css/app.css

@@ -650,6 +650,12 @@ input.visually-hidden[type="checkbox"] {
     inset: 0 0 0 auto;
     z-index: var(--z-panel);
     box-shadow: var(--shadow-lg);
+    /* Narrower than the panel wants is the normal case here, so the width has
+       to be allowed to give. `--inspector-width` is a *preference* -- somebody
+       can drag it to 2400px (LAYOUT_BOUNDS) -- and without this that number
+       arrives verbatim on a phone. There was no cap at all. */
+    width: min(var(--inspector-width), 100vw);
+    min-width: 0;
   }
 }
 
@@ -948,6 +954,27 @@ body.is-resizing .canvas__body { pointer-events: none; }
   }
   .terminal { width: min(var(--terminal-width), 100vw); }
   .canvas { width: min(var(--canvas-width), 100vw); }
+
+  /* 🚨 And the minimum has to give as well, which is the half that was missing.
+     `min-width` is resolved *after* `width` and `max-width` and wins over both
+     -- CSS sizes an element by clamping width to max-width and then raising the
+     result to min-width -- so `width: min(…, 100vw)` above was simply overruled
+     by `min-width: 24rem`. Both panels were 384px wide on every screen narrower
+     than that, hanging off the edge with their left-hand content cut away, and
+     no amount of capping the width would have changed it.
+
+     Because they are `position: fixed`, none of this scrolled the page: fixed
+     overflow does not extend the scrollable area. So the failure was content
+     you could not reach rather than a scrollbar, which is why it survived a
+     narrow-width pass that looked for sideways scrolling.
+
+     This is the tree's standing rule in another shape: a minimum wider than the
+     screen is the bug, and the minimum is what must give. */
+  .terminal,
+  .canvas,
+  .inspector {
+    min-width: 0;
+  }
 }
 
 .topbar {
@@ -1306,6 +1333,20 @@ body.is-resizing .canvas__body { pointer-events: none; }
 }
 
 @media (max-width: 48rem) {
+  /* A side panel on a phone is a sheet over the conversation, not a column
+     beside it. `max-width: 80vw` is right on a tablet -- you can still see what
+     you were reading -- and wrong here, because 20% of 360px is 72px of
+     conversation, which is not a view of anything. Full width and dismissible
+     is what the sidebar already does on the other side.
+
+     Set here rather than in the 64rem block so the tablet keeps its column. */
+  .inspector,
+  .terminal,
+  .canvas {
+    width: 100vw;
+    max-width: 100vw;
+  }
+
   /* The bar is the densest row in the application and the one with the least
      room: a toggle, a title, a model, and up to four panel buttons. Tighter
      padding and a smaller gap buy back about 24px, which is the difference