@7365admin1/core 3.80.0 → 3.82.0

package/CHANGELOG.md

@@ -1,5 +1,72 @@
 # @iservice365/core
 
+## 3.82.0
+
+### Minor Changes
+
+- dbc439a: 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.
+
+## 3.81.0
+
+### Minor Changes
+
+- fde0167: Cleaning robot: robot cloud connector, and stop projecting robot credentials
+
+  Adds the signed client for the cleaning-robot cloud (`robot-cloud.util.ts`,
+  `robot-cloud.service.ts`): request signing, the status vocabulary, the
+  pixel/metre transform and the area colour conversions, plus the nine
+  request/response endpoints. Credentials are passed in by the caller and are
+  never read from the environment, logged, or placed in a request body.
+
+  Also fixes a credential disclosure in the existing robot listing: `getRobots`
+  projected `appKey` and `appToken` — the pair that signs every command sent to
+  that estate's robots — into the response, so anyone holding `see-all-robots`
+  received them. They are no longer returned.
+
+  Fixes `POST /robots`, which had never worked: the service assigned an ObjectId
+  where the model's schema wanted a string, so every create ended in
+  `400 "createdBy" must be a string` and no robot could be registered at all.
+
+  Adds the server-side enforcement of the five robot permissions, which have
+  existed in the client catalogue but were never checked by the API. `"*"` allows
+  everything; an empty list allows everything only on a `type: "admin"` role (the
+  Seven365 staff role is seeded with `[]`, so enforcing it would refuse the
+  platform owner); a non-empty list is enforced exactly.
+
+  Adds `robotSn` to the robot record (optional, discovered from `get-robot-list`
+  when absent) and `robot-fleet.service.ts`, which bridges a stored robot to the
+  vendor cloud: live state, maps, map image URLs minted at use, and dispatch.
+
+  Adds a table of which application may set up and monitor which robot type, so
+  cleaning robots and security robots share one module while each app sees only
+  its own.
+
+  Adds an optional `type` ("cleaning" | "security") to the robot record with an
+  optional filter, so both device classes share one module and one collection
+  while each app lists only its own. Existing rows are untouched and an
+  unfiltered query behaves exactly as before.
+
 ## 3.80.0
 
 ### Minor Changes