FLS21 — the COST of permission-change propagation, measured. Every write to a metadata member
entity (an Entity Field Permission row included) schedules one debounced full metadata refresh
on the server — a complete MJ_Metadata reload from SQL plus the in-memory graph rebuild. This
check times two back-to-back hard refreshes (the exact operation the event-driven mechanism
runs) so the duration is recorded on every CI run and a regression shows up as a trend, not a
surprise. N writes inside one 500ms debounce window still cost ONE of these (the burst
coalescing is unit-tested in providerBase.metadataMemberRefresh.test.ts); only writes spaced
wider than the window pay it again. Deliberately NO wall-clock assertion beyond a generous
sanity ceiling — machine speed varies and this check exists for visibility, not gating.
FLS21 — the COST of permission-change propagation, measured. Every write to a metadata member entity (an Entity Field Permission row included) schedules one debounced full metadata refresh on the server — a complete MJ_Metadata reload from SQL plus the in-memory graph rebuild. This check times two back-to-back hard refreshes (the exact operation the event-driven mechanism runs) so the duration is recorded on every CI run and a regression shows up as a trend, not a surprise. N writes inside one 500ms debounce window still cost ONE of these (the burst coalescing is unit-tested in providerBase.metadataMemberRefresh.test.ts); only writes spaced wider than the window pay it again. Deliberately NO wall-clock assertion beyond a generous sanity ceiling — machine speed varies and this check exists for visibility, not gating.