feat: deterministic scoring pipeline, enterprise dashboard, and survey system

[sungmanch]

Summary

• Deterministic scoring pipeline: Phase 1.1 (DeterministicScorer) and Phase 1.2 (DeterministicTypeMapper) compute rubric-based scores and type classifications without LLM calls, providing consistent baselines that workers override with
• Enterprise dashboard: Full team management UI with member table, invite/edit dialogs, skill gap analysis, type distribution chart, and overview stats
• Survey system: Post-analysis feedback collection with bottom sheet UI, API endpoint, and Supabase migration

Changes

1. feat(pipeline): add deterministic scoring and type mapping stages
2. feat(models): extend schemas for deterministic scores and worker insights
3. feat(workers): integrate deterministic score overrides into insight workers
4. feat(pipeline): wire deterministic stages into orchestrator pipeline
5. feat(enterprise): add team dashboard with member management and analytics
6. feat(survey): add post-analysis survey with bottom sheet UI
7. refactor(ui): redesign report insights layout and remove dead components
8. feat(app): add opengraph image, active timer hook, and API route updates
9. feat(cli): add radar chart renderer and streaming chat display
10. refactor(desktop): update renderer for new pipeline output format
11. docs: update agent docs for deterministic scoring pipeline

Test Plan

• TypeScript compilation passes (npx tsc --noEmit)
• Unit tests pass (npm test)
• Manual verification of enterprise dashboard
• Manual verification of survey bottom sheet
• CLI radar chart rendering test

---

Generated with Claude Code using /ship-it

[vercel]

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

Project	Deployment	Actions	Updated (UTC)
no-more-ai-slop	Ready	Preview, Comment	Feb 10, 2026 8:51am

[sungmanch]

Code Review

Found 1 issue (filtered from 9 candidates, threshold: score ≥ 80):

1. Missing environment variable validation in Survey API (score: 80)

   app/api/survey/route.ts uses non-null assertion (!) for NEXT_PUBLIC_SUPABASE_URL and SUPABASE_SERVICE_ROLE_KEY without validation, unlike other API routes (e.g., app/api/analysis/results/[resultId]/route.ts:134-139) which check for missing env vars before creating the Supabase client. At system boundaries, env var validation should be explicit per project conventions.

   https://github.com/sungmanch/no-more-AI-slop/blob/'"${FULL_SHA}"'/app/api/survey/route.ts#L19-L20

---

Also reviewed (no blocking issues):

• CLAUDE.md compliance: All rules followed (language, no-fallback, structured JSON, dual data path filtering)
• Git history: Clean rebase, no conflicting patterns
• Previous PR feedback: N/A (no prior review comments)
• Code comments: No stale comments or debug artifacts in new code

Generated with Claude Code

_{If useful, react with a thumbs-up. Otherwise, thumbs-down.}