fleet-sim-change

To keep fleet-sim code and documentation synchronized, coordinate changes across src/fleet-sim, release wiring, and simulator-owned docs as a single subsystem to prevent drift and misalignment.

Fleet-sim change management is a trigger-driven consolidation process that enforces running agent reports and simulator validation to ensure surface stability and alignment with maintained contracts before release.

Validate fleet-sim updates by running the agent-report workflow to verify routing, enforce simulator validation checks, and surface stability issues before proceeding with the release wiring.

Yes, you must update website and internal docs together when changing fleet-sim, because the process covers both documentation surfaces that must stay in sync with the code to prevent misalignment.

The best way to prevent drift when updating simulator release wiring is applying inline guidance that treats code, APIs, and deployment workflows as a single subsystem with automated validation gating.