08f170aeab
spawnPoolBackend() is not on every dial path: a primary route (startHermes), a registry remote scope (connectRegistryBackend), a reused primary SSH backend, or a guard rejection all settle the claim without requesting a slot, so a foreground mark set for that dial stayed in pendingForegroundSpawns and would have upgraded the next background hydration spawn of the same key. applySpawnPriority() now returns the cleanup; both IPC handlers run it in a finally around the claim. The mark is also taken right before the slot request instead of at function entry, so the remote branch never consumes it.