@godxjp/ui 28.10.0 → 28.13.0

package/agent/START-HERE.md

@@ -3,7 +3,7 @@
 You are about to write code against a design system you did not author. This file is the whole
 contract. Read it before you write JSX.
 
-**This catalog describes `@godxjp/ui` 28.10.0.** If the project you are editing has a different
+**This catalog describes `@godxjp/ui` 28.13.0.** If the project you are editing has a different
 version in its `package.json`, read the pinned catalog for THAT version instead
 (`…/v<their-version>/agent/…`). A catalog newer than the installed package describes props that do
 not exist yet; older, and it hides props that do. Neither failure announces itself.
@@ -56,7 +56,7 @@ Then ask it: `search_components`, `get_component`, `get_tokens`, `get_rule`, `li
    its `importPath`, and its examples. Fetch only the handful you picked in step 1.
 3. `rules.json` — 47 cardinal rules. The ones about raw HTML and hardcoded colour are not
    style advice.
-4. `tokens.json` — 1684 design tokens. Only when you need a specific knob's name.
+4. `tokens.json` — 1685 design tokens. Only when you need a specific knob's name.
 5. `anti-ai-tells.json` — 26 shapes that make generated UI look generated, each with the
    fix. Read before you reach for a gradient hero or a wall of coloured chips.
 

package/agent/components/AppLauncher.json

@@ -60,6 +60,16 @@
       "name": "appearance",
       "type": "\"bar\" | \"icon\""
     },
+    {
+      "description": "Which way the panel opens. DERIVED from `appearance` when unset — `bottom` in a bar (the panel drops below the trigger, the only direction that does not cover the bar itself), `right` otherwise, because a rail is vertical and its panel goes beside it. State it when the chrome can be RE-DOCKED: `appearance` says the trigger is NOT in a bar, and it cannot say which way is out — a rail pinned to the top edge is not a bar and still opens downward. Measured without it, an embedded bar trigger at (2,50) put its panel at (12,90), lying over the host application's sidebar. Not used by `responsive=\"fullscreen\"`, which has no side.",
+      "name": "side",
+      "type": "\"top\" | \"right\" | \"bottom\" | \"left\""
+    },
+    {
+      "description": "Where the panel sits along the `side` edge — the cross-axis half of the same decision, and derived the same way: `end` in a bar (the Workspace shape, flush with the bar's end), `start` otherwise (aligned to the rail trigger's own start). State it alongside `side` when you state either.",
+      "name": "align",
+      "type": "\"start\" | \"center\" | \"end\""
+    },
     {
       "description": "Controlled open state.",
       "name": "open",

package/agent/components/Attachments.json

@@ -50,6 +50,31 @@
       "description": "Child mode: visible trigger; upload runs through a hidden input beside it.",
       "name": "children",
       "type": "ReactElement"
+    },
+    {
+      "description": "antd Upload `onRemove`, narrowed to the attachment row. RETURNING `false` (or a promise of it) VETOES the removal and the card stays — anything else, including `undefined`, lets it go. That is how you gate a removal behind a confirm dialog without owning `items` yourself. It is awaited, so an async guard works.",
+      "name": "onRemove",
+      "type": "(item: AttachmentsItemProp) => boolean | void | Promise<boolean | void>"
+    },
+    {
+      "description": "Ant Design X `classNames` — per-part classes (root, list, card, file, upload, placeholder). DECLARED AND FORWARDED, and the only semantic part map in this package: docs/DESIGN-AUTHORITY.md rules that antd's `classNames`/`styles` maps are NOT adopted because this library answers that layer with tokens (cardinal rule #45), and Attachments is the one component that carries them anyway. Recorded there as a contradiction, not a pattern — do not copy it onto another component, and retune through `--attachments-*` instead.",
+      "name": "classNames",
+      "type": "Partial<Record<AttachmentsSemanticProp, string>>"
+    },
+    {
+      "description": "Ant Design X `styles` — the same part map as `classNames`, as inline styles, and under the same standing ruling against it. Inline styles beat every stylesheet rule, so this is the one handle in the package that can take a part off the design system entirely. The `--attachments-*` tokens are the supported route.",
+      "name": "styles",
+      "type": "Partial<Record<AttachmentsSemanticProp, React.CSSProperties>>"
+    },
+    {
+      "description": "Ant Design X `rootClassName` — the outermost node. It is not a duplicate of `className`: in the full-screen-drop mode (`getDropContainer`) the outermost node is the OVERLAY rather than the inline tray, which is why antd separates the two. Both are applied.",
+      "name": "rootClassName",
+      "type": "string"
+    },
+    {
+      "description": "ACCEPTED AND INERT. Ant Design X forwards it to its own Image preview; this package has no Image primitive yet, so the prop exists only so an Ant X call site type-checks, and passing it changes nothing on screen. Do not reach for it expecting a preview knob.",
+      "name": "imageProps",
+      "type": "Record<string, unknown>"
     }
   ],
   "related": [
@@ -67,7 +92,8 @@
   "usage": [
     "DO keep antd field names on each item (`thumbUrl`, `originFileObj`, `uid`) — an Ant X call site should compile unchanged.",
     "DO use `ref.select({ accept, multiple })` to open the picker programmatically (Ant X 2.0).",
-    "DON'T expect `styles`/`classNames` from Ant X — retune through `--attachments-*` tokens."
+    "Ant X's `classNames` / `styles` / `rootClassName` ARE declared and forwarded, although docs/DESIGN-AUTHORITY.md rules that antd's semantic part maps are not adopted here. The older note in this slot said not to expect them at all; the type has never agreed with it, so an agent reading only the catalog was told the opposite of what autocomplete offered. Retune through the `--attachments-*` tokens, and treat the maps as a recorded contradiction on this one component rather than a pattern to reuse.",
+    "The card is a FIXED box — 268x68 (Ant X's own), from `--attachments-card-size` (inline) and `--attachments-card-block-size`. The block size is also the `+` tile's square and the `overflow=\"scrollY\"` one-row viewport, so retune it once and all three follow. The file input is `sr-only`: never style it visible."
   ],
   "useCases": [
     "The attachment tray above a ChatComposer in an assistant surface.",

package/agent/components/BranchScopePicker.json

@@ -63,6 +63,16 @@
       "description": "Override the localized radio labels (e.g. domain wording like 全店舗).",
       "name": "allLabel / selectedLabel",
       "type": "ReactNode"
+    },
+    {
+      "description": "Native form name, forwarded to the MODE radio group — the all / selected choice is what submits under it. The checked branch ids are not native fields; they live in the single `{ mode, branchIds }` value and are yours to serialise.",
+      "name": "name",
+      "type": "string"
+    },
+    {
+      "description": "DOM id on the picker root, and the SEED for the ids beneath it — the validation message is `${id}-error`, which is what `aria-errormessage` points at. Left out, a `useId`-based id is generated, so the association still holds; set it when a server-rendered page needs those ids to be stable.",
+      "name": "id",
+      "type": "string"
     }
   ],
   "related": [

package/agent/components/Cascader.json

@@ -175,6 +175,11 @@
       "description": "Search query change (antd `showSearch.onSearch`).",
       "name": "onSearchChange",
       "type": "(query: string) => void"
+    },
+    {
+      "description": "Accessible name for the COMBOBOX TRIGGER — the element a keyboard user lands on, not the panel. Inside a FormField it is injected for you and you do not pass it; on a bare Cascader (a toolbar scope filter, a compact drilldown with no label row) it is the only name the control has, and cardinal rule 227 requires one. Route it through t(). The rest of the field-a11y contract — aria-labelledby / describedby / errormessage / invalid / required — is accepted on every form-capable component here and is FormField's to wire.",
+      "name": "aria-label",
+      "type": "string"
     }
   ],
   "related": [

package/agent/components/Checkbox.json

@@ -29,6 +29,12 @@
       "name": "id",
       "type": "string"
     },
