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/templates/base.html

@@ -142,15 +142,40 @@
 {#
   The version in the query string is what versions the worker's cache, so a
   release invalidates it without anyone remembering to bump a constant.
-  serviceWorker is absent over plain http, which is why a LAN install without
-  TLS silently offers no install prompt -- that is the browser's rule, not ours.
+
+  🚨 The outcome is *recorded*, not swallowed. serviceWorker is absent over plain
+  http and registration is refused on a page with a certificate error, and in
+  both cases the only symptom was that the Install button never appeared -- with
+  a hint beside it saying installing needs HTTPS, which is true and is not an
+  answer. A self-signed or private-CA certificate the phone does not trust looks
+  exactly like a browser that cannot install at all. `window.lembasWorker` is
+  what `app.js` turns into a sentence on the settings page.
 #}
 <script>
-  if ("serviceWorker" in navigator) {
+  window.lembasWorker = { state: "unsupported" };
+  if (!window.isSecureContext) {
+    /* Reported separately from an outright failure: the fix is different. */
+    window.lembasWorker = { state: "insecure" };
+  } else if ("serviceWorker" in navigator) {
+    window.lembasWorker = { state: "registering" };
     window.addEventListener("load", function () {
-      navigator.serviceWorker.register("/sw.js?v={{ version }}").catch(function () {
-        /* An install failure must never break the page it was loaded from. */
-      });
+      /* Two callbacks rather than .then().catch(): a throw inside the success
+         path must not be reported as a registration failure. */
+      navigator.serviceWorker.register("/sw.js?v={{ version }}").then(
+        function () {
+          window.lembasWorker = { state: "ready" };
+          document.dispatchEvent(new CustomEvent("lembas:worker"));
+        },
+        function (error) {
+          window.lembasWorker = {
+            state: "failed",
+            reason: (error && error.name) || "Error",
+            detail: (error && error.message) || ""
+          };
+          document.dispatchEvent(new CustomEvent("lembas:worker"));
+          /* An install failure must never break the page it was loaded from. */
+        }
+      );
     });
   }
 </script>