@fleetless/contracts 1.0.5 → 1.0.6

package/artifacts/schema/job-response.schema.json

@@ -11,7 +11,7 @@
               "type": "string",
               "format": "uuid",
               "pattern": "^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$",
-              "description": "The job's id, minted by the cloud when the invocation is accepted. Informative: state is observed by slug, and this id is what a cancel names when a caller wants to stop one specific job rather than whatever is running."
+              "description": "The job's id, minted by the cloud when the invocation is accepted. Informative — state is observed by slug; a cancel names this id to stop one specific job rather than whatever is running."
             },
             "robot_id": {
               "type": "string",
@@ -35,13 +35,13 @@
                 "cancelled",
                 "lost"
               ],
-              "description": "Where the job stands: `running`, `succeeded`, `failed`, `cancelled` or `lost`. `lost` is a real outcome — the bridge restarted mid-job and the result is gone — and is said out loud rather than left reading `running` because nobody contradicted it."
+              "description": "Where the job stands: `running`, `succeeded`, `failed`, `cancelled` or `lost`. `lost` is a real outcome — the bridge restarted mid-job and the result is gone — stated rather than left reading `running` by default."
             },
             "started_at": {
               "type": "string",
               "format": "date-time",
               "pattern": "^(?:(?:\\d\\d[2468][048]|\\d\\d[13579][26]|\\d\\d0[48]|[02468][048]00|[13579][26]00)-02-29|\\d{4}-(?:(?:0[13578]|1[02])-(?:0[1-9]|[12]\\d|3[01])|(?:0[469]|11)-(?:0[1-9]|[12]\\d|30)|(?:02)-(?:0[1-9]|1\\d|2[0-8])))T(?:(?:[01]\\d|2[0-3]):[0-5]\\d(?::[0-5]\\d(?:\\.\\d+)?)?(?:Z))$",
-              "description": "When the cloud minted this job, as an ISO 8601 timestamp. For a job adopted from a reconnecting bridge it is **adoption time**, not the real start, because the cloud never minted it and has no honest alternative."
+              "description": "When the cloud minted this job, as an ISO 8601 timestamp. For a job adopted from a reconnecting bridge, this is **adoption time**, not the real start — the cloud never minted it."
             },
             "updated_at": {
               "type": "string",

package/artifacts/schema/job-run-list-response.schema.json

@@ -11,7 +11,7 @@
             "type": "string",
             "format": "uuid",
             "pattern": "^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$",
-            "description": "The run's id, which is the same id the invocation was answered with — so a caller that kept a job id can find its durable record here later."
+            "description": "The run's id — the same id the invocation was answered with, so a caller that kept a job id can find its durable record here later."
           },
           "robot_id": {
             "type": "string",
@@ -128,7 +128,7 @@
                   "app_user",
                   "server_key"
                 ],
-                "description": "What the caller was acting as: a `developer` in the console, an `app_user` of one app, or a `server_key` used by server-side code. A bridge invokes nothing, so it is deliberately not a case here. `end_user` appears only on runs recorded before app users replaced the organisation-wide user pool — it is kept so a history page can still render them, and nothing writes it any more."
+                "description": "What the caller was acting as: a `developer` in the console, an `app_user` of one app, or a `server_key` used by server-side code. A bridge invokes nothing, so it is deliberately not a case here. `end_user` appears only on runs recorded before app users replaced the organisation-wide user pool — kept so old runs still render; nothing writes it now."
               },
               "id": {
                 "type": "string",

package/artifacts/schema/job-run.schema.json

@@ -6,7 +6,7 @@
       "type": "string",
       "format": "uuid",
       "pattern": "^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$",
-      "description": "The run's id, which is the same id the invocation was answered with — so a caller that kept a job id can find its durable record here later."
+      "description": "The run's id — the same id the invocation was answered with, so a caller that kept a job id can find its durable record here later."
     },
     "robot_id": {
       "type": "string",
@@ -123,7 +123,7 @@
             "app_user",
             "server_key"
           ],
