@felloinnovations/brand-kit 0.5.0 → 0.5.3

package/AGENTS.md

@@ -1,4 +1,4 @@
-# brand-kit for coding agents (0.5.0)
+# brand-kit for coding agents (0.5.3)
 
 Read this before writing UI in any Fello project that uses `@felloinnovations/brand-kit`. It ships inside the
 package at `node_modules/@felloinnovations/brand-kit/AGENTS.md`. The HubSpot website (felix-theme) is out of scope:
@@ -22,9 +22,10 @@ All paths are under `node_modules/@felloinnovations/brand-kit/`.
 | `dist/fello.scoped.css` | The whole kit under a `.fello` root, for an app inside a host it does not own. |
 | `tokens/tokens.css` | Tokens only, as a Tailwind v4 `@theme`. |
 | `scripts/check-palette.mjs` | Checks an app's own palette file against the contract (Palettes, below). |
+| `scripts/check-drift.mjs` | Lists every line of an app's source that drifted from the kit, by file and line; with a baseline, fails CI only on new drift (Checking it, below). Also `npx brand-kit-drift`. |
 
 The same guide is hosted, always current, at `https://brand-kit-site-production.up.railway.app/latest/llms.txt`
-(pinned copies under `/v/0.5.0/`).
+(pinned copies under `/v/0.5.3/`).
 
 ---
 
@@ -170,10 +171,12 @@ public web page, email, deck, mockup). The face sets one of two layers, never mi
   already shipped a bug. Never `--radius-xl` or `--radius-2xl` for a product corner: those are Tailwind's.
 - **Semantic tokens over primitives**: `var(--color-text-heading)`, not `var(--color-brand-navy)`, for the same job.
   The semantic layer is what lets a colour be retuned, and what turns in dark.
-- **Check the catalog before building a component.** Never redraw one. If the kit has nothing for it, build it in
-  the consuming app from tokens and say what was missing, as an issue
-  (`https://github.com/FelloInnovations/brand-kit/issues/new?template=feedback.yml`). Do not add it to brand-kit and do not open a PR against it
-  from a consuming app; the kit's owners take it from there.
+- **Check the catalog before building a component. Never build a new one in an app** (Nikhil and Amit, 10 Nov
+  2026: built once in the kit, everyone uses it and raises what is missing). If the kit has nothing for it, compose
+  the nearest catalog parts (a `Card` with its band, a `Menu`, a `Table`, a recipe), file the gap as an issue
+  (`brand-feedback`, or `https://github.com/FelloInnovations/brand-kit/issues/new?template=feedback.yml`) and say in
+  the PR which issue the screen waits on. When the kit ships it, `brand-catchup` swaps it in. Do not add it to
+  brand-kit and do not open a PR against it from a consuming app; the kit's owners take it from there.
 - **Close but not exact**: pass `className` to a React export (merged through `tailwind-merge`, so your utility wins).
   Do not fork it.
 - **Layout**: one content edge per surface; numbers in fixed right-aligned columns; rows in a list share one
@@ -238,8 +241,22 @@ fold, enter and exit is already there. The situations, with markup, are in `desi
 
 ## Checking it
 
-The kit's own checks run in the kit's repo, for anyone changing a catalog component (only `check-palette.mjs` ships in
-the package; the rest show what "done" means for your own screens too):
+**In an app**, the drift check reads every file of its source and lists what drifted (raw colours, each marked
+against the nearest token, kit tokens redefined, kit classes restyled, px type, raw radii and shadows, hand-rolled
+motion, links underlined at rest, em dashes, local copies of kit components). Run it before calling UI done, and keep
+it in CI with a baseline so nothing new gets in while old drift is fixed:
+
+```sh
+node node_modules/@felloinnovations/brand-kit/scripts/check-drift.mjs src                          # the report; exit 1 on any drift
+node node_modules/@felloinnovations/brand-kit/scripts/check-drift.mjs src --write-baseline .brand-drift.json
+node node_modules/@felloinnovations/brand-kit/scripts/check-drift.mjs src --baseline .brand-drift.json   # CI: fails only on new drift
+```
+
+A line that is right as it is carries `brand-kit-ignore: <why>` on it or the line above. Updating to a newer kit is
+the `brand-catchup` skill (only what the releases changed), never `brand-adopt` again.
+
+The kit's own checks run in the kit's repo, for anyone changing a catalog component (only `check-palette.mjs` and
+`check-drift.mjs` ship in the package; the rest show what "done" means for your own screens too):
 
 ```sh
 node scripts/check-geometry.mjs --only Name1,Name2 --widths 320,390,1440   # alignment, spacing, centring, clipping, targets
@@ -249,6 +266,7 @@ node scripts/check-geometry.mjs --only Name1,Name2 --hover                 # res
 node scripts/check-geometry.mjs --only Name1,Name2 --hover --motion        # the same with motion on: a lift that only plays then
 node scripts/check-scope.mjs                                               # the scoped build leaks nothing; fello.css resets miss the host
 node scripts/check-palette.mjs [file.css]                                  # the built-ins, or a palette file, against the contract
+node scripts/check-drift.mjs --selftest                                    # the drift check catches every planted drift
 ```
 
 Open every screenshot the geometry check writes. In an app, run the same eye over the screen at 320, 390 and 1440,
@@ -282,5 +300,7 @@ size, radius, shadow or duration. Motion comes with the catalog's classes (`desi
 hand-roll a transition. Check the catalog (`design-system/components/`) before building a component. Write
 `text-[color:var(--x)]`, never `text-[var(--x)]`. Dark is opt-in (`data-theme`). This app's own colours are a palette
 (`data-palette`, `design-system/20-palettes.md`), checked with `scripts/check-palette.mjs` and shipped as its
