{"version":"2.1.227","anchor":"directory-sync-reports-pull-push-base-capture-and-rehoming","canonical_anchor":"directory-sync-reports-pull-push-base-capture-and-rehoming","heading":"Directory sync reports pull, push, base capture and rehoming","tier":"internal","area":"File Sync","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.227\/e\/directory-sync-reports-pull-push-base-capture-and-rehoming","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.227","markdown":"### Directory sync reports pull, push, base capture and rehoming\n\nNew reporting covers directory sync pulls, pushes, initial scans and workspace re-pointing.\n\n**What**\n\nFour events cover the new worker sync: `tengu_dir_sync_worker_pull` and `tengu_dir_sync_worker_push` carry per-turn counts of files considered, filtered, applied, already equal, conflicted, stale, failed and deferred, while `tengu_dir_sync_worker_base` and `tengu_dir_sync_worker_rehome` cover the initial scan and workspace re-pointing.\n\n**Details**\n\n- Structured pass\/fail statuses are also recorded with reasons including `session_refused`, `auth_refused`, `rows_deferred`, `over_budget` and `too_many_paths`.\n- Emitted only on remote worker sessions, under the same environment gate as the syncer.\n\n**Evidence**\n\n`tengu_dir_sync_worker_push`\n\n- Area: File Sync\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 4\/5"}