@flowstack-ui/agent-tools 0.1.0-bootstrap.0

package/public/packages/atom/0.24.0/components/label.txt

@@ -0,0 +1,121 @@
+# Label
+
+Source: @flowstack-ui/atom@0.24.0
+Kind: component
+ID: label
+
+# Label agent guide
+
+## Purpose
+
+Provide a server-safe native label for one form control, with optional consumer-owned state metadata and no independent behavior contract.
+
+## Use when
+
+- One native form control needs a standalone visible text label and does not require coordinated description, error, or Field state wiring.
+
+## Choose something else when
+
+- The control also needs coordinated required, disabled, invalid, description, or error relationships, or the text labels a group of controls. Use Field.Label or Fieldset.
+
+## Required composition
+
+- Render clear visible text in Root and either match htmlFor to exactly one labelable control id or wrap that control. Mirror optional metadata props only when useful for selectors, while applying real disabled, required, readOnly, and invalid state to the control itself.
+
+## Rules
+
+- **MUST:** Associate Root with one labelable control through matching htmlFor and id or valid native wrapped-control labeling.
+- **MUST:** Use clear visible label text; do not replace an ordinary form label with placeholder text or an unlabeled icon.
+- **MUST:** Treat disabled, required, readOnly, and invalid props as data metadata only and apply the corresponding native or ARIA state to the associated control.
+- **MUST:** Use Field.Label when label, control, description, error, and shared state need coordinated IDs and relationships.
+- **MUST:** Do not use one Label for several controls; use Fieldset and Legend or the component's group labeling contract.
+
+## Common mistakes
+
+- **Avoid:** Setting Label required or invalid and assuming the control announces or enforces that state. **Instead:** Apply actual required and invalid semantics to the control and keep Label metadata synchronized.
+- **Avoid:** Using htmlFor that does not match an id, wrapping multiple controls, or using Label as general text styling. **Instead:** Maintain one valid native label-control association and use ordinary text elements for non-form content.
+
+## Validation checklist
+
+- Verify explicit htmlFor/id and wrapped-control variants focus or activate the intended native control and expose the correct accessible name.
+- Verify disabled, required, read-only, and invalid data attributes reflect consumer state while the control independently exposes and enforces its real state.
+- Confirm complex fields use Field, control groups use Fieldset or their group primitive, and asChild or render overrides preserve valid labeling semantics, props, and refs.
+
+## Related guidance
+
+- `field`
+- `fieldset`
+- `input`
+
+## Machine record
+
+```json
+{
+  "schema": "flowstack.agent-component.v1",
+  "id": "label",
+  "name": "Label",
+  "package": "@flowstack-ui/atom",
+  "layer": "atom",
+  "kind": "component",
+  "purpose": "Provide a server-safe native label for one form control, with optional consumer-owned state metadata and no independent behavior contract.",
+  "useWhen": [
+    "One native form control needs a standalone visible text label and does not require coordinated description, error, or Field state wiring."
+  ],
+  "avoidWhen": [
+    {
+      "condition": "The control also needs coordinated required, disabled, invalid, description, or error relationships, or the text labels a group of controls.",
+      "useInstead": "Field.Label or Fieldset"
+    }
+  ],
+  "composition": [
+    "Render clear visible text in Root and either match htmlFor to exactly one labelable control id or wrap that control. Mirror optional metadata props only when useful for selectors, while applying real disabled, required, readOnly, and invalid state to the control itself."
+  ],
+  "rules": [
+    {
+      "id": "label-native-association",
+      "level": "must",
+      "statement": "Associate Root with one labelable control through matching htmlFor and id or valid native wrapped-control labeling."
+    },
+    {
+      "id": "label-visible-name",
+      "level": "must",
+      "statement": "Use clear visible label text; do not replace an ordinary form label with placeholder text or an unlabeled icon."
+    },
+    {
+      "id": "label-state-boundary",
+      "level": "must",
+      "statement": "Treat disabled, required, readOnly, and invalid props as data metadata only and apply the corresponding native or ARIA state to the associated control."
+    },
+    {
+      "id": "label-field-boundary",
+      "level": "must",
+      "statement": "Use Field.Label when label, control, description, error, and shared state need coordinated IDs and relationships."
+    },
+    {
+      "id": "label-group-boundary",
+      "level": "must",
+      "statement": "Do not use one Label for several controls; use Fieldset and Legend or the component's group labeling contract."
+    }
+  ],
+  "commonMistakes": [
+    {
+      "mistake": "Setting Label required or invalid and assuming the control announces or enforces that state.",
+      "correction": "Apply actual required and invalid semantics to the control and keep Label metadata synchronized."
+    },
+    {
+      "mistake": "Using htmlFor that does not match an id, wrapping multiple controls, or using Label as general text styling.",
+      "correction": "Maintain one valid native label-control association and use ordinary text elements for non-form content."
+    }
+  ],
+  "validation": [
+    "Verify explicit htmlFor/id and wrapped-control variants focus or activate the intended native control and expose the correct accessible name.",
+    "Verify disabled, required, read-only, and invalid data attributes reflect consumer state while the control independently exposes and enforces its real state.",
+    "Confirm complex fields use Field, control groups use Fieldset or their group primitive, and asChild or render overrides preserve valid labeling semantics, props, and refs."
+  ],
+  "related": [
+    "field",
+    "fieldset",
+    "input"
+  ]
+}
+```

