AssignmentServer now controls it's own logic (I pulled route logic from DetectionsServer and instead just reference the vars needed).
AssignmentServer no longer controls the order of assignments. The scraper fetches its list (/) then calls start (/start) on each one. It then calls finish (/finish) to retrieve results for saving.
Only session/ files are saved: botStats.json, bucketStats.json and browser-flags/ are no longer created.
Most of this was done in the process of me trying to figure out the flow... it also now separates the running from the processing of results, making it easy to move scrapers into scraper-report.
/) then calls start (/start) on each one. It then calls finish (/finish) to retrieve results for saving.scraper-report.