@deeptrekker/api-domain 1.0.38-collisionavoidanceprototype.0 → 1.0.38-collisionavoidanceprototype.1

package/dist/constants/schema/schema.json

@@ -780,6 +780,10 @@
                     "description": "\"unknown\" | \"outside\" | \"inside\"",
                     "type": "string"
                 },
+                "forceUnlock": {
+                    "description": "Write-only. Set true to force any axis currently latched INSIDE (holding that state through stale/unusable sensor data) back to unknown, so the next sensor reading re-determines its real state. Has no effect on an axis that is not latched. Never reported back by the backend.",
+                    "type": "boolean"
+                },
                 "fwdError": {
                     "type": "string"
                 },

package/dist/constants/versions/index.d.ts

@@ -1 +1 @@
-export declare const API_VERSION = "1.0.38-collisionavoidanceprototype.0";
+export declare const API_VERSION = "1.0.38-collisionavoidanceprototype.1";

package/dist/constants/versions/index.js

@@ -2,4 +2,4 @@
 Object.defineProperty(exports, "__esModule", { value: true });
 exports.API_VERSION = void 0;
 /* AUTO GENERATED FILE */
-exports.API_VERSION = "1.0.38-collisionavoidanceprototype.0";
+exports.API_VERSION = "1.0.38-collisionavoidanceprototype.1";

package/dist/types/devices/vehicles/rovDrive/index.d.ts

@@ -61,7 +61,22 @@ export type CollisionAvoidance = {
     /** "unknown" | "outside" | "inside" */
     fwdState?: string;
     fwdError?: string;
+    /**
+     * True when the axis reports "inside" because it latched - it saw an obstacle in the
+     * keep-out zone and has held that state through sensor data it cannot use - rather
+     * than because it can currently see the obstacle. Only a latched axis responds to
+     * forceUnlock.
+     */
+    fwdLatched?: boolean;
     /** "unknown" | "outside" | "inside" */
     downState?: string;
     downError?: string;
+    downLatched?: boolean;
+    /**
+     * Write-only. Set true to force any axis currently latched INSIDE (holding that
+     * state through stale/unusable sensor data) back to unknown, so the next sensor
+     * reading re-determines its real state. Has no effect on an axis that is not
+     * latched. Never reported back by the backend.
+     */
+    forceUnlock?: boolean;
 };

package/package.json

@@ -1,6 +1,6 @@
 {
     "name": "@deeptrekker/api-domain",
-    "version": "1.0.38-collisionavoidanceprototype.0",
+    "version": "1.0.38-collisionavoidanceprototype.1",
     "description": "A business domain of types and schemas that the Deep Trekker topside communicates with via an API.",
     "main": "dist/index.js",
     "engines": {