prime-ui-kit 0.10.0 → 0.11.1

package/src/components/voice-player/examples/transcript.tsx

@@ -0,0 +1,50 @@
+/** Voice messages with a transcript: one known, one asked for on the first open — `transcript`, `onTranscribe`. */
+import { Message, VoicePlayer } from "prime-ui-kit";
+
+import styles from "./examples.module.css";
+
+const VOICE_URL = "https://interactive-examples.mdn.mozilla.net/media/cc0-audio/t-rex-roar.mp3";
+
+const CLIENT_WAVEFORM = [
+  0.24, 0.4, 0.66, 0.82, 0.58, 0.34, 0.5, 0.76, 0.92, 0.7, 0.46, 0.28, 0.54, 0.8, 0.62, 0.36, 0.22,
+  0.44, 0.7, 0.86, 0.6, 0.32,
+];
+
+const AGENT_WAVEFORM = [
+  0.3, 0.56, 0.74, 0.5, 0.28, 0.62, 0.88, 0.72, 0.42, 0.26, 0.48, 0.68, 0.84, 0.58, 0.36, 0.52,
+  0.78, 0.64, 0.4, 0.2,
+];
+
+const CLIENT_TRANSCRIPT =
+  "Добрый день! По заказу 4821 пришли две коробки вместо трёх, в накладной указаны три места. Подскажите, когда довезут остальное?";
+
+const AGENT_TRANSCRIPT =
+  "Третья коробка уехала отдельной машиной, она будет у вас завтра до обеда. Трек-номер пришлю сообщением.";
+
+/** The speech service answers in a moment. */
+function transcribeAgentVoice(): Promise<string> {
+  return new Promise((resolve) => setTimeout(() => resolve(AGENT_TRANSCRIPT), 1200));
+}
+
+export default function VoicePlayerTranscriptExample() {
+  return (
+    <div className={styles.thread}>
+      <Message.Root direction="incoming" time="14:20">
+        <VoicePlayer
+          src={VOICE_URL}
+          waveform={CLIENT_WAVEFORM}
+          duration={18}
+          transcript={CLIENT_TRANSCRIPT}
+        />
+      </Message.Root>
+      <Message.Root direction="outgoing" time="14:22" status="read">
+        <VoicePlayer
+          src={VOICE_URL}
+          waveform={AGENT_WAVEFORM}
+          duration={11}
+          onTranscribe={transcribeAgentVoice}
+        />
+      </Message.Root>
+    </div>
+  );
+}

package/src/components/voice-player/examples/transfer.tsx

