chore: repackage as single publishable ui-lineage npm package

[officialCodeWork]

Make it publishable as ui-lineage

You asked whether this could ship to npm. Findings: the @coderadar/* scope is owned by another account (gbh24679), so it's unusable — but every ui-lineage name is free. This PR turns the CLI package into one self-contained package named ui-lineage, bundling the internal workspace packages in so consumers depend only on ui-lineage + three external deps.

Changes

• packages/cli → ui-lineage: bin ui-lineage; new src/lib.ts re-exports the core query API + the React scanner; main/exports/types → dist/lib.
• tsup bundle: inlines @coderadar/core + @coderadar/parser-react into both the JS and the .d.ts (dts.resolve), keeps ts-morph/yaml/commander external, preserves the CLI shebang.
• @coderadar/core + @coderadar/parser-react → private: true — their code ships bundled inside ui-lineage; also prevents accidental publish to the taken scope.
• Rebranded CLI name/help/default graph filename; added package README (npm listing) + prepublishOnly; ignore *.graph.json.

Verified (not published — packaging only)

• pnpm -r build / typecheck / test + pnpm eval: 185 checks green, precision/recall 1.000.
• Real consumer test: npm pack → npm install ./ui-lineage-0.1.0.tgz in a clean project →
  • ui-lineage scan + ui-lineage journeys bin works
  • import { scanReact, journeys } from "ui-lineage" resolves (bare specifier)
  • zero @coderadar imports in the bundle; tarball is 10 files / ~89 KB.

How to actually publish (your call, your npm account)

git checkout development && git pull        # after merge
pnpm -r build
cd packages/cli
npm login                                    # your own account
npm publish                                  # ui-lineage is unscoped → public by default

ui-lineage is a fresh name so 0.1.0 is fine. Consider npm publish --tag next while it's pre-1.0.

🤖 Generated with Claude Code