-`--emit` writes it, never tokens retuned on `:root`. Run `design-system/18-checklist.md` before calling UI done.
+`--emit` writes it, never tokens retuned on `:root`. Run `design-system/18-checklist.md` and
+`node node_modules/@felloinnovations/brand-kit/scripts/check-drift.mjs src --baseline .brand-drift.json` before calling
+UI done. To take a newer kit, use the `brand-catchup` skill, not `brand-adopt`.
 ```

package/CHANGELOG.md

@@ -1,5 +1,115 @@
 # Changelog
 
+## 0.5.3 (11 Nov 2026)
+
+Madan's eighteen gaps from moving Marketing OS onto the kit (#15 to #32), and Hemanth's sidebar. Nikhil (10 Nov):
+Marketing OS shows the new UI to Stephen before Thursday, and apps never build a missing component with Claude, so the
+kit carries each of these. Everything adds; nothing that exists changes how it looks. Rulings in Decisions, 11 Nov 2026.
+
+- **New components**: `Calendar` (things on dates in a month or a week, an agenda in a narrow column; #23),
+  `PlanTimeline` (a plan's phases and tasks as bars on one date scale, today one line through every row; #24),
+  `InlineEdit` (words that become a field in place, nothing jumps; #25), `CommentThread` (remarks anchored to content,
+  one level of replies, mentions, resolve; #26), `TextDiff` (what was removed and what was added, by line or inline,
+  never by colour alone; #28).
+- **`AppShell`'s sidebar holds sections**: `__section` folds a page's own pages open in place, one level in, its
+  chevron turning; folded, a section is a button that opens its pages as a Menu panel beside the rail (`__fly`,
+  `__panel`); the person at the foot opens the account menu (`__me`). Enough for Customer Value to drop its own rail.
+- **Fields**: `DateInput` jumps to a far month or year (`__jump`) and has Today and Clear in a foot (`__foot`; #20), and
+  takes a time and a date with a time on the browser's own picker (#27); `Combobox` ticks the chosen row and keeps the
+  sunk ground for the keyboard's (#19); `ws-colour-field`, a swatch beside its hex, in `Input` (#29).
+- **Acts and tags**: `ws-btn-join` joins an act to a caret that opens a menu of its other forms (#22); `Chip --sm` (20
+  tall, 12 px words) for several tags together (#30); `Avatar --xs` (20) for dense pickers (#16).
+- **Surfaces**: `ws-dialog--mounted` with `ws-dialog__scrim`, so a dialog Radix mounts enters and leaves like the
+  native one, out on `data-state="closed"` (#18); `Fold` gains acts beside the summary, an end status, words shown only
+  while folded (`ws-fold__peek`) and three tones (#31); `ws-card__media` rounds its own corners and `ws-card--ring`
+  with `ws-card__tick` marks a chosen tile in a grid (#32); `ws-table__prose` wraps a short prose cell with no 200 px
+  floor (#21). A button card no longer carries the browser's default button padding.
+- **Status colours and two tokens**: error, warning, success and info map onto the kit's alert, needs, positive and
+  working tones (the "Status sets" table in Colour; #15). New `--ws-tint-alert` (the ground of an error status, with
+  `Banner --alert` and `Chip --alert`) and `--ws-shadow-rise` (a drawer rising from a pane; #17), both following every
+  palette, light, night and navy.
+- **Pinned links keep working**: `/v/0.5.2/` is kept as a snapshot (`hosted/v/0.5.2`). Pinned links now point at
+  `/v/0.5.3/`.
+
+**Upgrading from 0.5.2**: nothing to change; take it with `brand-catchup`. Then, on a yes, swap what the app hand-built:
+a calendar, a Gantt, an editable title, a comment list, a diff, a split button, a nested sidebar or a dialog's own
+animation for the kit's; a local warning or info colour for the status sets; a button card's padding reset can go.
+
+## 0.5.2 (10 Nov 2026)
+
+What Hemanth was missing when he built the Customer Value app on the kit (10 Nov call with Amit). Everything here adds;
+nothing that exists changes how it looks (the look stays locked at 0.5). Rulings in Decisions, 10 Nov 2026.
+
+- **Update with `brand-catchup`, never a second adopt.** A new skill brings an app already on the kit up to the newest
+  release: it reads this changelog from the app's version to the latest, bumps the package (or re-fetches a guest app's
+  vendored scoped CSS), applies each release's "Upgrading from" notes and nothing else, lists where the app hand-built
+  something the kit now has (and swaps it only on a yes), and proves nothing new drifted.
+- **`check-drift` lists every drifted line, so adopt stops stopping halfway.** `scripts/check-drift.mjs` ships in the
+  package (also `npx brand-kit-drift`): raw colours (each marked as matching a token, close to one, or no token),
+  Tailwind palette classes, kit tokens redefined, kit classes restyled, px type, raw radii and shadows, the
+  `text-[var(--x)]` trap, hand-rolled motion and hover lifts, links underlined at rest, em dashes in markup and local
+  copies of kit components, every one by file and line. `--baseline .brand-drift.json` makes it a CI check that fails
+  only on new drift; `brand-kit-ignore: <why>` keeps a line that is right; `--selftest` proves each rule. `brand-adopt`
+  is done only when it finds nothing left (or names every leftover), then leaves the baseline in CI; `brand-audit`'s
+  static half runs it first.
+- **A whole page's loader.** `Skeleton` documents the page ghost it promised: the page's own `PageBar` with its name
+  shown at once and its data-bound words and act as ghosts, then a board of tile and card skeletons where the real
+  ones land, so nothing jumps. No new CSS. List and board pages use `Table`'s and `KanbanBoard`'s own ghosts.
+- **`TrendLine` draws up to three series** in one unit on one axis: a `__series` box per extra line, navy, teal then
+  purple, a key (`__key--2`, `__key--3`), a column per series in the table, and a hover that reads every series for
+  the period. Several series are lines only. Different units, or one series more than four times another: two
+  TrendLines stacked in one card on the same periods, never two value axes.
+- **`Stepper` reads across and holds milestones.** `--across` lays a thing's stages left to right in equal columns, the
+  in-hand stage opening in view on a track that scrolls on a phone; `--milestones` puts dated points on one row with
+  the measure on each ("First value 15 days") and one quiet act on one not yet reached; `__late` says a stall or a late
+  milestone in needs-you words ("Stalled 40 days").
+- **One card for every board.** `KanbanBoard` documents the standard card (`ws-kanban-board__card`): the kind and its
+  figure with the time in stage (`__age`, `--stalled`), the title as the card's link covering it, meta, up to three
+  chips, a foot with people, a tally and one icon act, and one well act (`__card-act`) when the stage waits on the
+  person. Ticket and onboarding examples in the preview; a card-tall ghost for loading.
+- **Calvin's desk.** `ChatCard` gains four kinds: Email, Call and Text (the time at the head's right, the sender's words
+  quoted on a sunk plate, three lines at most; Reply, or Listen for a call) and Account (its standing as a rating chip,
+  its numbers on the stats plate, one navy act). Page recipe 25, "An agent desk: one thread per account", composes the
+  threads by account, the open thread, the daily briefing on top and the layouts at 1440 and 390 from catalog parts.
+- `check-geometry` counts a title whose cover spans its card as the card's target.
+- **Next.js imports `fello.css` from the root layout** (`brand-adopt`, `brand-new`): under Turbopack an `@import` in
+  `globals.css` put its font `@import` after rules and `next dev` failed on every page (#14).
+- **Apps never build a missing component** (Nikhil and Amit, 10 Nov): compose the nearest catalog parts, file the gap
+  with `brand-feedback`, name the issue in the PR; the kit builds it once and `brand-catchup` swaps it in. AGENTS.md,
+  How Claude decides and `brand-feedback` say so.
+- **Pinned links keep working**: `/v/0.5.1/` is kept as a snapshot (`hosted/v/0.5.1`). Pinned links in the docs now
+  point at `/v/0.5.2/`.
+
+**Upgrading from 0.5.1**: nothing to change; take it with `brand-catchup`. Then, in an app that hand-built any of these,
+swap on a yes: a page loader made of divs for the page ghost (`Skeleton`); a second chart line drawn in its own SVG for
+`TrendLine`'s `__series`; a horizontal stage track or milestone row for `Stepper --across` or `--milestones`; a board
+card per board (column rails, stage hues, underlined titles) for `ws-kanban-board__card`; email, call or text bubbles
+in a chat for the `ChatCard` message kinds. Add `check-drift` to CI with a baseline (`brand-adopt`, stage 8).
+
+## 0.5.1 (10 Nov 2026)
+
+Loaders are calm: the shimmer is one quiet grey. Amit looked at the skeletons in an app built on the kit and did not
+like the salmon, purple and green tints sweeping every grey ghost block (Decisions, 10 Nov 2026).
+
+- **The shimmer is one neutral tone.** `--ws-shimmer` is the ghost grey with a lighter pass of the same grey, no chart
+  hues, in light, night, the navy ground and every palette. North's timing stays: 1.8 s on `--ws-loop-shimmer` and
+  `--ws-ease-shimmer`, the 300 % band at 100 deg; still under reduced motion. Every ghost that wears the shimmer
+  (Skeleton, a pending Stat, StatTiles, Table, Well, TickStrip, ShareBar, ScoreHero and the rest) changes with no
+  markup change.
+- **One ghost grey at rest and in motion.** `--ws-shimmer-ground` is now `--ws-ghost` (#E3DFDB, the night's #273544),
+  so a ghost shows on the cream (1.29:1) and on the tray (1.13:1) alike, and the still ghost under reduced motion is the
+  same grey. Skeleton's own ground for a card's foot or band is gone.
+- **The chart ghost's colour band is gone.** `ws-skeleton__chart`'s bars are ghosts under the same shimmer; the band
+  that crossed the drawing in blend mode colour is removed (a neutral band there would paint nothing).
+- **The docs say so**: the Skeleton card and preview, the Motion card (the shimmer row is now Close, the chart band row
+  Not yet), Colour, Motion, Patterns, Charts, Choosing components and every loading line in the catalog.
+- **Pinned links keep working**: `/v/0.5.0/` is kept as a snapshot (`hosted/v/0.5.0`), so a page pinned to it still
+  loads after the bump. Pinned links in the docs now point at `/v/0.5.1/`.
+
+**Upgrading from 0.5.0**: nothing to change. A copy of the old gradient, or of #ECE8E4 as the shimmer's grey, should
+become `var(--ws-shimmer)` or `var(--ws-shimmer-ground)`. `StatusLine`'s working words keep their colours for now (open
+in Decisions).
+
 ## 0.5.0 (4 Nov 2026)
 
 The kit the whole team can trust: teams kept hitting alignment, spacing and placement bugs, and Seth (the designer) has

package/README.md

@@ -59,11 +59,17 @@ The plugin carries the same `fello-brand-kit` skill as claude.ai, plus four comm
 | Command | What it does |
 | --- | --- |
 | `/brand-kit:brand-audit` | Read-only report: raw values, drift from tokens, pages that cannot scroll, fields with no white ground, small targets, contrast, console errors. |
-| `/brand-kit:brand-adopt` | Migrates an existing app onto the kit, in stages, building between each. |
+| `/brand-kit:brand-adopt` | Migrates an existing app onto the kit, in stages, until the drift check finds nothing left, then guards it in CI. |
+| `/brand-kit:brand-catchup` | Brings an app already on the kit up to the newest release: only what the releases changed, never a second adopt. |
 | `/brand-kit:brand-new` | Scaffolds a new app already on the kit. |
 | `/brand-kit:brand-feedback` | Sends what the kit was missing or got wrong as one issue per gap on this repo. The other skills offer it when they finish. |
 
-Audit before adopt, so someone who does not read code sees what is wrong before anything is rewritten.
+Audit before adopt, so someone who does not read code sees what is wrong before anything is rewritten. Adopt once;
+after that, catch up.
+
+`npx brand-kit-drift src` (or `node node_modules/@felloinnovations/brand-kit/scripts/check-drift.mjs src`) lists every
+line of an app that drifted from the kit; `--baseline .brand-drift.json` makes it a CI check that fails only on new
+drift.
 
 ### In code
 
@@ -112,7 +118,7 @@ Then point the repo's agents at the guide: paste the block at the end of [AGENTS
 One line, pinned to a version:
 
 ```html
