- Fix TypeScript errors in project-faq.tsx:
  - Remove unused imports (cn, FAQAnswer type)
  - Fix RepoStats type usage (removed non-existent health/activity properties)
  - Properly handle pr.author object structure for contributor indexing
  - Remove unsupported title prop from Sparkles icon

- Fix TypeScript errors in faq-service.ts:
  - Remove unused imports and variables
  - Fix type casting for cache service
  - Handle contributor data structure properly in reduce operations
  - Fix sort function type assertions

- Work around Rollup conditional expression bug:
  - Temporarily disable treeshaking to fix build error
  - Added TODO to re-enable once Rollup issue is resolved
  - Reference: rollup/rollup#5747

Build now completes successfully with all TypeScript errors resolved.

…rnaries

Root cause: Rollup 4.45.0 has a bug with nested ternary operators during treeshaking
that causes 'Cannot add property 0, object is not extensible' error.

Changes:
- Simplified complex nested ternary in env.ts to avoid triggering bug
- Refactored nested ternaries in project-faq.tsx to if-else statements
- Disabled treeshaking as temporary workaround for remaining nested ternaries
- Added detailed comments explaining the Rollup bug and workaround

Impact:
- Build now completes successfully
- Bundle size increased to ~5.5MB (exceeds 5MB budget) due to disabled treeshaking
- Performance Budget Check will fail until treeshaking is re-enabled

Next steps:
- Upgrade Rollup when fix is released
- Or refactor all remaining nested ternaries across codebase
- Then re-enable treeshaking to reduce bundle size

References: rollup/rollup#5747

* feat: add FAQ sections to project pages in insights sidebar

- Create ProjectFAQ component with schema markup for better SEO
- Generate 7 dynamic FAQs per project based on repository data
- Include expand/collapse UI with smooth interactions
- Add FAQ section to insights sidebar for both desktop and mobile
- Implement proper loading states and error handling
- Questions cover contributor count, activity, trends, and patterns
- Updates dynamically when time range changes

Addresses #270

