Fleet Control — cookies in, product ids out (per proxy)
Drop
Set the drop time and assign a product id to each instance below, then
Arm. At drop time the server detects each queue and fires issueTicket through every
instance's own proxy — each ticket's wr is handed back to its client.
Predicted drops
The list monitor watches your favorites list near the drop and flags SKUs whose
price/stock changed since the baseline — the tell that a Walmart-direct drop is imminent.
It's a prediction, not a guarantee: click Assign to all to load a SKU into every
instance, then Arm. Nothing is assigned or armed automatically.
Instances
Rows appear automatically when a fan-out client checks in — one per proxy.
A green dot means the client is currently running. Assign a product id to each.
Proxy / Instance
Session
Last check-in
Product id
Ticket
No clients connected yet — start the fan-out browsers.
Drop log
Everything the server does — arming, instance eligibility, queue detection
(probe counts, errors, what seot returned), and every issueTicket attempt with failure
bodies. Persisted on the VPS at data/droplog.jsonl; survives restarts.