Does Gatling reset CSV feeder state between repeated simulation runs?

Goal

Execute the same Gatling 3.x simulation repeatedly inside one Maven, SBT, or Gradle session without restarting the build tool, while keeping CSV feeder records available on every run.

Uncertainty

Gatling feeders behave as iterators: each record is consumed once per feeder instance and is not automatically restored when the simulation runs again. If the build tool retains the simulation object, later executions may see an exhausted feeder. This assumption applies to Gatling 3.x; Gatling 2.x semantics may differ.

Does Gatling reset feeder state between repeated simulation runs in the same build-tool session? Is a circular feeder required for repeatable local runs, or must the feeder instance be recreated before each invocation?