-          "description": "What the caller was acting as: a `developer` in the console, an `app_user` of one app, or a `server_key` used by server-side code. A bridge invokes nothing, so it is deliberately not a case here. `end_user` appears only on runs recorded before app users replaced the organisation-wide user pool — it is kept so a history page can still render them, and nothing writes it any more."
+          "description": "What the caller was acting as: a `developer` in the console, an `app_user` of one app, or a `server_key` used by server-side code. A bridge invokes nothing, so it is deliberately not a case here. `end_user` appears only on runs recorded before app users replaced the organisation-wide user pool — kept so old runs still render; nothing writes it now."
         },
         "id": {
           "type": "string",

package/artifacts/schema/job.schema.json

@@ -6,7 +6,7 @@
       "type": "string",
       "format": "uuid",
       "pattern": "^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$",
-      "description": "The job's id, minted by the cloud when the invocation is accepted. Informative: state is observed by slug, and this id is what a cancel names when a caller wants to stop one specific job rather than whatever is running."
+      "description": "The job's id, minted by the cloud when the invocation is accepted. Informative — state is observed by slug; a cancel names this id to stop one specific job rather than whatever is running."
     },
     "robot_id": {
       "type": "string",
@@ -30,13 +30,13 @@
         "cancelled",
         "lost"
       ],
-      "description": "Where the job stands: `running`, `succeeded`, `failed`, `cancelled` or `lost`. `lost` is a real outcome — the bridge restarted mid-job and the result is gone — and is said out loud rather than left reading `running` because nobody contradicted it."
+      "description": "Where the job stands: `running`, `succeeded`, `failed`, `cancelled` or `lost`. `lost` is a real outcome — the bridge restarted mid-job and the result is gone — stated rather than left reading `running` by default."
     },
     "started_at": {
       "type": "string",
       "format": "date-time",
       "pattern": "^(?:(?:\\d\\d[2468][048]|\\d\\d[13579][26]|\\d\\d0[48]|[02468][048]00|[13579][26]00)-02-29|\\d{4}-(?:(?:0[13578]|1[02])-(?:0[1-9]|[12]\\d|3[01])|(?:0[469]|11)-(?:0[1-9]|[12]\\d|30)|(?:02)-(?:0[1-9]|1\\d|2[0-8])))T(?:(?:[01]\\d|2[0-3]):[0-5]\\d(?::[0-5]\\d(?:\\.\\d+)?)?(?:Z))$",
-      "description": "When the cloud minted this job, as an ISO 8601 timestamp. For a job adopted from a reconnecting bridge it is **adoption time**, not the real start, because the cloud never minted it and has no honest alternative."
+      "description": "When the cloud minted this job, as an ISO 8601 timestamp. For a job adopted from a reconnecting bridge, this is **adoption time**, not the real start — the cloud never minted it."
     },
     "updated_at": {
       "type": "string",

package/artifacts/schema/mcp-consent-grant-list-response.schema.json

@@ -20,12 +20,12 @@
                 "type": "null"
               }
             ],
-            "description": "What the client calls itself, or `null` when its registration is gone and there is no longer anything to have named. **Unverified** — see `client_name_verified`."
+            "description": "What the client calls itself, or `null` once its registration is gone. **Unverified** — see `client_name_verified`."
           },
           "client_name_verified": {
             "type": "boolean",
             "const": false,
-            "description": "Always `false`. The client registered itself without authentication and chose this name about itself, so it must be rendered as a claim and never as an identity. There is no verified case, which is why this is a literal and not a boolean: a `true` branch would be dead code that looked like a safeguard."
+            "description": "Always `false`. The client registered itself without authentication and named itself, so it must be rendered as a claim and never as an identity. There is no verified case, which is why this is a literal and not a boolean: a `true` branch would be dead code that looked like a safeguard."
           },
           "granted_at": {
             "type": "string",

package/artifacts/schema/mcp-consent-grant.schema.json

@@ -15,12 +15,12 @@
           "type": "null"
         }
       ],
