I'll help you convert the class timetable from manual data to automatic seeding via a script, similar to how semester fees and scholarships work. Let me first examine the current setup.

Let me search for the actual file locations:

Let me try reading with direct paths:

Now let me read the ai-service to understand how timetables are queried:

Now let me read the rest of seed-campus-data to see how it currently seeds timetables:

Now I understand the complete architecture. The class timetables are imported from lib/data/class-timetables.ts and seeded in seed-campus-data.ts. I need to:

1. Delete the manual data file lib/data/class-timetables.ts
2. Update seed-campus-data.ts to embed the timetable data directly (like scholarships, circulars, etc.) instead of importing from an external file
3. Add timetables for ALL programs and ALL semesters (not just B.Tech)

Now I have a complete understanding. Let me implement the changes:

1. Delete the manual data file lib/data/class-timetables.ts
2. Update seed-campus-data.ts to embed all class timetable data directly and add timetables for ALL programs (BTECH, BSC, BBA, BCOM, MSC, MBA) and all their semesters

I've made the following changes:

1. Deleted lib/data/class-timetables.ts - the manual data file is no longer needed

2. Updated lib/utils/seed-campus-data.ts to:

   • Embed all timetable data directly in the file via generateClassTimetables() function
   • Include complete timetables for ALL 6 programs (BTECH, BSC, BBA, BCOM, MSC, MBA) and ALL their semesters (32 total timetables)
   • Automatically seed timetables when the website runs, just like FAQs and other campus data

The timetables now cover:

• B.Tech: 8 semesters with detailed CSE-focused schedules
• B.Sc: 6 semesters with Physics/Math/Chemistry subjects
• BBA: 6 semesters with business management subjects
• B.Com: 6 semesters with accounting/commerce subjects
• M.Sc: 4 semesters with advanced specialization subjects
• MBA: 4 semesters with complete management curriculum (including Saturday classes)

I see the issue - the ChatHistory model requires an expiresAt field but it's not being set when saving chat history. Let me fix this.

Now let me check the ChatHistory model to see the expiresAt field requirement:

I see the issue. The ChatHistory.create() method bypasses the pre-save hook that sets expiresAt. The pre-save hook only works when using .save() method, not when using .create(). I need to either:

1. Explicitly set expiresAt when using ChatHistory.create()
2. Or change from create() to instantiate and save

Let me fix the chat route to explicitly set expiresAt:

The issue was that ChatHistory.create() bypasses the Mongoose pre-save hook that sets expiresAt. I've fixed all 3 places in the chat API route where ChatHistory.create() is called by explicitly setting the expiresAt field to 30 days from now. This ensures the TTL (Time-To-Live) functionality works correctly for auto-deleting old chat history.