Server route data cleanup

[mattrix14]

Summary

This PR cleans up the FTServer route-data contract so the emitted JSON, schema, example payloads, and generated docs are aligned and easier to reason about.

What Changed

• Reordered boatData fields into a more coherent, stable order.
• Reordered portData fields into a more coherent, stable order.
• Removed the legacy BoatDepartureDelay alias and standardized on DepartureDelay.
• Updated the JSON Schema to match the actual runtime payload more closely.
• Updated example route payloads to match the current contract and ordering.
• Regenerated schema docs from the updated schema.
• Removed stale generated doc entries for deprecated fields.
• Added/updated schema coverage for current runtime fields including:
  • MMSI
  • PositionUpdated
  • TerminalID
  • PortETA
  • PortStopTimer
  • PortArrivalTimeMinus

Why

The route payload had drifted over time:

• field ordering was inconsistent and harder to scan
• the schema no longer fully matched the live runtime payload
• generated docs were stale
• both BoatDepartureDelay and DepartureDelay existed for the same concept

This PR makes the contract cleaner and more consistent without changing the meaning of the data, aside from the intentional removal of the old BoatDepartureDelay alias.

Notes

• boatData is not just reordered: BoatDepartureDelay is removed in favor of DepartureDelay.
• portData keeps the same runtime fields, but they are now emitted in a more coherent order.
• The schema and docs now reflect the current FTServer payload rather than older historical variants.

Testing

• Verified the schema JSON parses successfully.
• Regenerated docs with npm run docs.
• Ran targeted tests:

npm test -- --runTestsByPath test/FerryTempo.test.js test/Utils.test.js

[mattrix14]

Roger that on the line count. Apologies. It should primarily be a re-ordering of the json fields, other than renaming BDD to just DD. It suggested keeping both for the time being, for the exact breaking issue you mentioned. But it will only break DD dial (if I’m not mistaken). And so few clocks are out there, that I decided to just go bold. Only you and Alex will need to update (Keith’s clock is on display downstairs, so I’ll flash as soon as the server is live).Thank you Craig!On Mar 24, 2026, at 17:04, Craig Kulfan ***@***.***> wrote: @ckulfan commented on this pull request. In data/ExampleRouteData.json:

@@ -69,7 +77,7 @@

"AtDock": null, "ScheduledDeparture": null, "LeftDock": null, - "BoatDepartureDelay": null, Just reaffirming that this will break existing clock functionality until those devices have been updated to the latest version of FTClient. —Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: ***@***.***>