Implement the following plan:

Update TODOS.md: group leave and join code items

Changes

1. Remove "Show join code on every group member's page" TODO

Already discussed and decided: current behavior (code behind "Show code for another student" link) is the right tradeoff. Third members are uncommon; optimize for the common 2-person case.

2. Update "Allow students to leave groups" TODO with analysis notes

Replace the current sparse description with what we learned:

• No cross-partner dependencies exist today (no "both must submit" gates)
• The dangerous case is remaining member in a 2-person group losing content access mid-activity
• Instructor unlock API exists (POST /admin/:groupKey/:activityId/unlock) as an escape hatch
• Recommended approach when implemented: auto-unlock remaining member (continue solo) rather than resetting to pending
• 3-person groups are simple (remaining 2 still valid)
• Table until more classroom experience clarifies the needed behavior

Files modified

Verification

Review the updated TODOS.md to confirm accuracy.

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/33a88e5a-55b8-4f3b-a41e-bfe904d2c88c.jsonl

We were thinking about allowing partners to leave.

Yes.

I mean, there's not even a way for a student to leave, right? If they got up and left it doesn't matter.

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.

Please add a TODO on allowing a student to receive feedback from the evaluator after an assessment is complete about what they got wrong. We may also want to even surface the per-answer rubric evaluations at that point.

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 to design Thursday's activity. If you check the syllabus this is supposed to be on content creation, creativity using AI. I think we want to have students creating images, movies, music, and stories. I'd like a way for students to share out their creations during the activity, potentially by uploading images, text, or sharing a link (music or movies). We'll need to find services for them to use, ideally free, or maybe just make multiple suggestions, and the ability to share artifacts would be a plus. It would be cool if, after each creative task, I could show the results to the students on my display.

I'd suggest four sections, each with separate partners, separated by share outs. Probably start with images, then video, then music, then stories.

One idea is to have the partners come up with an idea together, work separately to prompt the AI, and then compare results. This would also get across the idea that AI outputs can vary. They could even use different tools. Anyway, these are just ideas.

Actually, maybe let's skip the text story part? Part of the goal here is both creativity but also showing that AI can generate more than text. Three activities would give us time to discuss the creativity / energy tradeoffs toward the end.