Constant MUTATING_MAP_CACHE_OPS 

pub const MUTATING_MAP_CACHE_OPS: &[&str];

Decision C (#1165): the closed sets of mutating storage-op names, one pub constant per kind group — read by bynk_lower::body_writes_state’s own Callee::Store-keyed write-detection walk (P6.8, Decision B), which needs no receiver-name gate at all: a Callee::Store already carries the field’s own resolved identity, not a name that could be shadowed. Until #1196, this module also had its own bare-Ident-receiver-name-matching reader (block_writes_state’s own mutating_op, deleted) — a single shared source avoided the class of drift #1164’s own review caught twice for a different pair of independently hand-maintained copies (cache_ttl_millis’s DurationLit extraction, store_map_indexes’s dedup); now there is only the one reader. Live in bynk-ir (not bynk-emit or bynk-lower specifically, moved here from bynk-emit::emitter at the P7.12 crate carve, no behaviour change) since a future bynk-emit-side reader (a Service handler’s own write detection, say) may need them again, the same reasoning that kept them pub(crate) rather than bynk-lower-private before the carve. Map/Cache share one list — both support the same four entry ops — rather than two identical ones.