Plow-ridge recheck: sending someone back after the city re-buries an entrance

The re-accumulation problem

Your crew clears a property perfectly. Twenty minutes later the municipal plow roars past and throws a wall of hard-packed snow across the entrance you just opened. The property is "done" on paper and buried in reality. A fixed route list has no way to express "go back to this one later."

Snowmass does.

How the recheck works

This is an operator-triggered flow with automatic re-dispatch:

1. The operator flags it. When a crew finishes a property but the road plow has re-buried the entrance, they mark it "cleared with issues" instead of simply done.
2. Snowmass holds a recheck. The property isn't just reopened immediately — the engine schedules a recheck and waits out an org-set cooldown (default 45 minutes), so you're not sending someone back before the plow is even finished.
3. The swarm re-queues it. After the cooldown, the property flows back into the open pool and the swarm sends someone to reclear it — tracking the attempt count and the plow-lag each time.

An honest description

The trigger is human — an operator has to mark the plow-ridge condition; Snowmass does not automatically detect that a city plow came by. What's automatic is everything after: the cooldown, the re-queue, and the re-dispatch. That division is deliberate — the person on the property is the reliable sensor, and the engine handles the follow-through.

Why it matters

• The re-burial gets fixed — a problem static route lists literally cannot represent.
• No premature return trips — the cooldown avoids reclearing before the plow is done.
• A paper trail — attempt counts and plow-lag show how often a property re-accumulates, useful for talking to the municipality and to customers.