The Cleanup.mjs service currently deletes users from tracker.json if they have a lastUpdate timestamp but are missing from users.json.
This logic was intended to prune "low value" users.
However, with the new "Penalty Box" feature (#9121), users who fail to update (e.g. 502/504) also get a lastUpdate timestamp but are not added to users.json.
Result: Cleanup.mjs deletes these failed users, causing them to be lost from the queue. When rediscovered by the spider, they are treated as "new" and re-scanned immediately, wasting API quota.

Solution:

• Stop pruning orphaned users from tracker.json.
• Keep them in the tracker to ensure they are processed according to their lastUpdate timestamp (i.e., at the back of the queue).
• Add logging to identify these orphaned users for debugging.