Enhance school simulation and management by integrating roster functionality, allowing for the installation and persistence of student and staff data. Update the school architecture to include a roster alongside existing components, ensuring proper validation against map layouts. Revise room definitions to support homeroom designations and update related tests to validate new functionalities and ensure robustness in roster handling.

2026-08-18 19:21:40 +03:00
parent e6182e0e45
commit 52c5082418
27 changed files with 732 additions and 66 deletions
@@ -12,6 +12,7 @@ way; this file is *how to work in them*.
 | defs, JSONC catalog, map validation | `src/HSchool.Content` |
 | skills, traits, body, needs, name sets | `src/HSchool.Content` |
 | people generation, families, roster records | `src/HSchool.People` |
+| people in a school's World, need decay | `src/HSchool.Simulation` |
 | the menu API (list, create, delete, mods, catalog) | `src/HSchool.Server/Api` **and** `docs/protocol.md` |
 | what the socket carries | `src/HSchool.Protocol` **and** `src/HSchool.Client/src/net/protocol.ts` **and** `docs/protocol.md` |
 | connection handling, workers, saves | `src/HSchool.Server` |
@@ -104,6 +105,7 @@ say so explicitly in the change description.
 ## Testing policy

 - Simulation changes need a `GameClock` or `SchoolRegistry` test. They are fast and need no host.
+  Putting a roster into `World` and ticking needs belongs there too.
 - People generation belongs in `tests/HSchool.People.Tests`. Same seed, map and name set must
  produce the same roster; the suite does not boot a host.
 - Catalog, inheritance, patches and map validation belong in `tests/HSchool.Content.Tests`.