Implement the following plan:

Auto-Discover Meeting Files from Frontmatter

Problem

The current meetingsRegistry in apps/web/lib/meetings.ts duplicates data from MDX frontmatter. When a meeting MDX file is created, it must also be manually added to the registry - which is error-prone (as demonstrated by the missing AI Scavenger Hunt meeting).

Solution

Auto-discover meeting files from the content/{semester}/meetings/ directory and extract metadata from their frontmatter. This eliminates the manual registry entirely.

Implementation

Modify apps/web/lib/meetings.ts

Replace the manual registry with file system scanning:

import fs from "fs";
import path from "path";
import matter from "gray-matter";

const CONTENT_DIR = path.join(process.cwd(), "../../content");

// Cache for discovered meetings
const meetingsCache = new Map<string, MeetingMeta[]>();

// Discover meetings by scanning the filesystem and reading frontmatter
function discoverMeetings(semesterId: string): MeetingMeta[] {
  if (meetingsCache.has(semesterId)) {
    return meetingsCache.get(semesterId)!;
  }

  const meetingsDir = path.join(CONTENT_DIR, semesterId, "meetings");

  if (!fs.existsSync(meetingsDir)) {
    return [];
  }

  const files = fs.readdirSync(meetingsDir)
    .filter(f => f.endsWith(".mdx"));

  const meetings: MeetingMeta[] = files.map(filename => {
    const filePath = path.join(meetingsDir, filename);
    const content = fs.readFileSync(filePath, "utf-8");
    const { data } = matter(content);

    return {
      slug: filename.replace(".mdx", ""),
      date: data.date,
      title: data.title,
      summary: data.summary,
    };
  });

  meetingsCache.set(semesterId, meetings);
  return meetings;
}

Update Existing Functions

• getMeetings() → calls discoverMeetings() instead of reading from registry
• getMeetingSlugs() → same change
• Remove meetingsRegistry entirely

Files to Modify

• apps/web/lib/meetings.ts - Replace registry with auto-discovery
• apps/web/package.json - Add gray-matter dependency

Commands

cd apps/web && bun add gray-matter

Verification

1. Run bun run dev and check /spring2026/meetings
2. Verify both meetings appear (Welcome and AI Scavenger Hunt)
3. Verify the AI Scavenger Hunt meeting is shown as "Upcoming" (since today is Jan 26, meeting is Jan 27)
4. Click through to verify meeting pages load correctly
5. Run bun run build to ensure static generation works

If you need specific details from before exiting plan mode (like exact code snippets, error messages, or content you generated), read the full transcript at: ~/.claude/projects/-Users-challen-www-usingandunderstanding-ai/ddad923f-a276-444b-ae3e-835237130518.jsonl

Your task

First, run git status, git diff, and git log --oneline -10 to understand the current state.

Then add and commit all modified files with a descriptive message. Break the changes into multiple commits if appropriate. If there are untracked files, ask if they should be added or added to the appropriate .gitignore file. The user may also want to take over at this point, so provide an abort option as well. Always check changes for unnecessary debugging statements or logging that might have been accidentally included. Prompt the user if you find any, and offer to remove each one by one. Do not use interactive git staging (git add -p) as it does not work.

OK. Now, we need some kind of instructor view for group activities and stages. Right now the group activity shows the Find a Partner dialog to me, but I should not need to do that since I'm an instructor.