Directory sync treats a full store as non-blocking, and a full lane now counts as store_full

What

Directory sync sends your session's file changes to another machine before a command runs there. When the store holding those changes is full (store_full):

• The failure is still recorded, but the exchange with the other machine carries on. Before, any failed push stopped at that point.
• The remote command now just runs, instead of failing with a message and a suggested fix.
• store_full was added to the file-sync failure reasons.

In the git-based sync worker, a lane_full answer while detached now marks the store as full. Before, it went through the generic not-sent path and was counted as a failed upload. Bundles that are too large no longer take a separate early exit in that mode. A record rebuilt from an earlier stored row now carries its real unshipped flag instead of always false.

Why

A full sync store no longer blocks commands on the other machine. The catch is that such a command may run on files that are missing your latest changes, and you get no note saying so.