{"version":"2.1.234","anchor":"cyber-refusal-state-survives-resuming-a-session","canonical_anchor":"cyber-refusal-state-survives-resuming-a-session","heading":"Cyber refusal state survives resuming a session","tier":"internal","area":"Safety Fallbacks","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.234\/e\/cyber-refusal-state-survives-resuming-a-session","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.234","markdown":"### Cyber refusal state survives resuming a session\n\nA cyber-refusal mitigation now sticks after you resume a session instead of being forgotten.\n\n**What**\n\nThe refusal-fallback record now carries a sticky flag, `sawCyberRefusal`, merged forward each time the fallback state is updated. On resume, the mitigation header is re-applied if either the current refusal category or the sticky flag says cyber, so it still applies after the original categorised event has scrolled out of the conversation.\n\n**Details**\n\n- Serialised as `saw_cyber_refusal`.\n\n**Evidence**\n\n`sawCyberRefusal`\n\n- Area: Safety Fallbacks\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 3\/5"}