package/public/packages/atom/0.24.0/components/link.txt

@@ -0,0 +1,100 @@
+# Link
+
+Source: @flowstack-ui/atom@0.24.0
+Kind: component
+ID: link
+
+# Link agent guide
+
+## Purpose
+
+Provide native destination navigation with composition support for router-owned anchors.
+
+## Use when
+
+- The user moves to a URL, route, document, download, email address, or telephone destination.
+
+## Choose something else when
+
+- The interaction changes current application state without navigating. Use Button.
+
+## Required composition
+
+- Render an anchor with a real href, or compose a router link that preserves anchor semantics and href output.
+
+## Rules
+
+- **MUST:** Provide a real navigable destination.
+- **MUST:** Make the accessible name describe the destination or result.
+
+## Common mistakes
+
+- **Avoid:** Using a click handler on a non-link element for navigation. **Instead:** Render Link or a router anchor through the public composition API.
+
+## Validation checklist
+
+- Inspect the rendered href.
+- Confirm Enter activates navigation and the link appears in the accessibility tree.
+
+## Related guidance
+
+- `button`
+- `pressable`
+- `breadcrumb`
+- `nav-list`
+- `navigation-menu`
+
+## Machine record
+
+```json
+{
+  "schema": "flowstack.agent-component.v1",
+  "id": "link",
+  "name": "Link",
+  "package": "@flowstack-ui/atom",
+  "layer": "atom",
+  "kind": "component",
+  "purpose": "Provide native destination navigation with composition support for router-owned anchors.",
+  "useWhen": [
+    "The user moves to a URL, route, document, download, email address, or telephone destination."
+  ],
+  "avoidWhen": [
+    {
+      "condition": "The interaction changes current application state without navigating.",
+      "useInstead": "Button"
+    }
+  ],
+  "composition": [
+    "Render an anchor with a real href, or compose a router link that preserves anchor semantics and href output."
+  ],
+  "rules": [
+    {
+      "id": "link-real-destination",
+      "level": "must",
+      "statement": "Provide a real navigable destination."
+    },
+    {
+      "id": "link-purpose",
+      "level": "must",
+      "statement": "Make the accessible name describe the destination or result."
+    }
+  ],
+  "commonMistakes": [
+    {
+      "mistake": "Using a click handler on a non-link element for navigation.",
+      "correction": "Render Link or a router anchor through the public composition API."
+    }
+  ],
+  "validation": [
+    "Inspect the rendered href.",
+    "Confirm Enter activates navigation and the link appears in the accessibility tree."
+  ],
+  "related": [
+    "button",
+    "pressable",
+    "breadcrumb",
+    "nav-list",
+    "navigation-menu"
+  ]
+}
+```

package/public/packages/atom/0.24.0/components/list.txt

