@trinityui/design-system 2.11.1 → 2.13.1

package/CONTRIBUTING.md

@@ -22,33 +22,28 @@ Please be respectful and constructive in all interactions. We are committed to p
 
 ### Prerequisites
 
-- Node.js 18+ 
-- npm 9+
+- Node.js 24 (the version CI uses)
+- pnpm 10 (pinned in `package.json` `packageManager`; `corepack enable` provides it)
 - Git
 
 ### Setup
 
 1. Clone the repository:
    ```bash
-   git clone https://github.com/your-org/trinity-design-system.git
+   git clone https://github.com/Trinity-UI-Components/trinity-design-system.git
    cd trinity-design-system
    ```
 
 2. Install dependencies:
    ```bash
-   npm install
+   pnpm install --frozen-lockfile
    ```
 
    Commercial licensing note: For MUI, AG Grid, or Syncfusion license procurement/renewal, contact Arun Manoharan, Rahul Desai, or Sangeetha before production rollout.
 
-3. Start the development server:
+3. Start Storybook, the development environment (there is no separate app dev server):
    ```bash
-   npm run dev
-   ```
-
-4. Start Storybook:
-   ```bash
-   npm run storybook
+   pnpm start
    ```
 
 ## Development Workflow
@@ -149,12 +144,28 @@ export const MyComponent: React.FC<MyComponentProps> = ({
 
 ### Export Components
 
-Add exports to `src/components/index.ts`:
+A component is public only when a package entry exports it. `src/index.ts` is the root entry: add the component and its types there, in the section for its kind, with the `// Import:` comment the other exports use.
 
 ```typescript
-export * from './MyComponent';
+// src/index.ts
+// Import: import { MyComponent } from '@trinityui/design-system';
+export { MyComponent } from './components/MyComponent';
+export type { MyComponentProps } from './components/MyComponent';
 ```
 
+- An AI component also goes in the AI barrel, `src/components/AI/index.ts`.
+- A component that belongs in the `essentials` or `data-table` entry also goes in `src/essentials.ts` or `src/data-table.ts`.
+- There is no `src/components/index.ts`. A barrel that no entry imports never reaches consumers (see `docs/remediation/HITL-A-15-components-barrel.md`).
+
+Then build and update the public API snapshot in the same PR:
+
+```bash
+pnpm run build
+node scripts/check-api-surface.mjs --update   # rewrites docs/api/public-api.json
+```
+
+Every new export needs `@since x.y` in its JSDoc and a minor changeset. A new component also needs an approved entry in `docs/process/approved-proposals.json`. `node scripts/check-api-surface.mjs` checks all three against the base branch (`docs/remediation/HITL-A-18-api-surface.md`).
+
 ## Styling Guidelines
 
 ### Use Theme Tokens
@@ -169,6 +180,26 @@ Always use theme tokens from `src/theme.ts`:
 <Box sx={{ color: '#003366', borderRadius: '16px' }}>
 ```
 
+`trinity/color-literal` reports hex colors, `rgba()`/`hsla()` strings and px-only literals in `sx`/`style` on the lines you change in `src/components` and `src/hooks` ([TOKEN_USAGE_RULES.md](docs/TOKEN_USAGE_RULES.md)). A deliberate literal takes `// eslint-disable-next-line trinity/color-literal -- @intentional-color: <category> - <reason>` with a category from [INTENTIONAL_EXCEPTIONS.md](docs/INTENTIONAL_EXCEPTIONS.md).
+
+### Linting
+
+- CI runs `pnpm lint:changed`: ESLint with `eslint.config.js` on the files changed since the base, failing on any finding (warnings included) on a changed line. A new or extracted file counts as changed in full. Existing debt elsewhere is not reported; `pnpm lint` shows it.
+- Every `eslint-disable` names the rules it disables and says why after ` -- `; an unused directive is an error. This mirrors the behavior contract's waivers.
+- In `src/components` and `src/patterns`, three structural rules also run on changed lines (B-18):
+  - `trinity/sx-spread` (ADR-04): never spread the `sx` prop into an object. Merge it as an array: `sx={[baseSx, ...(Array.isArray(sx) ? sx : [sx])]}`.
+  - `trinity/rtl-physical` (ADR-11): use logical keys (`marginInlineStart`, `paddingInlineEnd`, `insetInlineStart`) instead of `ml`, `mr`, `pl`, `pr`, `marginLeft`, `paddingRight`, `left` or `right` in `sx` and `style`. Two cases are real exceptions and take a reasoned disable: centering (`left: '50%'` with `translateX(-50%)`) and data or measured coordinates (a bar's x on a time axis, a position from `getBoundingClientRect`). Example: `// eslint-disable-next-line trinity/rtl-physical -- data coordinate: x is a value on the time axis`.
+  - `trinity/units-px` (ADR-20): `aiSpacing` values are theme units, so never write `${aiSpacing.md}px`. Use `theme.spacing(aiSpacing.md)`.
+- In `src/components` and `src/patterns`, the theming rules also run on changed lines (E-08; [TOKEN_USAGE_RULES.md](docs/TOKEN_USAGE_RULES.md) §1, §8-§11):
+  - `trinity/color-source` (ADR-03, ADR-26): read colors through `useTrinityPalette()` or `getTrinityPalette(theme)`, never `aiTokens.colors`, `semanticTokens.colors`/`.effects`, `brandColors`, raw `theme.palette.trinity` or `'trinity.*'` palette path strings.
+  - `trinity/mode-branch` (ADR-03): never compare `palette.mode` or call `applyStyles('dark')`; the resolver already returns the active mode's role.
+  - `trinity/token-hook-branch` (E-31): `useTrinityTokens()`'s `getColor`, `isDarkMode` and `getSemanticColor` are for app code; components use the resolver.
+  - `trinity/global-keyframes` (ADR-11): use `keyframes()` from `@mui/material/styles`, not a `'@keyframes name'` key, whose global name another component can override.
+  - `trinity/motion-literal` (ADR-22-R7): durations come from `theme.transitions` or the motion tokens, and timeouts are 0 under reduced motion. A decorative loop whose period is part of the design takes a reasoned disable, for example `// eslint-disable-next-line trinity/motion-literal -- decorative spinner: its period is not a UI transition`.
+  - `trinity/inline-font-size` (AI surfaces only): use a Typography variant, `theme.typography.<variant>` or an `aiTypography` token instead of a px, rem, em or numeric `fontSize`. Icon sizes are exempt.
+- A new file, or code you move into a new file, is linted in full: every line counts as changed. Fix or disable (with a reason) every finding in it before you open the PR, including findings in code you only moved.
+- New rule families go into the one local plugin, `eslint/plugin-trinity.js`, as `trinity/*` rules: a family of AST selectors is a `SELECTOR_RULES` entry with an invalid and a valid example per selector; a rule that needs more context is a rule object. Never add a `no-restricted-syntax` entry or block (DN-07 a): one shared id makes every waiver silence every family, and `src/__tests__/eslintRules.test.ts` fails when a config sets it for component files.
+
 ### Accessible Color Combinations
 
 Use `accessibleCombinations` for text/background pairs:
@@ -191,7 +222,7 @@ import { accessibleCombinations } from '../theme';
 
 ## Accessibility Requirements
 
-All components must meet **WCAG 2.1 AA** standards:
+All components must meet **WCAG 2.2 AA** standards:
 
 ### Minimum Requirements
 
@@ -203,26 +234,70 @@ All components must meet **WCAG 2.1 AA** standards:
 
 ### Behavior Contract (enforced in CI)
 
-Don't hand-roll behaviors the design system already provides: live announcements, clipboard, reduced motion, focus trapping, roving focus, visually hidden text, controlled state, expand/collapse, ids, pressable elements, icon-button names. [docs/BEHAVIOR_CONTRACT.md](docs/BEHAVIOR_CONTRACT.md) names the one sanctioned implementation for each.
+Don't hand-roll behaviors the design system already provides. [docs/BEHAVIOR_CONTRACT.md](docs/BEHAVIOR_CONTRACT.md) §2 names the one sanctioned implementation for each, and the export it comes from:
+
+| Behavior | Use |
+|---|---|
+| A message a screen reader should read ("Copied", "Saved") | `useAnnounce()` |
+| A live container (chat log, streaming answer) | `liveRegionProps()`, inside the package wrapped in `LiveRegionProvider` |
+| An async action (Save, Confirm, Retry) | `useAsyncAction()`; its failure in `AsyncOutcomeAlert` (internal) |
+| Copy to clipboard | `useClipboard({ announce })` |
+| CSS motion / JS-timed motion / smooth scrolling | `[REDUCED_MOTION_QUERY]` in `sx` / `useReducedMotion()` |
+| Focus trapping | MUI's built-in trap (`Dialog`, `Popover`, `Menu`, temporary `Drawer`); `useFocusTrap` is deprecated |
+| Arrow keys within a group | MUI's own widget, else `useRovingTabIndex()` (registry form) |
+| Screen-reader-only text | `VisuallyHidden`, or `visuallyHiddenSx` for an element that cannot be one |
+| Controlled and uncontrolled props | `useControlled` from `@mui/utils/useControlled` |
+| Expand/collapse and popup triggers | `useDisclosure()` |
+| A focused control that unmounts or disables itself | `useFocusOnReplace()` (internal) |
+| Ids and ARIA relationships | `React.useId()`, with the id prop as an override |
+| Anything clickable | `Button`, `IconButton`, `ButtonBase`, `ListItemButton`; a clickable card or row with nested actions uses the primary-action overlay (internal) |
+| Icon-only buttons | `aria-label` plus a `Tooltip` with the same text |
+| Untrusted HTML and URLs | `renderSafeHtml()`, `isSafeHref()`, `isSafeSrc()` (internal) |
+
+Live demos are in Storybook under Foundation/Accessibility and Utilities/Hooks. Composite widgets follow their keyboard model in [docs/remediation/keyboard-models.md](docs/remediation/keyboard-models.md) (ADR-34).
 
 `pnpm check:behavior` runs on every PR and fails on new hand-rolled behavior. Run `pnpm check:behavior --report` to see each finding with its fix.
 
+The findings it still allows are recorded in `scripts/behavior-contract-baseline/`, one shard per source file, and every finding names its one owner, the plan item that fixes it ([README](scripts/behavior-contract-baseline/README.md)). After a fix, run `pnpm check:behavior --update` and commit the changed shard with the fix.
+
+**Hot-file rule (`hot-file:behavior-baseline`).** A PR that changes more than one shard, such as a guard change that re-baselines many files (B-16, B-17, B-19, B-54), carries the `hot-file:behavior-baseline` label and lands alone (ADR-28). A PR that changes only its own component's shard needs no label and can land in parallel with others.
+
+### Icons (enforced in CI)
+
+Components render icons through `Icon` (ADR-10). A direct import of `@mui/icons-material` or `react-feather` in `src/components` fails `trinity/icon-imports` on the changed line, and `pnpm check:icon-imports` fails when a new file imports one. The files that still do are listed in `scripts/icon-imports-baseline.json`; the list only shrinks.
+
+- **Touching a listed file:** migrate its icons in a separate commit of the same PR, with a PNG compare of the affected stories (ADR-10 (8), OD-B6 (a)). If a glyph has no Icon name with an approved optical match yet, migrate that file in an immediate follow-up PR instead (OD-B6 (b)).
+- **After migrating:** run `pnpm check:icon-imports --update` and commit the shorter baseline.
+- **A missing name:** request it through C-28 in [the I-06 manifest](docs/remediation/I-06-icon-manifest.md). Names are never synonyms of existing ones.
+- **No library pins.** A component's `<Icon>` follows the app's `IconProvider`; it never passes `library` (C-38+ removed the last pins, see [D icon pins](docs/remediation/D-icon-pins.md), and `Icon.pins.test.ts` fails on a new one). A migration whose glyph differs from the file's old import is a visible correction: it carries the PNG compare under both libraries and its own changeset.
+
 ### Testing Accessibility
 
+Tests use the helpers in `src/testing/` (B-01): `expectNoA11yViolations` (axe, light and dark), `readAnnouncements` (what a screen reader would announce right now), `assertNoNestedLive` (no live region inside another), user-event keyboard helpers and `createMatchMediaController` (reduced motion). Every axe check sits inside `describe('Accessibility')`.
+
 ```tsx
-// Use accessibility utilities
-import { useReducedMotion, VisuallyHidden } from '../accessibility';
+import { describe, expect, it } from 'vitest';
+import { render, screen, waitFor, expectNoA11yViolations } from '../../testing/test-utils';
+import { readAnnouncements } from '../../testing/announcements';
+import { assertNoNestedLive } from '../../testing/assertNoNestedLive';
+import { MyComponent } from '../MyComponent';
 
-const MyComponent = () => {
-  const prefersReducedMotion = useReducedMotion();
-  
-  return (
-    <button>
-      <VisuallyHidden>Screen reader text</VisuallyHidden>
-      <Icon aria-hidden="true" />
-    </button>
-  );
-};
+describe('Accessibility', () => {
+  it('has no accessibility violations in light and dark', async () => {
+    const light = render(<MyComponent />);
+    await expectNoA11yViolations(light.container);
+    light.unmount();
+    const dark = render(<MyComponent />, { theme: 'dark' });
+    await expectNoA11yViolations(dark.container);
+  });
+
+  it('announces the outcome and keeps live regions flat', async () => {
+    const { user } = render(<MyComponent />);
+    await user.click(screen.getByRole('button', { name: 'Save' }));
+    await waitFor(() => expect(readAnnouncements().polite).toContain('Saved'));
+    assertNoNestedLive(document.body);
+  });
+});
 ```
 
 ### Storybook Accessibility Addon
@@ -245,62 +320,70 @@ src/
 
 ```bash
 # Run all tests
-npm test
+pnpm test
 
-# Run tests with coverage
-npm run test:coverage
+# Run tests with a coverage report (no thresholds are configured)
+pnpm test:coverage
 
 # Run tests in watch mode
-npm run test:watch
+pnpm test:watch
+
+# Run the accessibility lane (tests named "Accessibility")
+pnpm test:a11y
 ```
 
 ### Test Template
 
+Copy `src/testing/component.template.test.tsx`. It is organised as rendering, variants, accessibility, keyboard, interaction, integration and edge cases, and its accessibility section already holds the cases every component needs: axe in light and dark, under a brand colour and right to left, the accessible name, announcements read with `readAnnouncements` and checked with `assertNoNestedLive`, and keyboard paths driven through user-event (`render` returns `user`). The short form:
+
 ```tsx
-import { describe, it, expect, vi } from 'vitest';
-import { render, screen, fireEvent } from '@testing-library/react';
+import { describe, expect, it, vi } from 'vitest';
+import { render, screen, expectNoA11yViolations } from '../../testing/test-utils';
 import { MyComponent } from '../MyComponent';
 
 describe('MyComponent', () => {
-  it('should render with default props', () => {
+  it('renders with default props', () => {
     render(<MyComponent>Content</MyComponent>);
     expect(screen.getByText('Content')).toBeInTheDocument();
   });
 
-  it('should handle click events', () => {
+  it('runs onClick from the keyboard', async () => {
     const onClick = vi.fn();
-    render(<MyComponent onClick={onClick}>Click me</MyComponent>);
-    
-    fireEvent.click(screen.getByText('Click me'));
-    expect(onClick).toHaveBeenCalled();
+    const { user } = render(<MyComponent onClick={onClick}>Click me</MyComponent>);
+    await user.tab();
+    await user.keyboard('{Enter}');
+    expect(onClick).toHaveBeenCalledTimes(1);
   });
 
-  it('should apply custom styles', () => {
-    render(<MyComponent sx={{ color: 'red' }}>Styled</MyComponent>);
-    // Assert styles
+  describe('Accessibility', () => {
+    it('has no accessibility violations', async () => {
+      const { container } = render(<MyComponent>Content</MyComponent>);
+      await expectNoA11yViolations(container);
+    });
   });
 });
 ```
 
-### Coverage Requirements
+### Test Requirements
 
-- Minimum 80% code coverage for new components
+- No coverage threshold is enforced (`pnpm test:coverage` only reports).
 - All public APIs must have tests
 - Edge cases and error states should be tested
+- A CPU-bound test (it spawns a process, parses the repository, imports a whole package entry or renders a large tree) takes its timeout from `src/testing/timeouts.ts` (`CPU_BOUND`), never a number; the `test-time-budgets` guard checks it. The rule is in [docs/TESTING_STRATEGY.md](docs/TESTING_STRATEGY.md#time-budgets-for-cpu-bound-tests).
 
 ## Documentation
 
 ### Storybook Stories
 
-Every component needs a Storybook story:
+Every component needs a Storybook story, in the CSF-factory form [STORYBOOK_STANDARDS.md](docs/STORYBOOK_STANDARDS.md) describes (start from `src/stories/utils/ComponentTemplate.stories.tsx.txt`):
 
 ```tsx
 // src/stories/MyComponent.stories.tsx
-import type { Meta, StoryObj } from '@storybook/react';
+import preview from '#.storybook/preview';
 import { MyComponent } from '../components/MyComponent';
 
-const meta: Meta<typeof MyComponent> = {
-  title: 'Components/MyComponent',
+const meta = preview.meta({
+  title: 'Data Display/MyComponent', // an IA category from docs/NAMING.md, then the component
   component: MyComponent,
   tags: ['autodocs'],
   argTypes: {
@@ -310,25 +393,35 @@ const meta: Meta<typeof MyComponent> = {
       description: 'Visual variant',
     },
   },
-};
-
-export default meta;
-type Story = StoryObj<typeof meta>;
+});
 
-export const Default: Story = {
+export const Default = meta.story({
   args: {
     children: 'Default content',
   },
-};
+});
 
-export const Secondary: Story = {
+export const Secondary = meta.story({
   args: {
     variant: 'secondary',
     children: 'Secondary variant',
   },
-};
+});
 ```
 
+#### Internal-block stories (`STORYBOOK_INCLUDE_INTERNAL`)
+
+Stories for internal blocks (ADR-02) live in `src/stories/internal/` with the title `Internal/<Name>`. They are part of the build only when the environment variable `STORYBOOK_INCLUDE_INTERNAL=1` is set:
+
+| Command | Internal stories |
+|---|---|
+| `pnpm start` | included |
+| `pnpm test:storybook` | included (they are tested) |
+| `pnpm build-storybook:internal` | included (output `storybook-static-internal/`, for visual review) |
+| `pnpm build-storybook` | **never**: this is the published build behind the docs site, `index.json` and the MCP manifest |
+
+The first three set the variable through `scripts/with-internal-stories.mjs`, which works in every shell; do not set it by hand for the published build. `check-story-titles --artifact` fails a published build that contains an `Internal/` entry, and the Figma link check ignores `src/stories/internal/`. (The a11y canary in `src/stories/internal/canary/` has its own variable, `STORYBOOK_A11Y_CANARY=1`, which only CI sets.)
+
 ### JSDoc Comments
 
 All exported functions and components should have JSDoc comments:
@@ -351,19 +444,35 @@ export const getAccessibleColor = (backgroundColor: string): string => {
 };
 ```
 
+### Generated regions
+
+Some text in the docs is generated, and a test fails when it is edited by hand. Change the generator (or the source it reads), then run its `--write` command:
+
+| Region | Markers | Generator | Test |
+|---|---|---|---|
+| README intro, Key Capabilities (component, AI, chart, template, hook, export and CSS variable counts), Packages & Entry Points (`entry-points`: the exports of each subpath) and the AI table (`ai-table`: the AI components by group with their Storybook page, the contracts and helpers, the deprecated AI exports with their replacements); the same counts for the Storybook guide pages in `src/stories/generated/catalogCounts.ts` (the whole file) | `<!-- catalog-counts:start <id> -->` ... `<!-- catalog-counts:end <id> -->` | `node scripts/generate-catalog-counts.mjs --write` | `src/__tests__/docs/catalog-counts.test.ts` |
+| DEFINITION_OF_DONE automated list | `<!-- automated:begin ... -->` ... `<!-- automated:end -->` | `node scripts/render-definition-of-done.mjs --write` | `src/__tests__/docs/definition-of-done.test.ts` |
+
+The counts come from the export manifest (`docs/api/public-api.json`, kept equal to the build by `pnpm check:api`), so a change that adds or deprecates a root export reruns the catalog-counts generator. A new AI component also needs its row in `AI_TABLE` (a deprecated one, its replacement in `AI_DEPRECATED`) in `scripts/generate-catalog-counts.mjs`: until then the render fails and names it. Do not type a catalog count ("100+ components", "17 chart types") anywhere else: the same test rejects one on the README and the guidance pages.
+
 ## Pull Request Process
 
+A pull request is done when it meets the [definition of done](docs/DEFINITION_OF_DONE.md): every automated check of the guard registry passes, and the manual items (screen-reader scenarios, story prose, the visual review, React and CSS parity) are covered.
+
 ### Before Submitting
 
-1. ✅ Run `npm run lint` and fix any issues
-2. ✅ Run `npm test` and ensure all tests pass
-3. ✅ Run `npm run build` to verify build succeeds
-4. ✅ Update documentation if needed
+1. ✅ Run `pnpm lint:changed` and fix any finding on the lines you changed
+2. ✅ Run `pnpm test` and ensure all tests pass
+3. ✅ Run `pnpm typecheck` and `pnpm build`
+4. ✅ Update documentation if needed (`pnpm check:docs` checks links and script names)
 5. ✅ Add/update Storybook stories
-6. ✅ Update CHANGELOG.md with your changes
+6. ✅ Add one changeset (`pnpm changeset`, or `pnpm changeset --empty` if the PR changes no code, types, styles, LICENSE file or dependencies; [.changeset/README.md](.changeset/README.md) has the rule, including docs that ship in the tarball). Never edit CHANGELOG.md or a package version by hand; release PRs do that from the changesets (docs/CHANGESETS.md).
+7. ✅ Optionally run `pnpm verify:release`, the full gate CI runs as the `verify` check
 
 ### PR Template
 
+GitHub fills in `.github/PULL_REQUEST_TEMPLATE.md` on every PR. The short form:
+
 ```markdown
 ## Description
 Brief description of the changes.
@@ -378,21 +487,23 @@ Brief description of the changes.
 - [ ] Tests added/updated
 - [ ] Documentation updated
 - [ ] Storybook stories added/updated
-- [ ] CHANGELOG.md updated
-- [ ] Accessibility requirements met
+- [ ] One changeset added (CHANGELOG.md is never edited by hand)
+- [ ] Accessibility requirements met (WCAG 2.2 AA)
 - [ ] Behavior contract passes (`pnpm check:behavior`); any waiver has a reason
-- [ ] Token compliance verified (`npm run lint:tokens`)
-- [ ] Any `eslint-disable` for colors references [INTENTIONAL_EXCEPTIONS.md](docs/INTENTIONAL_EXCEPTIONS.md)
+- [ ] `pnpm lint:changed` passes (token rules included)
+- [ ] Every `eslint-disable` names its rules and gives a reason; color disables use `@intentional-color: <category> - <reason>` from [INTENTIONAL_EXCEPTIONS.md](docs/INTENTIONAL_EXCEPTIONS.md)
 
 ## Screenshots (if applicable)
 ```
 
 ### Review Process
 
-1. Create PR against `main` branch
-2. Request review from team members
-3. Address feedback and update PR
-4. Squash and merge when approved
+1. Create the PR against `main` (or against a release line, `release/<major>.<minor>.x`, for a maintenance fix). Name the branch `<ws>/<ITEM-ID>-<slug>` for plan items.
+2. Keep one concern and one changeset per PR (see [CHANGESETS.md](docs/CHANGESETS.md)).
+3. Wait for the required checks, including `verify`. Address feedback by pushing new commits; do not force-push a branch that is under review.
+4. Merge with a **merge commit**. Squash and rebase merges are turned off on `main` and on release lines: commit boundaries are evidence (a characterization commit stays separate from its fix, a dependency bump from its lockfile change), and a merge commit keeps every cited SHA valid.
+
+A commit that records today's behavior before a fix carries the trailer `Characterizes: <Component> (ADR-17)`; the `characterization-proof` check runs its tests at its own SHA and expects its `it.fails` cases to be flipped by the fix. The full rules, the rulesets and the single-maintainer sign-off are in [docs/process/BRANCHING.md](docs/process/BRANCHING.md).
 
 ## Questions?
 

package/LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2026 Trinity Design
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.