{"version":"2.1.242","anchor":"incoming-file-bundles-are-quarantined-and-audited-before-the","canonical_anchor":"incoming-file-bundles-are-quarantined-and-audited-before-the","heading":"Incoming file bundles are quarantined and audited before they land","tier":"notice","area":"Directory Sync","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.242\/e\/incoming-file-bundles-are-quarantined-and-audited-before-the","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.242","markdown":"### Incoming file bundles are quarantined and audited before they land\n\nIncoming file bundles are unpacked and verified in a scratch directory before touching your repo.\n\n**What**\n\nWhen a cloud session sends your machine a bundle of file changes, Claude Code now unpacks it into a throwaway directory first and checks it end to end before letting any of it into the repository. A bundle that does not match what it claims to contain is refused whole.\n\n**Details**\n\n- The bundle is indexed with `index-pack --strict` into a per-run quarantine directory, then verified four ways: every tip it names must be a commit the bundle actually delivered, the stated commit range must name exactly the objects carried, and anything it depends on must be history this side already has.\n- A record of the delivered object ids is written before the bundle is moved into permanent storage, so a half-applied transfer is detectable later.\n- Failures produce one fixed reason rather than a per-check message, and the quarantine is swept. Stale quarantine directories, leftover `.keep` files and orphaned delivery records are cleaned up on subsequent runs.\n- Part of the git sync engine; there is no separate switch for the audit.\n\n**Evidence**\n\n`the pack was refused: malformed, not self-contained, or not exactly what its range names`\n\n- Area: Directory Sync\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 3\/5"}