@@ -0,0 +1,131 @@
+# List
+
+Source: @flowstack-ui/atom@0.24.0
+Kind: component
+ID: list
+
+# List agent guide
+
+## Purpose
+
+Render server-safe native ordered or unordered list structure without adding selection, activation, focus, or navigation behavior.
+
+## Use when
+
+- Content is naturally a set of peer items or a sequence whose order may carry meaning.
+
+## Choose something else when
+
+- Items are persistent route destinations. Use NavList.
+- Items form a keyboard-operated choice or action collection. Use Listbox, Menu, RadioGroup, or another matching interactive primitive.
+- Content only needs visual spacing and has no list relationship. Use the styled layer's layout primitive.
+
+## Required composition
+
+- Compose List.Root with List.Item children and set ordered only when item sequence changes meaning.
+- Preserve ul or ol and li semantics when using render or asChild.
+- Treat Item disabled state as descriptive metadata; separately disable or remove every interactive descendant when required.
+
+## Rules
+
+- **MUST:** Preserve a native list root and list-item descendants unless an equivalent composed host retains the same semantics.
+- **MUST:** Use ordered=true only when sequence changes meaning; visual numbering alone is not enough.
+- **MUST:** Do not add selection, activation, roving focus, or route-current behavior to List; choose the primitive that owns that interaction.
+- **SHOULD:** Keep static List composition server-safe unless authored descendants introduce a genuine client behavior requirement.
+
+## Common mistakes
+
+- **Avoid:** Using List as a generic row layout or adding click and keyboard behavior to its items. **Instead:** Use native list semantics only for real item relationships and select NavList, Listbox, Menu, or another behavior owner for interaction.
+- **Avoid:** Assuming Item disabled metadata disables nested controls. **Instead:** Apply the correct disabled contract to each interactive descendant because List only exposes descriptive item metadata.
+
+## Validation checklist
+
+- Inspect the rendered ul or ol and li anatomy and confirm ordered meaning, start, reversed, and item values where used.
+- Check list announcement in assistive technology, nested-list ownership, long content, zoom, and custom-render semantics.
+- Confirm List adds no keyboard model and every interactive descendant owns its own accessible name and disabled state.
+
+## Related guidance
+
+- `nav-list`
+- `listbox`
+- `menu`
+- `feed`
+
+## Machine record
+
+```json
+{
+  "schema": "flowstack.agent-component.v1",
+  "id": "list",
+  "name": "List",
+  "package": "@flowstack-ui/atom",
+  "layer": "atom",
+  "kind": "component",
+  "purpose": "Render server-safe native ordered or unordered list structure without adding selection, activation, focus, or navigation behavior.",
+  "useWhen": [
+    "Content is naturally a set of peer items or a sequence whose order may carry meaning."
+  ],
+  "avoidWhen": [
+    {
+      "condition": "Items are persistent route destinations.",
+      "useInstead": "NavList"
+    },
+    {
+      "condition": "Items form a keyboard-operated choice or action collection.",
+      "useInstead": "Listbox, Menu, RadioGroup, or another matching interactive primitive"
+    },
+    {
+      "condition": "Content only needs visual spacing and has no list relationship.",
+      "useInstead": "the styled layer's layout primitive"
+    }
+  ],
+  "composition": [
+    "Compose List.Root with List.Item children and set ordered only when item sequence changes meaning.",
+    "Preserve ul or ol and li semantics when using render or asChild.",
+    "Treat Item disabled state as descriptive metadata; separately disable or remove every interactive descendant when required."
+  ],
+  "rules": [
+    {
+      "id": "list-native-semantics",
+      "level": "must",
+      "statement": "Preserve a native list root and list-item descendants unless an equivalent composed host retains the same semantics."
+    },
+    {
+      "id": "list-order-meaning",
+      "level": "must",
+      "statement": "Use ordered=true only when sequence changes meaning; visual numbering alone is not enough."
+    },
+    {
+      "id": "list-no-interaction",
+      "level": "must",
+      "statement": "Do not add selection, activation, roving focus, or route-current behavior to List; choose the primitive that owns that interaction."
+    },
+    {
+      "id": "list-server-safe",
+      "level": "should",
+      "statement": "Keep static List composition server-safe unless authored descendants introduce a genuine client behavior requirement."
+    }
+  ],
+  "commonMistakes": [
+    {
+      "mistake": "Using List as a generic row layout or adding click and keyboard behavior to its items.",
+      "correction": "Use native list semantics only for real item relationships and select NavList, Listbox, Menu, or another behavior owner for interaction."
+    },
+    {
+      "mistake": "Assuming Item disabled metadata disables nested controls.",
+      "correction": "Apply the correct disabled contract to each interactive descendant because List only exposes descriptive item metadata."
+    }
+  ],
+  "validation": [
+    "Inspect the rendered ul or ol and li anatomy and confirm ordered meaning, start, reversed, and item values where used.",
+    "Check list announcement in assistive technology, nested-list ownership, long content, zoom, and custom-render semantics.",
+    "Confirm List adds no keyboard model and every interactive descendant owns its own accessible name and disabled state."
+  ],
+  "related": [
+    "nav-list",
+    "listbox",
+    "menu",
+    "feed"
+  ]
+}
+```

