Documentation

What ecluse dredger's own flags settled, carried from the command line to the sweep.

Whether the run deletes, or previews what a run that deletes would reach.

Whether the role cycles for the life of the process, or runs one cycle and exits.

The role a Dredger invocation boots under, settled from its own flags before the boot's vetting pass runs, so the pass and the runtime agree on what the process may do to a store.

The pacing, the per-cycle cap, and the shape the dredger group settled over the stores a cycle sweeps, beside the boot lines naming where each resolved bound came from.

How a run reports what it removed. A preview counts under its own arm and past the cap, so it reports the full reach a real run would have rather than stopping at the breaker.

Whether a first cycle waits for the first advisory sync. A rule set with no advisory rule never needs one, so it starts at once.

How many times a first cycle checks for the advisory sync before it starts anyway. The bound is the cycle pause, so waiting never costs more than one cycle's worth of time.

How long the first cycle waits between checks for the advisory sync.

What a one-shot run reports as its own ending, or Nothing where it ends cleanly. A run that deletes ends on the halt its cycle raised, and a preview ends on completeness alone.

The detail a halted one-shot run reports as its own non-zero ending, so a scheduler reads the outcome from the status and the reason from the same line.