dos-supervise-looplisted

# dos-supervise-loop — the generic worker-population supervisor > **The init/PID-1 of a dispatch fleet.** It keeps `--target` worker > dispatch-loops alive across the lane roster: each tick it counts live lane > leases, classifies each worker's liveness, and fills the roster up to target by > launching one `/dos-dispatch-loop` per free admissible lane. The *what to do* > is a typed kernel verdict — `dos loop` emits a spawn/reap/flag plan; this skill > only carries it out. It reaps a worker ONLY when the kernel says STALLED, never > a healthy one, and it FLAGs a SPINNING worker to the operator rather than > killing it (acting on a spin is not the supervisor's job). The supervisor's whole contract is one rule the kernel owns: **the population is filled from the plan, not from a guess.** A tick is `gather evidence → ask `dos loop` → carry out spawn/reap/flag`. The four dispositions are the kernel's: 1. **SPAWN** — a free, admissible lane below target: launch one worker on it. 2. **REAP** — a STALLED lease: scavenge it so the lane is free to refill. 3. **HOLD** — an ADVANCING (or alive-counted SPINNING) worker: leave it alone. 4. **FLAG** — a SPINNING worker (advisory) or an excess over target: surface it, do not kill it. ## Inputs - `--target <N>` (default 1) — the desired live-worker population. The kernel caps the achievable population at the *admissible* count (how many roster lanes can simultaneously hold a worker given their disjointness); a `--target` above t