exams

The Exams submodule is split across three controllers that together cover authoring and taking exams. `ExamController` (`/lms/exams`) owns exam definitions — title, code, scoring threshold, time limit, shuffle/answer-key-visibility flags, level, and status — plus a nested question-management surface for adding, editing, removing, and reordering each exam's questions. Five question types are supported: multiple_choice and true_false are auto-graded against marked-correct alternatives (true_false strictly requires exactly two), essay is stored ungraded for manual review, fill_blank is graded by case-insensitive exact match against one or more accepted answers, and matching is graded by exact left/right pair-set comparison. A small but easy-to-miss design choice: `GET /lms/exams/:id` returns `null` rather than a 404 when the exam doesn't exist, and several question-management endpoints (delete, reorder) are no-ops rather than errors when the target doesn't exist or the submitted id set doesn't match — callers should check response shape rather than relying purely on HTTP status.

`QuestionController` (`/lms/questions`) is a separate, flatter standalone question bank — questions created here are not linked to any exam at creation time, useful for building a reusable item bank before assembling exams, or for other parts of the platform that need ad-hoc graded questions outside the exam-attempt flow.

`ExamAttemptController` (also under `/lms/exams`) is the learner-facing half: starting an attempt, saving in-progress answers, and submitting for grading. `GET /:id/attempt` auto-finalizes an attempt if its time limit has silently elapsed, and resolves which `person` record the attempt belongs to via a fallback chain — explicit `studentId` override, then email-matched person, then (as a last resort) auto-creating a new person record for the calling user, which is a notable side effect worth knowing about before scripting against this endpoint with a fresh service account. Starting a new attempt is idempotent against an existing unexpired in-progress attempt, and submission publishes an `lms.exam.attempt.submitted` integration event carrying the final score and pass/fail outcome for downstream consumers (e.g. achievement-granting or enterprise license reporting) to react to.