{"version":"2.1.238","anchor":"module-level-mutable-state-moved-into-per-process-holders","canonical_anchor":"module-level-mutable-state-moved-into-per-process-holders","heading":"Module-level mutable state moved into per-process holders","tier":"internal","area":"Session State","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.238\/e\/module-level-mutable-state-moved-into-per-process-holders","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.238","markdown":"### Module-level mutable state moved into per-process holders\n\nVarious long-lived globals moved onto per-process state objects; nothing behaves differently.\n\n**What**\n\nSeveral long-lived variables, including the feedback-notice state, MCP auth caches, dropped-tool sequence maps, live shell command sets and the plugin marketplace memo, now live on lazily built state objects instead of loose module variables. No behaviour changes.\n\n**Evidence**\n\n`Ip.feedbackNotice`\n\n- Area: Session State\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}