git-asmt-page

git-asmt-page — Canvas page for a git assignment (L1 child)

The Canvas half of git-asmt. It does not build the repo (that's git-asmt-repo). It builds the page and its parts, in the standard format the global builder produces. You never hand-write the page HTML or the gDoc — you fill the asmt dict and call git_page; it renders the instruction gDoc AND the page from the same dict (so they always agree) and uploads it (unpublished).

import sys
sys.path.insert(0, "$CANVAS_LMS_ROOT/.claude/skills/assignment-page-builder")
from git_page import git_page
out = git_page(course_slug, asmt, points=N, push=True, due_at="…Z")

The parts this page must carry (the "common elements")

Every git-assignment page, built from the asmt dict:

• Instruction — what to make: gist (1 line) + spec (what each case does) + algorithm.
• Function contract — the core prototype, parameters, return (io: Parameter / Return lines). For a stdin program instead, the I/O is the stdin→stdout contract (no prototype).
• Examples — call → output pairs (verbatim from the spec/slides; RUN it, paste the real result).
• Restrictions — yellow box (what NOT to do; mirrors what the tests enforce).
• Elaboration — navy box: exactly what the student must WRITE (graded) — algorithm, edge correctness, errors→fixes with commit links.
• Test-items table — per grader (Compile/Run/T1..Tn) with max points and what it checks, taken from the ACTUAL test file (never invented).
• Per-item points / Rubric — the Item | Points | Criteria table summing to points_possible (autograder / elaboration / commit / repo-link split — GRADING.md). points=N → git_page distributes by rubric_weights; never hardcode per-item numbers.
• Request link — …/classroom/issues/new?template=<request_form>&assignment=<CODE> (git_page builds it from request_id=CODE; requires the CODE registered by git-asmt-repo first). ⛔ ONE VALUE, FOUR PLACES. request_id = code = the assignment slot in the student repo name = the org-hub config.json key: <course>-<term>-A612-<student-login> · <COURSE>A612Starter · key "A612". request_id exists only for the ~1% assignment whose request key genuinely differs — passing a different value is a DECLARATION, not a default, and git_page now STOPS on a silent divergence. Why: on 2026-08-04 all 14 CSCI-19A chapter-5 pages shipped assignment=5-6-style TITLES while the register held A56, and nothing noticed for a whole chapter — the student request form is a dropdown generated from config.json, so students picked the right entry and the broken pre-fill stayed invisible.
• Full guide — the embedded instruction gDoc (git_page makes it in pages_folder).