Clustered clone timestamps point to browser automation

When code_sign_clone folders pile up, run ls -lat on the directory and look at creation times. Dozens created within minutes (about 32 in 10 minutes here) suggest a script repeatedly launching and killing Chrome, such as Selenium or Puppeteer, not normal use. An in-browser extension does not launch new Chrome processes, so it is an unlikely cause. To stop recurrence, shut automated browsers down cleanly; the specific tool was not confirmed in this case.