{"version":"2.1.218","anchor":"forked-skill-resume-security-hardened","canonical_anchor":"forked-skill-resume-security-hardened","heading":"Forked Skill Resume Security Hardened","tier":null,"area":null,"scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.218\/e\/forked-skill-resume-security-hardened","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.218","markdown":"### Forked Skill Resume Security Hardened\n\nWhen a session resumes and picks up a forked-skill agent, the resumption path now validates:\n\n- The scoping record file (`.forked-skill.json`) must be present and parseable\n- The record must name the same skill as the agent's task record\n- For cold restarts, a provenance-marker witness (`.forked-skill.marker.json`) must also be present and corroborate the fork identity\n\nIf any check fails, the agent refuses to resume and logs a clear error rather than running without its intended permission scoping. This prevents forked-skill agents from running with wrong or missing permission boundaries after a restart.\n\n**Evidence**\n\nResume validation guards (search for `\"refusing to resume it without the skill's permission scoping\"`)"}