@7365admin1/core 3.79.1-staging.341 → 3.79.1-staging.343

package/.changeset/robot-fleet-endpoints.md

@@ -0,0 +1,26 @@
+---
+"@7365admin1/core": minor
+---
+
+Cleaning robot: fleet endpoints, and the lift contract
+
+Adds `robot-fleet.controller.ts` — live state, floors and areas, map image URLs,
+the cleaning schedule, and one command endpoint covering full, area, spot and
+return. Every handler loads the robot first and authorises the estate named on
+the STORED record, never one named in the request, so a robot cannot be reached
+by quoting its id; credentials are read server-side and never enter a response.
+
+Adds `parseRobotCommand`, pure, so the command rules can be asserted without a
+robot. Fields are refused on commands that do not use them rather than ignored —
+silently dropping a spot polygon from an area command would clean the wrong
+thing and report success.
+
+Adds `getRobotById` and `setRobotSn` to the robot repository. `setRobotSn` only
+ever fills a blank serial, so a later discovery cannot re-point a nickname at a
+different machine.
+
+Adds `lift-contract.util.ts` — the lift vocabulary, with field names and enum
+values taken verbatim from Open-RMF's `rmf_lift_msgs`, plus an in-memory lift
+simulator. No Modbus and no register numbers: the Inovance open-protocol
+register map has not been supplied, so the driver sits behind an interface and
+the queue and session logic can be built and tested against the simulator first.

package/.changeset/robot-multi-brand.md

@@ -0,0 +1,28 @@
+---
+"@7365admin1/core": minor
+---
+
+Robot fleet: a vendor-neutral adapter contract, so any brand can be integrated
+
+Adds `robot-adapter.util.ts` — the capability model, the tier calculation and the
+brand registry — and `ounitech.adapter.ts`, the first brand behind it.
+
+The capability names and tier requirements are Open-RMF's, verbatim from the
+Fleet Adapters table: Full Control, Traffic Light, Read Only, No Interface. That
+means a brand's datasheet reads straight into a tier, and a vendor conversation
+gets a name ("your API is Read Only, we need Traffic Light") rather than a list
+of features we would like.
+
+Screens ask the adapter what the robot can do rather than assuming, so a brand
+that cannot pause a process is never shown a Pause button that would fail.
+`commandSupported` refuses an unsupported command at the service too, because a
+command can also arrive from an API caller or a scheduled job.
+
+`uncontrollableFleetWarning` enforces Open-RMF's rule that a shared space may
+contain at most one fleet it cannot control — a read-only cleaning fleet plus a
+security robot with no interface is the exact pair the book says makes deadlock
+avoidance nearly impossible.
+
+Adds `brand` to the robot record so a row says whose protocol it answers.
+Defaulted to `ounitech` because every existing row is one; a second brand makes
+it a required choice rather than a fallback.