The bell freezes the game mid-frame

Fourth period ends in ninety seconds and nobody in the game-design elective wants to stop play-testing.

They don't have to lose anything. At the bell, a cron-driven script POSTs /api/v1/system/processes/freeze to every container in the class, targeting the game by name with include_descendants: true. SIGSTOP suspends the whole process tree: in-memory state intact, score intact, the level exactly where it was. The containers keep running; only the games sleep.

Tomorrow, fourth period's first request is /unfreeze, and thirty games resume mid-frame, as if the school day were one long pause menu.

Nothing was saved, because nothing needed saving. The bell is an API call.