Fix build issue: Correct type error in lib/system-prompt.ts regarding 'map' usage

[Emlembow]

Description

The build is currently failing due to a type error in lib/system-prompt.ts at line 328. The error message indicates that the property map does not exist on type AboutContent | ProfileInfo | Education | Experience[] | Reference[] | BlogPost[] | Project[] and specifically points out that it does not exist on type AboutContent.

./lib/system-prompt.ts:328:54
Type error: Property 'map' does not exist on type 'AboutContent | ProfileInfo | Education | Experience[] | Reference[] | BlogPost[] | Project[]'.
  Property 'map' does not exist on type 'AboutContent'.

 326 |
 327 |     // Format work experience
> 328 |     const workExperience = experiences ? experiences.map((exp, index) => `
 329 | ### ${index + 1}. ${exp.title} at ${exp.company}
 330 | - **Duration**: ${exp.startDate} to ${exp.endDate}
 331 | - **Location**: ${exp.location}

Expected Behavior

The build should compile successfully without any type errors. The map function should be used only when experiences is an array.

Proposed Fix

• Investigate the type definition of experiences to understand why it might be of type AboutContent (or other non-array types).
• Implement proper type checking or type guards to ensure that .map is only invoked when experiences is actually an array.
• Alternatively, update the type definitions so that experiences is typed correctly as an array where applicable.

Steps to Reproduce

1. Clone the repository Emlembow/ChatWithPortfolio from branch master at commit 11007f8.
2. Run npm install to install dependencies.
3. Execute the build command: npm run build.

Additional Context

This issue surfaces during the Next.js build process when formatting work experience in the system prompt.

[Emlembow]

@claude analyze how system prompt is being built, find all issues and fix them.

[claude]

Claude finished @Emlembow's task in 3m 9s —— View job • claude/issue-11-20250610_185433 • Create PR ➔

---

Analyzing System Prompt Build Issues ✅

I've analyzed the system prompt building process and fixed the build issues.

Todo List:

• Set up development environment and install dependencies (Note: Cannot run npm/build commands without Bash permissions)
• Read and analyze lib/system-prompt.ts to understand the type error
• Examine content type definitions and loading logic
• Fix type issues with proper type guards or corrections
• Test the build to ensure it passes (Note: Requires user to test build with npm run build)
• Commit fixes and provide PR link

Analysis & Fix:

Root Cause: In lib/system-prompt.ts:317, the code destructures results from Promise.allSettled() which can return null values when promises are rejected. TypeScript correctly identified that .map() doesn't exist on potentially null values.

Solution: Added Array.isArray() checks before all .map() calls on:

• experiences (line 328)
• projects (line 340)
• references (line 357)
• blogPosts (line 369)
• Technology aggregation (lines 380-381)
• Current role check (line 395)

Changes Made:

✅ Fixed - Added proper type guards using && Array.isArray() before all .map() calls
✅ Committed - All fixes pushed to current branch

Next Steps:

Please test the build with npm run build to verify the TypeScript errors are resolved.

---