v1.3.3

Install an item at this release, npx shadcn@latest add ourostack/ouro-ui/<item>#v1.3.3; its Ouro dependencies install from the same tag. Every install from GitHub needs a release tag: main has no registry.json, so an address without one fails. In an app with Tailwind CSS v4 and an "@/*" path alias, run shadcn's init once first, with the Base UI base:

npx shadcn@latest init --base base --preset nova --yes --no-monorepo
npx shadcn@latest add ourostack/ouro-ui/ouro-base#v1.3.3 ourostack/ouro-ui/dialog#v1.3.3

The tests, stories and specs are optional, one item per component: npx shadcn@latest add ourostack/ouro-ui/dialog#v1.3.3 ourostack/ouro-ui/dialog-tests#v1.3.3, or ourostack/ouro-ui/ouro-tests#v1.3.3 for all of them. List every item with npx shadcn@latest search 'ourostack/ouro-ui#v1.3.3'.

Changes in this release

• New: Ouro AX: ax-component declares a component's agent side, what an agent reads from it and each action's effect, with agent: true or a personOnly reason, never both or neither, and bindAx binds each read and agent action to its CLI twin and returns the X-ray inventory's ui entries.
• New: Ouro AX: defineCli({ personOnly }) declares the words only the person acts on, which refuse with the reason and how the person does it, as a refused outcome under --json, and help --json lists them under personOnly.
• New: Ouro AX: claim set 1.2.0 and ax-xray 1.2.0 check a ui inventory: every twin is a command with the action's effect, person-only words refuse, a read of what people say answers needs-human until the person asks the agent to follow, its stream refuses every line without a words trigger, and a read resumes from --cursor; a CLI with no ui inventory has no ui surface checked.
• New: Ouro AX: RESERVED_PERSON_ONLY keeps the person's microphone, camera and screen, answering, joining and declining a call, admitting from the lobby and recording person-only in every component, and expectAxRendered(ax, container) checks that a component renders data-ax-action="<id>" on each declared action's control.
• New: Ouro AX: reserved person-only actions are matched by meaning, so aliases such as mic-on, share-screen, accept, start-recording, a bare mic, any toggle such as toggle-mute, join-meeting and admit-all are the person's too, while mute, camera-off, stop-share and call verbs away from a call, such as share-link and answer-message, stay an agent's; a component imports the kit as @/registry/ouro/ax/component, which installs as the app's lib alias.
• Combobox items take media (an Avatar, shown on the row and on the chip), description (a second, muted line, cut to one line and whole on hover) and meta (a mark such as a Badge at the row's end), so it can pick people (test).
• Combobox takes autoHighlight, so Enter picks the first match; onInputKeyDown, which hears each key before Combobox and can stop its handling with preventDefault(); inputValue, the text when the app keeps it; and readOnly (test).
• Combobox's list sits 1000 above --ouro-layer, as Select's does, so inside a Dialog it shows over the dialog instead of behind it (test).
• An icon or picture inside a Combobox item keeps its own size; only the check before a picked item is drawn at 16px (test).
• Changed: when Command's results change while the search stays the same (results from a slow source), the highlight stays on the same command, by its new value (its label by default), and goes to the first command when that one has gone.
• New: Command says how many results there are, politely and once after they settle, in words from resultsLabel.
• New: a command with restoreFocus: false leaves focus where its onSelect puts it when the palette closes, instead of returning it to the trigger.
• New: a command's description is a second line under its label, which the search matches too, and Command's highlightMatches marks the words of the search in both, or where a command's highlight ranges say, in colours that keep their contrast in light, dark and forced colours.
• New: Emoji takes placeholder, an image's address or an element, which shows in the emoji's own box until its picture has loaded and decoded; the picture then fades in over --ouro-duration-fast, at once with reduced motion or under <OuroProvider motion="reduced">, and a picture that fails to load or decode leaves the placeholder showing. With it, the emoji's root is a <span> around the <img>, and className goes on the <span>.
• New: EmojiPicker with a catalogue takes placeholder and passes it to every emoji it draws.
• Installs from GitHub take a release tag, npx shadcn@latest add ourostack/ouro-ui/<item>#v<version>, or go through the @ouro namespace (@ouro/<item>): main no longer commits registry.json, so an address without a tag, or with a branch or a commit, stops with "did not return a root registry.json file".
• lib-claims: the claims check lints a generated surface (generated in claims.config.json) even when git ignores it.
• Fix: a dropdown Menu closes when focus moves anywhere outside it, as it does on a click outside. Left open, the focus guard Base UI keeps before its trigger sent a forward Tab back to what Tab was leaving, so Tab stuck once on the control before the trigger (test).
• Moment's art carries data-moment-art, with the new artName prop as its value ("waving"), and Celebrate carries data-celebrate while it celebrates, so checkers and tests find the art and the celebration without marking them by hand (test).
• Moment takes size="hero", with art up to 220px tall for the main state of a large, otherwise empty pane, holding at 96px in a pane narrower than 24rem (test).
• Moment's art has a motion budget: its looping animations settle at the end of their turn about 5 s after it appears (its SVG animations pause at their start), and with a dismissKey or id its entrance plays once a session, so a moment that comes back as people switch views arrives still (test).
• New: content that scrolls sideways shows that it scrolls. A ScrollArea (and so a Table), a CodeBlock and a Chart's visible table, while their content is wider than they are, fade it out at the side where it goes on, following the scroll and resizing. A ScrollArea's focus ring is now drawn on its root, and a CodeBlock's on an element over its code, so the fade leaves them whole; the ScrollArea's scrollbar thumb is CanvasText in forced colors.
• Fixed: under forced colours, the pressed SegmentedControl segment keeps its HighlightText letters while the pointer rests on it, where hover used to turn them back to the page's text colour on the Highlight thumb.
• New: Toaster's avoid takes a CSS selector for controls the toasts must stay clear of, such as a call's Join button in a corner: while one is in the lower half of the window under the toasts' column, the toasts sit 8px above it, and come back down when it goes.

Upgrading from v0.1.0

v0.1.0 installed each component with its tests, and v0.2.0 moves some shared helpers to new files, so update every Ouro component in one go.¹² Run the commands in your app's root, the folder with components.json. They find your folders the way shadcn does, from the aliases in components.json and the paths in your tsconfig (npx shadcn@latest info shows them), so they work in a src/ or an app/ layout as written.

What changed, by version

What an app on v0.1.0 has to know beyond these steps.³ The release notes list every change.⁴

• v0.2.0: each component's tests became an optional <name>-tests item, some helpers moved to new files (step 4), and v0.1.0's self-referential theme lines can go (step 2).²

• v0.3.0: sheets and dialogs stack at --ouro-layer, a z-index of 50 by default, instead of level 0, so an app element at z-index 1 to 49 that used to show above an open sheet or dialog now sits under it.⁵ Raise the token in a :root rule of your own if your app has fixed bars above z-50 (see "Theme" in the README), and drop any portal z-index workaround. A controlled Dialog opened by a touch or pen tap focuses its popup instead of its first input, and ConfirmDialog's finalFocus applies only after a confirmed action; drop workarounds for either. Every coverage hint is /* istanbul ignore … @preserve */, so a build plugin that kept the hints can go.⁶ A -tests item sets Vitest to ^5.

• v0.3.1: every component starts with "use client", so Next.js App Router pages can render them, and the @ouro namespace serves the newest release instead of main.⁷

• After v0.7.0: a required field's * is drawn with CSS on a new element around the label and is no longer a <span data-ouro-required> inside it, so tests that expected the label text "Email*" now find "Email".⁸ The clear, show-password and choose-date buttons in TextField and DatePicker are named by hidden text, not aria-label, so replace button[aria-label="…"] selectors with [data-ouro-clear], [data-ouro-show-password] or [data-ouro-choose-date]. The same goes for a file's remove button in FileField ([data-ouro-file-remove]), Combobox's clear and chip remove buttons ([data-ouro-combobox-clear], [data-ouro-combobox-chip-remove]) and NumberField's steppers ([data-ouro-increment], [data-ouro-decrement]). A remove button's hidden text holds the file or item name, so a loose getByText("pasta.png") now finds it too; pass { exact: true }. FieldLabel's className now goes on the new element around the label, which also carries [data-ouro-required], and a group's label id is on the inner <span>; style, id, data-* and handlers still go on the <label>. A numeric size on TextField is now a type error and a development warning; set a width with className="w-40". FormErrors values are now ErrorMessages | null | undefined, so code that reads errors.email as string | string[] no longer type checks until it handles null and React nodes.⁸ For action answers, import formErrors from @/lib/ouro/form-answer and pass errors={formErrors(actionData, actionData?.errors)} from the initial render; this replaces the unreleased separate result prop. It identifies equal new answers while keeping cleared fields masked on pending/client renders and rendering current uncleared messages. Cached/reused answers need { key: acceptedAnswerKey }, changed on actual acceptance, not submit start. Raw records remain compatible but content-only. Reconstruct the value beside Form after JSON/spread/cloning or server-component transport: only messages serialize, not private identity; a safely transported acceptance key can identify the locally reconstructed answer. On a phone, a Link that is not in running text is now a box at least 44px tall and wide that takes its room in the layout, so a column of links grows; pass inline to a link in a sentence inside your own <div> or <span>.⁹ A Form's top message element exists only while there is a message. Component roots no longer set m-0, so a parent's space-y-* now spaces them; remove any margin you added to work around that.⁸

• v0.8.0: no component installs ouro-base; add it once (step 1 does), and later adds leave your stylesheet alone.⁸ A component installs only the helpers it imports, one item per file in lib/ouro, and a -tests item brings the tests of everything its component installs.⁸ The -tests items no longer set a version for Vitest, Storybook or Playwright.¹⁰ The specs import test and expect from e2e/ouro-fixtures.ts, a file of yours (step 1).⁸ lib/ouro/use-dev-warnings.ts is now lib/ouro/use-dev-messages.ts (step 4).⁸ Earlier releases installed every helper in lib/ouro with any component, and an update deletes nothing: audit references before deleting unused historical helpers and their own tests (step 5).⁸ OuroProvider now comes only with the components that render links and with tooltip; your copy stays, and a new app adds lib-ouro-provider by name.

• After v0.8.2: ouroTestProjects({ page }) also sizes the touch project's Playwright host, preventing Vitest 4 from scaling landscape touch frames.¹¹ The logical touch viewport still starts at 390x844 with mobile/touch input, but an explicitly enlarged host changes outer-window/screen dimensions and screen orientation; do not treat those as hardware-phone measurements.¹¹ Without page, the touch host stays 390x844.¹¹ On Vitest 4, retain a host large enough for every requested test viewport, such as the Testing guide's 1600x1200 example.¹¹

• v1.0.0: the first stable release keeps the component APIs, theme tokens, defaults and test-tool minimums from v0.8.4.¹² An app already on v0.8.4 needs no component API migration: review the update with --dry-run and --diff, then overwrite only the items it already uses and reapply its local edits.¹² Runtime components and their optional -tests items remain separate; keep your app-owned fixtures and test configuration. Apps on older releases still need the applicable migration steps above and below.

• After v1.0.2: sheets, and a Menu shown as a bottom sheet, read their shadow from --ouro-shadow-sheet-<side>, and Checkbox's tick draws over --ouro-duration-draw, both of which only a fresh ouro-base adds (step 1 adds it again); without it a sheet draws no shadow and the tick appears at once.¹³ Every other shadow reads shadcn's --shadow-* tokens, and headings and overlay titles --font-heading, so a theme that sets them now restyles Ouro too.¹³¹⁴

• After v1.0.1: formErrors now declares its already-frozen message arrays readonly.¹⁵ Keep mutable FormErrors and ErrorMessages for raw builders; annotate returned snapshots as FormErrorValue or ReadonlyFormErrors, or let their type infer. Form, EditSheet, field error props and the normalization helper accept readonly projections. This corrects a false mutation permission, so a snapshot no longer fits a mutable raw-map annotation.¹⁵ TypeScript's Array.isArray narrows to any[] and can bypass readonly; unchanged runtime freezing still rejects container mutation, without deeply freezing React nodes.

• After v1.2.2: Button accepts reloadDocument for a document request through an internal href, and its downloads use a plain anchor like Link's.¹⁶ A false or null download no longer forces document navigation; pass reloadDocument when a resource route needs it without a download.¹⁶

• After v1.2.4: Select, Menu, Combobox, Popover, Tooltip, HoverCard and NavigationMenu open their popups at the end of <body> unless OuroProvider is given a portalContainer, and in development each warns once when it opens outside every landmark of a page with a <main>.¹⁷ To keep popups in a landmark, make const popups = useRef<HTMLDivElement>(null), wrap the app in <OuroProvider portalContainer={popups}> and render <div ref={popups} /> last inside <main>, outside any element with a transform, filter or contain, which would clip or move the popups. In a Next.js App Router layout, which is a server component, put the provider and the ref in a small client component. Inside a dialog your app draws itself, wrap its content in <OuroProvider portalContainer={null}> so its popups open where Base UI puts them.¹⁸ Dialogs, sheets and toasts still open at the end of <body>. The landmark warning goes to console.warn, so a test that fails on console output fails until the popups are in a landmark. SidebarLayout's header now renders in a <header>, the page's banner, so remove a banner your page draws around SidebarLayout.¹⁹ The testing/axe kit has a new audit, which fails every violation at any impact and every result axe could not decide unless it measures it, in both color schemes.²⁰ The ouro-testing item now names axe-core among its devDependencies, so an update adds it to an app that lacks it.²¹

• After v1.2.8: the Toaster's Notifications region is no longer a live region: two live regions last inside it say each toast's message and description, the assertive one a role="alert", so for its first seven seconds a toast's words are in the page twice.²² Find a toast in a test by its role and name, getByRole("dialog", { name: "Saved" }), or "alertdialog" for a destructive toast, not with getByText, and expect no aria-live on the region. Dismiss buttons and destructive toasts are no longer hidden from screen readers while the stack is collapsed.²³ The testing/axe kit's audit now leaves focus, the selection and every scroll position as it found them, and throws, naming what changed, when its Tab walk closes a popup it cannot open again; audit the page before that popup opens.²⁴

• After v1.2.14: Avatar's initials take a hue from the name, from the tokens --avatar-1 to --avatar-8, which only a fresh ouro-base adds (step 1 adds it again); without them the initials show with no tint.²⁵ Pass color="neutral" to keep the plain grey. Avatar's presence dot sits over its edge, so the picture now rounds its own corners instead of the avatar clipping it.²⁶

0. Commit first

--overwrite replaces every Ouro file, including files you edited.²⁷ Commit before you start. Afterwards, git diff shows your own edits being overwritten, so reapply the ones you need.

Review the diff of your Tailwind CSS file too, the one components.json names in tailwind.css, because step 1 adds ouro-base, the one item that writes there, and shadcn add rewrites more than Ouro's tokens. It adds @custom-variant dark (&:is(.dark *)); when the file has no @custom-variant (shadcn@4.21.1 does this for any item with theme variables on Tailwind CSS v4), adds the tokens your file lacks to :root, .dark and @theme inline (among them --input, --radius and the radius scale, if your theme has none), and collapses blank lines.²⁸ Keep the new lines and step 2's deletions, and revert the rest. After this upgrade no component add opens the file again.⁸

1. Update every Ouro component, with its tests

Update every Ouro component in your app, not only the items you typed: v0.1.0 added each component's dependencies too, so an app that added only dialog also has button and sheet. Each component is one .tsx file in your components/ouro/ folder (dialog/ holds dialog and confirm-dialog, and text/ holds text and heading).¹ Add each one as <name> and <name>-tests, plus ouro-base, in one command at the same ref, with --overwrite (without it the CLI stops to ask about each file). For the app that added only dialog, that is ouro-base button button-tests dialog dialog-tests sheet sheet-tests. No component installs ouro-base any more, so this is where your stylesheet gets the tokens added since v0.1.0.⁸

This command finds the components, prints them and adds them. If it finds none, it stops before adding anything²⁹; run it in the folder with components.json. If you use the Ouro theme, add ourostack/ouro-ui/ouro-theme#v1.3.3 to the add in it.

( p() { npx shadcn@latest info --json | node -p "JSON.parse(require('fs').readFileSync(0, 'utf8')).config.resolvedPaths.$1"; }; ouro="$(p components)/ouro"; items=$(find "$ouro" -name '*.tsx' ! -name '*-parts.tsx' ! -name '*.test.tsx' ! -name '*.stories.tsx' 2>/dev/null | sed -E 's|.*/(.*)\.tsx$|\1|' | sort); [ -n "$items" ] || { echo "No Ouro components in $ouro. Run this in the folder with components.json." >&2; exit 1; }; echo "Updating: $(echo "$items" | paste -sd " " -)"; npx shadcn@latest add $(echo "$items" | sed -E 's|.*|ourostack/ouro-ui/&#v1.3.3 ourostack/ouro-ui/&-tests#v1.3.3|') ourostack/ouro-ui/ouro-base#v1.3.3 --overwrite )

This keeps the tests v0.1.0 installed, deletes none of your files and adds no component you didn't have. shadcn may print Skipped N files: (files might be identical, use --overwrite to overwrite) even with --overwrite: those files already equal the release's, so nothing was missed.²⁷ The -tests items name Vitest, Storybook and Playwright without a version, so the versions in your package.json stay as they are. v0.7.0's items still carry versions: after an add at v0.7.0, restore every test-tool version you had pinned (git diff package.json): Vitest and its companions, Playwright and Storybook.³⁰ The tests need Vitest 4.1.11 or later, Playwright 1.58.1 or later and Storybook 10.2.10 or later; update those yourself if yours are older (the README's "Details" links the Testing page).³¹ The specs in e2e/ouro now import test and expect from e2e/ouro-fixtures.ts, a file of yours: add it with the one line export { expect, test } from "@playwright/test";, or export your own fixtures from it.

2. Remove the self-referential theme lines

v0.1.0 wrote a line into @theme inline for each Ouro token that points at itself, such as --ouro-press-scale: var(--ouro-press-scale);, and --color-ouro-backdrop-color: var(--ouro-backdrop-color);.³² Delete them from your Tailwind CSS file, the one components.json names in tailwind.css. The values stay in :root and .dark. This command finds the file and deletes the lines:

perl -i -ne 'print unless /^\s*--(color-)?ouro-[\w-]+:\s*var\(--ouro-[\w-]+\);\s*$/' "$(npx shadcn@latest info --json | node -p "JSON.parse(require('fs').readFileSync(0, 'utf8')).config.resolvedPaths.tailwindCss")"

3. Optional: drop Ouro's tests

To keep only the components, delete the files Ouro owns for its tests: the test, type-test and story files in your components/ouro/ and lib/ouro/ folders, the test kit in lib/ouro/testing and the specs in e2e/ouro. The command stops if it can't find those folders.

( p() { npx shadcn@latest info --json | node -p "JSON.parse(require('fs').readFileSync(0, 'utf8')).config.resolvedPaths.$1"; }; c="$(p components)/ouro"; l="$(p lib)/ouro"; [ -d "$c" ] && [ -d "$l" ] || { echo "No Ouro folders at $c and $l. Run this in the folder with components.json." >&2; exit 1; }; find "$c" "$l" \( -name '*.test.ts' -o -name '*.test.tsx' -o -name '*.test-d.ts' -o -name '*.stories.tsx' \) -delete; find "$l/testing" e2e/ouro -delete )

Then remove the ouroTestProjects import and call from your Vitest config. Only if Ouro's tests were the only tests using them, also delete vitest.config.ts, playwright.config.ts and .storybook/, and uninstall vitest, @vitest/browser-playwright, playwright, @playwright/test, storybook and @storybook/react-vite with your package manager.

4. Change imports of moved helpers

If your own code imports these helpers, change the import:

• useOuro: from lib/ouro/ouro-provider to lib/ouro/use-ouro.
• sheetSides, sideWarning, sheetHint, iosBackdrop and footerClass: from components/ouro/sheet/sheet-parts to components/ouro/sheet/sheet-styles.
• dialogSizes and dialogSizeWarning: from components/ouro/dialog/dialog-parts to components/ouro/dialog/dialog-styles.
• alignClasses and checkAlign: from components/ouro/text/text to components/ouro/text/text-styles.
• useDevWarnings: from lib/ouro/use-dev-warnings to lib/ouro/use-dev-messages. Delete the old lib/ouro/use-dev-warnings.ts; nothing imports it after step 1.

5. Delete the helpers nothing imports

Releases before v0.8.0 installed every helper in lib/ouro with any component.⁸ From v0.8.0 a component installs only the helpers it imports, but an update deletes nothing.⁸ Remove unused historical helpers rather than excluding them from coverage.

Before deleting anything, perform a read-only import/reference audit across the whole app, including scripts, tests, stories and configuration outside src/. Use the app's actual tsconfig and bundler aliases to resolve references to each helper's full path. Check relative imports, explicit extensions, re-exports and dynamic imports too; an importing file with the same basename is still a different file. A text search for lib/ouro/<name> alone cannot prove a helper is unused.

Delete a helper and its own tests only after verifying that no remaining app file or retained Ouro file references it (references from that helper's own tests do not require keeping an otherwise unused helper). Check again after each removal: another historical helper may have been used only by the one you removed. If a reference is unresolved or you cannot verify a file's use, keep it until you can. Keep ouro-provider.tsx if you mean to use it and have not yet, and retain ambient declarations such as env.d.ts that the app's type check needs even without an import.

Then type check and build your app. CI runs steps 1 to 3 on a v0.1.0 app, with these commands read from this file (scripts/install-test.sh upgrade).³

Or through the @ouro namespace, which serves the newest release: this one, once main is prepared for the next release. Add it to components.json once:

"registries": { "@ouro": "https://ui.ouro.bot/r/{name}.json" }

npx shadcn@latest add @ouro/ouro-base @ouro/dialog

Items, by name. The docs describe each component, and the tag's registry.json holds every item's description:

ouro-base, ouro-theme, ouro-lib, ouro-testing, lib-announce, lib-appearance-hints, lib-claims, lib-class-name-check, lib-cn, lib-color-scheme, lib-color-scheme-script, lib-control-ref, lib-current-path, lib-dev, lib-env, lib-feedback, lib-floating, lib-focus-handoff, lib-form-answer, lib-insert-text, lib-keep-clear, lib-key-shortcuts, lib-last-input, lib-navigation-key, lib-open-mode, lib-ouro-provider, lib-page-scroll-hold, lib-portal-container, lib-refs, lib-router-link, lib-scroll-fade, lib-server-element, lib-share, lib-spring, lib-stretched-link, lib-toast, lib-tones, lib-touch-target, lib-use-backdrop-anchor, lib-use-command-shortcut, lib-use-dev-messages, lib-use-drag, lib-use-field, lib-use-install-prompt, lib-use-keyboard-scrollable, lib-use-media-query, lib-use-mounted-open, lib-use-ouro, lib-use-reduced-motion, lib-use-sheet-presentation, lib-use-timer, button, text, heading, sheet, dialog, confirm-dialog, field, fieldset, link, text-field, text-area, checkbox, checkbox-group, radio-group, switch, form, edit-sheet, select, native-select, number-field, slider, combobox, toaster, spinner, progress, skeleton, avatar, badge, alert, separator, kbd, popover, tooltip, hover-card, menu, command, tabs, segmented-control, accordion, collapsible, show-more, card, item, item-group, empty, scroll-area, aspect-ratio, stack, row, navbar, sidebar, sidebar-layout, stacked-layout, auth-layout, breadcrumb, pagination, navigation-menu, table, description-list, toggle, toggle-group, button-group, otp-field, file-field, color-field, swipe-actions, reorderable, calendar, date-picker, carousel, resizable, chart, message, message-list, attachment, thread-summary, checklist, inspector, skip-link, tab-bar, route-progress, color-scheme-toggle, page-header, copy-button, code-block, timer, timer-tray, celebrate, choice-card, image-cropper, image-field, share-button, sync-status, local-date, relative-time, install-prompt, conversation-list, attention-card, reaction-bar, lightbox, composer, emoji-picker, navigation-rail, time-grid, toolbar, autocomplete, emoji, moment, lib-announce-tests, lib-appearance-hints-tests, lib-claims-tests, lib-class-name-check-tests, lib-cn-tests, lib-color-scheme-script-tests, lib-color-scheme-tests, lib-control-ref-tests, lib-current-path-tests, lib-dev-tests, lib-feedback-tests, lib-floating-tests, lib-focus-handoff-tests, lib-form-answer-tests, lib-insert-text-tests, lib-keep-clear-tests, lib-key-shortcuts-tests, lib-last-input-tests, lib-navigation-key-tests, lib-ouro-provider-tests, lib-page-scroll-hold-tests, lib-portal-container-tests, lib-scroll-fade-tests, lib-server-element-tests, lib-share-tests, lib-spring-tests, lib-use-command-shortcut-tests, lib-use-dev-messages-tests, lib-use-drag-tests, lib-use-install-prompt-tests, lib-use-keyboard-scrollable-tests, lib-use-media-query-tests, lib-use-mounted-open-tests, lib-use-reduced-motion-tests, lib-use-sheet-presentation-tests, lib-use-timer-tests, button-tests, text-tests, heading-tests, sheet-tests, dialog-tests, confirm-dialog-tests, field-tests, fieldset-tests, link-tests, text-field-tests, text-area-tests, checkbox-tests, checkbox-group-tests, radio-group-tests, switch-tests, form-tests, edit-sheet-tests, select-tests, native-select-tests, number-field-tests, slider-tests, combobox-tests, toaster-tests, spinner-tests, progress-tests, skeleton-tests, avatar-tests, badge-tests, alert-tests, separator-tests, kbd-tests, popover-tests, tooltip-tests, hover-card-tests, menu-tests, command-tests, tabs-tests, segmented-control-tests, accordion-tests, collapsible-tests, show-more-tests, card-tests, item-tests, item-group-tests, empty-tests, scroll-area-tests, aspect-ratio-tests, stack-tests, row-tests, navbar-tests, sidebar-tests, sidebar-layout-tests, stacked-layout-tests, auth-layout-tests, breadcrumb-tests, pagination-tests, navigation-menu-tests, table-tests, description-list-tests, toggle-tests, toggle-group-tests, button-group-tests, otp-field-tests, file-field-tests, color-field-tests, swipe-actions-tests, reorderable-tests, calendar-tests, date-picker-tests, carousel-tests, resizable-tests, chart-tests, message-tests, message-list-tests, attachment-tests, thread-summary-tests, checklist-tests, inspector-tests, skip-link-tests, tab-bar-tests, route-progress-tests, color-scheme-toggle-tests, page-header-tests, copy-button-tests, code-block-tests, timer-tests, timer-tray-tests, celebrate-tests, choice-card-tests, image-cropper-tests, image-field-tests, share-button-tests, sync-status-tests, local-date-tests, relative-time-tests, install-prompt-tests, conversation-list-tests, attention-card-tests, reaction-bar-tests, lightbox-tests, composer-tests, emoji-picker-tests, navigation-rail-tests, time-grid-tests, toolbar-tests, autocomplete-tests, emoji-tests, moment-tests, ouro-lib-tests, ouro-tests, ouro-census, ouro-source-rules, ax-claims, ax-cli, ax-command, ax-component, ax-effects, ax-example, ax-exit-codes, ax-flows, ax-lint, ax-mcp, ax-outcome, ax-output, ax-problem, ax-voice, ax-wait, ax-work-event, ax-xray, ax-claims-tests, ax-cli-tests, ax-command-tests, ax-component-tests, ax-effects-tests, ax-exit-codes-tests, ax-flows-tests, ax-lint-tests, ax-mcp-tests, ax-outcome-tests, ax-output-tests, ax-problem-tests, ax-voice-tests, ax-wait-tests, ax-work-event-tests, ax-xray-tests, ouro-ax, ouro-ax-tests

1. https://github.com/ourostack/ouro-ui/releases/tag/v0.1.0 verify:urlOk(https://github.com/ourostack/ouro-ui/releases/tag/v0.1.0) ↩ ↩²

2. https://github.com/ourostack/ouro-ui/releases/tag/v0.2.0 verify:urlOk(https://github.com/ourostack/ouro-ui/releases/tag/v0.2.0) ↩ ↩²

3. scripts/install-test.sh; scripts/upgrade-note.mjs verify:testExists(scripts/upgrade-note.test.mjs::the upgrade install test runs the note's commands and copies none) verify:ciJob(install-upgrade) ↩ ↩²

4. https://github.com/ourostack/ouro-ui/releases; .github/workflows/release.yml; scripts/release-commit.sh verify:urlOk(https://github.com/ourostack/ouro-ui/releases) verify:fileLine(.github/workflows/release.yml, /scripts/release-commit.sh "$VERSION"/) verify:fileLine(scripts/release-commit.sh, /changes.mjs assemble/) ↩

5. https://github.com/ourostack/ouro-ui/releases/tag/v0.3.0 verify:urlOk(https://github.com/ourostack/ouro-ui/releases/tag/v0.3.0) verify:fileLine(registry/ouro/theme/ouro-base.css, /--ouro-layer: 50;/) ↩

6. scripts/source-rules.mjs verify:testExists(scripts/source-rules.test.mjs::every istanbul hint in registry/ carries @preserve, so it survives esbuild in an app) ↩

7. https://github.com/ourostack/ouro-ui/releases/tag/v0.3.1 verify:urlOk(https://github.com/ourostack/ouro-ui/releases/tag/v0.3.1) ↩

8. https://github.com/ourostack/ouro-ui/releases/tag/v0.8.0 verify:urlOk(https://github.com/ourostack/ouro-ui/releases/tag/v0.8.0) verify:testExists(scripts/registry.test.mjs::only ouro-base and ouro-theme touch the app's stylesheet, and no other item installs them) verify:testExists(scripts/registry.test.mjs::each lib helper is its own item, so an item installs only the helpers it imports) ↩ ↩² ↩³ ↩⁴ ↩⁵ ↩⁶ ↩⁷ ↩⁸ ↩⁹ ↩¹⁰ ↩¹¹ ↩¹²

9. registry/ouro/components/ouro/link/link.touch.test.tsx verify:testExists(registry/ouro/components/ouro/link/link.touch.test.tsx::gives a link on its own line a 44px box, centred on its text) ↩

10. test:scripts/registry.test.mjs::devDependencies are named without a version, so the CLI installs it only when the app lacks it and never changes a version the app has verify:testExists(scripts/registry.test.mjs::devDependencies are named without a version, so the CLI installs it only when the app lacks it and never changes a version the app has) ↩

11. registry/ouro/lib/ouro/testing/vitest.ts; https://github.com/ourostack/ouro-ui/releases/tag/v0.8.3 verify:urlOk(https://github.com/ourostack/ouro-ui/releases/tag/v0.8.3) verify:testExists(scripts/testing-kit.test.mjs::page sizes every Playwright host while the touch frame keeps its phone viewport and input) verify:testExists(scripts/testing-kit.test.mjs::ouroTestProjects leaves the page size to Vitest unless the app sets one) verify:fileLine(registry/ouro/lib/ouro/testing/vitest.ts, /390x844/) verify:fileLine(docs/guides/testing.md, /1600/) ↩ ↩² ↩³ ↩⁴

12. https://github.com/ourostack/ouro-ui/releases/tag/v1.0.0 verify:urlOk(https://github.com/ourostack/ouro-ui/releases/tag/v1.0.0) ↩ ↩²

13. https://github.com/ourostack/ouro-ui/releases/tag/v1.1.0 verify:urlOk(https://github.com/ourostack/ouro-ui/releases/tag/v1.1.0) verify:fileLine(registry/ouro/theme/ouro-base.css, /--ouro-shadow-sheet-/) verify:fileLine(registry/ouro/theme/ouro-base.css, /--ouro-duration-draw:/) ↩ ↩²

14. test/theme-tokens.test.tsx verify:testExists(test/theme-tokens.test.tsx::standard shadow and font tokens > falls back to the inherited font for headings when the theme names none, and Kbd always keeps it) ↩

15. https://github.com/ourostack/ouro-ui/releases/tag/v1.0.2 verify:urlOk(https://github.com/ourostack/ouro-ui/releases/tag/v1.0.2) verify:fileLine(registry/ouro/lib/ouro/form-answer.ts, /Snapshot arrays are readonly/) ↩ ↩²

16. https://github.com/ourostack/ouro-ui/releases/tag/v1.2.2; registry/ouro/components/ouro/button/button.test.tsx; registry/ouro/components/ouro/link/link.test.tsx verify:urlOk(https://github.com/ourostack/ouro-ui/releases/tag/v1.2.2) verify:testExists(registry/ouro/components/ouro/button/button.test.tsx::link branch > uses the document for reloadDocument and downloads, retaining router navigation otherwise) verify:testExists(registry/ouro/components/ouro/link/link.test.tsx::Link > treats only a present download as document navigation, including an empty filename) ↩ ↩²

17. registry/ouro/lib/ouro/portal-container.test.tsx verify:testExists(registry/ouro/lib/ouro/portal-container.test.tsx::usePortalContainer > leaves a popup at the end of , Base UI's default, without a portalContainer) verify:testExists(registry/ouro/lib/ouro/portal-container.test.tsx::usePortalContainer > warns once, in development, when a popup opens outside every landmark of a page that has a main) ↩

18. registry/ouro/lib/ouro/portal-container.test.tsx verify:testExists(registry/ouro/lib/ouro/portal-container.test.tsx::usePortalContainer > gives popups Base UI's own place again inside an OuroProvider whose portalContainer is null, as an app's own dialog needs) ↩

19. registry/ouro/components/ouro/sidebar/sidebar-layout.test.tsx verify:testExists(registry/ouro/components/ouro/sidebar/sidebar-layout.test.tsx::SidebarLayout > puts the header in the page's banner landmark, and draws no empty landmark without one) ↩

20. registry/ouro/lib/ouro/testing/axe.test.ts verify:testExists(registry/ouro/lib/ouro/testing/axe.test.ts::audit > fails a violation whatever its impact: content outside every landmark is only moderate) ↩

21. scripts/registry.test.mjs verify:testExists(scripts/registry.test.mjs::npm dependencies are pinned to the ranges this repository tests) ↩

22. registry/ouro/components/ouro/toast/toaster.test.tsx verify:testExists(registry/ouro/components/ouro/toast/toaster.test.tsx::Toaster > renders an empty Notifications landmark in a portal, which holds its own live regions) ↩

23. registry/ouro/components/ouro/toast/toaster.test.tsx verify:testExists(registry/ouro/components/ouro/toast/toaster.test.tsx::toast() > keeps every toast, its action and its dismiss button reachable by a screen reader while the stack rests collapsed) ↩

24. registry/ouro/lib/ouro/testing/axe.test.ts verify:testExists(registry/ouro/lib/ouro/testing/axe.test.ts::audit > fails, naming what changed, when its Tab walk closes a popup that focus leaving closes, which it cannot open again) ↩

25. registry/ouro/theme/ouro-base.css verify:fileLine(registry/ouro/theme/ouro-base.css, /--avatar-8:/) verify:testExists(registry/ouro/components/ouro/avatar/avatar.test.tsx::Avatar colors > picks the same hue for the same name, and spreads names across the hues) ↩

26. registry/ouro/components/ouro/avatar/avatar.test.tsx verify:testExists(registry/ouro/components/ouro/avatar/avatar.test.tsx::Avatar shapes and icons > clips a square's picture to its corners) ↩

27. https://ui.shadcn.com/docs/cli verify:urlOk(https://ui.shadcn.com/docs/cli) ↩ ↩²

28. https://github.com/shadcn-ui/ui/blob/3502dbcde11d1eaf967a47ac375744dc336641f3/packages/registry/src/utils/updaters/update-css-vars.ts#L91-L124 verify:urlOk(https://github.com/shadcn-ui/ui/blob/3502dbcde11d1eaf967a47ac375744dc336641f3/packages/registry/src/utils/updaters/update-css-vars.ts#L91-L124) verify:testExists(scripts/install-check.test.mjs::a complete install passes, for each variant and stage) ↩

29. UPGRADING.md verify:fileLine(UPGRADING.md, /[ -n "$items" ] || { echo "No Ouro components/) ↩

30. https://github.com/ourostack/ouro-ui/releases/tag/v0.7.0 verify:urlOk(https://github.com/ourostack/ouro-ui/releases/tag/v0.7.0) ↩

31. scripts/registry.mts verify:fileLine(scripts/registry.mts, /vitest: "4.1.11"/) verify:fileLine(scripts/registry.mts, /playwright: "1.58.1"/) verify:fileLine(scripts/registry.mts, /storybook: "10.2.10"/) ↩

32. https://github.com/ourostack/ouro-ui/releases/tag/v0.2.0; scripts/install-check.mjs verify:urlOk(https://github.com/ourostack/ouro-ui/releases/tag/v0.2.0) verify:testExists(scripts/install-check.test.mjs::a token that refers to itself fails) ↩