Motivation

rewatch watch can start while another rewatch build is running, and the two commands intentionally use separate watch.lock and build.lock files. However, watch startup still had a gap in its build locking.

The watcher acquired build.lock while running initialize_build, then released it before entering async_watch, where the initial compile happened through a second lock acquisition. That left a window where another build process could start between watch initialization and the watcher’s initial compile. Since initialization and compilation both mutate build artifacts, that gap could allow concurrent artifact writes and trigger inconsistent build output.

Changes

• Run watch startup initialization and the initial compile under the same build.lock.
• Register the initial watch paths while that same startup build state is active.
• Remove the now-unused initial_build state from the async watch loop.
• Keep subsequent incremental and full rebuild behavior unchanged, including clear-screen behavior and formatted completion output.
• Share successful watch compile completion handling for initial, incremental, and full watch builds.

Covered cases

This now protects the startup path where:

• rewatch watch performs initialize_build
• initial source folders are discovered and registered
• the watcher performs its initial compile
• another rewatch build is already running or starts at the same time

The existing full rebuild path remains protected by build.lock, including rebuilds triggered by config changes, rename events, and editor atomic-save behavior.