fix(components): do not filter custom components in workspaces named ui/

[neilwashere]

Summary

isUIPrimitive in src/detectors/components.ts had a filePath.includes(\"/ui/\") check intended to filter shadcn primitives. The check is too broad: it matches every file under a monorepo workspace literally named `ui/` (e.g. `ui/src/components/*.tsx`), so every custom component in such a repo is wrongly dropped.

The real shadcn case (`components/ui/.tsx`) is still caught by the more specific `/components/ui/` check; lowercase primitive file names are still caught by the `UI_PRIMITIVES` set; vendor path checks (`@radix-ui`, `@shadcn`) are unchanged.

Reproduction

In our internal use we ran `codesight --wiki` against a pnpm workspace where the frontend package is literally named `ui` (the workspace tree is roughly `packages: shared, server, ui`). The scanner correctly identified `react` in the aggregated workspace deps and set `project.componentFramework = "react"`, but `detectComponents` returned an empty array, so the generated wiki reported `0 components` and skipped the `ui.md` article entirely.

After the fix the same repo reports 130 components with prop signatures extracted via AST (component names + props from `AppShell`, `BubbleContextMenu`, `ChatBubble`, etc.), and the `ui.md` article is generated as expected.

Change

One-line removal of the over-broad path check, plus a comment explaining why the bare `/ui/` segment is unsafe.

 function isUIPrimitive(filePath: string): boolean {
   const name = basename(filePath, extname(filePath)).toLowerCase();
   return (
     UI_PRIMITIVES.has(name) ||
-    filePath.includes(\"/ui/\") ||
     filePath.includes(\"/components/ui/\") ||
     filePath.includes(\"@radix-ui\") ||
     filePath.includes(\"@shadcn\")
   );
 }

Test plan

• Added regression test `detects components in a workspace named \`ui/\` without filtering them as shadcn primitives` in `tests/detectors.test.ts`. Fixture has both a workspace-level `ui/src/components/AppShell.tsx` (must be detected) and a real shadcn `ui/src/components/ui/button.tsx` (must still be filtered). New test passes.
• Existing `detects React components with props` test still passes (no regression on shadcn-primitive-name filtering or on the standard `src/` layout).
• Full `pnpm test` suite: 116/117 pass on this branch. The single failure (`tests/monorepo.test.ts:312`, "creates CLAUDE.md with package count and index reference") also fails on `main` pre-change (verified by stash + re-run), so it is unrelated to this PR.
• Manual end-to-end: re-ran `npx codesight --wiki` against the affected repo. Component count went 0 -> 130; total wiki tokens 15,736 -> 19,077; `ui.md` article now generated with component name + props + file paths.

🤖 Generated with Claude Code