-      "description": "What the client calls itself, or `null` when its registration is gone and there is no longer anything to have named. **Unverified** — see `client_name_verified`."
+      "description": "What the client calls itself, or `null` once its registration is gone. **Unverified** — see `client_name_verified`."
     },
     "client_name_verified": {
       "type": "boolean",
       "const": false,
-      "description": "Always `false`. The client registered itself without authentication and chose this name about itself, so it must be rendered as a claim and never as an identity. There is no verified case, which is why this is a literal and not a boolean: a `true` branch would be dead code that looked like a safeguard."
+      "description": "Always `false`. The client registered itself without authentication and named itself, so it must be rendered as a claim and never as an identity. There is no verified case, which is why this is a literal and not a boolean: a `true` branch would be dead code that looked like a safeguard."
     },
     "granted_at": {
       "type": "string",

package/artifacts/schema/oauth-authorize-query.schema.json

@@ -20,7 +20,7 @@
     "code_challenge": {
       "type": "string",
       "minLength": 1,
-      "description": "The PKCE challenge; the verifier is presented at the token endpoint. Only non-emptiness is checked here — length and alphabet are not — since the verifier is what actually has to match."
+      "description": "The PKCE challenge; the verifier is presented at the token endpoint. Only non-emptiness is checked here — length and alphabet are not — since the verifier is what has to match."
     },
     "code_challenge_method": {
       "type": "string",

package/artifacts/schema/oauth-token-request.schema.json

@@ -31,7 +31,7 @@
       "description": "The PKCE verifier whose `S256` hash was sent as the challenge at the authorize step. Between `43` and `128` unreserved characters, per RFC 7636 §4.1 — it is compared rather than parsed, so a length nobody checks is a length an attacker chooses. PKCE is mandatory for every client under OAuth 2.1."
     },
     "resource": {
-      "description": "The resource the token is being requested for, per RFC 8707. It must match the audience the code was authorized for, or the answer is `invalid_target`; omitted, the code's own audience stands. It becomes the token's `aud`, and a resource refuses a token whose audience names something else — which is what keeps a token minted for one app out of another app's endpoint.",
+      "description": "The resource the token is requested for, per RFC 8707. It must match the audience the code was authorized for, or the answer is `invalid_target`; omitted, the code's own audience stands. It becomes the token's `aud`, and a resource refuses a token whose audience names something else — which is what keeps a token minted for one app out of another app's endpoint.",
       "type": "string",
       "format": "uri"
     }

package/artifacts/schema/patch-org-response.schema.json

@@ -30,7 +30,7 @@
         "created_at"
       ],
       "additionalProperties": false,
-      "description": "The organisation as it now stands, after the patch was applied. The whole resource comes back, not only the fields that changed."
+      "description": "The organisation as it now stands, after the patch. The whole resource comes back, not only the changed fields."
     }
   },
   "required": [

package/artifacts/schema/patch-robot-response.schema.json

@@ -30,7 +30,7 @@
         "created_at"
       ],
       "additionalProperties": false,
-      "description": "The robot as it now stands, after the patch was applied. The whole resource comes back, not only the fields that changed."
+      "description": "The robot as it now stands, after the patch. The whole resource comes back, not only the changed fields."
     }
   },
   "required": [

package/artifacts/schema/robot-config-doc.schema.json

@@ -106,7 +106,7 @@
             ]
           },
           "description": {
-            "description": "Prose about what this value is, for whoever meets it in the console later. It changes nothing the robot does, so a publish that touches only it pushes no configuration at all — but it is carried verbatim into `robot_describe`, where a model that has never seen this robot reads it. The datapoint is offered whenever the role grants it; without one it is offered with `description: null` and the model has less to go on, as for actions, services, publishers and cameras. Omission is the only way to say nothing; an empty string is refused, here and on all five.",
+            "description": "Prose about what this value is, for whoever meets it in the console. It changes nothing the robot does, so a publish that touches only it pushes no configuration at all — but it is carried verbatim into `robot_describe`, where a model that has never seen this robot reads it. The datapoint is offered whenever the role grants it; without one it is offered with `description: null` and the model has less to go on, as for actions, services, publishers and cameras. Omission is the only way to say nothing; an empty string is refused, here and on all five.",
             "examples": [
               "What this value is, for whoever meets it in the console."
             ],

package/artifacts/schema/robot-jobs-response.schema.json

@@ -11,7 +11,7 @@
             "type": "string",
             "format": "uuid",
             "pattern": "^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$",
-            "description": "The job's id, minted by the cloud when the invocation is accepted. Informative: state is observed by slug, and this id is what a cancel names when a caller wants to stop one specific job rather than whatever is running."
+            "description": "The job's id, minted by the cloud when the invocation is accepted. Informative — state is observed by slug; a cancel names this id to stop one specific job rather than whatever is running."
           },
           "robot_id": {
             "type": "string",
@@ -35,13 +35,13 @@
               "cancelled",
               "lost"
             ],
