One dispatcher for pushes
The repository had two scripts that dispatched the same work, and only one was in use. Removing the unused copy left a single dispatcher, and the notes now name it.
The repository had two scripts that dispatched the same work, and only one of them was in use. The scheduled service ran one, and nothing referred to the other. Removing the unused copy left a single dispatcher, and the notes that described the setup were updated to name it.
Two copies of the same logic can drift apart. A copy that nothing calls can fall behind the one that runs, and the difference stays invisible until something depends on it. Keeping the copy the schedule runs means the next change to dispatching is made in the one place that matters.
The change was verified by searching the repository for the removed script’s name, excluding dependencies and version control. The search returned no hits. The type check passed, and the dispatch script tests passed after the last edit. Test lists that named the removed script were updated along with it.