@@ -0,0 +1,88 @@
+/** One look for a recording on its way in either direction: the client's voice message waits to be fetched and then arrives, the reply is being sent — the play disk itself carries the cross and the ring of the share, a dropped connection offers a retry, and the play glyph comes back once it is through — `transfer`, `transferProgress`, `transferDirection`, `onCancel`, `onRetry`, `onDownload`. */
+import { Message, type TransferState, VoicePlayer } from "prime-ui-kit";
+import * as React from "react";
+
+import styles from "./examples.module.css";
+
+const VOICE_URL = "https://interactive-examples.mdn.mozilla.net/media/cc0-audio/t-rex-roar.mp3";
+
+const CLIENT_WAVEFORM = [
+  0.24, 0.4, 0.66, 0.82, 0.58, 0.34, 0.5, 0.76, 0.92, 0.7, 0.46, 0.28, 0.54, 0.8, 0.62, 0.36, 0.22,
+  0.44, 0.7, 0.86, 0.6, 0.32,
+];
+
+const REPLY_WAVEFORM = [
+  0.3, 0.56, 0.74, 0.5, 0.28, 0.62, 0.88, 0.72, 0.42, 0.26, 0.48, 0.68, 0.84, 0.58, 0.36, 0.52,
+  0.78, 0.64, 0.4, 0.2,
+];
+
+const TICK_MS = 400;
+const STEP = 0.08;
+/** The stand-in network drops the first attempt to send past this share. */
+const DROP_AT = 0.6;
+
+type Transfer = { state: TransferState; progress: number; attempt: number };
+
+const REMOTE: Transfer = { state: "remote", progress: 0, attempt: 0 };
+const SENDING: Transfer = { state: "loading", progress: 0, attempt: 1 };
+
+/** One step of a stand-in transfer; `drops` fails its first attempt past `DROP_AT`. */
+function advance(transfer: Transfer, drops: boolean): Transfer {
+  if (transfer.state !== "loading") return transfer;
+  const progress = Math.min(1, transfer.progress + STEP);
+  if (drops && transfer.attempt === 1 && progress > DROP_AT)
+    return { ...transfer, state: "failed" };
+  return { ...transfer, progress, state: progress === 1 ? "done" : "loading" };
+}
+
+const start = (transfer: Transfer): Transfer => ({
+  state: "loading",
+  progress: 0,
+  attempt: transfer.attempt + 1,
+});
+
+const messageStatus = (transfer: Transfer) =>
+  transfer.state === "done" ? "sent" : transfer.state === "failed" ? "failed" : "sending";
+
+export default function VoicePlayerTransferExample() {
+  const [incoming, setIncoming] = React.useState(REMOTE);
+  const [reply, setReply] = React.useState(SENDING);
+
+  React.useEffect(() => {
+    const timer = window.setInterval(() => {
+      setIncoming((transfer) => advance(transfer, false));
+      setReply((transfer) => advance(transfer, true));
+    }, TICK_MS);
+    return () => window.clearInterval(timer);
+  }, []);
+
+  return (
+    <div className={styles.thread}>
+      <Message.Root direction="incoming" time="14:20">
+        <VoicePlayer
+          src={VOICE_URL}
+          waveform={CLIENT_WAVEFORM}
+          duration={18}
+          unplayed
+          transfer={incoming.state}
+          transferProgress={incoming.progress}
+          transferDirection="download"
+          onDownload={() => setIncoming(start)}
+          onCancel={() => setIncoming(REMOTE)}
+          onRetry={() => setIncoming(start)}
+        />
+      </Message.Root>
+      <Message.Root direction="outgoing" time="14:22" status={messageStatus(reply)}>
+        <VoicePlayer
+          src={VOICE_URL}
+          waveform={REPLY_WAVEFORM}
+          duration={11}
+          transfer={reply.state}
+          transferProgress={reply.progress}
+          onCancel={() => setReply((transfer) => ({ ...transfer, state: "failed" }))}
+          onRetry={() => setReply(start)}
+        />
+      </Message.Root>
+    </div>
+  );
+}

package/src/layout/app-header/COMPONENT.md

@@ -8,10 +8,11 @@
 ## When to use
 - The top row of an app built on [AppShell](../app-shell/COMPONENT.md): the section title or the path, the ⌘K search entry, notifications, the account, one primary action.
 - The phone header: the menu button that opens the off-canvas Sidebar, the title, search as an icon.
+- A page without its own heading row in main (a board, a chat, a dense register): the header carries the page title (`AppHeader.Title as="h1"`) and the page tools (`AppHeader.Tools` with a PageToolbar).
 
 ## When not to use
-- The page heading, its description and page actions inside main → use [PageContent](../../components/page-content/COMPONENT.md) (`PageContent.Title` is the `<h1>`).
-- Tabs, filters and search for the data on the page → use [PageToolbar](../../components/page-toolbar/COMPONENT.md).
+- A page that has its heading, description and page actions in main → use [PageContent](../../components/page-content/COMPONENT.md) (`PageContent.Title` is the `<h1>`); then the header title stays a plain name.
+- Tabs, filters and search for the data on the page while the page has its own heading in main → put the [PageToolbar](../../components/page-toolbar/COMPONENT.md) in main, not in `AppHeader.Tools`.
 - App navigation → use [Sidebar](../sidebar/COMPONENT.md) and, on a phone, [BottomNav](../bottom-nav/COMPONENT.md); the header holds at most the menu button.
 - The search dialog itself → use [CommandMenu](../../components/command-menu/COMPONENT.md); `AppHeader.Search` only opens it.
 
@@ -30,20 +31,22 @@ AppHeader.Root               <header>, one sticky row as high as the Sidebar bra
 │     ├─ AppHeader.Icon      decorative glyph on a tile shaped like a soft button m
 │     └─ AppHeader.Description  muted caption under the name
 ├─ AppHeader.Search          field-looking button that opens the CommandMenu