🤖 Generated with [Claude Code](https://claude.ai/code)

Co-authored-by: Brian Douglas <[email protected]>

* feat: enhance FAQ with LLM service and embeddings integration

- Add faq-service.ts with OpenAI-powered dynamic answers
- Implement semantic question matching using MiniLM embeddings
- Enhanced project-faq.tsx with AI indicators and confidence scores
- Add FAQ sitemap generator for improved SEO
- Include FAQ URLs in main sitemap for major repositories
- Support graceful fallback to static answers when AI unavailable
- Add structured data and citations for better search visibility

Co-authored-by: Brian Douglas <[email protected]>

* docs: add FAQ LLM integration documentation

* fix: resolve TypeScript errors and Rollup build issue

- Fix TypeScript errors in project-faq.tsx:
  - Remove unused imports (cn, FAQAnswer type)
  - Fix RepoStats type usage (removed non-existent health/activity properties)
  - Properly handle pr.author object structure for contributor indexing
  - Remove unsupported title prop from Sparkles icon

- Fix TypeScript errors in faq-service.ts:
  - Remove unused imports and variables
  - Fix type casting for cache service
  - Handle contributor data structure properly in reduce operations
  - Fix sort function type assertions

- Work around Rollup conditional expression bug:
  - Temporarily disable treeshaking to fix build error
  - Added TODO to re-enable once Rollup issue is resolved
  - Reference: rollup/rollup#5747

Build now completes successfully with all TypeScript errors resolved.

* fix: resolve Rollup conditional expression bug and refactor nested ternaries

Root cause: Rollup 4.45.0 has a bug with nested ternary operators during treeshaking
that causes 'Cannot add property 0, object is not extensible' error.

Changes:
- Simplified complex nested ternary in env.ts to avoid triggering bug
- Refactored nested ternaries in project-faq.tsx to if-else statements
- Disabled treeshaking as temporary workaround for remaining nested ternaries
- Added detailed comments explaining the Rollup bug and workaround

Impact:
- Build now completes successfully
- Bundle size increased to ~5.5MB (exceeds 5MB budget) due to disabled treeshaking
- Performance Budget Check will fail until treeshaking is re-enabled

Next steps:
- Upgrade Rollup when fix is released
- Or refactor all remaining nested ternaries across codebase
- Then re-enable treeshaking to reduce bundle size

References: rollup/rollup#5747

* refactor: replace nested ternaries with lookup objects and helper functions

Refactored nested ternary operators to use cleaner patterns:
- web-vitals-monitoring.ts: Use lookup objects for rating emojis/colors
- pagespeed-insights.ts: Extract helper functions for delta formatting
- badge-generator.tsx: Use color constants and helper functions
- env.ts: Simplify complex nested conditional logic

These changes reduce complexity and make the code more maintainable.
However, treeshaking still needs to be disabled due to remaining
nested ternaries throughout the codebase.

The Rollup bug (issue #5747) is triggered by ANY nested ternary,
so a complete refactor of all ternaries would be needed to re-enable
treeshaking without upgrading Rollup.

Impact:
- Cleaner, more maintainable code
- Partial progress toward fixing Rollup issue
- Bundle size still exceeds 5MB limit due to disabled treeshaking

* perf: implement lazy loading for insights sidebar components

Implemented code-splitting optimizations:
- Lazy load all insights sidebar sections (FAQ, Health, Recommendations, etc)
- Dynamic import heavy embeddings/transformers library in FAQ service
- Add loading skeletons for better UX during lazy loading
- Move insights components out of main bundle

Impact:
- FAQ and embeddings now load only when needed (~820KB saved from initial load)
- Improved initial page load performance
- Better code organization with clear async boundaries

Trade-offs:
- Bundle still exceeds 5MB due to disabled treeshaking (Rollup bug workaround)
- Treeshaking must remain disabled until Rollup issue #5747 is fixed
- Performance Budget Check will continue to fail

Next steps:
- Consider downgrading Rollup to avoid the bug
- Or systematically replace ALL nested ternaries across codebase
- Continue identifying more components for lazy loading

* fix: add Rollup treeshake workaround to Storybook config

The same Rollup 4.45.0 bug that affects the main build also affects
Storybook builds. Added treeshake: false to the Storybook viteFinal
configuration to match the main build workaround.

This fixes the 'Cannot add property 0, object is not extensible' error
during Storybook builds in CI.

Impact:
- Storybook builds now complete successfully
- Build and Deploy Storybook workflow should pass
- Slightly larger Storybook bundle (acceptable for documentation)

Note: This workaround can be removed once Rollup issue #5747 is fixed
or all nested ternaries are refactored.

* fix: make FAQ answers ultra-concise and fix text overflow

- Reduce FAQ cache to 24 hours for better freshness
- Make AI answers max 50 words (was 100, then 200)
- Make static answers 60-70% more concise
- Add cache version key (v3-ultra-concise) to bust old verbose cached answers
- Fix text overflow with break-words CSS class
- Ensure FAQs fit properly in sidebar window

* fix: properly constrain FAQ width in sidebar to prevent overflow

- Add overflow-hidden to parent container in insights-sidebar
- Use line-clamp-2 for FAQ questions (shows 2 lines max)
- Remove unnecessary break-words and overflow classes
- Simplify text display with standard wrapping

* fix: increase sidebar width to 420px for better FAQ readability

- Increase insights sidebar from 320px (w-80) to 420px for proper content display
- Remove line-clamp-2 restriction on FAQ questions
- FAQ questions and answers now have enough space to display properly

* fix: update FAQ design to match app design language

- Remove blue border and use standard card hover effect
- Remove blue Sparkles icons throughout
- Simplify AI confidence display
- Use consistent spacing (space-y-3) like other sections
- Use standard p-4 padding like recommendations section
- Simplify footer text for cleaner appearance

* fix: FAQ now generates specific answers for each question

- Remove broken generateFAQInsight that was hijacking health analysis
- Add dedicated callOpenAIForFAQ method with FAQ-specific system prompt
- System prompt emphasizes answering the specific question asked
- Cache version v4-specific-answers to force regeneration
- Each FAQ question now gets a unique, relevant answer instead of generic health advice

* fix: add local fallback for repository summary when Edge Function fails

- Add generateLocalSummary function for when Edge Function returns 500
- Generate basic summary from repository data and PR titles
- Prevents error state when Edge Function has issues
- Provides graceful degradation for summary feature

* fix: improve Edge Function error handling and deploy fix

- Add detailed error logging to repository-summary Edge Function
- Check for missing environment variables before use
- Continue without embeddings if generation fails (non-critical)
- Add fallback summary generation in client when Edge Function fails
- Provide detailed error information in response for debugging
- Successfully deployed updated Edge Function to production

* fix: resolve TypeScript build errors

- Remove unused avgPerDay and avgTitleLength variables
- Fix repositoryData reference in fallback summary generation
- Fetch repository data when needed for fallback
- Build now passes successfully

* feat: humanize numbers in repository summaries

- Add humanizeNumber function to format large numbers (27357 -> 27.4k)
- Apply to both local fallback and Edge Function summaries
- Update AI prompt to use humanized format in generated text
- Numbers now display as 1.2k, 5.7M instead of full values
- Better readability for repository metrics

---------

Co-authored-by: claude[bot] <209825114+claude[bot]@users.noreply.github.com>

* feat: add FAQ sections to project pages in insights sidebar

- Create ProjectFAQ component with schema markup for better SEO
- Generate 7 dynamic FAQs per project based on repository data
- Include expand/collapse UI with smooth interactions
- Add FAQ section to insights sidebar for both desktop and mobile
- Implement proper loading states and error handling
- Questions cover contributor count, activity, trends, and patterns
- Updates dynamically when time range changes

Addresses #270

🤖 Generated with [Claude Code](https://claude.ai/code)

Co-authored-by: Brian Douglas <[email protected]>

* feat: enhance FAQ with LLM service and embeddings integration

- Add faq-service.ts with OpenAI-powered dynamic answers
- Implement semantic question matching using MiniLM embeddings
- Enhanced project-faq.tsx with AI indicators and confidence scores
- Add FAQ sitemap generator for improved SEO
- Include FAQ URLs in main sitemap for major repositories
- Support graceful fallback to static answers when AI unavailable
- Add structured data and citations for better search visibility

Co-authored-by: Brian Douglas <[email protected]>

* docs: add FAQ LLM integration documentation

* fix: resolve TypeScript errors and Rollup build issue

- Fix TypeScript errors in project-faq.tsx:
  - Remove unused imports (cn, FAQAnswer type)
  - Fix RepoStats type usage (removed non-existent health/activity properties)
  - Properly handle pr.author object structure for contributor indexing
  - Remove unsupported title prop from Sparkles icon

- Fix TypeScript errors in faq-service.ts:
  - Remove unused imports and variables
  - Fix type casting for cache service
  - Handle contributor data structure properly in reduce operations
  - Fix sort function type assertions

- Work around Rollup conditional expression bug:
  - Temporarily disable treeshaking to fix build error
  - Added TODO to re-enable once Rollup issue is resolved
  - Reference: rollup/rollup#5747

Build now completes successfully with all TypeScript errors resolved.

* fix: resolve Rollup conditional expression bug and refactor nested ternaries

Root cause: Rollup 4.45.0 has a bug with nested ternary operators during treeshaking
that causes 'Cannot add property 0, object is not extensible' error.

Changes:
- Simplified complex nested ternary in env.ts to avoid triggering bug
- Refactored nested ternaries in project-faq.tsx to if-else statements
- Disabled treeshaking as temporary workaround for remaining nested ternaries
- Added detailed comments explaining the Rollup bug and workaround

Impact:
- Build now completes successfully
- Bundle size increased to ~5.5MB (exceeds 5MB budget) due to disabled treeshaking
- Performance Budget Check will fail until treeshaking is re-enabled

Next steps:
- Upgrade Rollup when fix is released
- Or refactor all remaining nested ternaries across codebase
- Then re-enable treeshaking to reduce bundle size

References: rollup/rollup#5747

* refactor: replace nested ternaries with lookup objects and helper functions

Refactored nested ternary operators to use cleaner patterns:
- web-vitals-monitoring.ts: Use lookup objects for rating emojis/colors
- pagespeed-insights.ts: Extract helper functions for delta formatting
- badge-generator.tsx: Use color constants and helper functions
- env.ts: Simplify complex nested conditional logic

These changes reduce complexity and make the code more maintainable.
However, treeshaking still needs to be disabled due to remaining
nested ternaries throughout the codebase.

The Rollup bug (issue #5747) is triggered by ANY nested ternary,
so a complete refactor of all ternaries would be needed to re-enable
treeshaking without upgrading Rollup.

Impact:
- Cleaner, more maintainable code
- Partial progress toward fixing Rollup issue
- Bundle size still exceeds 5MB limit due to disabled treeshaking

* perf: implement lazy loading for insights sidebar components

Implemented code-splitting optimizations:
- Lazy load all insights sidebar sections (FAQ, Health, Recommendations, etc)
- Dynamic import heavy embeddings/transformers library in FAQ service
- Add loading skeletons for better UX during lazy loading
- Move insights components out of main bundle

Impact:
- FAQ and embeddings now load only when needed (~820KB saved from initial load)
- Improved initial page load performance
- Better code organization with clear async boundaries

Trade-offs:
- Bundle still exceeds 5MB due to disabled treeshaking (Rollup bug workaround)
- Treeshaking must remain disabled until Rollup issue #5747 is fixed
- Performance Budget Check will continue to fail

Next steps:
- Consider downgrading Rollup to avoid the bug
- Or systematically replace ALL nested ternaries across codebase
- Continue identifying more components for lazy loading

* fix: add Rollup treeshake workaround to Storybook config

The same Rollup 4.45.0 bug that affects the main build also affects
Storybook builds. Added treeshake: false to the Storybook viteFinal
configuration to match the main build workaround.

This fixes the 'Cannot add property 0, object is not extensible' error
during Storybook builds in CI.

Impact:
- Storybook builds now complete successfully
- Build and Deploy Storybook workflow should pass
- Slightly larger Storybook bundle (acceptable for documentation)

Note: This workaround can be removed once Rollup issue #5747 is fixed
or all nested ternaries are refactored.

* fix: make FAQ answers ultra-concise and fix text overflow

- Reduce FAQ cache to 24 hours for better freshness
- Make AI answers max 50 words (was 100, then 200)
- Make static answers 60-70% more concise
- Add cache version key (v3-ultra-concise) to bust old verbose cached answers
- Fix text overflow with break-words CSS class
- Ensure FAQs fit properly in sidebar window

* fix: properly constrain FAQ width in sidebar to prevent overflow

- Add overflow-hidden to parent container in insights-sidebar
- Use line-clamp-2 for FAQ questions (shows 2 lines max)
- Remove unnecessary break-words and overflow classes
- Simplify text display with standard wrapping

* fix: increase sidebar width to 420px for better FAQ readability

- Increase insights sidebar from 320px (w-80) to 420px for proper content display
- Remove line-clamp-2 restriction on FAQ questions
- FAQ questions and answers now have enough space to display properly

* fix: update FAQ design to match app design language

- Remove blue border and use standard card hover effect
- Remove blue Sparkles icons throughout
- Simplify AI confidence display
- Use consistent spacing (space-y-3) like other sections
- Use standard p-4 padding like recommendations section
- Simplify footer text for cleaner appearance

* fix: FAQ now generates specific answers for each question

- Remove broken generateFAQInsight that was hijacking health analysis
- Add dedicated callOpenAIForFAQ method with FAQ-specific system prompt
- System prompt emphasizes answering the specific question asked
- Cache version v4-specific-answers to force regeneration
- Each FAQ question now gets a unique, relevant answer instead of generic health advice

* fix: add local fallback for repository summary when Edge Function fails

- Add generateLocalSummary function for when Edge Function returns 500
- Generate basic summary from repository data and PR titles
- Prevents error state when Edge Function has issues
- Provides graceful degradation for summary feature

* fix: improve Edge Function error handling and deploy fix

- Add detailed error logging to repository-summary Edge Function
- Check for missing environment variables before use
- Continue without embeddings if generation fails (non-critical)
- Add fallback summary generation in client when Edge Function fails
- Provide detailed error information in response for debugging
- Successfully deployed updated Edge Function to production

* fix: resolve TypeScript build errors

- Remove unused avgPerDay and avgTitleLength variables
- Fix repositoryData reference in fallback summary generation
- Fetch repository data when needed for fallback
- Build now passes successfully

* feat: humanize numbers in repository summaries

- Add humanizeNumber function to format large numbers (27357 -> 27.4k)
- Apply to both local fallback and Edge Function summaries
- Update AI prompt to use humanized format in generated text
- Numbers now display as 1.2k, 5.7M instead of full values
- Better readability for repository metrics

---------

Co-authored-by: claude[bot] <209825114+claude[bot]@users.noreply.github.com>