+    {
+      "defaultValue": "false",
+      "description": "Keeps its HTML spelling here and becomes react-aria's `isRequired`, so unlike Switch — where the same prop only ANNOUNCES the requirement — this is real constraint validation on the underlying input: an unchecked box blocks native form submission. The consent checkbox is the case it exists for. It does not render an asterisk; the required MARK belongs to FormField's label.",
+      "name": "required",
+      "type": "boolean"
+    },
     {
       "description": "antd `<Checkbox>label</Checkbox>` — the INLINE label: box first, label at inline-end on the same line, the same markup as a `Checkbox.Group` option. A real `<label for>`: clicking the text toggles the box and the text is its accessible name. `className` then styles the labelled row.",
       "name": "children",

package/agent/components/CredentialReveal.json

@@ -46,12 +46,23 @@
       "name": "onAcknowledge",
       "type": "() => void"
     },
+    {
+      "description": "Copy on the button `onAcknowledge` creates. Defaults to a localized \"I've saved it\" — override it when the confirmation claims something more specific than having read the secret (\"保管しました\", \"Stored in 1Password\"). Consumer-owned wording: route it through t().",
+      "name": "acknowledgeLabel",
+      "type": "React.ReactNode"
+    },
     {
       "defaultValue": "false",
       "description": "Offer a download-as-file button.",
       "name": "downloadable",
       "type": "boolean"
     },
+    {
+      "defaultValue": "\"credential.txt\"",
+      "description": "Name of the file `downloadable` writes. The default is deliberately anonymous; set it when the user will hold several at once (`api-key-prod.txt`) so the saved files are still telling apart in a downloads folder.",
+      "name": "downloadFileName",
+      "type": "string"
+    },
     {
       "defaultValue": "\"md\"",
       "description": "Action button size tier.",
@@ -63,6 +74,16 @@
       "description": "Caution banner severity.",
       "name": "tone",
       "type": "\"warning\" | \"destructive\" | \"info\""
+    },
+    {
+      "description": "DOM id on the root. Useful here because the surface is usually inside a Dialog: it is what a `aria-describedby` on the dialog, or a deep link back to the issued credential, can point at.",
+      "name": "id",
+      "type": "string"
+    },
+    {
+      "description": "Accessible name for the credential region when `label` is not set or is a non-string node. `label` is the VISIBLE caption and already names the region when it is a plain string, so reach for this only when the caption is rich content or when the surrounding dialog title is the only thing saying which secret this is.",
+      "name": "aria-label",
+      "type": "string"
     }
   ],
   "related": [

package/agent/components/InputOTP.json

@@ -70,6 +70,41 @@
       "description": "Main-axis alignment of the whole code row (groups + separators) inside the field. `center` is the canonical auth challenge. Before this existed, every consumer wrapped the OTP in their own flex-centring div — do not. A service that wants all code fields centred sets `--otp-container-align` once instead.",
       "name": "align",
       "type": "\"start\" | \"center\" | \"end\""
+    },
+    {
+      "description": "Fires ONCE the last slot fills, whether the user typed it or pasted the whole code. This is the auto-submit hook: a 2FA challenge with a visible submit button is a step nobody wants, and the alternative — watching `value.length === maxLength` in an effect — re-fires on every re-render. Keep the submit button anyway for the paste-then-correct case.",
+      "name": "onComplete",
+      "type": "(value: string) => void"
+    },
+    {
+      "description": "Rewrites CLIPBOARD text before it reaches the field. Distinct from `formatter`, which normalises every value: this one only sees a paste, which is where the junk arrives — `\"123 456\"`, `\"code: 123456\"`, a copied SMS line. Note the order the field applies them: `pattern` is matched against the RAW keystroke first, so a pattern must accept what a user actually types, not only what these two produce.",
+      "name": "pasteTransformer",
+      "type": "(pasted: string) => string"
+    },
+    {
+      "description": "Class on the ROW container `input-otp` renders (the slots' flex parent), which `className` cannot reach — `className` lands on the hidden input, because that is the real field. Prefer `align` and the `--otp-*` tokens; this is the vendored escape hatch underneath them.",
+      "name": "containerClassName",
+      "type": "string"
+    },
+    {
+      "description": "`input-otp`'s answer to the 1Password / LastPass badge that browsers float over a code field and that covers the last slot. `increase-width` (its default) reserves room so the badge sits beside the row; `none` turns the accommodation off, which is what a row already centred by `align` usually wants. Pure layout — it changes no value and no keyboard behaviour.",
+      "name": "pushPasswordManagerStrategy",
+      "type": "\"increase-width\" | \"none\""
+    },
+    {
+      "description": "The `<noscript>` stylesheet `input-otp` injects so the slots are still visible with JS disabled. Pass `null` to suppress it — the one real reason being a CSP that forbids inline styles and that `nonce` cannot satisfy. Leave it alone otherwise.",
+      "name": "noScriptCSSFallback",
+      "type": "string | null"
+    },
+    {
+      "description": "CSP nonce stamped on the stylesheet `input-otp` injects. Required only under a `style-src 'nonce-…'` policy, where the field otherwise renders unstyled and the console reports a blocked inline style. Pass the same nonce the document was served with.",
+      "name": "nonce",
+      "type": "string"
+    },
+    {
+      "description": "`input-otp`'s headless mode: you draw the entire row from the slot state instead of composing InputOTPGroup / InputOTPSlot. It is mutually exclusive with `children` — the vendor types the two as a union and this component keeps that union. Reaching for it means giving up the slot styling, the group outline and the separator this package owns, so it is the last resort, not a customisation point.",
+      "name": "render",
+      "type": "(props: InputOTPRenderProps) => React.ReactNode"
     }
   ],
   "related": [

package/agent/components/PermissionMatrix.json

@@ -54,6 +54,11 @@
       "description": "Accessible table name (localized default).",
       "name": "label",
       "type": "string"
+    },
+    {
+      "description": "DOM id on the grid root. Worth setting on a permissions page that also renders a summary or a legend elsewhere: it is the anchor those can point at, and the stable handle for an E2E selector that must not depend on the localized `label`.",
+      "name": "id",
+      "type": "string"
     }
   ],
   "related": [

package/agent/components/SearchInput.json

@@ -67,6 +67,11 @@
       "description": "Disable search input and clearing.",
       "name": "disabled",
       "type": "boolean"
+    },
+    {
+      "description": "Class on the `<input>` itself. SearchInput renders a WRAPPER (label, icon, clear button, input), so `className` lands on that wrapper and never reaches the field — this is the second handle, for the case where the field and its chrome need different treatment. Layout and colour still belong to tokens; use it for the rare geometry a token cannot reach.",
+      "name": "inputClassName",
+      "type": "string"
     }
   ],
   "related": [

package/agent/components/ServiceLauncherCard.json

@@ -1,15 +1,20 @@
 {
-  "example": "import { Clock } from \"lucide-react\";\nimport {\n  ServiceCatalogCta,\n  ServiceLauncherCard,\n  ServiceLauncherCardSkeleton,\n} from \"@godxjp/ui/data-display\";\nimport { Button } from \"@godxjp/ui/general\";\nimport { ResponsiveGrid } from \"@godxjp/ui/layout\";\n\n// ResponsiveGrid owns the canonical 3 → 2 → 1 ladder; the page writes no tracks.\n<ResponsiveGrid columns={{ sm: 1, md: 2, lg: 3 }}>\n  {loading\n    ? services.map((s) => <ServiceLauncherCardSkeleton key={s.id} label={t(\"loadingService\")} />)\n    : services.map((s) => (\n        <ServiceLauncherCard\n          key={s.id}\n          icon={Clock}\n          title={s.name}\n          statusLabel={s.accessLabel}\n          statusTone={s.accessTone}\n          description={s.description}\n          metadata={s.hostnameAndPlan}\n          disabledReason={s.blockedReason}\n          action={\n            <Button asChild={s.canLaunch} disabled={!s.canLaunch}>\n              {s.canLaunch ? <a href={s.launchUrl}>{t(\"launch\")}</a> : t(\"launch\")}\n            </Button>\n          }\n        />\n      ))}\n  <ServiceCatalogCta\n    title={t(\"addFromCatalog\")}\n    action={<Button variant=\"outline\">{t(\"viewCatalog\")}</Button>}\n  />\n</ResponsiveGrid>",
+  "example": "import { Clock } from \"lucide-react\";\nimport {\n  ServiceCatalogCta,\n  ServiceLauncherCard,\n  ServiceLauncherCardSkeleton,\n} from \"@godxjp/ui/data-display\";\nimport { Button } from \"@godxjp/ui/general\";\nimport { ResponsiveGrid } from \"@godxjp/ui/layout\";\n\n// ResponsiveGrid owns the canonical 3 → 2 → 1 ladder; the page writes no tracks.\n<ResponsiveGrid columns={{ sm: 1, md: 2, lg: 3 }}>\n  {loading\n    ? services.map((s) => <ServiceLauncherCardSkeleton key={s.id} label={t(\"loadingService\")} />)\n    : services.map((s) => (\n        <ServiceLauncherCard\n          key={s.id}\n          icon={Clock}\n          // The uploaded mark when there is one; the tile falls back to `icon` when there is not,\n          // and again if the file behind the URL has gone away.\n          logo={s.logoUrl ?? undefined}\n          title={s.name}\n          statusLabel={s.accessLabel}\n          statusTone={s.accessTone}\n          description={s.description}\n          metadata={s.hostnameAndPlan}\n          disabledReason={s.blockedReason}\n          action={\n            <Button asChild={s.canLaunch} disabled={!s.canLaunch}>\n              {s.canLaunch ? <a href={s.launchUrl}>{t(\"launch\")}</a> : t(\"launch\")}\n            </Button>\n          }\n        />\n      ))}\n  <ServiceCatalogCta\n    title={t(\"addFromCatalog\")}\n    action={<Button variant=\"outline\">{t(\"viewCatalog\")}</Button>}\n  />\n</ResponsiveGrid>",
   "group": "data-display",
   "importPath": "@godxjp/ui/data-display",
   "name": "ServiceLauncherCard",
   "props": [
     {
-      "description": "Decorative service glyph rendered in the canonical semantic icon surface.",
+      "description": "Decorative glyph for the KIND of service, rendered in the canonical semantic icon surface. Stays required because it is also what `logo` falls back to when an upload is missing or broken.",
       "name": "icon",
       "required": true,
       "type": "LucideIcon"
     },
+    {
+      "description": "URL of the service's OWN uploaded mark (the PNG/WebP an administrator uploaded). When it loads it replaces `icon` in the medallion, in the glyph's exact box (--card-service-launcher-icon-glyph-size, object-fit: contain). It is a fallback chain, not a switch: the tile renders `icon` while the URL is in flight and KEEPS rendering `icon` if the URL 404s or is empty — a broken logo never reaches the DOM as an <img>. Decorative (alt=\"\", medallion aria-hidden), so there is no logoAlt prop: the service name is already beside it.",
+      "name": "logo",
+      "type": "string"
+    },
     {
       "description": "Real downstream service display name.",
       "name": "title",
@@ -68,13 +73,15 @@
   "subParts": [
     "ServiceLauncherCardSkeleton"
   ],
-  "tagline": "Token-owned downstream-service launcher tile with semantic icon, status, metadata, action, disabled reason, matching skeleton, and companion catalog CTA.",
+  "tagline": "Token-owned downstream-service launcher tile with an uploaded service logo (falling back to a semantic icon), status, metadata, action, disabled reason, matching skeleton, and companion catalog CTA.",
   "usage": [
     "DO provide status, hostname, plan, access state and action from the product's real API contract. ServiceLauncherCard deliberately performs no entitlement or URL inference — it has no href/entitlement/available prop at all.",
     "DO own the layout with ResponsiveGrid columns={{ sm: 1, md: 2, lg: 3 }} — the canonical 3→2→1 launcher grid. ResponsiveGrid queries its OWN container (40/48/64rem), so never hand-write grid-template-columns or a media query in the page. The shorthand columns={3} also works but widens to 2 columns earlier (40rem).",
     "DO render ServiceLauncherCard directly as a grid child; it already owns its Card shell, its 36px medallion (--control-height-lg tier) and the canonical internal rhythm.",
     "DO replace it with ServiceLauncherCardSkeleton while loading (it carries a required `label` and aria-busy, and deliberately opens no live region). Use ServiceCatalogCta as the peer tile only when a real catalog/add route exists.",
     "DO keep `metadata` to machine identifiers (hostname · plan) — it is the only mono line. Sentences belong in `description` / `disabledReason`.",
+    "DO pass BOTH `logo` and `icon` when a service may have an uploaded mark: `logo={s.logoUrl ?? undefined}` with `icon` as the kind glyph. `icon` is not optional and must not be treated as redundant — it is the tile a freshly created service, and a service whose logo file has been deleted, actually shows.",
+    "DON'T wrap an <img> in a component to squeeze it through `icon`, and DON'T style the medallion to fit a picture. `logo` sizes the image to the glyph's own token, so a grid mixing logo tiles and glyph tiles keeps one optical weight.",
     "DON'T recreate launcher geometry with page-local CSS, utility padding, grid tracks, or a hand-built Card hierarchy. Retune it with the --card-service-launcher-* tokens instead.",
     "DON'T show LIVE, a hostname, subscribed plan, or launch action merely because a service is active in the global catalog."
   ],

package/agent/components/ServiceRolePanel.json

@@ -56,6 +56,11 @@
       "description": "Forwarded to MasterDetail (localized region labels by default). Never re-derive tracks or breakpoints in the app.",
       "name": "railWidth / masterViewport / collapseBelow / masterLabel / detailLabel",
       "type": "MasterDetail geometry + region labels"
+    },
+    {
+      "description": "DOM id on the panel root — the two-region MasterDetail wrapper, not the rail or the detail. It is the handle for a deep link onto the roles panel of a settings page, and for an E2E selector that must survive `masterLabel` being localized.",
+      "name": "id",
+      "type": "string"
     }
   ],
   "related": [

package/agent/components/Switch.json

@@ -47,6 +47,12 @@
       "name": "id",
       "type": "string"
     },
+    {
+      "defaultValue": "false",
+      "description": "ANNOUNCES the requirement; it does not enforce it. react-aria's Switch omits `isRequired`, and a switch is never the target of native constraint validation in this library, so this writes `aria-required=\"true\"` onto the real input and stops there. The form layer (FormField / your schema) still owns whether an unflipped switch blocks submit — pairing this with nothing that validates is how a screen reader ends up promising a check the form never makes.",
+      "name": "required",
+      "type": "boolean"
+    },
     {
       "defaultValue": "false",
       "description": "Disable the toggle.",

package/agent/components/Tabs.json

@@ -116,6 +116,16 @@
       "description": "Ant Design `onTabScroll`, fired whenever the trigger strip's own scrollport moves — a swipe, a wheel, or the component re-pinning the active trigger (antd reports its own re-pins too). LOGICAL VALUES instead of antd's `left | right | top | bottom`: two of those four are just the other axis of the same event, and upstream's pair is read off the sign of an inner transform, so in an RTL strip its `left` means the opposite of what it means in LTR. `start`/`end` say the same thing on whichever axis and in whichever direction the strip is written. Only fires for the `items` API, which is the path that owns the strip element.",
       "name": "onTabScroll",
       "type": "(info: { direction: \"start\" | \"end\" }) => void"
+    },
+    {
+      "description": "Class on the TRIGGER STRIP (`TabsList`) under the `items` API — the handle that composing the tree manually gives you as `<TabsList className>`. `className` reaches only the root, which holds the strip AND the panels, so anything meant for the bar alone belongs here. Almost always unnecessary: placement, size, centring and the card rail are props and `--tabs-*` tokens.",
+      "name": "listClassName",
+      "type": "string"
+    },
+    {
+      "description": "Class on EVERY panel (`TabsContent`) under the `items` API. It is written so it can WIN: the joined card body travels to CSS as `data-bodied` on the root rather than as a class, precisely so a consumer class on the panel is not fighting a utility the component already claimed (gh#762). Reach for the `bodied` prop and the `--tabs-panel-*` tokens first — this is for the geometry no token exposes.",
+      "name": "contentClassName",
+      "type": "string"
     }
   ],
   "related": [

package/agent/components/TimeRangePicker.json

@@ -30,6 +30,11 @@
       "name": "allowEmpty",
       "type": "[boolean,boolean]"
     },
+    {
+      "description": "A PAIR, one per endpoint — TimePicker's single-string `placeholder` is omitted from this type on purpose, because a range has two empty fields and one string would label both of them the same. Route both through t().",
+      "name": "placeholder",
+      "type": "[string,string]"
+    },
     {
       "description": "Native names are name_from and name_to.",
       "name": "name",

package/agent/components/Transfer.json

@@ -94,6 +94,11 @@
       "name": "className",
       "type": "string"
     },
+    {
+      "description": "Lands on the `role=\"group\"` shuttle container, not on any one input — a two-pane shuttle has no single labelable control, so this is what a FormField label points at. FormField injects it; pass it yourself only for a bare Transfer.",
+      "name": "id",
+      "type": "string"
+    },
     {
       "description": "Controlled selection state as a tuple: index 0 = keys checked in the source panel, index 1 = keys checked in the target panel. Omit to use internal (uncontrolled) selection state. Must be paired with `onSelectChange` when provided.",
       "name": "selectedKeys",

package/agent/components/Upload.json

@@ -67,6 +67,11 @@
       "name": "className",
       "type": "string"
     },
+    {
+      "description": "Lands on the native `<input type=\"file\">`, NOT on the wrapper — the hidden input is the semantic focus target, so this is what makes a `<label htmlFor>` (or FormField, which injects it) actually focus the picker. Putting it on the visible dropzone instead is the usual reason a label click does nothing.",
+      "name": "id",
+      "type": "string"
+    },
     {
       "description": "Custom button label for variant='button'. Falls back to the i18n 'Upload file' string.",
       "name": "children",

package/agent/components-index.json

@@ -224,7 +224,7 @@
   {
     "group": "data-display",
     "name": "ServiceLauncherCard",
-    "tagline": "Token-owned downstream-service launcher tile with semantic icon, status, metadata, action, disabled reason, matching skeleton, and companion catalog CTA."
+    "tagline": "Token-owned downstream-service launcher tile with an uploaded service logo (falling back to a semantic icon), status, metadata, action, disabled reason, matching skeleton, and companion catalog CTA."
   },
   {
     "group": "data-display",