{"version":"2.1.280","anchor":"internal-chained-update-bundle-verification-logic","canonical_anchor":"internal-chained-update-bundle-verification-logic","heading":"Self-update bundle verification and syncing gains worktree-commit-aware 'link' checks","tier":"internal","area":"Elsewhere","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280\/e\/internal-chained-update-bundle-verification-logic","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280","markdown":"### Self-update bundle verification and syncing gains worktree-commit-aware 'link' checks\n\nClient self-update now validates chained bundles and syncs lightweight 'link' records tied to a worktree commit\n\n**What**\n\n- Two new internal functions validate a client self-update \"chain\": one checks whether an update chain is well-formed or absent, and another classifies a chained bundle record as `single`, `invalid` (with reasons `absent`, `ahead`, or `untied`), or `links`, by comparing generation, `worktreeCommit`, sha256, and size against the current bundle.\n\n- The directory-sync transport used between laptop and worker machines gained `putLink`\/`getLink` methods, keyed by `generation` and `worktreeCommit`, alongside the existing `putOutbound`\/`getInbound` methods used for full content sync.\n\n**Why** This adds a lighter-weight way to verify and sync update-bundle identity between machines, without needing to transfer full directory content each time.\n\n- Area: Elsewhere\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 2\/5"}