agenda-wrapup

Weekly Agenda + Wrap-up pages (GLOBAL, config-driven)

Two Canvas PAGES per week/module, both derived from the same module data:

• Agenda (week start): what to do this week.
• Wrap-up (week end): the same to-dos as a checklist + what you learned + confirm you finished.

The Wrap-up is the Agenda's to-do list, condensed and recast — so generate both from one module read. Reference origin: .claude/code/gen_agenda.py + workflows/45weekagenda.md (; that was a per-course requests script — this uses the central canvas_rest instead).

Shared core — read the module ONCE

1. Find the module for the week: canvas_rest.list_modules(base, tok, cid) → match the week in the name ([Week N], Week N, 👉 Week N, …); a week can span multiple modules → collect all. (Or the user gives the module id directly (usually they do). Per-course week↔module ids are not stored here — pass the module id, or keep a map in that course's input/course-info.md if you want one.)
2. Read items: canvas_rest.get(base, tok, f"/courses/{cid}/modules/{mid}/items").
3. Categorize (item type + SubHeader labels): Readings/OER, Video lectures, Lecture slides, Jupyter/practice, Labs, Assignments, Quizzes, Exams. Skip existing Agenda/Wrap-up Page items (we're regenerating those).
4. Due dates: each Assignment item → fetch_assignment(base, tok, cid, content_id)["due_at"]; each Quiz item → fetch_quiz(base, tok, cid, content_id)["due_at"]. Convert with canvas_rest.to_localtime(due) — NEVER show raw UTC (this Canvas = CCC / California). Null → "No due date set".

Render — Agenda (week start), 3 sections

1. This week's to-dos — what to read, what to practice, further reading / references (pulled & condensed from the module's pages/readings).
2. Graded — do these — assignments / quizzes / exams, each with its due date in PDT/PST.
3. Closing — a short encouragement, an easy "reach out anytime" line, kind words.