package/public/packages/atom/0.24.0/components/listbox.txt

@@ -0,0 +1,120 @@
+# Listbox
+
+Source: @flowstack-ui/atom@0.24.0
+Kind: component
+ID: listbox
+
+# Listbox agent guide
+
+## Purpose
+
+Present a persistently visible single- or multiple-selection option collection with listbox semantics, active-descendant focus, typeahead, grouping, and optional form submission.
+
+## Use when
+
+- A visible option list should let users choose one or several values while remaining one composite keyboard control.
+
+## Choose something else when
+
+- Choices should stay collapsed, users must type to filter, entries are commands, or every choice should be a separate native form control. Use Select or MultiSelect, Combobox, Menu, or RadioGroup or CheckboxGroup.
+
+## Required composition
+
+- Give Root an accessible name, choose multiple deliberately, and compose uniquely valued Option parts. Add OptionText when option content is complex or needs explicit typeahead text, and pair Group with Label only for announced option sections.
+
+## Rules
+
+- **MUST:** Give the focusable Root an accessible name through native ARIA or Field labeling and preserve its listbox role and active-descendant relationship.
+- **MUST:** Use scalar or null state for single selection and array state for multiple selection; keep value, defaultValue, and onValueChange shapes aligned with multiple.
+- **MUST:** Give every Option a stable unique value and accessible text, using label or OptionText when rendered children do not provide reliable searchable text.
+- **MUST:** Keep DOM focus on Root and preserve aria-activedescendant, orientation-specific Arrow movement, Home/End, loop policy, typeahead, disabled-option skipping, and Enter/Space selection.
+- **MUST:** Preserve disabled, read-only, required, invalid, Field descriptions, named hidden value submission, and controlled/uncontrolled behavior without turning Options into independent form controls.
+
+## Common mistakes
+
+- **Avoid:** Using Listbox for commands, giving every Option a Tab stop, mixing scalar and array values, or relying on decorative content for typeahead and naming. **Instead:** Choose Menu for commands, keep Root as the composite focus owner, align state to multiple, and provide explicit option text where needed.
+
+## Validation checklist
+
+- Verify Root and Option names, single and multiple controlled/uncontrolled state, unique values, active-descendant focus, orientation Arrow keys, Home/End, loop boundaries, typeahead, Enter/Space, pointer selection, and disabled options.
+- Verify read-only navigation without selection, required and invalid exposure, Field relationships, named single and repeated multiple hidden inputs, group-label relationships, OptionText registration, and asChild/render prop and ref merging.
+
+## Related guidance
+
+- `select`
+- `multi-select`
+- `combobox`
+- `menu`
+- `radio-group`
+- `checkbox-group`
+
+## Machine record
+
+```json
+{
+  "schema": "flowstack.agent-component.v1",
+  "id": "listbox",
+  "name": "Listbox",
+  "package": "@flowstack-ui/atom",
+  "layer": "atom",
+  "kind": "component",
+  "purpose": "Present a persistently visible single- or multiple-selection option collection with listbox semantics, active-descendant focus, typeahead, grouping, and optional form submission.",
+  "useWhen": [
+    "A visible option list should let users choose one or several values while remaining one composite keyboard control."
+  ],
+  "avoidWhen": [
+    {
+      "condition": "Choices should stay collapsed, users must type to filter, entries are commands, or every choice should be a separate native form control.",
+      "useInstead": "Select or MultiSelect, Combobox, Menu, or RadioGroup or CheckboxGroup"
+    }
+  ],
+  "composition": [
+    "Give Root an accessible name, choose multiple deliberately, and compose uniquely valued Option parts. Add OptionText when option content is complex or needs explicit typeahead text, and pair Group with Label only for announced option sections."
+  ],
+  "rules": [
+    {
+      "id": "listbox-name",
+      "level": "must",
+      "statement": "Give the focusable Root an accessible name through native ARIA or Field labeling and preserve its listbox role and active-descendant relationship."
+    },
+    {
+      "id": "listbox-selection-shape",
+      "level": "must",
+      "statement": "Use scalar or null state for single selection and array state for multiple selection; keep value, defaultValue, and onValueChange shapes aligned with multiple."
+    },
+    {
+      "id": "listbox-option-values",
+      "level": "must",
+      "statement": "Give every Option a stable unique value and accessible text, using label or OptionText when rendered children do not provide reliable searchable text."
+    },
+    {
+      "id": "listbox-focus",
+      "level": "must",
+      "statement": "Keep DOM focus on Root and preserve aria-activedescendant, orientation-specific Arrow movement, Home/End, loop policy, typeahead, disabled-option skipping, and Enter/Space selection."
+    },
+    {
+      "id": "listbox-state-form",
+      "level": "must",
+      "statement": "Preserve disabled, read-only, required, invalid, Field descriptions, named hidden value submission, and controlled/uncontrolled behavior without turning Options into independent form controls."
+    }
+  ],
+  "commonMistakes": [
+    {
+      "mistake": "Using Listbox for commands, giving every Option a Tab stop, mixing scalar and array values, or relying on decorative content for typeahead and naming.",
+      "correction": "Choose Menu for commands, keep Root as the composite focus owner, align state to multiple, and provide explicit option text where needed."
+    }
+  ],
+  "validation": [
+    "Verify Root and Option names, single and multiple controlled/uncontrolled state, unique values, active-descendant focus, orientation Arrow keys, Home/End, loop boundaries, typeahead, Enter/Space, pointer selection, and disabled options.",
+    "Verify read-only navigation without selection, required and invalid exposure, Field relationships, named single and repeated multiple hidden inputs, group-label relationships, OptionText registration, and asChild/render prop and ref merging."
+  ],
+  "related": [
+    "select",
+    "multi-select",
+    "combobox",
+    "menu",
+    "radio-group",
+    "checkbox-group"
+  ]
+}
+```

