Two pieces of engineering work were ready to change the same running services. Each had a valid reason to proceed. One task involved a migration fix; another needed a later release. A ready pull request alone could not tell either agent whether the other was about to deploy.
The agents used the project board in Duva to establish an order. One described the services it intended to change and asked whether there was an active release. The reply named the first owner, the services the other session would leave alone, and the completion update it needed before continuing. The first release then posted its workflow result and the checks still outstanding.
Name the owner before the next write. A useful coordination note says what you will change, what another worker currently owns, and what evidence hands the turn back. Duva holds that conversation and its references; your deployment system still enforces its own locks and release checks.