docs: added docs for ui components

[harish-viswa]

No description provided.

[netlify]

✅ Deploy Preview for harness-design ready!

Name	Link
🔨 Latest commit	da13a7a
🔍 Latest deploy log	https://app.netlify.com/sites/harness-design/deploys/67ab81f92b7d360008334ead
😎 Deploy Preview	https://deploy-preview-1070--harness-design.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[netlify]

✅ Deploy Preview for harness-xd-review ready!

Name	Link
🔨 Latest commit	da13a7a
🔍 Latest deploy log	https://app.netlify.com/sites/harness-xd-review/deploys/67ab81f9372543000858c5d1
😎 Deploy Preview	https://deploy-preview-1070--harness-xd-review.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[knagurski]

Can we break this up into different PRs? This is too much to review without blindly rubber-stamping

[knagurski]

These appear to be mass-produced AI-generated docs with issues. All docs additions should be their own PRs and need to be checked over to make sure they're correct (e.g. the first component is BranchSelector, but is in a file called branch-chooser with Branch Chooser referenced etc).

[abhinavrastogi-harness]

agreed with the bocker here. we need to ensure correctness and basic quality. individual PRs would help with that.

however, we do need to get some basic docs ready for a majority of components, because we want to open up the component library to other teams very soon. AI can be a good way to kickstart something, but we should not be blindly committing "AI Slop".

[harish-viswa]

These appear to be mass-produced AI-generated docs with issues. All docs additions should be their own PRs and need to be checked over to make sure they're correct (e.g. the first component is BranchSelector, but is in a file called branch-chooser with Branch Chooser referenced etc).

@knagurski Actually the file-name is Branch Chooser but the component being exported is BranchSelector, we may need to update this in BranchChooser component, and update the docs as well. Thought could take this separately

[harish-viswa]

@knagurski @abhinavrastogi-harness
I was not able to mass produce the results actually, due to free tier usage 😢
I created two to three components as a group and reviewed each of them for

1. Usage correctness
2. Props for components and sub-components

we may have to re-look at the text content being generated which I did not give much importance to,
since it can be fine-tuned later