Record slice 3 recheck after later slices drifted staffing paths.

Pin homeroom seats, the management money row and assign-from-card, and drop the stale top-three skills claim from the protocol.

Co-authored-by: Cursor <cursoragent@cursor.com>

docs/protocol.md

@@ -686,9 +686,9 @@ one.
 Applicants here are the same people as in `saves/{id}.people.json`. A parent keeps the same
 id on the roster; hiring them sets `isStaff` on that person and does not create a second
 entity. Generated candidates (`aN.p0`) join the roster only when hired. `skills` on an
-applicant are the three strongest, for the management list; the card lists every skill they
-have, not the three strongest. `positions` and `subjects` are the school's catalog, so the hire and assign pickers
-do not need a second request.
+applicant are every skill they have (the applicant window compares the whole row, not a
+top-three summary); the person card lists the same set. `positions` and `subjects` are the
+school's catalog, so the hire and assign pickers do not need a second request.
 
 `GET /api/schools/{id}/people/{personId}` also opens a card for someone who is only in the
 applicant pool (needs are the frozen snapshot — they are not in the World yet). Unknown