Correct Goal 7 documentation for kDisco-based speed control

[Copilot]

Goal 7 in LONG_TERM_GOALS.md described simulation speed control as a native capability of the simulation engine. This updates the goal text to reflect the current architecture and marks Goal 7 as completed.

• Goal 7 correction

  • Replaced the misleading claim that the underlying simulation library already provides speed control.
  • Clarified that the simulation-library interface (historically jDisco, now kDisco/KMP) runs in pure simulation time and has no native wall-clock synchronization.

• Architecture alignment

  • Documented the current two-mechanism reality explicitly.
  • Clarified that the production speed-control path for ShuntingLoop uses RealTimeSynch inside sim/ShuntingLoop.kt.
  • Clarified that SimulationRunner.throttle() remains the external extension point for wall-clock throttling outside the simulation engine.

• Goal status

  • Added **Status:** ✅ COMPLETE to Goal 7.

• PR scope cleanup

  • Reverted an unrelated change in core/src/jvmTest/kotlin/cz/vutbr/fit/interlockSim/sim/TrainPathInteractionTest.kt so this stacked PR stays focused on the Goal 7 documentation update.

**Implementation Notes:**
- The simulation library interface used by the model (historically jDisco, now kDisco/KMP) runs in pure simulation time and has no native wall-clock speed control or synchronization.
- For the current `ShuntingLoop` production path, wall-clock pacing is implemented inside `sim/ShuntingLoop.kt` via `RealTimeSynch`.
- `SimulationRunner.throttle()` remains the external extension point for wall-clock throttling around simulation execution in callers that choose to use it.

[Copilot]

Pull request overview

Updates Goal 7 (“Simulation Speed Control”) documentation in LONG_TERM_GOALS.md to correct the description of how speed control is intended to work, clarifying that the simulation engine runs in pure simulation time and that wall-clock pacing is applied externally.

Changes:

• Replaced the prior claim that the simulation library “already supports speed control” with an explanation of pure simulation-time execution.
• Documented wall-clock throttling via SimulationRunner around SimulationContext.run() as the intended speed-control mechanism.

[bedaHovorka]

add notice about that is Goal 7 completed

[Copilot]

add notice about that is Goal 7 completed

Added in 4732543 — Goal 7 in LONG_TERM_GOALS.md now includes **Status:** ✅ COMPLETE.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud