fix(admin): use field-generic wording for details/error prop docs

[sordaz00]

What

The shared FieldDetailsProps.details and FieldErrorProps.error JSDoc in src/surfaces/admin/components.d.ts was written for checkbox:

Supplementary text displayed below the checkbox to provide additional context, instructions, or help. Use this to explain what checking the box means or provide guidance to users.

Both interfaces are inherited by every Admin and App Home form component, so this checkbox-specific copy renders on ~18 non-checkbox reference pages, where it reads incorrectly. Reported via shopify.dev CSAT feedback on the App Home text field page.

How

Two JSDoc blocks changed. The docs generator expands inherited members, so those two blocks produce all 40 occurrences per generated file — the fix corrects every inheriting component in one change:

text-field, text-area, select, color-field, date-field, email-field, money-field, number-field, password-field, search-field, url-field, choice-list, switch, plus the FieldProps / BaseTextFieldProps / RequiredMoneyFieldProps interfaces.

Contrary to the issue's description, checkbox had no override — it inherited the same string, so no component had correct wording. The new generic phrasing reads correctly for checkbox too, so no override was added.

Generated docs

generated_docs_data_v2.json updated for admin_extensions/2026-07-rc, app_home, and app_home_ui_extension/2026-07-rc — 40 replacements each across four distinct literals (20 flattened error, 18 flattened details, and the two interface source blocks).

These were patched textually rather than by running yarn docs:admin, because the generator copies these strings verbatim and the branch is cut from the freshly-regenerated files in c44c777. The diff arithmetic closes exactly (40 × 3 + 4 = 124), all three files re-parse as valid JSON, and no residual checkbox wording remains under src/ or docs/.

Follow-up (not in this PR)

This file is a vendored copy of @shopify/admin-ui-components, bulk-replaced by bump admin-ui-components commits. The durable fix lives in World at libraries/javascript/polaris/admin-ui-components/lib/publicDocsMemberDescriptions.js, which hand-overrides the (already-correct) ui-api-design JSDoc and duplicates the bad string per component — 36 strings across 19 entries, including DropZone. Without that change this regresses on the next vendor bump. Tracked in shop/issues-learn#2959.

🤖 Generated with Claude Code

[github-actions]

This PR targets a stable release branch (2026-07). Once merged, the change typically also needs to be forward-ported to 2026-10-rc so it ships in the next release.

When you open the forward-port PR, include a line like this in its body so the needs-rc-port label gets removed automatically when that PR merges:

Forward-port of #4662

Accepted formats (comma-separated for multiple):

• #4662
• GH-4662
• 4662
• https://github.com/Shopify/ui-extensions/pull/4662

If a forward-port isn't needed (e.g., the change is stable-only), you can remove the needs-rc-port label manually.

[github-actions]

We detected some changes in packages/*/package.json or packages/*/src, and there are no updates in the .changeset directory. If the changes are user-facing and should cause a version bump, run yarn changeset to track your changes and include them in the next release CHANGELOG. If you are making simple updates to repo configuration, examples, or documentation, you do not need to add a changeset.