Kleine fehler beseitigt

AGENTS.md

@@ -32,7 +32,7 @@ user-facing text.
 │   ├── Test.html            # main app (served at /)
 │   ├── js/                  # shared modules (classic scripts, global fns)
 │   │   ├── globals.js       # Konstanten (LPHS, ROLES, LPH-Farben, DEPARTMENTS) + db/currentDepartment
-│   │   ├── utils.js         # esc, uid, Datum-/Differenz-Helfer, personIdForName, weekSortKey-Quelle
+│   │   ├── utils.js         # esc, uid, Datum-/Differenz-Helfer, personIdForName, peopleByRole, assignKey, weekSortKey-Quelle
 │   │   ├── ui.js            # LocalStorage-UI-State, Header-Collapse, Theme
 │   │   ├── date-picker.js   # Datums-/Bereichspicker-Overlays
 │   │   ├── csv.js           # CSV-Parser/Serializer + weekSortKey, filenameForWeek
@@ -147,6 +147,17 @@ docker compose up --build # Docker variant (compose file is at repo root)
   `_people.csv` — not just the changed week. Exception: `js/plan/plan-state.js`
   `savePlan()` bypasses `save()` and writes only the current week's CSV directly
   via `sendCsvToServer()`.
+- `switchDepartment()` cancels a pending save debounce before switching, and
+  `load()` discards stale `/load-all` responses after a department switch
+  (frozen `requestedDepartment`), so late responses can never render or persist
+  data under the wrong department.
+- Person drag-and-drop in the people tab: drag handle (`.drag-handle`) binds
+  `ondragstart`/`ondragend`, the `.people-sortable` container binds
+  `ondragover`/`ondrop`; insertion is computed by `getDragAfterElement(container,
+  y, selector)` (`js/projects/projects.js`, used with `.person-card` here and
+  `.person-list-item` in the projects tab). `reorderPeople()` updates both
+  `db.globalPeople` and the current week's person copy, then `save()`. No drag
+  handles are rendered on locked weeks.
 - Weeks are sorted by calendar week extracted from the label (`KW XX / YYYY`)
   via `weekSortKey()`, not alphabetically/by filename.
 - `applyAutoLock()` locks every week except the chronologically last one after