feat(#3159): Add JSDoc comments to React and Angular component wrappers

[Copilot]

• Understand the codebase patterns (Svelte → React/Angular JSDoc mapping)
• Create scripts/add-jsdocs.js — re-runnable script that reads JSDoc from Svelte source and injects into React/Angular wrappers
  • Idempotent: safe to run multiple times — only adds where missing
  • --dry-run mode for previewing changes without writing
  • Handles @required, @deprecated, @default tags
  • Normalises "false"/"true" string defaults → false/true booleans
  • Covers both lib/ and experimental/ Angular wrappers
  • Skips @internal Svelte props
• Apply script to fix 43 additional wrapper files with missing JSDoc (missed by initial commits)
• Fix pre-existing corruption in experimental/checkbox-list/checkbox-list.tsx (Svelte imports injected into interface by original codegen)
• Update scripts/README.md with full usage documentation for the new script

Original prompt

---

This section details on the original issue you should resolve

<issue_title>JSDocs in Wrappers</issue_title>
<issue_description># Info

It would be extremely beneficial to developers using our component wrappers to see better descriptions of properties in components. This would better allow them to stay in their IDE instead of having to switch between IDE and documentation website to figure out what they want to do.

Just a normal comment on a property:

A proper full JSDoc comment on that same property:

As you can see above, with just that one property. It properly gives a description of the property, what type of data it allows for (this can be expanded even further by documenting that type properly as well), whether it's optional or required, and what the default value is so they know.

We only need to create the comments for either Angular or React wrappers, and then have a script to copy them to other set of wrappers.

Acceptance Criteria:

1. Give proper full JSDoc comments for every property in every component, in either Angular or React
2. Use AI to duplicate to either Angular or React</issue_description>

<agent_instructions>1. Look at the JSDoc comments in the Svelte components
2. Add corresponding JSDoc comments to the React and Angular wrappers

Example:

• Svelte component: libs/web-components/src/components/button/Button.svelte
• React wrapper: libs/react-components/src/lib/button/button.tsx
• Angular wrapper: libs/angular-components/src/lib/components/button/button.ts
• Experimental React wrapper: libs/react-components/src/experimental/button/button.tsx
• Experimental Angular wrapper: libs/angular-components/src/experimental/button/button.ts</agent_instructions>

Comments on the Issue (you are @copilot in this section)

• Fixes JSDocs in Wrappers #3361

---

💬 Send tasks to Copilot coding agent from Slack and Teams to turn conversations into code. Copilot posts an update in your thread when it's finished.

[bdfranck]

Here's the script Copilot created:
https://gist.github.com/bdfranck/5f090c4addfd064cbbc77563a056d546

[bdfranck]

@copilot There some properties that aren't in the Svelte component but are in the React and Angular Wrappers. They are TemplateRef<any> in Angular and ReactNode in React. These allow the developer to insert something into a slot. Here's an example:

libs/angular-components/src/experimental/work-side-menu/work-side-menu.ts

  @Input() primaryContent!: TemplateRef<any>;
  @Input() secondaryContent!: TemplateRef<any>;
  @Input() accountContent!: TemplateRef<any>;

libs/react-components/src/experimental/work-side-menu/work-side-menu.tsx

primaryContent?: ReactNode;
secondaryContent?: ReactNode;
accountContent?: ReactNode;

Here's what to do:

1. Find all of these TemplateRef<any> and ReactNode properties in the wrappers
2. Add a placeholder JSDoc comment
3. Write "TO DO: Write a description" for the placeholder description