An instance that can be somebody else's

A name, a tagline, a logo, a favicon and the launcher icons derived from it; the
Middle-earth strings as data; themes as token sets; and a stylesheet for what
none of that reaches. All four are on one page, in one settings group.

The snapshot is a Jinja global over a process-level cache, because render() has
no session and four render paths never reach it at all -- the sign-in page, the
error pages, the offline page and the SSE fragments. A context value would have
had to be threaded through every one and would still have missed those. It being
a global is also what lets mark() branch on an uploaded logo without any of its
six call sites learning about branding; the macro that renders the sidebar link
is called brandlink now, because a macro imported as `brand` shadows the global
for the whole template and took out every page at once.

Defaults in code and overrides in the database, as the prompt fragments do, with
one difference stated in the module: an empty fragment means off, an empty
flavour string means the shipped wording. And blanked rather than dropped --
settings_store.update merges, so an omitted key leaves what was stored last time
and "I typed the default back in" would store something different from "I changed
nothing".

A custom theme sets a handful of tokens and inherits the rest, and the
inheritance is a CSS fact: tokens.css matches [data-base="shire"] as well as
[data-theme="shire"], so a custom light theme lands on parchment rather than four
light colours on near-black. Values are validated on read rather than on save,
because a theme written straight into the settings table still has to produce a
stylesheet that parses -- a `}` in a value ends the rule and silently breaks
every rule after it. The soft variants are derived from the accent, or a changed
accent leaves focus rings in the old hue and reads as half-working.

/branding.css is a route, not an inline block: an external stylesheet has no HTML
context to escape from. The link carries a content hash, so a save is not left to
the browser's cache, and it is deliberately outside the service worker's precache
list, which is versioned by the release.

The instance name moved off /admin/general rather than being duplicated there.
An upgrade keeps it: the general row is read as a seed exactly while the branding
row has never mentioned the name, which is `key in row` and not `row[key] is
truthy` -- the two read alike would resurrect the old name underneath a cleared
one.

The theme list stops being a hard-coded pair in five places. Every failure mode
in that area is silent, so it is driven under a DOM stub as well as tested.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

src/lembas/services/settings_store.py

@@ -32,6 +32,7 @@ AGENTS = "agents"
 IMAGES = "images"
 SCHEDULES = "schedules"
 SUBAGENTS = "subagents"
+BRANDING = "branding"
 
 
 def _general_defaults() -> dict[str, Any]:
@@ -40,7 +41,12 @@ def _general_defaults() -> dict[str, Any]:
         # When on, new accounts land in the `pending` role and cannot sign in
         # until an administrator approves them. Reserved for the users pass.
         "require_approval": False,
-        "instance_name": "LLeMbas",
+        # `instance_name` used to be here and now lives in the BRANDING group,
+        # with the rest of what makes an instance somebody else's. The key is
+        # deliberately not listed any more: an upgraded instance still has it in
+        # its stored general row, and `branding.snapshot` reads that once as a
+        # seed. Leaving a default here as well would give the name two sources
+        # and no answer to which one wins.
         # Applied to every chat that has no model or chat prompt of its
         # own. See services.chat.effective_system_prompt.
         "system_prompt": "",
@@ -382,9 +388,22 @@ _DEFAULTS: dict[str, Any] = {
     IMAGES: _images_defaults,
     SCHEDULES: _schedules_defaults,
     SUBAGENTS: _subagents_defaults,
+    # Whose instance this is. The defaults live in `services/branding.py`
+    # beside the code that reads them, because every one of them is paired with
+    # a label and a hint for the admin page and splitting the three across two
+    # modules is how one of them goes stale.
+    BRANDING: lambda: _branding_defaults(),
 }
 
 
+def _branding_defaults() -> dict[str, Any]:
+    """Imported inside the call: `services/branding.py` imports this module for
+    the group key, so a top-level import back is a cycle."""
+    from lembas.services import branding
+
+    return branding.defaults()
+
+
 def defaults(key: str = GENERAL) -> dict[str, Any]:
     """The built-in values for a settings group, with nothing stored applied."""
     factory = _DEFAULTS.get(key)