-            "description": "Where the job stands: `running`, `succeeded`, `failed`, `cancelled` or `lost`. `lost` is a real outcome — the bridge restarted mid-job and the result is gone — and is said out loud rather than left reading `running` because nobody contradicted it."
+            "description": "Where the job stands: `running`, `succeeded`, `failed`, `cancelled` or `lost`. `lost` is a real outcome — the bridge restarted mid-job and the result is gone — stated rather than left reading `running` by default."
           },
           "started_at": {
             "type": "string",
             "format": "date-time",
             "pattern": "^(?:(?:\\d\\d[2468][048]|\\d\\d[13579][26]|\\d\\d0[48]|[02468][048]00|[13579][26]00)-02-29|\\d{4}-(?:(?:0[13578]|1[02])-(?:0[1-9]|[12]\\d|3[01])|(?:0[469]|11)-(?:0[1-9]|[12]\\d|30)|(?:02)-(?:0[1-9]|1\\d|2[0-8])))T(?:(?:[01]\\d|2[0-3]):[0-5]\\d(?::[0-5]\\d(?:\\.\\d+)?)?(?:Z))$",
-            "description": "When the cloud minted this job, as an ISO 8601 timestamp. For a job adopted from a reconnecting bridge it is **adoption time**, not the real start, because the cloud never minted it and has no honest alternative."
+            "description": "When the cloud minted this job, as an ISO 8601 timestamp. For a job adopted from a reconnecting bridge, this is **adoption time**, not the real start — the cloud never minted it."
           },
           "updated_at": {
             "type": "string",

package/artifacts/schema/role-list-response.schema.json

@@ -27,7 +27,7 @@
           },
           "builtin": {
             "type": "boolean",
-            "description": "`true` for the two roles every app starts with. Their **rights may be re-scoped** exactly like a custom role's, through `PUT /api/apps/:id/roles/:roleId/permissions` — the flag exists so the console can explain where they came from, not to protect them. It does not make them renamable or deletable, because no route renames or deletes any role."
+            "description": "`true` for the two roles every app starts with. Their **rights may be re-scoped** exactly like a custom role's, through `PUT /api/apps/:id/roles/:roleId/permissions` — the flag exists so the console can explain where they came from, not to protect them. It does not make them renamable or deletable — no route does that for any role."
           }
         },
         "required": [

package/artifacts/schema/role.schema.json

@@ -22,7 +22,7 @@
     },
     "builtin": {
       "type": "boolean",
-      "description": "`true` for the two roles every app starts with. Their **rights may be re-scoped** exactly like a custom role's, through `PUT /api/apps/:id/roles/:roleId/permissions` — the flag exists so the console can explain where they came from, not to protect them. It does not make them renamable or deletable, because no route renames or deletes any role."
+      "description": "`true` for the two roles every app starts with. Their **rights may be re-scoped** exactly like a custom role's, through `PUT /api/apps/:id/roles/:roleId/permissions` — the flag exists so the console can explain where they came from, not to protect them. It does not make them renamable or deletable — no route does that for any role."
     }
   },
   "required": [

package/artifacts/schema/server-key-list-response.schema.json

@@ -11,7 +11,7 @@
             "type": "string",
             "format": "uuid",
             "pattern": "^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$",
-            "description": "The key row, and what the rotate and delete routes address. It is not the key: the secret itself is never carried by this shape."
+            "description": "The key row, and what the rotate and delete routes address. It is not the key: this shape never carries the secret."
           },
           "app_id": {
             "type": "string",
@@ -54,7 +54,7 @@
         ],
         "additionalProperties": false
       },
