Module scenarios 

Named scenarios: small compositions of the control primitives, exposed as one command.

A scenario earns its place only by composing something data alone cannot express — an armed fault — or by being a hands-free dev demo; per-spec fixtures come from the seed instead.

Each writes the course unit for its courseCode whole, so its caller has to own that course code, and returns the identifiers it minted plus the scope its rows are ticked with.

Structs

ScenarioArgs

Constants

PASS_FAIL_SCALE 🔒

SCENARIOS

Functions

apply

arm 🔒

arm_after_import 🔒

course_code 🔒

ensure_course 🔒

A five-credit pass/fail course Suotar carries: the scenarios differ in the fault they arm, not in their data.

merge 🔒

plain 🔒

put_enrolment 🔒

put_person 🔒

string_field 🔒

timeout 🔒

sisuTimeout after the write, with the written submission’s id in result: the case a client cannot resolve without verifying.

unanswered 🔒

The import lands but its item is missing from the response, so the client learns no id at all.