-└─ AppHeader.Actions         trailing buttons: notifications, account, primary action
+├─ AppHeader.Actions         trailing buttons: notifications, account, primary action
+└─ AppHeader.Tools           second row, full width: the page tools (a PageToolbar.Root)
 ```
+`AppHeader.Title as="h1"` makes the name (not the description) the page heading.
 
 ## API
 
 <!-- Generated from api.ts by `bun run docs:build`. Edit api.ts, not this section. -->
 
 ### AppHeader.Root
-`ref` → `HTMLElement`. The `<header>` bar at the top of the content panel: one row as high as the Sidebar brand row, on the panel surface with no divider, sticky with the top safe-area inset (static below 480px of viewport height); inline padding is the shell gutter, so it lines up with the page in main (16 outside a shell). Its controls are size `m`; icon buttons inside are `soft` (a light fill), not `ghost`. A container (`prime-app-header`): below 36rem the icon tile and the description go and the search folds into an icon.
+`ref` → `HTMLElement`. The sticky `<header>` bar at the top of the content panel, one row as high as the Sidebar brand row and lined up with the page. Icon buttons inside are `soft`, not `ghost`.
 
 | Prop | Type | Default | Description |
 |---|---|---|---|
 | `labels` | `Partial<AppHeaderLabels>` | — | Built-in strings, see Labels. |
-| `…rest` | `HTMLAttributes<HTMLElement>` | — | `children` (`AppHeader.Start`, `AppHeader.Search`, `AppHeader.Actions`), `className` and the other attributes. |
+| `…rest` | `HTMLAttributes<HTMLElement>` | — | `children` (`AppHeader.Start`, `AppHeader.Search`, `AppHeader.Actions`, `AppHeader.Tools`), `className` and the other attributes. |
 
 ### AppHeader.Start
 `ref` → `HTMLDivElement`. The leading zone that takes the free width: the menu button, a back button, the title or a Breadcrumb.
@@ -53,10 +56,11 @@ AppHeader.Root               <header>, one sticky row as high as the Sidebar bra
 | `…rest` | `HTMLAttributes<HTMLDivElement>` | — | `children`, `className` and the other div attributes. |
 
 ### AppHeader.Title
-`ref` → `HTMLDivElement`. Where you are: an optional `AppHeader.Icon`, the name (title-s, truncates) and an optional `AppHeader.Description` under it — the anatomy of the Sidebar brand. Not a heading: the page `<h1>` is PageContent.Title.
+`ref` → `HTMLDivElement`. Where you are: an optional `AppHeader.Icon`, the name (title-s, truncates) and an optional `AppHeader.Description` under it. Not a heading unless `as="h1"`.
 
 | Prop | Type | Default | Description |
 |---|---|---|---|
+| `as` | `"span" \| "h1"` | `"span"` | Tag of the name. `h1`: the header carries the page title — only the name is the heading, the description stays outside its accessible name; the look does not change. |
 | `…rest` | `HTMLAttributes<HTMLDivElement>` | — | `children` (the name, `AppHeader.Icon`, `AppHeader.Description` in any order), `className` and the other div attributes. |
 
 ### AppHeader.Icon
@@ -89,6 +93,13 @@ AppHeader.Root               <header>, one sticky row as high as the Sidebar bra
 | `shortcut` | `ReactNode` | `"⌘K"` | The key hint at the end (a `Kbd`, hidden from assistive tech); `null` hides it. Bind the key yourself. |
 | `…rest` | `ButtonHTMLAttributes<HTMLButtonElement>` | — | `onClick`, `className` and the other button attributes. |
 
+### AppHeader.Tools
+`ref` → `HTMLDivElement`. The page's tools in the header (a `PageToolbar.Root`): the header's second row, full width under the title row, wherever it is written.
+
+| Prop | Type | Default | Description |
+|---|---|---|---|
+| `…rest` | `HTMLAttributes<HTMLDivElement>` | — | `children` (a `PageToolbar.Root`), `className` and the other div attributes. |
+
 ### AppHeader.Actions
 `ref` → `HTMLDivElement`. The trailing row of buttons: notifications, the account, one primary action. Never wraps.
 
@@ -119,10 +130,18 @@ AppHeader.Root               <header>, one sticky row as high as the Sidebar bra
 | Breadcrumb in Start | A soft back button, `AppHeader.Separator` and the path | A nested record page | |
 | with `AppHeader.Search` | A field-looking button with a key hint between Start and Actions | The app has a CommandMenu | |
 | with `AppHeader.Actions` | A row of buttons at the end | Notifications, account, one primary action | |
+| with `AppHeader.Tools` | A second row under the title row with the page's PageToolbar | The header carries the page: no heading row in main | |
+
+### as (Title)
+| Value | Looks like | Use when | Default |
+|---|---|---|---|
+| `span` | the name, no heading | the page has `PageContent.Header` in main | yes |
+| `h1` | the same look; the name is the page `<h1>`, the description stays outside its name | the header carries the page title | |
 
 ## States
 | State | Driven by | DOM |
 |---|---|---|
+| with page tools | an `AppHeader.Tools` child | Root renders it after the title row (DOM and Tab order follow the rows), full width, `--prime-space-3` under it |
 | narrow header | header width below 36rem (container `prime-app-header`) | the icon tile and the description hide; the search folds into a square button, its text stays as the name |
 | menu button hidden | `show="narrow"` and viewport from 768px | `data-show="narrow"` on MenuButton |
 | short viewport | viewport below 480px high (a phone on its side) | Root stops sticking |
@@ -134,21 +153,24 @@ AppHeader.Root               <header>, one sticky row as high as the Sidebar bra
 - Gaps: `--prime-space-3` between zones, `--prime-space-2` inside Start and Actions; `AppHeader.Separator` adds `--prime-space-2` on each side (16 in all) and is 20 high.
 - `AppHeader.Icon` is a 36 tile with the radius and fill of a soft neutral button m, so it lines up with the buttons on the bar.
 - On the panel surface with no divider or shadow (depth from fill); `z-index: --prime-z-sticky`.
+- Sticky at `top: 0` of its scroller (static on a viewport below 480px high). The shared sticky surface paints its fill one border width past the top edge, so no sub-pixel seam of the scrolling rows shows above it.
 - Search: up to 288 wide, shrinks first; field tier m and the fill of the panel layer it sits on. Controls inside are size `m`.
+- `AppHeader.Tools` is the header's second row: the full width under the title row, 12 apart, sticky with it. The PageToolbar inside lays itself out from that width — one row from 56rem, two below — so on a phone the page tools wrap under the title, never squeeze it. The page's primary action goes into `PageToolbar.Actions` there, and `AppHeader.Actions` keeps notifications and the account.
 
 ## Accessibility
 
 ### Keyboard
 | Key | Action |
 |---|---|
-| `Tab` | Moves through the menu button, the path links, the search and the actions in reading order. |
+| `Tab` | Moves through the menu button, the path links, the search and the actions in reading order, then the page tools in the second row. |
 | `Enter` · `Space` | Presses the focused button: opens the menu, the search or runs the action. |
 
 ### ARIA
 - Root is a `<header>`: the banner landmark when it sits at the top level of the page.
 - Search is a button named by its text; the key hint is `aria-hidden`, and the app binds the shortcut.
 - MenuButton is named by `labels.menu`; pass `aria-expanded` (whether the Sidebar is open).
-- Title is not a heading: the page `<h1>` stays with PageContent.Title.
+- Title is not a heading by default: the page `<h1>` stays with PageContent.Title. With `as="h1"` the name is the page heading; the description sits next to it, outside its accessible name. One `<h1>` per page either way.
+- `AppHeader.Tools` follows the title row in the DOM, so Tab and screen readers meet the page tools after the header's own buttons.
 
 ### Labels
 <!-- Generated from api.ts by `bun run docs:build`. Edit api.ts, not this section. -->
@@ -162,12 +184,15 @@ AppHeader.Root               <header>, one sticky row as high as the Sidebar bra
 |---|---|
 | [overview.tsx](examples/overview.tsx) | The top bar of a screen: where you are, global search, notifications and the primary action — `AppHeader.Title`, `AppHeader.Search`, `AppHeader.Actions`. |
 | [breadcrumbs.tsx](examples/breadcrumbs.tsx) | A nested page: a back button, a separator and the path instead of a title, actions on the record at the end — `AppHeader.Separator`, `AppHeader.Actions`. |
+| [page-title.tsx](examples/page-title.tsx) | The header carries the page: the title is the page heading, the page tools (sections, the period, the primary action) are its second row and lay themselves out from its width — `AppHeader.Title`, `as`, `AppHeader.Tools`. |
 | [in-app-shell.tsx](examples/in-app-shell.tsx) | The header in the app frame: one row with the Sidebar brand across the two planes, sticky over main — `AppShell`, `Sidebar.Brand`. |
 | [narrow.tsx](examples/narrow.tsx) | On a phone: the menu button opens the navigation, the description goes and the search folds into an icon — `AppHeader.MenuButton`, `show`. |
 
 ## Mistakes
 - A border or shadow under the header → it sits on the panel surface; the fill is the boundary.
-- `AppHeader.Title` as the page `<h1>` → the heading belongs to PageContent.Title in main.
+- `AppHeader.Title as="h1"` while main also has `PageContent.Title` → two `<h1>`; the header carries the title only when main has no heading row.
+- Page tools crammed into `AppHeader.Actions` → `AppHeader.Tools` with a PageToolbar: it wraps under the title instead of squeezing it.
+- A heading element of your own inside `AppHeader.Title` → `as="h1"`, so the description stays out of the heading.
 - A real text input for global search → `AppHeader.Search` opens the CommandMenu, where typing happens.
 - More than three actions → keep one primary action; the rest go into the page or a Dropdown.
 - A hand-made menu button with a media query → `AppHeader.MenuButton` follows the Sidebar breakpoint.
@@ -175,4 +200,4 @@ AppHeader.Root               <header>, one sticky row as high as the Sidebar bra
 
 ## Related
 - **Built from:** [Button](../../components/button/COMPONENT.md), [Kbd](../../components/kbd/COMPONENT.md), [Divider](../../components/divider/COMPONENT.md), Icon (`action.search`, `nav.menu`)
-- **See also:** [AppShell](../app-shell/COMPONENT.md), [Sidebar](../sidebar/COMPONENT.md), [PageContent](../../components/page-content/COMPONENT.md), [PageToolbar](../../components/page-toolbar/COMPONENT.md), [CommandMenu](../../components/command-menu/COMPONENT.md), [Breadcrumb](../../components/breadcrumb/COMPONENT.md)
+- **See also:** [AppShell](../app-shell/COMPONENT.md), [Sidebar](../sidebar/COMPONENT.md), [PageContent](../../components/page-content/COMPONENT.md), [PageToolbar](../../components/page-toolbar/COMPONENT.md) (inside `AppHeader.Tools`), [CommandMenu](../../components/command-menu/COMPONENT.md), [Breadcrumb](../../components/breadcrumb/COMPONENT.md)

package/src/layout/app-header/examples/page-title.tsx

@@ -0,0 +1,85 @@
+/** The header carries the page: the title is the page heading, the page tools (sections, the period, the primary action) are its second row and lay themselves out from its width — `AppHeader.Title`, `as`, `AppHeader.Tools`. */
+import { AppHeader, Button, Icon, PageToolbar, SegmentedControl, Select } from "prime-ui-kit";
+import * as React from "react";
+
+import styles from "./examples.module.css";
+
+const SECTIONS = [
+  { value: "all", label: "Все" },
+  { value: "mine", label: "Мои" },
+  { value: "overdue", label: "Просроченные" },
+];
+
+const PERIODS = [
+  { value: "month", label: "Октябрь" },
+  { value: "quarter", label: "IV квартал" },
+  { value: "year", label: "2026 год" },
+];
+
+export default function AppHeaderPageTitleExample() {
+  const [section, setSection] = React.useState("all");
+  const [period, setPeriod] = React.useState("month");
+
+  return (
+    <div className={styles.window}>
+      <AppHeader.Root>
+        <AppHeader.Start>
+          <AppHeader.Title as="h1">
+            Сделки
+            <AppHeader.Description>Отдел продаж</AppHeader.Description>
+          </AppHeader.Title>
+        </AppHeader.Start>
+        <AppHeader.Actions>
+          <Button.Root variant="soft" tone="neutral" aria-label="Уведомления">
+            <Button.Icon>
+              <Icon name="object.bell" />
+            </Button.Icon>
+          </Button.Root>
+        </AppHeader.Actions>
+        <AppHeader.Tools>
+          <PageToolbar.Root aria-label="Сделки">
+            <PageToolbar.Sections>
+              <SegmentedControl.Root
+                fullWidth
+                value={section}
+                onValueChange={setSection}
+                aria-label="Раздел"
+              >
+                {SECTIONS.map((item) => (
+                  <SegmentedControl.Item key={item.value} value={item.value}>
+                    {item.label}
+                  </SegmentedControl.Item>
+                ))}
+              </SegmentedControl.Root>
+            </PageToolbar.Sections>
+            <PageToolbar.View>
+              <Select.Root value={period} onValueChange={setPeriod}>
+                <Select.Trigger aria-label="Период">
+                  <Select.TriggerIcon>
+                    <Icon name="field.calendar" />
+                  </Select.TriggerIcon>
+                  <Select.Value />
+                </Select.Trigger>
+                <Select.Content>
+                  {PERIODS.map((item) => (
+                    <Select.Item key={item.value} value={item.value}>
+                      {item.label}
+                    </Select.Item>
+                  ))}
+                </Select.Content>
+              </Select.Root>
+            </PageToolbar.View>
+            <PageToolbar.Actions>
+              <Button.Root>
+                <Button.Icon>
+                  <Icon name="action.add" />
+                </Button.Icon>
+                Новая сделка
+              </Button.Root>
+            </PageToolbar.Actions>
+          </PageToolbar.Root>
+        </AppHeader.Tools>
+      </AppHeader.Root>
+    </div>
+  );
+}

package/src/layout/app-shell/COMPONENT.md

@@ -60,7 +60,7 @@ Every child of Root that is not `AppShell.Nav` is placed into the content panel.
 | `…rest` | `HTMLAttributes<HTMLElement>` | — | `children`, `className` and the other attributes. |
 
 ### AppShell.Footer
-`ref` → `HTMLDivElement`. Sticky bottom bar of the panel for `BottomNav`; no padding of its own. A container (`prime-shell-footer`): BottomNav inside shows only while the panel is narrower than 640px.
+`ref` → `HTMLDivElement`. Sticky bottom bar of the panel for `BottomNav`; no padding of its own. Shows only while the shell has no navigation column on screen (no `AppShell.Nav`, or the Sidebar is off-canvas); with the rail on screen the footer leaves.
 
 | Prop | Type | Default | Description |
 |---|---|---|---|
@@ -99,7 +99,7 @@ Every child of Root that is not `AppShell.Nav` is placed into the content panel.
 | with `AppShell.Nav` | Two columns: a rail one layer above the page + the panel that is the page | Apps with navigation | |
 | without Nav | Panel takes the full width | Single-page tools, auth screens | |
 | with `AppHeader.Root` | Sticky bar at the top of the panel | Title or breadcrumbs, global search, actions, the mobile menu button | |
-| with `AppShell.Footer` | Sticky bar at the bottom of the panel, shown while it holds a visible bar | BottomNav on a phone | |
+| with `AppShell.Footer` | Sticky bar at the bottom of the panel, shown while no navigation column is on screen | BottomNav on a phone | |
 
 `AppShell.Template` with `nav={<Sidebar.Root …/>}` and `PageContent` inside is the standard app; `contentWidth="contained"` + `PageContent.Root maxWidth="readable"` for docs and articles.
 
@@ -107,13 +107,18 @@ Every child of Root that is not `AppShell.Nav` is placed into the content panel.
 | State | Driven by | DOM |
 |---|---|---|
 | fixed frame | `fillViewport` | `data-fill-viewport="true"` on Root |
+| navigation column | an `AppShell.Nav` child | `data-nav="true"` on Root (two grid columns) |
 | content width | `contentWidth` | `data-content-width` on Main |
-| footer bar | panel width (container `prime-shell-footer` on Footer) | BottomNav inside leaves from 640px of panel width; the empty footer takes no room |
+| footer bar | the navigation column: `AppShell.Nav` with a Sidebar that is not off-canvas | the footer is `display: none` while the rail is on screen; without Nav or with an off-canvas Sidebar it stays at any width |
 
 ## Layout & spacing
 - Two full-height planes edge to edge: no inset, radius, shadow or border — the boundary is the fill change (the Sidebar rail is layer 1, the panel the page: white rail beside a gray page in light, a rail one step lighter than the near-black page in dark).
-- Gutters in Main: `--prime-layout-gutter-s` (16) → `-m` (24) from 640px → `-l` (32) from 1024px. Main top padding `--prime-space-6` (24) → `--prime-space-10` (40) from 1024px; bottom `--prime-space-16`.
+- Gutters in Main (and in an `AppHeader.Root` in the panel): `--prime-layout-gutter-s` (16) → `-m` (24) from 640px → `-l` (32) from 1024px. Main top padding `--prime-space-6` (24) → `--prime-space-10` (40) from 1024px; bottom `--prime-space-16`. Children of Main start from their own gutters, not the shell's.
+- A page that fills the panel height (`PageContent.Root fill`): Main's bottom padding drops to the side gutter, so no long scroll tail stays under it.
+- Main scrolls with `overscroll-behavior: contain`, so its scroll never chains to the document.
+- Nav column: sticky at the top, viewport high, `z-index: --prime-z-sticky` (above the panel, so the compact Sidebar toggle can ride the rail edge); with `fillViewport` it fills the shell height instead.
 - Footer: no padding of its own (BottomNav keeps the bottom safe-area inset), sticky at the bottom, `z-index: --prime-z-sticky`.
+- A floating BottomNav (`floating`) in the footer: the footer takes no height, the capsule overlays the page, and Main keeps extra bottom room (the capsule height and the safe-area inset) so its last line never ends up under it.
 - The panel is the page (layer 0 of the surface ladder, gray in light): fields on it take the page fill, a Card inside is layer 1 — white in light with the raised whisper — and cards in cards go deeper.
 
 ## Accessibility
@@ -135,7 +140,7 @@ No `labels`.
 |---|---|
 | [overview.tsx](examples/overview.tsx) | The app frame: Sidebar in the nav column, breadcrumbs in the AppHeader, the page in main; only main scrolls — `fillViewport`. |
 | [contained.tsx](examples/contained.tsx) | A shell without navigation whose main column is centred and capped for long reads — `contentWidth`. |
-| [footer.tsx](examples/footer.tsx) | A phone-wide app: the bar in the footer stays at the bottom while main scrolls under it, and leaves once the panel is 640px wide — `AppShell.Footer`. |
+| [footer.tsx](examples/footer.tsx) | A phone app without a Sidebar: the bar in the footer stays at the bottom while main scrolls under it — `AppShell.Footer`. |
 | [template.tsx](examples/template.tsx) | Root, nav, header and main in one component; main scrolls back to the top whenever the page changes — `AppShell.Template` with `scrollResetKey`. |
 
 ## Mistakes
@@ -143,6 +148,7 @@ No `labels`.
 - Wrapping Main content in another scroll container → Main scrolls (with `fillViewport`) or the document does.
 - A border or shadow between nav and panel → the fill change is the boundary.
 - Putting the Sidebar directly in Root without `AppShell.Nav` → it lands inside the content panel.
+- BottomNav anywhere but `AppShell.Footer` → it stays next to the Sidebar rail on a desktop; the footer is what leaves while the rail is on screen.
 - `AppShell.Template` in a router app without `scrollResetKey` → a new page opens at the old scroll position; pass the pathname.
 
 ## Related

package/src/layout/app-shell/examples/examples.module.css

@@ -28,7 +28,7 @@
   height: 100%;
 }
 
-/* footer.tsx: the same window, phone-wide, so the bar in the footer stays (it leaves from 640px). */
+/* footer.tsx: the same window, phone-wide; no Nav, so the bar in the footer stays. */
 .phone {
   box-sizing: border-box;
   display: flex;

package/src/layout/app-shell/examples/footer.tsx

@@ -1,4 +1,4 @@
-/** A phone-wide app: the bar in the footer stays at the bottom while main scrolls under it, and leaves once the panel is 640px wide — `AppShell.Footer`. */
+/** A phone app without a Sidebar: the bar in the footer stays at the bottom while main scrolls under it — `AppShell.Footer`. */
 import { AppHeader, AppShell, BottomNav, Icon, PageContent, Typography } from "prime-ui-kit";
 
 import styles from "./examples.module.css";