-      "description": "The app's server keys as metadata, oldest first by `created_at`. The raw secret is not here and never will be: it exists once, in the answer to the request that created or rotated the key."
+      "description": "The app's server keys as metadata, oldest first by `created_at`. The raw secret is not here and never will be: it exists once, in the response that created or rotated the key."
     }
   },
   "required": [

package/artifacts/schema/server-key.schema.json

@@ -6,7 +6,7 @@
       "type": "string",
       "format": "uuid",
       "pattern": "^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$",
-      "description": "The key row, and what the rotate and delete routes address. It is not the key: the secret itself is never carried by this shape."
+      "description": "The key row, and what the rotate and delete routes address. It is not the key: this shape never carries the secret."
     },
     "app_id": {
       "type": "string",

package/artifacts/schema/service-call-response.schema.json

@@ -3,7 +3,7 @@
   "type": "object",
   "properties": {
     "result": {
-      "description": "What the service returned, shaped by the ROS service itself. A service call is awaited to completion, so there is no job to observe afterwards and no id to hold on to."
+      "description": "What the service returned, shaped by the ROS service. A service call is awaited to completion, so there is no job to observe afterwards and no id to hold on to."
     }
   },
   "required": [

package/artifacts/schema/sign-up-response.schema.json

@@ -44,7 +44,7 @@
           "type": "string",
           "format": "uuid",
           "pattern": "^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$",
-          "description": "The organisation this person belongs to. Every developer route is already scoped to the caller's org, so this confirms what a client is looking at rather than being a filter it applies."
+          "description": "The organisation this person belongs to. Every developer route is already scoped to the caller's org, so this confirms what a client is looking at, not a filter it applies."
         },
         "email": {
           "type": "string",
@@ -71,7 +71,7 @@
             "owner",
             "developer"
           ],
-          "description": "The console powers this person holds. **Required** — every Fleetless user is a member of the team and has a tier; the optional version of this field existed only while the org also held people with no console powers to grade, and that pool is gone."
+          "description": "The console powers this person holds. **Required** — every Fleetless user has a tier; it was optional only while the org also held people with no console powers to grade, and that pool is gone."
         },
         "created_at": {
           "type": "string",

package/artifacts/schema/urdf-completeness.schema.json

@@ -21,7 +21,7 @@
             "type": "string",
             "minLength": 1,
             "maxLength": 500,
-            "description": "The reference, verbatim, that no stored asset answers — a `package://` URI the workspace does not hold, or an absolute or bare relative path nothing will ever fetch. A developer whose URDF names one of the latter is entitled to be told so."
+            "description": "The reference, verbatim, that no stored asset answers — a `package://` URI the workspace does not hold, or an absolute or bare relative path nothing will ever fetch."
           },
           "element": {
             "type": "string",
@@ -38,7 +38,7 @@
         ],
         "additionalProperties": false
       },
