devdocs - Deferred: client keeps cached enum lists and menu across upgrades until logout

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

devdocs/modernization/NET10-PORT.md

@@ -289,6 +289,7 @@ Found during the port, out of scope. One line each.
 - Found in case 4739: reports rendered by the server for customer notifications use the subscription's time zone, and when it is empty `resource/rpt/ay-report.js` falls back to `America/Winnipeg` (date, time and date-time helpers), an arbitrary zone like the client's old New York default. Decide on a better default (the server's own zone?)
 - Found in case 4683 (pre-existing, raven-client and sockeye-client): the **Today** and **Now** buttons of the date, date-time and time pickers (`components/date-time-control.vue`, `time-control.vue`) take the date and time from the browser's own clock (`DateTime.local()`), not from the user's time zone override. The moment set by Now is still right (the time carries the browser's offset), but for a user whose override zone is far from the browser's zone, Today near midnight can pick the neighbouring day
 - From Sockeye case 4468 (pre-existing in AyaNova, no user impact today): `ReviewBiz` does not check that a review has a record type and id, so an API caller can save a review that belongs to nothing (`AType` 0). AyaNova's own client always sends both. Sockeye now refuses it (`VALIDATION_REQUIRED` on `SockType` / `ObjectId`); the same two checks in AyaNova's `ReviewBiz.ValidateAsync` would close it
+- Found in Sockeye 8.1.4 and 8.2.0 (pre-existing, raven-client and sockeye-client): the client keeps enum lists (e.g. `NotifyEventType`) and the navigation menu in the browser's saved state (`vuex-persistedstate`) until logout, so after an upgrade that adds or removes event types or menu entries a user still signed in sees the old lists. Fix: clear the cached enum lists (and rebuild the menu) when the server version differs from the one they were cached under
 
 ## Log