feat: WorkSight MVP integration — runs on @worksight/common, uniform Vercel config, honest docs

[kuyacarlo]

Summary

Integrates the MVP stack (#15 #16 #17 #18 #19 #20) into one verified branch. Each workstream keeps its own PR (#21–#26) for review; this is the merge-ready result.

WorkSight now actually runs on the shared data classes: Nest serves @worksight/common fixtures, and the web app renders them end to end.

What made this more than a merge

Wiring the API to @worksight/common (#17) surfaced three latent defects that a green build had been hiding:

1. nest build was emitting an empty dist. apps/api inherited noEmit: true from the root tsconfig, so the build "succeeded" while producing nothing runnable. Fixed with a proper tsconfig.build.json.
2. @worksight/common was unloadable by Node. It emitted ESM with directory imports (export * from './data'), which Node cannot resolve. Build now runs tsc-alias --resolve-full-paths.
3. BaseLookup.filter() returned garbage. It reconstructed subclasses with the wrong constructor arity, so every chained lookup silently produced wrong data — /users/:id 404'd for valid ids and /tasks/stats 500'd. Fixed via prototype clone.

On the deploy side (#20), apps/api/vercel.json used a legacy builds/routes block that disables Vercel's install and build steps entirely, and the Supabase anon key was hardcoded in vercel.json. Both fixed; env is dashboard-managed.

Verified on this branch

pnpm type-check                          → 7/7 tasks successful
pnpm lint                                → 7/7 tasks successful
pnpm --filter @worksight/api test        → 2 suites, 10 tests passed
pnpm --filter @worksight/{api,web,docs} build → all succeed

End-to-end smoke, API on :3199 and web on :3198:

GET /health     → {"status":"ok"}
GET /users      → 15      GET /teams      → 5
GET /tasks      → 8       GET /activities → 14
GET /tasks/stats/:id → completionRate 50, storyPoints 21/13
GET /demo (web) → HTTP 200, renders fixtures, shows "Nest API" source badge

Vercel

Three projects, uniform per-app config, matching the applied dashboard settings:

Project	Root Directory	Build
worksight	apps/web	pnpm --filter @worksight/web build
worksight-api	apps/api	pnpm --filter @worksight/api build
worksight-docs	apps/docs	pnpm --filter @worksight/docs build

Vercel loads exactly one vercel.json per project — the one at that project's Root Directory — so "centralized" means uniform configs, not one shared file.

Not built (deliberately)

No Supabase persistence for the new API routes; attendance/survey/burnout types have no endpoints; the API still has no serverless handler, so Docker remains its working deploy path; some @worksight/common fixture ids are not valid UUIDs, so strict zod parsing would reject them even though the TS shapes match.

Test plan

• Repo-wide type-check and lint green
• API unit tests pass
• All three apps build
• Live API + web smoke test through /demo
• Confirm preview deployments on this PR

Made with Cursor

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
worksight	Ready	Preview, Comment	Jul 25, 2026 6:53am
worksight-api	Ready	Preview, Comment	Jul 25, 2026 6:53am
worksight-docs	Ready	Preview, Comment	Jul 25, 2026 6:53am

[kuyacarlo]

CI caught a real bug — fixed in 5b37377

The worksight-api preview deployment failed on the first push with four TS2307 errors: nest build could not find @worksight/common.

Cause: pnpm --filter <pkg> build runs only that package's build script — it does not build the package's workspace dependencies first. Turbo's dependsOn: ["^build"] does. This never surfaced earlier because local runs had a stale packages/common/dist lying around, and apps/api/vercel.json previously used a legacy builds block that skipped Vercel's build step entirely.

Fix: all three vercel.json build commands now use Turbo filters, and the Vercel dashboard build commands were updated to match so they cannot drift. Verified from a clean slate (all dist/.next deleted) that each app builds from its own Root Directory, with common built first.

All six checks are now green, including Vercel – worksight-docs, which had never produced a successful deployment before this branch.

The same fix was pushed to #23 so that PR is not a footgun if merged on its own.