-      "description": "The references nothing in the store answers, each with the element that asked for it. A bare count is a dead end that sends a developer hunting through a workspace by hand; the references are what they can act on, so the references travel."
+      "description": "The references nothing in the store answers, each with the element that asked for it. A bare count would send a developer hunting through the workspace by hand; the references are what they can act on."
     }
   },
   "required": [

package/artifacts/schema-outgoing/bridge-asset-progress.schema.json

@@ -59,7 +59,7 @@
                     "type": "integer",
                     "exclusiveMinimum": 0,
                     "maximum": 9007199254740991,
-                    "description": "How large the refused file actually is, in bytes. With `limit_bytes` beside it a developer can tell whether to shrink the mesh or raise the limit; \"too large\" alone answers neither."
+                    "description": "How large the refused file is, in bytes. With `limit_bytes` beside it a developer can tell whether to shrink the mesh or raise the limit; \"too large\" alone answers neither."
                   }
                 },
                 "required": [

package/dist/alerts.d.ts

@@ -1,24 +1,22 @@
 // SPDX-License-Identifier: Apache-2.0
 import { z } from 'zod';
-/**
 /**
  * Datapoint alerts and per-datapoint chart display config.
  *
- * An alert is a **state machine** (`ok ⇄ firing`), not a fire-once event. The
+ * An alert is a **state machine** (`ok ⇄ firing`), not a fire-once event: the
  * definition and the runtime state (`state`, `state_since`, `last_value`) are
- * read together, and the cloud evaluates the alert at ingest.
+ * read together, and the cloud evaluates it at ingest.
  *
  * **The definitions live in the configuration document.** The alert definition
  * is `config.ts`'s `datapointAlert`, nested under the datapoint it watches; the
- * chart bounds are `datapointChart`. They therefore take effect on publish
- * rather than immediately, and in exchange every change to them is versioned,
- * comparable and revertible. The runtime state stays in the database: it has no
- * business in a versioned document.
+ * chart bounds are `datapointChart`. They take effect on publish, not
+ * immediately — in exchange, every change is versioned, comparable, revertible.
+ * The runtime state stays in the database: it has no business in a versioned
+ * document.
  *
  * **What is here is the read surface.** `GET /api/robots/:id/alerts` and
- * `GET /api/org/alerts` answer with the definition joined to its state, and the
- * shapes below are what they answer with. No alert sends mail, so nothing here
- * describes one.
+ * `GET /api/org/alerts` answer with the definition joined to its state — the
+ * shapes below. No alert sends mail, so nothing here describes one.
  */
 /**
  * `above`/`below` compare the numeric sample value (already scale/offset
@@ -27,11 +25,11 @@ import { z } from 'zod';
  * threshold itself: `above` resolves at `value ≤ threshold −
  * resolve_hysteresis`, mirrored for `below`. Defaulted rather than left
  * `optional` so a parsed entity never makes a consumer re-derive "absent
- * means 0" — the cloud always sends an explicit resolve point, and every
- * reader gets the same number whether it was sent or not. `equals` compares
- * the raw value for equality — the shape for boolean/string datapoints a
- * threshold cannot describe ("Hindernis erkannt" = `equals true`) — and
- * carries no hysteresis, because equality has no direction to relax.
+ * means 0" — the cloud always sends an explicit resolve point. `equals`
+ * compares the raw value for equality — the shape for boolean/string
+ * datapoints a threshold cannot describe (an obstacle-detected flag as
+ * `equals true`) — and carries no hysteresis: equality has no direction to
+ * relax.
  *
  * A discriminated union on `kind` rather than one object with optional
  * fields: an `equals` alert carrying a stray `threshold` would otherwise
@@ -101,8 +99,8 @@ export type AlertState = z.infer<typeof alertState>;
  * cloud joins the two per request (`routes/alerts.ts`'s `toWire`).
  *
  * **There are no mail settings here.** The configuration format has no mail
- * fields, so no alert can be configured to send one, and a shape describing
- * recipients would describe a delivery path that does not exist.
+ * fields, so no alert can send one, and a shape describing recipients would
+ * describe a delivery path that does not exist.
  */
 export declare const datapointAlertRow: z.ZodObject<{
     id: z.ZodUUID;

package/dist/alerts.js

@@ -1,25 +1,23 @@
 // SPDX-License-Identifier: Apache-2.0
 import { z } from 'zod';
 import { slug } from './common.js';
-/**
 /**
  * Datapoint alerts and per-datapoint chart display config.
  *
- * An alert is a **state machine** (`ok ⇄ firing`), not a fire-once event. The
+ * An alert is a **state machine** (`ok ⇄ firing`), not a fire-once event: the
  * definition and the runtime state (`state`, `state_since`, `last_value`) are
- * read together, and the cloud evaluates the alert at ingest.
+ * read together, and the cloud evaluates it at ingest.
  *
  * **The definitions live in the configuration document.** The alert definition
  * is `config.ts`'s `datapointAlert`, nested under the datapoint it watches; the
- * chart bounds are `datapointChart`. They therefore take effect on publish
- * rather than immediately, and in exchange every change to them is versioned,
- * comparable and revertible. The runtime state stays in the database: it has no
- * business in a versioned document.
+ * chart bounds are `datapointChart`. They take effect on publish, not
+ * immediately — in exchange, every change is versioned, comparable, revertible.
+ * The runtime state stays in the database: it has no business in a versioned
+ * document.
  *
  * **What is here is the read surface.** `GET /api/robots/:id/alerts` and
- * `GET /api/org/alerts` answer with the definition joined to its state, and the
- * shapes below are what they answer with. No alert sends mail, so nothing here
- * describes one.
+ * `GET /api/org/alerts` answer with the definition joined to its state — the
+ * shapes below. No alert sends mail, so nothing here describes one.
  */
 /**
  * `above`/`below` compare the numeric sample value (already scale/offset
@@ -28,11 +26,11 @@ import { slug } from './common.js';
  * threshold itself: `above` resolves at `value ≤ threshold −
  * resolve_hysteresis`, mirrored for `below`. Defaulted rather than left
  * `optional` so a parsed entity never makes a consumer re-derive "absent
- * means 0" — the cloud always sends an explicit resolve point, and every
- * reader gets the same number whether it was sent or not. `equals` compares
- * the raw value for equality — the shape for boolean/string datapoints a
- * threshold cannot describe ("Hindernis erkannt" = `equals true`) — and
- * carries no hysteresis, because equality has no direction to relax.
+ * means 0" — the cloud always sends an explicit resolve point. `equals`
+ * compares the raw value for equality — the shape for boolean/string
+ * datapoints a threshold cannot describe (an obstacle-detected flag as
+ * `equals true`) — and carries no hysteresis: equality has no direction to
+ * relax.
  *
  * A discriminated union on `kind` rather than one object with optional
  * fields: an `equals` alert carrying a stray `threshold` would otherwise
@@ -98,8 +96,8 @@ export const alertState = z.enum(['ok', 'firing']);
  * cloud joins the two per request (`routes/alerts.ts`'s `toWire`).
  *
  * **There are no mail settings here.** The configuration format has no mail
- * fields, so no alert can be configured to send one, and a shape describing
- * recipients would describe a delivery path that does not exist.
+ * fields, so no alert can send one, and a shape describing recipients would
+ * describe a delivery path that does not exist.
  */
 export const datapointAlertRow = z.object({
     id: z.uuid(),

package/dist/app-users.d.ts

@@ -39,9 +39,9 @@ export declare const APP_USER_DISPLAY_NAME_MAX = 120;
  * buttons, where a hyphen is the conventional spelling — `azure-ad`, not
  * `azure_ad`.
  *
- * The two grammars are one character apart, which is exactly why this is its
- * own export with its own tests rather than a reuse: reusing the wrong one
- * would be invisible until a customer typed a hyphen.
+ * The two grammars are one character apart — why this is its own export with
+ * its own tests, not a reuse: reusing the wrong one would be invisible until
+ * a customer typed a hyphen.
  */
 export declare const providerSlug: z.ZodString;
 /**
@@ -338,9 +338,8 @@ export declare const APP_URL_PLACEHOLDERS: {
  * the mirror reason: it would mail every recipient the same link.
  *
  * **What it cannot check**: that the URL resolves, that the app serves that
- * path, or that the developer's page knows what to do with the token. Nothing
- * a schema can see says any of that, and a validator that looked sufficient
- * here would be read as an assurance.
+ * path, or that the developer's page knows what to do with the token — and a
+ * validator that looked sufficient here would be read as an assurance.
  */
 export declare function appUrlTemplate(placeholder: string): z.ZodString;
 /**

package/dist/app-users.js

@@ -40,14 +40,14 @@ export const APP_USER_DISPLAY_NAME_MAX = 120;
  * buttons, where a hyphen is the conventional spelling — `azure-ad`, not
  * `azure_ad`.
  *
- * The two grammars are one character apart, which is exactly why this is its
- * own export with its own tests rather than a reuse: reusing the wrong one
- * would be invisible until a customer typed a hyphen.
+ * The two grammars are one character apart — why this is its own export with
+ * its own tests, not a reuse: reusing the wrong one would be invisible until
+ * a customer typed a hyphen.
  */
 export const providerSlug = z
     .string()
     .max(40)
-    .regex(/^[a-z][a-z0-9]*(?:-[a-z0-9]+)*$/, 'a provider slug is lowercase and hyphen-separated, starting with a letter');
+    .regex(/^[a-z][a-z0-9]*(?:-[a-z0-9]+)*$/, 'must be lowercase and hyphen-separated, starting with a letter');
 /**
  * **The three states an app user can be in, and the order is the lifecycle.**
  *
@@ -95,10 +95,10 @@ export const appUser = z.object({
      * accepted — it does not mean blocked and it does not mean without access.
      */
     has_password: z.boolean().meta({
-        description: 'Whether this account has a Fleetless-held password at all. `false` is an identity-provider-only account, or an invitation not yet accepted — it does not mean blocked and it does not mean without access. No hash, no algorithm and no "last changed" travels here, and nothing on the wire can say whether a password is strong or already known to somebody else.',
+        description: 'Whether this account has a Fleetless-held password. `false` is an identity-provider-only account, or an invitation not yet accepted — it does not mean blocked and it does not mean without access. No hash, no algorithm and no "last changed" travels here, and nothing on the wire can say whether a password is strong or already known to somebody else.',
     }),
     providers: z.array(providerSlug).max(20).meta({
-        description: 'The slugs of the identity providers this account is linked to, empty for a password-only user. It is what lets a developer\'s user list say where an account came from without a second request.',
+        description: 'The slugs of the identity providers this account is linked to, empty for a password-only user. Lets a developer\'s user list say where an account came from without a second request.',
     }),
     last_login_at: z.iso.datetime().nullable().meta({
         description: 'When this user last signed in, or `null` if they never have. Required and nullable rather than optional, so *never logged in* stays distinguishable from *this field was not loaded*.',
@@ -269,7 +269,7 @@ export const appOidcProvider = z.object({
         description: 'Whether a federated login may join an **existing** app user with the same address. It needs the provider to assert `email_verified` as well: either condition alone is account takeover, since a provider that lets anyone type any address into a profile would otherwise hand over every matching account, and a developer who connects a provider for a subset of their users would otherwise silently merge strangers.',
     }),
     enabled: z.boolean().meta({
-        description: 'Whether this provider is offered at all. A disabled provider disappears from `GET /api/client/providers` and refuses a start with `provider_disabled`, without the row and its linked identities being deleted.',
+        description: 'Whether this provider is offered. A disabled provider disappears from `GET /api/client/providers` and refuses a start with `provider_disabled`, without the row and its linked identities being deleted.',
     }),
     created_at: z.iso.datetime().meta({ description: 'When the provider was configured, as an ISO 8601 timestamp.' }),
 }).strict();
@@ -371,9 +371,8 @@ export const APP_URL_PLACEHOLDERS = {
  * the mirror reason: it would mail every recipient the same link.
  *
  * **What it cannot check**: that the URL resolves, that the app serves that
- * path, or that the developer's page knows what to do with the token. Nothing
- * a schema can see says any of that, and a validator that looked sufficient
- * here would be read as an assurance.
+ * path, or that the developer's page knows what to do with the token — and a
+ * validator that looked sufficient here would be read as an assurance.
  */
 export function appUrlTemplate(placeholder) {
     return z

package/dist/apps.d.ts

@@ -5,7 +5,7 @@ import { z } from 'zod';
  *
  * The rule that shapes all of this: **roles are the only filter**. A robot
  * assigned to an app exposes every one of its services to that app; what a
- * role does not grant simply does not exist for that user. There is no second
+ * role does not grant does not exist for that user. There is no second
  * visibility mechanism, and adding one later would create two places to look
  * when someone cannot see something.
  */
@@ -15,8 +15,8 @@ import { z } from 'zod';
  *
  * **Globally unique, not per org.** `clientLoginRequest` carries only the
  * identifier, the email and the password — there is no org context to
- * disambiguate with, so a per-org identifier could not be resolved at login
- * at all. A collision is refused with `identifier_taken`.
+ * disambiguate with, so a per-org identifier could not be resolved at login.
+ * A collision is refused with `identifier_taken`.
  */
 export declare const appIdentifier: z.ZodString;
 export declare const app: z.ZodObject<{
@@ -129,9 +129,8 @@ export declare const createServerKeyResponse: z.ZodObject<{
 export type CreateServerKeyResponse = z.infer<typeof createServerKeyResponse>;
 /**
  * Every app starts with `observe` and `operate`; custom roles are allowed
- * too. `builtin` marks the two starting roles — they may be
- * edited like any other, the flag exists so the console can explain where
- * they came from.
+ * too. `builtin` marks the two starting roles — editable like any other,
+ * the flag only tells the console where they came from.
  */
 export declare const role: z.ZodObject<{
     id: z.ZodUUID;