-<link rel="stylesheet" href="https://brand-kit-site-production.up.railway.app/v/0.5.0/fello.css">
+<link rel="stylesheet" href="https://brand-kit-site-production.up.railway.app/v/0.5.3/fello.css">
 ```
 
 Then use the `ws-*` classes and `var(--token)`; the markup for each component is in the gallery. `/latest/` exists
@@ -183,11 +189,13 @@ is no longer maintained. Only the kit's owners (Amit and Arpan) change tokens.
 
 ## Releasing
 
-CI publishes. Bump `version` in `package.json` (and `plugin/.claude-plugin/plugin.json`, and the pinned `/v/` links
-in `skill/SKILL.md`), run `yarn build` and `yarn skill`, commit, then push a tag that matches:
+CI publishes. Before the bump, keep the released hosted tree: `yarn hosted`, then copy `site-dist/v/<released
+version>` to `hosted/v/` (the gallery serves every snapshot there, so pinned links keep working). Bump `version` in
+`package.json` and the pinned `/v/` links (`AGENTS.md`, `skill/SKILL.md`, this README, `Starter`, guide 01; the plugin is
+unversioned), run `yarn build` and `yarn skill`, commit, then push a tag that matches:
 
 ```sh
-git tag v0.5.0 && git push origin v0.5.0
+git tag v0.5.3 && git push origin v0.5.3
 ```
 
 `.github/workflows/publish.yml` checks the tag matches `package.json`, builds, and publishes to npm through npm's

package/design-system/01-how-claude-decides.md

@@ -57,7 +57,7 @@ rest; a mockup about to ship takes all steps.
 | Where | Setup |
 | --- | --- |
 | A claude.ai artifact | inline `fello-core.css` plus the styles of only the components used, in one `<style>` (an artifact loads stylesheets only from Google Fonts; the whole `fello.css` is too big to paste) |
-| A plain HTML page or a static site | link the pinned file: `https://brand-kit-site-production.up.railway.app/v/0.5.0/fello.css` |
+| A plain HTML page or a static site | link the pinned file: `https://brand-kit-site-production.up.railway.app/v/0.5.3/fello.css` |
 | A Next, Vite or Turbo app that owns its page | install `@felloinnovations/brand-kit`, import `fello.css` (it sits in Tailwind's layers, so utilities win) or `tokens.css` (Tailwind v4), with the Instrument Sans `@import` first (before `@import "tailwindcss"`) or a `<link>`; read its `AGENTS.md` |
 | An app inside a host it does not own (a shared bundle, a platform's guest app), or any Tailwind v3 app | the scoped build: `fello.scoped.css`, or the string from `@felloinnovations/brand-kit/scoped` injected in a `<style>`, under `class="fello"` on the app's root and on every portal's root; nothing outside it changes; it carries no font, so link Instrument Sans (the `brand-adopt` skill has the steps) |
 | Claude Design or Slides | this system is the organisation's default; nothing to load |
@@ -108,8 +108,10 @@ Choose the recipe first and adapt it (Page recipes); then the pattern (Patterns)
 and any chart (Charts). Do not invent a new surface; marketing and product pieces never cross faces.
 
 **When no product has a precedent**, decide it from the system (its principles, tokens, the nearest rule) rather than
-leave it out. A switch is navy when on because the tab thumb and a selected toggle are. A new component is built from tokens in the consuming project and listed in
-Decisions with the rules it derives from, so the kit's owners can take it.
+leave it out. A switch is navy when on because the tab thumb and a selected toggle are. **A missing component is never
+built in the app** (Nikhil and Amit, 10 Nov 2026): compose the nearest catalog parts in its place, file the gap
+(`brand-feedback`) with the rules it would derive from, and name the issue in the PR. The kit's owners build it once,
+in the kit, and `brand-catchup` swaps it in.
 
 ## 5. Apply the foundations
 

package/design-system/03-colour.md

@@ -35,12 +35,12 @@ positive. Marks keep Seth's exact tones; a word in a tone takes its AA step on t
 | Under halfway marks, needs-you dots | `ws-chart-under-half`, `color-brand-salmon` | salmon #FF725C |
 | Needs work marks | `ws-chart-needs-work` | pink #F370A4 |
 | Alert marks | `ws-chart-alert` | #B1042F |
-| Chip tints: needs you, done, needs work | `ws-tint-needs`, `ws-tint-live`, `ws-tint-needs-work` | |
+| Chip and banner tints: needs you, done, needs work, alert | `ws-tint-needs`, `ws-tint-live`, `ws-tint-needs-work`, `ws-tint-alert` | |
 | Hover washes (navy at .03, .05, .06) | `ws-hover-faint`, `ws-hover`, `ws-hover-strong` | |
 | The ink of a wash, a ring or a line of your own; the tint of a drop | `ws-ink`, `ws-shade` | navy (in dark, the heading's light ink and black) |
 | A floating navy message (a toast, the note tip) and the footer, and their words | `ws-inverse`, `ws-on-inverse` | the act and its words; in dark the brand navy and white |
 | An off control (a switch's track at rest) | `ws-control-off` | #7F7F7F |
-| The loading shimmer's ground | `ws-shimmer-ground` | #ECE8E4 |
+| The loading shimmer's ground: the ghost grey, with a lighter pass of the same grey (never a chart hue) | `ws-shimmer-ground` | #E3DFDB (`ws-ghost`) |
 | A hero's glows, an assistant's working orb | `ws-glow-rose`, `ws-glow-pink`, `ws-glow-blue`, `ws-orb` | from the chart tones |
 | Focus | `ws-focus-color` | navy |
 | Behind a dialog | `ws-scrim` | navy 35% |
@@ -83,6 +83,24 @@ A strip of ticks or a bar takes the band's one tone; its words take the band's w
 
 Never a state by colour alone: a word or a mark goes with it.
 
+## Status sets: error, warning, success, info
+
+An app whose statuses are named error, warning, success and info (a badge, a banner, an inline message) maps each onto
+the kit's tones; there are no separate status colours (#15).
+
+| Status | Means | Words | Ground (a chip, a banner) | Mark, icon or edge | Banner, Chip |
+| --- | --- | --- | --- | --- | --- |
+| Error | something is wrong now: failed, rejected, blocked | `ws-word-alert` | `ws-tint-alert` | `ws-chart-alert` | `--alert` |
+| Warning | needs the person: something to fix, ending soon | `ws-word-needs` | `ws-tint-needs` | `ws-chart-under-half` (salmon) | `--needs` |
+| Success | done, passed, gone well | `ws-word-positive` | `ws-tint-live` | `ws-chart-finished` (teal) | `--positive` / `--live` |
+| Info | working, still running, a plain note | `color-text-interactive` | `ws-card-tint-blue` (a chip: the plate) | `color-text-interactive` | `--working` / `--accent` |
+
+- **No solid status fills.** A status is its tint, its words and its mark; a solid fill with white words is navy's alone
+  (a count, the one act), and salmon and mid blue are never a fill.
+- **A field's error stays "needs"**: a salmon edge and `ws-word-needs` words under the field (Input), since the person
+  fixes it. Error red is for a thing that went wrong, not a field to correct.
+- A neutral status ("Draft", "Scheduled") is the plain chip or the `neutral` banner, never a tone.
+
 ## Rules
 
 - **Navy is for words, the one button and a few named fills**: the tab or segmented thumb, a selected toggle, a checked
@@ -99,7 +117,8 @@ Never a state by colour alone: a word or a mark goes with it.
 - **An assistant's mark** takes one of the four tones and keeps it; no other colour names it.
 - **The AI colours** (`color-ai-*`) exist only inside an assistant's orb mark, if the product has one, and as faint washes
   in `ws-cool-glow` and `ws-team-glow` behind a page hero. No conic rings, purple glows or gradient text, except the
-  status line's word while an answer works (`StatusLine`, in the chart colours) and the loading shimmer.
+  status line's word while an answer works (`StatusLine`, in the chart colours). The loading shimmer is one neutral
+  tone, the ghost grey and a lighter pass of it, never the chart colours (0.5.1).
 - **People are neutral**: a disc of `ws-surface-sunk` with navy initials.
 - **Marketing pages** keep the kit's own marketing colours (its gradient button, `color-text-primary`); they never enter a
   product screen.

package/design-system/05-space-and-layout.md

@@ -136,7 +136,8 @@ A public page's `KitCard` is 4.
 
 Everything is flat at rest. What floats lifts on one family of shadows, a single soft drop each: a popover
 (`ws-shadow-pop`), a menu (`ws-shadow-menu`), a tooltip or hover card (`ws-shadow-tip`), a floating chat or a tile opened
-out of its slot (`ws-shadow-float`). In dark each carries a 0.5 px light rim. Buttons never lift. Layers: `z-dropdown`
+out of its slot (`ws-shadow-float`), and a drawer that rises from the bottom of a pane (`ws-shadow-rise`, the menu's
+drop cast upward: the pane's content sits above it, so the shade falls on it). In dark each carries a 0.5 px light rim. Buttons never lift. Layers: `z-dropdown`
 for menus and tips, `z-modal` for a dialog or drawer, `z-toast` for a toast.
 
 ## The frame

package/design-system/08-choosing-components.md

@@ -14,6 +14,7 @@ Components new in 0.5.0 are marked (new).
 | A label that may be wider than its column (a long link act, a translation) | `Button` with `ws-btn--wrap` | a button is one line and never shrinks beside its row's words; only an opted-in label wraps, in balanced lines (a link, text or ghost reads from its start) |
 | Words that act inside a sentence | `Button` link (mid blue: goes somewhere or shows more) or text (navy: a quiet act) | never a boxed button in running words |
 | Go somewhere | `Button` as a link (`ButtonLink`), or `ws-link` | a link is a link in the markup, whatever it looks like |
+| One act with a few other forms of itself (approve now, approve and schedule) | `Button` joined with its caret (`ws-btn-join`) opening a `Menu` | the plain act is the common one; other acts go in a three-dots `Menu` |
 | An act with no words (send, close, more, previous, next) | `IconButton` with a label | |
 | Turn something on or off, stays on | `Button selected` or `IconButton selected` (navy) | a toggle's state is `aria-pressed` |
 | Switch between a few views of one thing | `Segmented` (a switch) | inside the card it filters |
@@ -23,6 +24,7 @@ Components new in 0.5.0 are marked (new).
 | Know where you are in a deep hierarchy | `Breadcrumb` | the root crumb never shrinks; collapse the middle over four levels |
 | Move through a long collection | `Pagination` in the card's foot | |
 | A product of several pages that is not chat-first | `AppShell` (with its sidebar) and `TopBar` | the same rows, gutters and one navy button as the chat shell |
+| A page with a few pages of its own, in the sidebar | `AppShell`'s section (`__section`) | folds in place, one level only; folded, a panel beside the rail; never a hand-built sidebar |
 | A single page: an artifact, a report, an internal page | `Page` with a `PageBar` | no shell; its board holds the cards; start from `Starter` |
 | A thread or app page in place of the chat | `PageBar`'s 56 px thread header | the page's name, the app's name, its acts, the way back |
 | Open the one thing's details | a link `Card`, a `Well` row, a `CheckRow`, a table row | it opens in the panel beside the chat, a drawer, or the page's side pane |
@@ -38,9 +40,11 @@ Components new in 0.5.0 are marked (new).
 | --- | --- | --- |
 | Type a short value | `Input` with a label above | the error under it with a warning mark |
 | Type several lines | `TextArea` | |
+| Change one value where it is read (a title, a brief's fact) | `InlineEdit` | the same box and type at rest and editing; Enter or blur saves, Escape reverts; one value at a time |
 | Choose one of a few visible options | `Radio` group with a legend | up to about 5; make them easy to compare |
 | Choose one of many | `Select` | over 5 options, or a choice that changes the data rather than the view |
 | Choose one of many with search, or several as tags | `Combobox` | over about 20 options, or when the list is open-ended ("Create 'Pine Street'") |
+| Choose a picture, a template or an asset from a grid | `Card` buttons with `ws-card__media`, `ws-card--ring` when chosen | a group of `aria-pressed` buttons (several) or a `radiogroup` (one); the tick and the ring, never a tab under a tile |
 | A number with a unit or steps | `NumberInput` | |
 | A value on a range (a team size, a share) | `Slider` (new) | the value said in words beside it |
 | A password | `PasswordInput` | |
@@ -48,8 +52,10 @@ Components new in 0.5.0 are marked (new).
 | Choose several | `Checkbox` | independent choices; the label is part of the target |
 | A setting that applies at once | `Switch`, with "Saved" shown for a moment | the whole row is the target |
 | Talk or type to an agent | `Composer` | the one chat box; a drawer's small ask field is its compact look |
-| Pick a date or a range | `DateInput` (native first, with its popover month grid) | |
+| Pick a date or a range | `DateInput` (native first, with its popover month grid) | a far date: the month and year selects (`__jump`); an optional one: Clear in the foot |
+| Pick a time, or a date with a time | `DateInput` on `type="time"` or `type="datetime-local"` (the platform's picker) | a zone other than the person's is named in the label |
 | Search a list | `Input` with the search icon, in the card it searches | (Patterns) |
+| Set a colour (brand colours, a palette) | `Input`'s colour field: a swatch that opens the picker, the hex beside it | the hex validates as it is typed; an invalid one keeps the last good swatch |
 
 ## Showing things
 
@@ -69,17 +75,23 @@ Components new in 0.5.0 are marked (new).
 | What to do next, one row a person or thing ("who needs a nudge") | `ActionList` in a `Card` | the reason in words with its figures; one secondary act per row; a bulk act in the band |
 | What happened, in order | `Timeline` | |
 | Things moving through stages | `KanbanBoard` | a card glides between stages |
+| Where one thing is in its stages | `Stepper --across` | the in-hand stage ringed, a stall in needs-you words under it |
+| One thing's dated milestones (signed, first value) | `Stepper --milestones` | the measure on each milestone; a late one in needs-you words |
+| Things on dates (posts, sends, tasks, touches by day) | `Calendar` (new) | a month or a week, Monday first; a narrow column reads it as an agenda |
+| A plan's phases and tasks across their dates | `PlanTimeline` (new) | a bar from start to end on one scale, the phase in hand navy, today one line through every row |
 | A few facts about one thing | a `Plate` of label and value rows | inside the card |
 | A score that answers a report | `ScoreHero` (new) | the 96 px score, its strip, the rating word and one sentence; one per report |
 | A number that matters | `GoalTicks` (the 72 px number with its change chip) or `StatTiles` (several figures) | one hero figure per card; tiles only where the answer is numbers |
 | A key metric that opens across its row | `MetricTile` (new) | closed: label, figure, pace bar, foot; open: its chart and side column |
 | Progress against a pace or a target | `PaceBar` (new) | the fill, the pace mark, the figure in words beside |
 | A change since when | `ChangeChip` (in `Chip`) | an arrow and words, never colour alone |
-| A count, a kind, a state | `Chip` | a rating's tag takes the rating's tint and word |
-| A disclosure ("Why", "All details", a chapter) | `Fold` (card, quiet or row) | the one disclosure; never a custom accordion |
+| A count, a kind, a state | `Chip` | a rating's tag takes the rating's tint and word; several on one card or in one cell: `--sm` (20) |
+| A disclosure ("Why", "All details", a chapter) | `Fold` (card, quiet or row) | the one disclosure; never a custom accordion. An act in its head that must not toggle it, words shown only while folded, or a notice's tone: the card look's `ws-fold__act`, `ws-fold__peek`, `ws-fold--needs` |
 | A small group inside a card | `Section` | |
 | A tile in a bento, or the row of what an app can do | `Tile` | the tile row sits on the well, each tile a door or the step it waits on |
 | People | `Avatar` (and its stack) | |
+| People commenting on a thing, with replies, mentions and resolve | `CommentThread` | anchored to the stretch it is on; one level of replies; a mention of you on the needs tint |
+| What changed between two versions of a text | `TextDiff` (by line or inline) | never colour alone: a sign, a strike, an underline |
 | An agent | the assistant's own mark, drawn by the designer (no catalog piece) | still outside the chat (AI experiences) |
 | A short tip on hover or focus | `Tooltip` | never the only place a label lives; its navy note holds a cell's full words |
 | A reading of a chart's mark under the pointer | `HoverCard` (new) | a caret to its mark; the value is still written beside the mark |
@@ -94,10 +106,14 @@ Components new in 0.5.0 are marked (new).
 | Inspect one thing while keeping the list or chat | `Panel` (440 beside the chat, or a rimmed drawer beside a report) or a page's side pane | the same view component in each |
 | The chat as a bar, docked beside a page, floating or full screen | `ChatShell` (new) | one chat; it moves between its modes as itself |
 | One long conversation, marked by topic | `TopicRail` (new) with `ChatShell` | the topics as a rail; the conversation stays one thread |
+| An email, a call or a text in the chat | `ChatCard`'s message kinds (Email, Call, Text) | only one to read or answer now; the rest named in the agent's words with the source |
+| An account that needs a decision, in the chat | `ChatCard`'s Account kind | its standing as a rating `Chip`, its numbers on a stats plate, one navy act |
+| A thread per account, with a daily briefing | Page recipes, 25 (`ListDetail` of threads, the thread, `Composer`) | one chat kept by the thing it is about; the briefing is the one time the agent speaks first |
 | A short blocking task (confirm, name, one field) | `Dialog` | sparingly; head, content, foot with the one primary last |
 | A list of acts | `Menu` | the three dots open it |
 | A quiet confirmation of a background act | `Toast` | essential information lives elsewhere |
 | A state of the whole page or card (offline, a trial ending, a job done) | `Banner` | never for a field's error |
+| An error, warning, success or info status on a badge, a banner or a line | `Chip` or `Banner` in the status's tone | error `alert`, warning `needs`, success `positive` (a chip `live`), info `working` (a chip `accent`) (Colour, Status sets) |
 | Something that cannot be undone | `ConfirmDialog` | as Patterns' editing table says |
 | A page that is not there, offline, an error | `StatusScreen` | plain words, one act; never a status code |
 | Something that needs you later | a chat card in its app's chat and a row in Needs you | never a popup |
@@ -106,7 +122,7 @@ Components new in 0.5.0 are marked (new).
 
 | Need | Component | Rule |
 | --- | --- | --- |
-| Content on its way | `Skeleton` (the shimmer in the chart colours over ghost shapes) | never a spinner for content |
+| Content on its way | `Skeleton` (the shimmer, one quiet grey, over ghost shapes) | never a spinner for content; a whole page keeps its own bar, its name shown at once, over a board of card skeletons (the page ghost) |
 | An answer at work | `StatusLine` (new) | the agent, what it is doing, the step |
 | A long load with no figure | `LoadBar` (new) | it never claims to finish before it has |
 | A press waiting on its answer | `Button pending` | keeps its width; a second press waits; the button stays focusable |

package/design-system/09-charts.md

@@ -18,7 +18,7 @@ piece.
 | A key number that opens into its story | a tile: label, figure, pace bar or a mini chart (columns of the periods behind it, or a line with dots), foot; it grows across its row into a chart and a side column | `MetricTile` (new) |
 | Where a whole goes (a bill, a team's time) | one stacked bar, 1 px cuts between parts, a key under it | `ShareBar` (new) |
 | How a value changes over time, against a reference | a step line, the reference dotted, the gap between them hatched, events marked | `StepLine` (new) |
-| How a value moves over periods (a month's ARR, a week's calls), read on an axis | a line with its dots and the hatched area under it, or columns, switching between the two by a morph; a plan as a dotted salmon line | `TrendLine` (new) |
+| How a value moves over periods (a month's ARR, a week's calls), read on an axis | a line with its dots and the hatched area under it, or columns, switching between the two by a morph; a plan as a dotted salmon line; two or three series in one unit as lines with a key | `TrendLine` (new) |
 | How several groups do on several measures | lanes by measures, each cell a tone and a figure | `Heatmap` (new) |
 | Compare a few categories (calls by kind) | horizontal bars with a fade, the number and label at the right | `GoalBars` |
 | Compare a few categories where height reads better (a hero) | vertical tubes with the number on a stalk | `GoalTubes` |
@@ -33,8 +33,8 @@ piece.
 | Yes or no across a few sources | a matrix of tone cells | `Matrix` (new) |
 | A sequence or a wait | steps on a line that fills | `Stepper` |
 
-Do not use: a pie with more than three parts (make it bars or a `ShareBar`), a free line chart (two series or more, or a
-line with no axis: make it thin bars, a `TrendLine` of one series over periods, or a `StepLine` where a designer draws
+Do not use: a pie with more than three parts (make it bars or a `ShareBar`), a free line chart (more than three series,
+or a line with no axis: make it thin bars, a `TrendLine` of up to three series in one unit over periods, or a `StepLine` where a designer draws
 a bill or a level over time; a `MetricTile`'s mini line with dots for a rate that holds near its target), an axis or a
 grid where thin bars suffice, stacked bars
 across categories (make two rows; one `ShareBar` for one whole is fine), a donut for a single number (make it the goal
@@ -74,6 +74,9 @@ Seth draws most shares as ticks. The rules every strip follows:
   labels, 12 before the plot; a `TrendLine` keeps 0.5 px value rules and right-aligned value labels, 12 before the plot,
   its columns starting at zero.
 - **A hover card may add detail, never be the only reading**: the value is written beside the mark.
+- **One value axis, never two.** Series in different units, or one more than four times another, are two `TrendLine`s
+  stacked in one card on the same periods, each with its own axis and a key of one, the period names only under the
+  last. Up to three series that share a unit share one axis, a line each, with a key; a hover reads every series.
 - One chart per card; one hero figure per card; a change is a `ChangeChip` (in `Chip`).
 
 ## Data rules
@@ -89,7 +92,7 @@ Seth draws most shares as ticks. The rules every strip follows:
 
 ## States
 
-Loading and empty follow Patterns (a shimmer in the chart colours over the chart's ghost; the same card with its act).
+Loading and empty follow Patterns (the shimmer, one quiet grey, over the chart's ghost; the same card with its act).
 
 | State | How |
 | --- | --- |

package/design-system/10-patterns.md

@@ -58,7 +58,7 @@ moves. A state never changes a thing's size, its type size or its place, so noth
 | Focus | a 2 px navy ring 2 px outside (`ws-focus-color`); inside a dense row, a well, a list or a clipped container the same ring drawn inside (`ws-focus-inset`) | `:focus-visible` only; never `outline: none` without the ring (Accessibility) |
 | Selected, open, current | the ground changes (the sunk cream, or the well for a pill in an inset list), the words go navy or 600; a list's selected fill slides from the row it left; the dividers beside an inset pill drop | the row keeps its height and type size; `aria-selected`, `aria-current` or `aria-expanded` says it |
 | Pending | the control keeps its width and its words; the working dot sits in its padding on the one beat; it stays focusable (`aria-disabled`, `aria-busy`) and refuses a second press | from 100 ms (Latency above); words that say what is happening ("Saving") |
-| Loading | the region's ghost in the chart colours' shimmer, the size of what it stands for; its head shows at once | never a spinner for content; still under reduced motion, with a word |
+| Loading | the region's ghost under the shimmer (one quiet grey), the size of what it stands for; its head shows at once | never a spinner for content; still under reduced motion, with a word |
 | Disabled | dimmed (the component's own opacity), no pointer events, the reason said nearby | prefer leaving the act out, or keeping it focusable and saying why |
 | Others step back | while one row, part or tile is in focus, the rest dim (a matrix's other rows to 20%, a chart's other parts to `ws-dim`); the dimmed keep their grounds and dividers. A word that must stay readable steps to muted grey instead of fading (a heatmap's other squares fade their heat and status bar, their words stay AA) | the focused one never changes |
 

package/design-system/11-page-recipes.md

@@ -161,7 +161,8 @@ What a person sees the first time they open an app's thread (issue #12, Seth's v
    interactive). The row wraps; a tile is never narrower than 168.
 4. **The composer** at the foot, with a few starters (`SuggestionChip`).
 
-Nothing proactive arrives on a first open; the agent speaks when asked.
+Nothing proactive arrives on a first open; the agent speaks when asked. (The daily briefing, recipe 25, starts once
+there is data to brief on.)
 
 ## 23. A report with its drawer
 
@@ -209,6 +210,44 @@ Seth's Grow review inbox (Figma 313:2671).
 - **Keyboard**: arrow keys move through the list; Previous and Next move the item and the chosen row together.
 - **On a phone** the tiles stack, the list is the screen and the item is its own screen with Back.
 
+## 25. An agent desk: one thread per account
+
+An agent that works a book of accounts with the person (Calvin in Customer Value): one chat, its threads kept by the
+account they are about, the day's briefing on top. Every part is in the catalog.
+
+- **The frame**: `AppShell`, the app's pages in its nav; the desk's row carries the count of what waits on the person.
+  The stage's wide body (`ws-app-shell__body ws-app-shell__body--wide`) holds one filled `ListDetail`
+  (`ws-list-detail ws-list-detail--fill`, joined), the list at North's 362 (`--ws-list-detail-list`): the threads,
+  then the open thread.
+- **The threads** (the list): its head holds the filter (`Segmented --clear --stretch`: "Waits on you" and "All", each
+  with its count); its scroller holds `SideList`'s picks, one per thread, the latest activity first. "Today", the
+  briefing, is always the first. Then one pick per account the person has talked about: the dot in the account's
+  rating tone (teal healthy, mid blue watch, pink at risk: Colour's rating tones, never salmon), the account's name,
+  its last line as the sub (the person's last question or the agent's last act), when at the end, and what waits on
+  the person there in salmon's AA word. Questions about the whole book go to one "Your book" thread. There is no "New
+  chat": a thread starts from the account ("Ask about this" on its page) or from the composer naming it.
+- **The open thread** (the detail): its head (`__top`) holds the account's name (`ws-section`) and its rating `Chip`,
+  "Open the account" at the right. Then the turns (`ChatTurn`): the person's in a bubble, the agent's as plain words,
+  each answer words plus at most one card (`ChatCard`): an email, a call or a text to read or answer now (the message
+  kinds), the Account card when a decision is due, a Suggestion holding a draft `Plate` for a reply it wrote. Every
+  other message is named in its words with its source ("From the 9 Nov call"); the full history is the account's
+  page. A long thread is marked by topic (`TopicRail`). The `Composer` sits at the detail's foot (where recipe 24's
+  acts sit), its starters for this account ("Catch me up", "Draft a reply to Jordan").
+- **The briefing** ("Today"): written once a day at the hour the person set (6:00 by default, in their own time zone),
+  and the desk opens on it. One sentence on the day ("Morning, Halli. Three accounts need you and two replies are ready
+  to send."), then what needs the person as one `Well` (Home's Needs you, recipe 1): a row per account and its one
+  ask, the state word at the right, each row opening that account's thread at the card it means. Then at most one card,
+  the most pressing (a ready reply to send). Nothing else is copied in: each account's cards stay in its own thread. A
+  day with nothing due says so in one line. Before there is data, the desk's first open is recipe 22.
+- **At 1440**: the nav open (232), the list 362, the thread the rest, about the chat's 760 reading column; cards at most
+  556, their trays at 80.
+- **At 390**: the nav is the bar's menu (AppShell's phone form); the list is the screen and the briefing its first
+  pick; a thread opens as its own screen with Back (recipe 24's phone form); the composer at the foot, clear of the
+  safe area; cards fill the column, their trays at 64.
+- **Everywhere else in the app**: "Ask about this" on an account opens its own thread docked (`ChatShell`), the same
+  thread the desk shows. One chat, never a second assistant on the page.
+- **Keyboard**: arrow keys move through the threads (recipe 24); `/` puts the focus in the composer.
+
 ## What every recipe shares
 
 One primary per page (navy in a product, the salmon gradient on a public page). The gutter is the stage's; one content

package/design-system/13-motion.md

@@ -105,7 +105,7 @@ follows cause to effect on the way in; on the way out the person has already mov
 | Component | Enters | Leaves | How the exit gets to play |
 | --- | --- | --- | --- |
 | `Menu`, `Popover` | out of the corner it hangs from, 4 px toward its control, from `--ws-open-scale` (0.97), on `--ws-spring-settle` ("Messages and steps settle") | back into that corner over `--ws-duration-exit` (120 ms) on `--ws-ease-exit` | a native `popover`: `@starting-style` and `allow-discrete` keep its box while it leaves, and a close mid-entrance turns back. Mounted by the app: `data-leaving`, then remove it |
-| `Dialog` | the scrim fades; the window rises 14 px out of `--ws-open-scale-pane` (0.98) on `--ws-spring-settle`, its parts settling in after it | 8 px down over `--ws-duration-exit` | a native `<dialog>` (`showModal()`, `close()`), the same way. A drawer slides in from its edge over `--ws-duration-grow` on `--ws-ease-grow` and back over `--ws-duration-shrink` |
+| `Dialog` | the scrim fades; the window rises 14 px out of `--ws-open-scale-pane` (0.98) on `--ws-spring-settle`, its parts settling in after it | 8 px down over `--ws-duration-exit` | a native `<dialog>` (`showModal()`, `close()`), the same way. A drawer slides in from its edge over `--ws-duration-grow` on `--ws-ease-grow` and back over `--ws-duration-shrink`. Mounted by a library (`ws-dialog--mounted` and `ws-dialog__scrim`): Radix's `data-state="closed"`, or `data-leaving`, then remove it |
 | `Toast` | up out of `--ws-open-scale-toast` (0.96) on `--ws-spring-settle` | 4 px down over `--ws-duration-exit` | `data-leaving`, then remove it |
 | `Tooltip` | pops from 0.9, 4 px toward its control, on `--ws-spring-pop` ("Tooltip pop-in"), after the 40 ms hover intent; at once on keyboard focus | fades off over 180 ms | CSS alone: hover, focus or `ws-tooltip--open` |
 | `HoverCard` | pops from 0.9 on `--ws-spring-pop`, its rows settling 45 ms apart; `--follow` glides after the pointer on `--ws-spring-follow`, which never bounces | to `--ws-pop-scale` over `--ws-duration-exit` | `data-leaving`, then remove it |
@@ -193,9 +193,9 @@ of cards wears `.ws-build`; each card in it wears `.ws-build__card` with `--ws-i
 
 ### Loading
 
-Content on its way is a ghost the size of what it stands for with the shimmer passing over it in the chart colours
-(`Skeleton`, or `.ws-shimmer` on a block of your own: every `--ws-loop-shimmer`, 1.8 s, on `--ws-ease-shimmer`), never
-a spinner. When the content lands, its details settle in top to bottom (`.ws-settle` with `--ws-i` on each, 22 ms
+Content on its way is a ghost the size of what it stands for with the shimmer passing over it: one quiet tone, the
+ghost grey and a lighter pass of the same grey, never a chart hue (`Skeleton`, or `.ws-shimmer` on a block of your own:
+every `--ws-loop-shimmer`, 1.8 s, on `--ws-ease-shimmer`), never a spinner. When the content lands, its details settle in top to bottom (`.ws-settle` with `--ws-i` on each, 22 ms
 apart). An answer at work shows a `StatusLine`; a long load with no figure a `LoadBar`; a pressed button waiting keeps
 its width and shows its working dot on `--ws-loop`. Why: the layout is already in place, so nothing jumps when the real
 thing arrives. Under reduced motion the shimmer stops on its ghost and the words say what is loading.

package/design-system/15-ai-experiences.md

@@ -19,6 +19,17 @@ sit in a bubble with navy text (`ChatTurn` has the sizes). Starters sit under th
 conversation is marked by topic (`TopicRail`), never split into threads the person did not ask for. A reply is words plus at most one card, never both saying the
 same thing. An act is a one-line receipt ("Drafted the opener for Nellie"), not a paragraph. A question is not echoed back.
 
+## Threads by account, and the daily briefing
+
+An agent that works a book of things with the person (accounts, deals) keeps one thread per thing, because the person
+works them one at a time: the thread belongs to the account, is opened from it or by naming it, and is never a split
+the person did not ask for. Inside one thread, subjects are still marked by topic (Page recipes, 25).
+
+The one time an agent speaks first is the daily briefing the person set up: once a day, at their hour, as the first
+turn of "Today". One sentence on the day, what needs them as one list, at most one card. Plain words with no bubble,
+nothing that says "AI", no popup or push of its own: the desk's count is the only notice. It never copies what each
+thread already holds, and it stays quiet until there is data to brief on.
+
 ## Streaming, working and cancelling
 
 A reply arrives as it is written; while it works, a status line (`StatusLine`) says who is working, what it is doing and