wizards 0.3.8 → 0.4.1

package/apps/runtime/dist/docs/dev/plugins/space.md

@@ -1,7 +1,7 @@
 ---
 title: The space
 description: Knowledge a plugin writes, a block and tools for every AI step of a space, texts in its search index, tools and cards of its assistant.
-version: 0.3.2
+version: 0.3.7
 ---
 
 A space holds what all its wizards share: a title, logos, colours, facts, and Knowledge —
@@ -93,6 +93,24 @@ server.registerSpaceContext({
 - A model on the device calls no tools: Apple Intelligence on a Mac, or the phone a run is
   followed on, which answers only steps that list no tools themselves. The step then gets the
   block without the tools.
+- `steps` says which steps get it: `["agent"]` when left out. `"html"` is the steps that write a
+  document or a dashboard as HTML; they get the block without the tools, after the space's
+  brand: how the brand's elements look, say.
+
+## The space's brand
+
+`server.spaces.brand(space)` reads what Info & brand holds of the space's look, for a block, a
+page or a model call in it:
+
+```ts
+const brand = await server.spaces.brand(space.id);
+// { name: "Mira Kaffee", colors: [{ name: "Primär", value: "#7a3e1d" }, …],
+//   fonts: [{ family: "Fraunces", role: "Headings", weights: [600] }, …] }
+```
+
+- The first colour is the accent. A font's `role` is what it is for, in the person's words.
+- `null` for a space the tenant does not have. The studio half gets the same as
+  `studio.useSpace().brand`.
 
 ## The search index
 

package/apps/runtime/dist/docs/dev/plugins/studio.md

@@ -1,7 +1,7 @@
 ---
 title: The studio half
 description: Pages, icons in the app bar, sections of the settings and of the space page — written in React, built once, drawn inside the studio.
-version: 0.3.4
+version: 0.3.7
 ---
 
 The studio half is `ui/plugin.tsx`. Its default export is a function; the studio calls it after
@@ -123,7 +123,7 @@ space page, behind the house icon (Space) in the app bar, shows them in four par
 
 | Part | `group` | Holds |
 |---|---|---|
-| Info & brand | `info` | Basics, Logos, Colours, Assets, Facts |
+| Info & brand | `info` | Basics, Facts, Logos, Colours, Brand assets |
 | Knowledge | `knowledge` | Documents, pages, tables and files with their Kategorien: what every AI step looks things up in |
 | Data | `data` | What the wizards keep |
 | Results | `results` | The runs that reached their result |
@@ -157,13 +157,50 @@ studio.registerSpaceSection({
 - `id` is the section's anchor: `/studio/space/data#contacts` opens the page there, and so does
   `/studio/space#contacts`. In Knowledge a section is a page of its own:
   `/studio/space/knowledge?show=s:<id>`, where `#<id>` leads too. Ids are unique on the whole
-  page; the space's own are taken: `base`, `logos`, `colors`, `assets`, `documents`, `facts`.
-- `studio.useSpace()` is a hook: `{ id, name, readOnly }`, or `null` while there is none. A
-  component that calls it draws again when the person picks another space. `readOnly`: the
-  space came from a local install, or nothing is built on this runtime; show it, change nothing.
+  page; the space's own are taken: `base`, `facts`, `logos`, `colors`, `typography`, `assets`,
+  `documents`.
+- `studio.useSpace()` is a hook: `{ id, name, readOnly, brand }`, or `null` while there is none.
+  A component that calls it draws again when the person picks another space, or changes its
+  brand. `readOnly`: the space came from a local install, or nothing is built on this runtime;
+  show it, change nothing. `brand` is what Info & brand holds of the look: `name`, `colors`
+  (`{ name, value }`, the first is the accent) and `fonts` (`{ family, role, weights }`).
 - Every wizard belongs to a space: a [run event](./events.md) names it as
   `wizard.projectId`. Keep it with what the plugin stores to show a space's part of it.
 
+### A part of the plugin's own
+
+A plugin whose subject is as big as one of the parts adds a part of its own: an entry in the
+parts' menu, with a page at `/studio/space/<id>` that the plugin draws whole. The part's menu
+lists what the page holds; `studio.useSpaceMenu` fills it while the page is drawn.
+
+```tsx
+function Library() {
+  const space = studio.useSpace();
+  const sections = useSections(space?.id);
+  studio.useSpaceMenu(sections.map((s) => ({ id: s.id, label: s.title, icon: Component })));
+  return sections.map((s) => (
+    <Anchor key={s.id} id={s.id}>
+      <Section title={s.title}>…</Section>
+    </Anchor>
+  ));
+}
+
+studio.registerSpacePart({
+  id: "library",
+  label: () => t("title"),
+  icon: Blocks,
+  after: "info",
+  component: Library,
+});
+```
+
+- `id` is the address: `/studio/space/library`. The parts' own (`info`, `knowledge`, `data`,
+  `results`) are taken.
+- `after` is the part it follows in the menu: `info`, `knowledge` or `data` (default).
+- Each entry of `useSpaceMenu` jumps to the element with its `id` in what the part draws, and
+  the menu marks the one in view. `Anchor` and `Section` draw them as the space's own parts do.
+- The component is drawn again for another space: keep the space's data under its id.
+
 ## Words in two languages
 
 The studio speaks German and English. `studio.i18n.register` takes the plugin's words and gives

package/apps/runtime/dist/docs/dev/plugins/styling.md

@@ -1,7 +1,7 @@
 ---
 title: Styles and components
 description: The studio's components, Tailwind against the studio's theme, and why a plugin's styles never leak.
-version: 0.3.2
+version: 0.3.7
 ---
 
 A plugin's page should look like the studio. Two things make that easy: the studio's components
@@ -34,6 +34,13 @@ and its theme.
 | `LinkedText` | A sentence with its web addresses as links, named by their host | `text` |
 | `cn(...)` | Joins class names, skipping what is false | |
 | `dateText(date, withWeekday?)` | A "YYYY-MM-DD" date in the studio's language: "Wed 14 Oct 2026" | |
+| `Anchor`, `Section` | A section of the space page and the spot the menu jumps to: the heading and its hint above the card | `id` on the anchor · `title`, `hint`, `save` (how the last save went), `action` (beside the heading), `plain` (the content draws its own cards) |
+| `InlineText` | Text edited where it stands, without a field's frame | `value`, `onChange`, `placeholder`, `label`, `maxLength`, `fit` (as wide as its text) |
+| `AddMenu` | The "Add" menu of a section's heading | `entries: { label, icon, onPick }[]` |
+| `AddRow` | A quiet "+ …" row at the end of a list | `label`, `onClick` |
+| `RuleRows`, `useRuleRows(saved)` | Rules as rows, each with its sign (bullet, do, don't, to check, important, numbered) | `rules` (what the hook gives), `placeholder`, `readOnly` |
+| `useAutosave(value, save)` | Saves a value a moment after it last changed; gives the state for a section's `save` | |
+| `newId()` | A short id for something new | |
 
 ```tsx
 import { Button, Card, Chip, Label, Input } from "@engenty-wizards/web/ui";

package/apps/runtime/dist/docs/user/command-line.md

@@ -1,7 +1,7 @@
 ---
 title: Command line
 description: The wizards command — start, setup, status, update — and the install's settings file.
-version: 0.3.2
+version: 0.3.4
 ---
 
 ## Commands
@@ -11,7 +11,8 @@ version: 0.3.2
 | `wizards` | What runs, and a menu: open the studio, restart and stop while it runs, "Start as service" or "Start here" (in this terminal) while it does not; update, which restarts what runs into the new version; "Service settings" (start at login); connect AI apps, status, setup, help. The first time, the setup runs first. Needs a terminal |
 | `wizards start` | Starts it and opens the studio. It runs in that terminal; Ctrl-C stops it. The first time, the setup runs first |
 | `wizards studio` | Opens the studio in your browser. When it does not run, it starts as a service first |
-| `wizards setup` | The guided setup again: an AI client to think with, the browser and ffmpeg, start at login, your AI apps |
+| `wizards setup` | The guided setup again: your account, an AI client to think with, the browser and ffmpeg, start at login, your AI apps. `--local` leaves the account out ([Local only](./local-only.md)) |
+| `wizards account` | How the install stands to your account: signed in as whom, which team, the credits. `sign-in` shows a code and opens the browser; `sign-out` disconnects the install |
 | `wizards open` | Lets this browser into the running studio. `--print` only shows the link; it works once, within a minute |
 | `wizards status` | What is installed and what runs, with the browser the app uses for PDF, PNG and websites |
 | `wizards doctor` | Status, and what is wrong |

package/apps/runtime/dist/docs/user/create-account.md

@@ -0,0 +1,47 @@
+---
+title: Create an account
+description: Your team, its space and your wizards live in your account at engenty.ai. Sign up with an invitation code, answer four questions, build.
+version: 0.3.4
+---
+
+engenty wizards is in a closed beta: a new account needs an invitation code. "Get started" on
+[engenty.ai](https://engenty.ai) takes your e-mail and puts you on the list; the code comes by
+mail as soon as a seat is free. With a code, the same step opens the sign-up.
+
+## Sign up
+
+1. Type the code at [account.engenty.ai/sign-up](https://account.engenty.ai/sign-up). The link
+   in the invitation mail has it filled in.
+2. Sign in with Google, GitHub, or a link by mail. There is no password.
+3. The studio opens at [engenty.ai/studio](https://engenty.ai/studio).
+
+Your account is a **team**: it holds your credits, your spaces and, on the Team plan, your
+colleagues. It starts with credits, some of which end on a date; the account pages at
+[account.engenty.ai](https://account.engenty.ai) show them.
+
+## The first visit
+
+The studio asks four things, one per page. Each but the first can be skipped and changed later.
+
+| Page | Asks | Goes to |
+|---|---|---|
+| Who you are | What your team is called: your company, your club, or just your name | The team's name at account.engenty.ai |
+| About you & your brand | Your website. engenty reads your name, what you do, your logo and colours from it; or you write a line about yourself | [Space → Info & brand](./space.md#info--brand) |
+| Knowledge | Documents the wizards may look things up in: price lists, your terms, an FAQ | [Space → Knowledge](./space.md#knowledge) |
+| Your space | Nothing: it explains the space that holds all of this, "Meine Wizards" | — |
+
+Then "Build your first wizard" opens the studio's start: describe a task in a sentence, or pick
+a template. See [Build a wizard](./build-a-wizard.md).
+
+## What the cloud does
+
+- Wizards built here run behind a link that works day and night, on the team's credits.
+- Share links, the tag for your website, QR codes and the channels of [Test and share](./test-and-share.md) work as on an install.
+- What the wizards think with is the team's: [Models and account](./models.md).
+
+## Also on your computer
+
+The same account works on your own computer: [install](./install.md) engenty wizards there and
+sign in during the setup. It thinks with your Claude, ChatGPT, Gemini or Cursor subscription,
+reads your local files and browses for you; what you publish there runs in the cloud too, behind
+the same links. "Also on your computer" on the studio's start page mails you the command.

package/apps/runtime/dist/docs/user/first-start.md

@@ -1,7 +1,7 @@
 ---
 title: First start
 description: Choose what engenty wizards thinks with. The studio opens once a test call works.
-version: 0.3.2
+version: 0.3.4
 ---
 
 The first page of the studio is the setup, "Choose your Engine". It asks one thing: what should
@@ -9,10 +9,18 @@ engenty think with?
 
 ![The setup: choose the engine, an installed AI client or your own keys](../../assets/setup.png)
 
+## Your account
+
+Above the engines stands your account: signed in during the [install](./install.md), it shows
+your name, your team and your credits, and your team's space is on this computer. Not signed in
+yet, "Sign in" opens your browser for it; an install that is [local only](./local-only.md)
+shows nothing here.
+
 ## Choose your engine
 
 | Engine | Runs on | Needs |
 |---|---|---|
+| engenty credits | Your account's credits, like in the cloud | An account signed in. Shown only then |
 | Claude Code | Your Claude subscription | The client installed and signed in |
 | Codex | Your ChatGPT subscription | The client installed and signed in |
 | Gemini CLI | Your Google account | The client installed and signed in |

package/apps/runtime/dist/docs/user/index.md

@@ -1,7 +1,7 @@
 ---
 title: User Guide
 description: Install engenty wizards, build a wizard, run and share it.
-version: 0.3.2
+version: 0.3.4
 ---
 
 engenty wizards turns something you do again and again into a wizard: pages that ask what it
@@ -17,30 +17,34 @@ briefing, an invoice, a quote, a damage report.
 | **Describe it** | Say in plain words what the wizard should do. The assistant builds the flow; you see it as a diagram and change any step. |
 | **Let AI steps work** | They research the web, write, draw images, render video, read PDFs, scans and mails, build documents and dashboards, and write into other services. Anything that changes an account asks first. |
 | **Share a link** | Anyone runs the wizard in a browser, on a phone too. Results download as PDF, Word, HTML, Markdown, PNG, MP4, MP3, CSV, Excel or JSON, or go out as a link. |
-| **Keep it on your machine** | It thinks with Codex, Claude Code, Gemini CLI or Cursor Agent on your own subscription, with your own keys, or with a local model. Wizards and results stay in a folder on your computer. |
+| **In the cloud, or on your computer** | Sign up and build in the browser; links run on your team's credits. Or install it on your computer: it thinks with Codex, Claude Code, Gemini CLI or Cursor Agent on your own subscription, with your own keys, or with a local model, and your files stay with you. |
 
 ## Where to start
 
-1. [Install](./install.md) it: one command on macOS or Linux.
-2. At the [first start](./first-start.md), choose what it thinks with.
-3. [Build a wizard](./build-a-wizard.md) from a sentence or a template.
-4. [Test and share](./test-and-share.md) it.
+1. [Create an account](./create-account.md) at engenty.ai, with an invitation code.
+2. [Build a wizard](./build-a-wizard.md) from a sentence or a template.
+3. [Test and share](./test-and-share.md) it.
+4. Also on your computer: [install](./install.md) it there, signed in to the same account, and at the [first start](./first-start.md) choose what it thinks with.
 5. Use it from your [AI apps](./ai-apps.md): Claude Desktop, Cursor, Codex and others.
 
 ## Words used here
 
 | Word | Means |
 |---|---|
-| Studio | Where you build wizards: `/studio` of your install |
+| Account | You, signed in at engenty.ai with Google, GitHub or a link by mail |
+| Team | What the sign-up creates: it holds your credits, your spaces and, on the Team plan, your colleagues |
+| Space | What all your wizards know and produce: name, logo, colours, facts, documents, data, results. A team's first one is "Meine Wizards" |
+| Studio | Where you build wizards: engenty.ai/studio, or `/studio` of your install |
 | Wizard | A flow of steps a person walks through on a link |
 | Step | One part of the flow: a page, an AI step, a review, the result |
 | Run | One person going through a wizard once |
-| Space | What all your wizards know: name, logo, colours, facts, documents |
 | Model class | The kind of model a step needs. Which model serves a class is a setting, not part of the wizard |
 
 ## Two places it runs
 
-This guide describes the install on your own computer: there you build. engenty.ai is the cloud:
-with an account, what you publish on your computer also runs there, behind a link that works
-while your computer is off, on the account's credits. The studio at engenty.ai shows those
-wizards and their runs and changes nothing ([Test and share](./test-and-share.md#in-the-cloud)).
+Your team, its space and your wizards live in your account. engenty.ai is the cloud: you build
+there in the browser, and links run day and night on the team's credits. Your computer can join:
+[install](./install.md) engenty wizards there, signed in to the same account, and it thinks with
+the AI clients and keys on that machine; what you publish there runs in the cloud as well
+([Test and share](./test-and-share.md#in-the-cloud)). An install without an account is
+[local only](./local-only.md).

package/apps/runtime/dist/docs/user/install.md

@@ -1,7 +1,7 @@
 ---
 title: Install
 description: One command on macOS or Linux. It brings its own Node.js and asks for no password.
-version: 0.3.2
+version: 0.3.4
 ---
 
 ## Install
@@ -18,6 +18,7 @@ command into `~/.local/bin` and then walks you through the rest:
 
 | Step | What it does |
 |---|---|
+| Your engenty account | Shows a code and opens the browser for the sign-in at account.engenty.ai (no account yet? the page takes an invitation code). Signed in, your team's space comes down to this computer, and what you publish here runs in the cloud too. "Later" skips it: `wizards account sign-in` does it any time. `--local` leaves the account out altogether: [Local only](./local-only.md) |
 | Something to think with | Looks for Codex, Claude Code, Gemini CLI and Cursor Agent and offers to install the ones that are missing. It proposes the one whose app (ChatGPT, Claude, Cursor) is on your Mac first, as that subscription is most likely yours already. You can also use an API key, [Ollama](https://ollama.com) or, on a Mac with Apple silicon and macOS 26, Apple Intelligence: the studio's [first page](./first-start.md) offers them |
 | A browser and ffmpeg | Names the browser for PDF and PNG exports and steps on websites: the first of Chrome, Edge and Chromium it finds (on a Mac also Brave). The app uses that one; [`CHROME_PATH`](./command-line.md#settings) picks another. Says whether there is ffmpeg for MP4 videos of animated widgets; with Homebrew it offers to install it |
 | Start at login (optional) | engenty wizards starts in the background when you log in, so links and AI clients always reach it. A LaunchAgent on a Mac, a systemd user service on Linux |
@@ -37,6 +38,7 @@ You install once; from then on you use the `wizards` command.
 | `wizards stop` | Stops it. Your data is kept |
 | `wizards status` | Whether it runs, and where |
 | `wizards restart` | Stops it and starts it again |
+| `wizards account` | How the install stands to your account; `sign-in` and `sign-out` |
 | `wizards` | A menu with all of it |
 
 The studio is at

package/apps/runtime/dist/docs/user/local-only.md

@@ -0,0 +1,38 @@
+---
+title: Local only
+description: An install without an account. Nothing leaves the computer; links answer on it only. The flag, what it means, and how to connect an account later.
+version: 0.3.4
+---
+
+An install normally signs in to your account during the setup: your team's space comes down to
+the computer, and what you publish runs in the cloud too. An install can also stay alone.
+
+## The flag
+
+```bash
+curl -fsSL https://engenty.ai/install.sh | bash -s -- --local
+```
+
+`--local` skips the account step of the setup and switches the account off for this install.
+On an install that is there already: `wizards setup --local`.
+
+## What it means
+
+- No account, nothing leaves this computer. Wizards, the space and results stay in
+  `~/.engenty/wizards/data` ([Your data](./data.md)).
+- Links answer on this computer only: `http://localhost:24368/w/…`. For others to open them,
+  run it [on a server](./server.md) of your own.
+- It thinks with your AI clients, your own keys, Ollama or Apple Intelligence
+  ([First start](./first-start.md)). Without an account, video and voice need a key of your own.
+- The studio shows no account surfaces: no sign-in offer, no credits, no cloud copy. The feature
+  switch `account` is off in the install's `.features` file; `wizards features` lists it.
+
+## Connect an account later
+
+```bash
+wizards account sign-in
+```
+
+The command shows a code and opens the browser for the sign-in; afterwards the install is
+connected, and the switch is on again. `wizards account` says how the install stands,
+`wizards account sign-out` disconnects it. Settings → Account in the studio does the same.

package/apps/runtime/dist/docs/user/meta.json

@@ -1,11 +1,12 @@
 {
   "title": "User Guide",
-  "description": "Install engenty wizards, build a wizard, run and share it.",
+  "description": "Create an account, build a wizard, run and share it, install it on your computer.",
   "root": true,
   "icon": "LifeBuoy",
   "pages": [
     "index",
     "---Start---",
+    "create-account",
     "install",
     "first-start",
     "---Wizards---",
@@ -24,6 +25,7 @@
     "---Your install---",
     "command-line",
     "data",
+    "local-only",
     "server",
     "troubleshooting"
   ]

package/apps/runtime/dist/docs/user/models.md

@@ -1,7 +1,7 @@
 ---
 title: Models and account
 description: Who does what your wizards ask for — an installed AI client, your own API keys, a local model, or credits.
-version: 0.3.2
+version: 0.3.4
 ---
 
 Settings → Models decides who does what your wizards ask for. On your computer it is yours; on
@@ -125,7 +125,8 @@ Text & reasoning) picks what builds your wizards in the editor's conversation:
 
 ## Account
 
-An account is optional. With it you
+An install normally signs in to your account during the setup ([Install](./install.md)); one
+without an account is [local only](./local-only.md). With an account you
 
 - use credits instead of your own keys (the editor's note about missing models says so where
   text, image or video models are missing),

package/apps/runtime/dist/docs/user/space.md

@@ -1,7 +1,7 @@
 ---
 title: Space
 description: What your wizards share and produce — who you are, what they look things up in, and the results of their runs.
-version: 0.3.2
+version: 0.3.7
 ---
 
 The house in the app bar, after the space's tile, opens your space: what all your wizards share,
@@ -13,7 +13,7 @@ the top leads back. On a phone the parts, a part's sections and the page take tu
 
 | Part | Sections | Used for |
 |---|---|---|
-| Info & brand | Basics, Logos, Colours, Assets, Facts | Who you are and how you look |
+| Info & brand | Basics, Facts, Logos, Colours, Brand assets | Who you are and how you look |
 | Knowledge | All, then each Kategorie, then the sections plugins add | What every AI step looks things up in |
 | Data | All data, then each wizard | Tables and pages the wizards keep |
 | Results | All results, then each wizard | The runs that reached their result |
@@ -23,10 +23,10 @@ the top leads back. On a phone the parts, a part's sections and the page take tu
 | Section | Holds | Used for |
 |---|---|---|
 | Basics | Title and "About": what you do, for whom, and the tone you write in | Texts sound like you. People who run a wizard see the title too |
+| Facts | Labelled values: address, VAT id, opening hours | Steps use them as written |
 | Logos | One or several, each with a description of what it is for | People see the main logo. The description tells a step what a variant is for |
 | Colours | Named colours, each with a note on its use | The first colour is the accent of documents, dashboards and public pages |
-| Assets | Images, graphics, videos, each with a description | AI steps place them in documents and choose by the description |
-| Facts | Labelled values: address, VAT id, opening hours | Steps use them as written |
+| Brand assets | Images, graphics, videos, sound, PDFs, fonts, Lottie and 3D files, in tabs | AI steps place pictures in documents and choose by the description |
 
 ## Knowledge
 

package/apps/runtime/dist/engine/steps.js

@@ -29,7 +29,6 @@ function today(ctx) {
         day: "numeric",
     });
 }
-const sectionTitle = (s) => s.description ? `${s.title} – ${s.description}` : s.title;
 function brandBlock(ctx) {
     const b = ctx.scope.brand;
     const parts = [
@@ -688,7 +687,7 @@ function placeableImages(step, ctx) {
         if (file) {
             out.push({
                 id: file.id,
-                label: `${p.tile ? "Pattern to tile" : "Background fill"}: ${p.name || file.name}${section ? ` (${sectionTitle(section)})` : ""}`,
+                label: `${p.tile ? "Pattern to tile" : "Background fill"}: ${p.name || file.name}${p.description ? ` – ${p.description}` : ""}${section ? ` (${section.title})` : ""}`,
             });
         }
     }
@@ -725,6 +724,8 @@ async function writeHtml(step, ctx, kind) {
         `Today is ${today(ctx)}.`,
         brandBlock(ctx),
         guide,
+        // What plugins hold for the space's look: a UI library, say.
+        ...(await spaceContextOf(ctx)).html,
         images.length
             ? `Images you can place with <img src="asset://ID">. Use those the brief asks for (a header image, a logo) and size them with CSS:\n${images.map((i) => `- asset://${i.id} — ${i.label}`).join("\n")}`
             : "",

package/apps/runtime/dist/engine/template.js

@@ -1,5 +1,5 @@
 import { allFields, isAudioValue, isLocationValue, itemsTotals, LOCALES, locationText, wizardLang, } from "@engenty-wizards/shared/definition";
-import { gradientCss, textStyleLine, } from "@engenty-wizards/shared/projects";
+import { fontLicenseWords, gradientCss, textStyleLine, } from "@engenty-wizards/shared/projects";
 import { listAsMarkdown } from "@engenty-wizards/shared/store";
 const TEMPLATE_RE = /\{\{\s*([^}]+?)\s*\}\}/g;
 function money(n, currency, locale) {
@@ -36,8 +36,8 @@ export function factLines(facts) {
     return facts.map((f) => `${f.label}: ${f.value}`).join("\n");
 }
 /**
- * The colours as a model reads them; a section's after the standard ones, with when to use them.
- * A gradients section names its gradients as CSS.
+ * The colours as a model reads them; a section's after the standard ones. A gradients section
+ * names its gradients as CSS, each with what it is for.
  */
 export function colorLine(colors, sections = [], gradients = []) {
     const line = (list) => list.map((c) => (c.name ? `${c.name} ${c.value}` : c.value)).join(", ");
@@ -45,29 +45,33 @@ export function colorLine(colors, sections = [], gradients = []) {
     return [
         line(colors.filter((c) => !known(c))),
         ...sections.map((s) => {
-            const head = s.description ? `${s.title} (${s.description})` : s.title;
             if (s.kind === "gradients") {
                 const own = gradients.filter((g) => g.section === s.id);
-                return own.length
-                    ? `${head}: ${own.map((g) => `${g.name || "gradient"} ${gradientCss(g)}`).join("; ")}`
-                    : "";
+                const one = (g) => `${g.name || "gradient"}${g.description ? ` (${g.description})` : ""} ${gradientCss(g)}`;
+                return own.length ? `${s.title}: ${own.map(one).join("; ")}` : "";
             }
             const own = colors.filter((c) => c.section === s.id);
-            return own.length ? `${head}: ${line(own)}` : "";
+            return own.length ? `${s.title}: ${line(own)}` : "";
         }),
     ]
         .filter(Boolean)
         .join(" · ");
 }
-/** The brand's type as a model reads it: its fonts, then its text styles. */
+/**
+ * The brand's type as a model reads it: its fonts with their licences, then its text styles. A
+ * licence that names its uses is binding.
+ */
 export function typeLines(fonts = [], styles = []) {
     const families = fonts.map((f) => {
         const weights = f.weights.length ? `, weights ${f.weights.join("/")}` : "";
-        return `- ${f.family}${f.role ? ` (${f.role})` : ""}${weights}`;
+        return `- ${f.family}${f.role ? ` (${f.role})` : ""}${weights}${fontLicenseWords(f)}`;
     });
     const scale = styles.map((s) => `- ${s.name}: ${textStyleLine(s, fonts)}`);
     return [
         families.length ? `Fonts:\n${families.join("\n")}` : "",
+        fonts.some((f) => f.uses?.length)
+            ? "A font's licence is binding: use a font only for what it may be used for, and set anything else in a system font."
+            : "",
         scale.length ? `Text styles:\n${scale.join("\n")}` : "",
     ]
         .filter(Boolean)

package/apps/runtime/dist/film/project.js

@@ -137,7 +137,12 @@ export async function prepareFilmFolder(step, ctx) {
                 const { data } = await projectFileContent(f.projectId, f.id);
                 const name = `patterns/${safeName(f.name.replace(/\.[^.]+$/, ""))}.${extFor(f.mime) === "bin" ? (f.name.split(".").pop() ?? "bin") : extFor(f.mime)}`;
                 await put(join(root, "brand"), name, data);
-                patterns.push({ file: name, name: p.name, tile: Boolean(p.tile) });
+                patterns.push({
+                    file: name,
+                    name: p.name,
+                    ...(p.description ? { description: p.description } : {}),
+                    tile: Boolean(p.tile),
+                });
             }
         }
         catch {
@@ -161,7 +166,7 @@ export async function prepareFilmFolder(step, ctx) {
         }
     }
     await put(join(root, "brand"), "brand.json", JSON.stringify({
-        note: "The space's brand. Colours are named by what they are for; the first is the accent. A logo's or a colour's section says when to use it; colorRules, logoRules and typeRules, where there are any, say how colours, logos and type may be used; text is set in the fonts.",
+        note: "The space's brand. Colours are named by what they are for; the first is the accent. A logo's section, a gradient's or a pattern's description says when to use it; colorRules, logoRules and typeRules, where there are any, say how colours, logos and type may be used; text is set in the fonts — a font with `uses` that leave out video is not used in a film: its text gets a system font.",
         name: b.name ?? "",
         about: b.about ?? "",
         colors: (b.colors ?? []).map((c) => {
@@ -172,6 +177,7 @@ export async function prepareFilmFolder(step, ctx) {
             ? {
                 gradients: b.gradients.map((g) => ({
                     name: g.name,
+                    ...(g.description ? { description: g.description } : {}),
                     section: b.colorSections?.find((x) => x.id === g.section)?.title,
                     css: gradientCss(g),
                 })),
@@ -182,7 +188,13 @@ export async function prepareFilmFolder(step, ctx) {
         ...(b.colorRules?.length ? { colorRules: ruleLines(b.colorRules).split("\n") } : {}),
         ...(b.fonts?.length
             ? {
-                fonts: b.fonts.map(({ family, role, weights }) => ({ family, role, weights })),
+                fonts: b.fonts.map(({ family, role, weights, license, uses }) => ({
+                    family,
+                    role,
+                    weights,
+                    ...(license ? { license } : {}),
+                    ...(uses?.length ? { uses } : {}),
+                })),
             }
             : {}),
         ...(b.textStyles?.length

package/apps/runtime/dist/manage.js

@@ -145,6 +145,18 @@ export async function tenantInfo(id, fresh = false) {
 export function forgetTenant(id) {
     tenants.delete(id);
 }
+/** Renames the team at the Manage-App; what it answers is the tenant as it stands now. */
+export async function renameTenant(id, name) {
+    const value = await call("PATCH", `/v1/tenants/${encodeURIComponent(id)}`, {
+        name,
+    });
+    tenants.set(id, { at: Date.now(), value });
+    return value;
+}
+/** The Manage-App mails the install command and the first steps to one of the team's people. */
+export function installMail(email, lang) {
+    return call("POST", "/v1/install-mail", { email, lang });
+}
 export function verifyKey(key) {
     return call("POST", "/v1/keys/verify", { key });
 }