The syllabus is a list of enabled services

Week one is the terminal. Nothing else. Students who have VS Code available in week one never find out what ls does.

Every Kit service in a student's container is a daemon program, managed by the same HTTP API as the student's own processes. So the syllabus becomes a schedule of enables. A cron entry in your instructor container walks forty student containers on Monday mornings: week three, POST /api/v1/daemon/programs/{id}/enable for hoody-code; week five, the same for hoody-sqlite; week nine, hoody-browser. Disabled, the service's URL has nothing listening behind it. Enabled, the proxy starts it on the student's first click. At term end, POST /api/v1/daemon/programs/reset returns every container to defaults for the next cohort.

Nobody is told not to use the editor. The editor isn't running yet.