diff --git a/.kiro/specs/worker-rejoin-resync/tasks.md b/.kiro/specs/worker-rejoin-resync/tasks.md
index c82a58a7..1f3c6ebb 100644
--- a/.kiro/specs/worker-rejoin-resync/tasks.md
+++ b/.kiro/specs/worker-rejoin-resync/tasks.md
@@ -104,6 +104,14 @@
   - _Boundary: xcecd_resync.c_
   - _Depends: 4.2_
 
+- [ ] 4.4 Gate the worker's other periodic background reporting on the same resync_pending flag
+  - Close a Requirement 3.8 gap found by feature-level validation, missed by task 4.3's own boundary: `checking_connection()`'s `rejoin_call()` is not the worker daemon's only periodic post-join activity — `src/worker/src/resource_sync.c`'s `resource_sync_thread()` is a separate pthread, started once at daemon init (unrelated to any join event), that periodically (every `LOAD_INDICES_INTERVAL_DEFAULT`, 15s) sends live `xcecd_send_load_indices()`/`xcecli_update_resvals()` RPCs to the controller over the same connection used for the resync exchange, with zero reference to `resync_pending`/`xcecd_resync_is_pending()` anywhere in that file — confirmed by inspection
+  - Make the periodic load-indices send check `xcecd_resync_is_pending()` first, the same way `checking_connection()`'s `rejoin_call()` already does (task 4.3), and skip/defer that cycle's send while a reconciliation report is still in flight — the send is already periodic, so a skipped cycle is naturally retried on the next tick, no new retry/queueing mechanism needed
+  - Observable completion: a load-indices send that would otherwise fire while `resync_pending` is set is observed not to fire during that window, and resumes firing on its normal periodic cadence once the flag clears; the existing periodic cadence and behavior when no reconciliation is in flight are unchanged
+  - _Requirements: 3.8_
+  - _Boundary: resource_sync.c_
+  - _Depends: 4.3_
+
 - [x] 5. (P) Core: exclude a reconciling host from scheduler dispatch candidacy
   - Extend the scheduler's existing candidate-host filter so a host currently undergoing job-state reconciliation is excluded from dispatch candidacy the same way an already-unavailable host is
   - When the reconciling status clears, the same filter must stop excluding that host without any separate action