feat: give every Ekklesia screen one set of design tokens and elements

Modules have owned their own UI since ADR 0021, but the platform has never
said what that UI should look like. Every screen here — the Dashboard shell,
the display host, the module template — invented its own hex colours, font
stack, spacing, and radii, and they already disagreed. A module author had no
vocabulary for "the ordinary panel background", so the only available answer
was to invent one, and two modules would invent two.

Add `@ekklesia/design-tokens`: one validated, enumerable registry of semantic
tokens. A token declares a name, label, description, and default value; its
category and `--ekklesia-*` identifier are derived from the name, so it can
never claim one category while being named for another. Construction rejects
duplicates, malformed names, unknown categories, empty or overlong text, and
any value that is not a bounded literal — no declaration terminator, rule
block, comment, at-rule, `url(`, `!important`, escape, control character, or
markup. A registry that constructs can therefore be emitted as CSS without
escaping, because nothing needing escaping can be in it. That validation is
also what makes a future theme editor implementable rather than aspirational.

Add `@ekklesia/ui`: button, icon button, text input, select, checkbox, field
wrapper, panel, dialog, tabs, table and list primitives, badge, toast, and
empty/error/loading states — every value a token reference, with real
`:focus-visible` treatment and status that never depends on colour alone.
Deliberately small: an element earns its place when two consumers need it.

The stylesheet is a string rather than a `.css` file so the identical bytes
install into a document or an isolated artifact root, and so hover, disabled,
and focus-visible are real CSS rather than JavaScript approximations of them.

`pnpm boundaries` opens exactly two shared roles to modules, by name — every
other role stays rejected — and pins both design packages to the bottom of the
presentation stack. Both are browser-safe by construction, proven by a real
compile of module-shaped source in which `process.env` must fail to typecheck.

The shell installs the defaults at its document root for the Dashboard and the
display; custom properties inherit into module artifacts, so a module reads
`var(--ekklesia-…)` with nothing to import at run time and nothing for a host
to forget to pass.

Co-Authored-By: Claude Opus 5 <[email protected]>

surfaces/shell/src/browser/main.tsx

@@ -1,3 +1,5 @@
+import { installEkklesiaDesignTokens } from "@ekklesia/design-tokens";
+import { EkklesiaUiStyles } from "@ekklesia/ui";
 import { createRoot } from "react-dom/client";
 import { type HostAuthLanding, readAuthLanding } from "../auth-protocol.js";
 import type { EkklesiaHostConfig } from "../host-protocol.js";
@@ -60,6 +62,24 @@ if (!container) {
   throw new Error("The Ekklesia shell requires a #ekklesia-host element.");
 }
 
+/**
+ * The host root installs the platform's default theme once, at the document (ADR 0039).
+ *
+ * This is what makes the tokens available to *everything* on the page, including each module UI
+ * artifact mounted inside its own isolated root: CSS custom properties inherit through a shadow
+ * boundary, so a module reads `var(--ekklesia-…)` without the host reaching into the artifact or the
+ * artifact importing the host. Only the values live here — the platform ships no theme editor, and
+ * an installation that wants different values overrides these declarations at its own root.
+ */
+installEkklesiaDesignTokens(document);
+
 createRoot(container).render(
-  authLanding ? <HostApp authLanding={authLanding} config={config} /> : <HostApp config={config} />,
+  <>
+    <EkklesiaUiStyles />
+    {authLanding ? (
+      <HostApp authLanding={authLanding} config={config} />
+    ) : (
+      <HostApp config={config} />
+    )}
+  </>,
 );