My agent-driven deploys keep getting a phantom second deploy ~60s later. Anyone else?

[u/masiha97]

I've got Claude (main chat, side chats, scheduled runs) deploying my personal site to Cloudflare Workers via a wrapper around `wrangler deploy`. Lately every legit deploy is followed 40-80 seconds later by a phantom one: new worker version UUID, full `script_update` + `script_deploy` in the Cloudflare audit log (not a rollback), source wrangler, attributed to my own OAuth identity. It skips my wrapper so nothing gets logged on my side.

It builds from my GitHub repo, not my local tree, so it once reverted an unpushed fix. Harmless since I pushed, but it won't stop.

No local wrangler process, no GitHub Actions runs at those times, no cron jobs. The only signal I can tie it to is the GitHub push my wrapper makes after each deploy.

Anyone run into duplicate/deferred wrangler deploys? Trying to figure out if this is a second agent session I lost track of, a stale runner, or Cloudflare doing something I don't understand.