Slingshot

Fleet Control

Slingshot

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.

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.
No events yet.