package/public/packages/atom/0.24.0/components/menu.txt

@@ -0,0 +1,126 @@
+# Menu
+
+Source: @flowstack-ui/atom@0.24.0
+Kind: component
+ID: menu
+
+# Menu agent guide
+
+## Purpose
+
+Provide the shared command and settings menu engine with real item focus, selection roles, typeahead, submenus, positioning, dismissal, and optional modal behavior.
+
+## Use when
+
+- A temporary list of commands or settings opens directly or a custom trigger primitive must reuse Atom's complete menu behavior.
+
+## Choose something else when
+
+- A visible button, contextual gesture, or persistent application command bar owns invocation, or the main job is choosing a form value or navigating links. Use DropdownMenu, ContextMenu, Menubar, Select, Listbox, or NavigationMenu.
+
+## Required composition
+
+- Compose Root around Content and uniquely valued Item parts; use ariaLabel when no trigger labels Content. Add Portal and Arrow only when needed, Group with Label for announced grouping, CheckboxItem for independent settings, RadioGroup with RadioItem for exclusive settings, and Sub with its paired SubTrigger and SubContent for a cascade.
+
+## Rules
+
+- **MUST:** Give standalone or context-driven Content an accessible name with ariaLabel; trigger-based compositions may use the generated trigger relationship.
+- **MUST:** Use Item, CheckboxItem, and RadioItem for their matching menuitem roles, provide unique values within each item registry, and provide textValue when rendered children do not expose searchable text.
+- **MUST:** Preserve Menu's real DOM item focus, disabled-item navigation without activation, typeahead, owner-aware Tab exit, Escape stack, and reason-aware focus restoration.
+- **MUST:** Choose closeOnSelect by interaction: commands normally close, while checkbox and radio settings normally remain open; do not close the tree with competing item handlers.
+- **MUST:** Keep SubTrigger and SubContent within one Sub, preserve direction-aware open and close keys, and do not silently replace the cascade with a viewport-inferred drill-in model.
+- **MUST:** Use the preventable onInteractOutside contract instead of document listeners so only completed top-layer activations dismiss the correct submenu or complete tree.
+
+## Common mistakes
+
+- **Avoid:** Using Menu for form selection or site navigation, manually roving aria-activedescendant, removing disabled items from keyboard movement, or treating a submenu as responsive drill-in navigation. **Instead:** Choose the semantic owner first and preserve Menu's real-focus item registry, selection roles, and explicit cascade; build a separate application-level drill-in flow when required.
+
+## Validation checklist
+
+- Verify accessible naming, controlled and uncontrolled open state, modal and non-modal focus behavior, Arrow keys, Home/End, typeahead, Enter/Space, disabled items, Tab exit, Escape, selection close policy, outside activation, and focus restoration.
+- Verify checkbox mixed state, radio-group scoping, group labels, indicators, nested submenu pointer and keyboard behavior, whole-tree dismissal, LTR and RTL, collision placement, long-content scrolling, portals, and parent-modal ownership.
+
+## Related guidance
+
+- `dropdown-menu`
+- `context-menu`
+- `menubar`
+- `select`
+- `listbox`
+- `navigation-menu`
+
+## Machine record
+
+```json
+{
+  "schema": "flowstack.agent-component.v1",
+  "id": "menu",
+  "name": "Menu",
+  "package": "@flowstack-ui/atom",
+  "layer": "atom",
+  "kind": "component",
+  "purpose": "Provide the shared command and settings menu engine with real item focus, selection roles, typeahead, submenus, positioning, dismissal, and optional modal behavior.",
+  "useWhen": [
+    "A temporary list of commands or settings opens directly or a custom trigger primitive must reuse Atom's complete menu behavior."
+  ],
+  "avoidWhen": [
+    {
+      "condition": "A visible button, contextual gesture, or persistent application command bar owns invocation, or the main job is choosing a form value or navigating links.",
+      "useInstead": "DropdownMenu, ContextMenu, Menubar, Select, Listbox, or NavigationMenu"
+    }
+  ],
+  "composition": [
+    "Compose Root around Content and uniquely valued Item parts; use ariaLabel when no trigger labels Content. Add Portal and Arrow only when needed, Group with Label for announced grouping, CheckboxItem for independent settings, RadioGroup with RadioItem for exclusive settings, and Sub with its paired SubTrigger and SubContent for a cascade."
+  ],
+  "rules": [
+    {
+      "id": "menu-content-name",
+      "level": "must",
+      "statement": "Give standalone or context-driven Content an accessible name with ariaLabel; trigger-based compositions may use the generated trigger relationship."
+    },
+    {
+      "id": "menu-item-model",
+      "level": "must",
+      "statement": "Use Item, CheckboxItem, and RadioItem for their matching menuitem roles, provide unique values within each item registry, and provide textValue when rendered children do not expose searchable text."
+    },
+    {
+      "id": "menu-owned-focus",
+      "level": "must",
+      "statement": "Preserve Menu's real DOM item focus, disabled-item navigation without activation, typeahead, owner-aware Tab exit, Escape stack, and reason-aware focus restoration."
+    },
+    {
+      "id": "menu-selection-close",
+      "level": "must",
+      "statement": "Choose closeOnSelect by interaction: commands normally close, while checkbox and radio settings normally remain open; do not close the tree with competing item handlers."
+    },
+    {
+      "id": "menu-submenu-contract",
+      "level": "must",
+      "statement": "Keep SubTrigger and SubContent within one Sub, preserve direction-aware open and close keys, and do not silently replace the cascade with a viewport-inferred drill-in model."
+    },
+    {
+      "id": "menu-outside-interaction",
+      "level": "must",
+      "statement": "Use the preventable onInteractOutside contract instead of document listeners so only completed top-layer activations dismiss the correct submenu or complete tree."
+    }
+  ],
+  "commonMistakes": [
+    {
+      "mistake": "Using Menu for form selection or site navigation, manually roving aria-activedescendant, removing disabled items from keyboard movement, or treating a submenu as responsive drill-in navigation.",
+      "correction": "Choose the semantic owner first and preserve Menu's real-focus item registry, selection roles, and explicit cascade; build a separate application-level drill-in flow when required."
+    }
+  ],
+  "validation": [
+    "Verify accessible naming, controlled and uncontrolled open state, modal and non-modal focus behavior, Arrow keys, Home/End, typeahead, Enter/Space, disabled items, Tab exit, Escape, selection close policy, outside activation, and focus restoration.",
+    "Verify checkbox mixed state, radio-group scoping, group labels, indicators, nested submenu pointer and keyboard behavior, whole-tree dismissal, LTR and RTL, collision placement, long-content scrolling, portals, and parent-modal ownership."
+  ],
+  "related": [
+    "dropdown-menu",
+    "context-menu",
+    "menubar",
+    "select",
+    "listbox",
+    "navigation-menu"
+  ]
+}
+```