@fleetless/sdk 3.0.0 → 3.0.2

package/dist/index.d.cts

@@ -1,16 +1,18 @@
+// SPDX-License-Identifier: MIT
 import { z } from 'zod';
 
+
 /**
- * Jobs (spec §6.1, §11.3): one running unit of work on a robot — an action
+ * Jobs: one running unit of work on a robot — an action
  * goal or a service call — with an id both sides know, so bridge and cloud
  * stay in sync across a disconnect.
  *
  * Two rules shape everything here:
  *
- * 1. **State is observed by slug, not by id.** The id is informative (§11.3);
- *    a client watches `robot × slug` and sees whatever job is running there,
- *    which is also why every observer of a slug sees the same job.
- * 2. **`lost` is a real outcome and must be said out loud** (§6.1). Job state
+ * 1. **State is observed by slug, not by id.** The id is informative; a client
+ *    watches `robot × slug` and sees whatever job is running there, which is
+ *    also why every observer of a slug sees the same job.
+ * 2. **`lost` is a real outcome and must be said out loud.** Job state
  *    lives only in the bridge's memory; if it restarts mid-job, the results
  *    are gone. The cloud then marks the job `lost` — never leaves it reading
  *    "running" because nobody contradicted it. A system that reports a
@@ -50,8 +52,8 @@ type Job = z.infer<typeof job>;
 /**
  * One update about a job, pushed to subscribers of its slug.
  *
- * `timestamp_ms` is the bridge's capture time, exactly as for a datapoint
- * (§6.3 says action feedback carries it too) — so a client computes the age
+ * `timestamp_ms` is the bridge's capture time, exactly as for a datapoint —
+ * action feedback carries it too — so a client computes the age
  * of a progress report the same way it computes the age of a sensor value,
  * and a burst of late-delivered feedback after a reconnect is visibly late
  * rather than looking current.
@@ -87,9 +89,8 @@ declare const jobEvent: z.ZodObject<{
 }, z.core.$strip>;
 type JobEvent = z.infer<typeof jobEvent>;
 /**
- * What a busy refusal tells the caller (spec §11.3: "inkl. Information, was
- * läuft"). A refusal that only says "busy" forces the caller to guess whether
- * to wait or to give up.
+ * What a busy refusal tells the caller: what is already running. A refusal that
+ * only says "busy" forces the caller to guess whether to wait or to give up.
  */
 declare const busyDetails: z.ZodObject<{
     running: z.ZodObject<{
@@ -118,7 +119,7 @@ type BusyDetails = z.infer<typeof busyDetails>;
 
 /**
  * The REST read of one datapoint. For bridge-captured data `timestamp_ms`
- * is the capture time at the bridge (spec §6.3); for the cloud-observed
+ * is the capture time at the bridge; for the cloud-observed
  * built-in `bridge_state` it is the time the cloud observed the state.
  */
 declare const datapointValue: z.ZodObject<{
@@ -129,20 +130,18 @@ declare const datapointValue: z.ZodObject<{
 type DatapointValue = z.infer<typeof datapointValue>;
 /**
  * Every job the platform currently believes this robot has — `GET
- * /api/robots/:id/jobs` (W6b).
+ * /api/robots/:id/jobs`.
  *
  * `jobResponse` answers "what is on this slug", which requires knowing the
- * slug first. That was enough while a job could only exist on a slug the
- * published configuration named. W6b breaks that assumption twice: a
- * reconnecting bridge can name a job the cloud has **no row for** and the
- * cloud adopts it, and a configuration change can leave a job on a slug the
- * document no longer contains. Both are jobs nobody can ask about, because
- * asking requires already knowing what to ask for.
+ * slug first. Two kinds of job break that assumption: a reconnecting bridge
+ * can name a job the cloud has **no row for**, and the cloud adopts it; and a
+ * configuration change can leave a job on a slug the document no longer
+ * contains. Both are jobs nobody can ask about, because asking requires
+ * already knowing what to ask for.
  *
- * So this route exists to answer the question the per-slug route cannot: not
- * "is something running here", but "what is this robot doing". A restarted
- * cloud that has just reconciled a robot's `hello.active_jobs` has exactly
- * this list and, until now, no way to say it out loud.
+ * So this route answers the question the per-slug route cannot: not "is
+ * something running here", but "what is this robot doing". A cloud that has
+ * just reconciled a robot's `hello.active_jobs` has exactly this list.
  *
  * The array is ordered newest first and is **never null**: a robot doing
  * nothing answers `{ jobs: [] }`. "Nothing is running" and "we did not look"
@@ -150,14 +149,11 @@ type DatapointValue = z.infer<typeof datapointValue>;
  * distinction `robotDeletionSummary` was made all-required for.
  *
  * **At most one entry per slug: the current job there, exactly what
- * `jobResponse` would answer for that slug.** This is not a history endpoint
- * and must not become one. The first implementation returned every job the
- * registry still held — six rows and four complete Fibonacci results after a
- * few minutes of gate traffic, and unbounded in both count and payload for a
- * robot that has been working all day. The list would have grown until a
- * console page carried a robot's entire past, and the one thing it exists to
- * answer — *what is this robot doing* — would have been the first line of a
- * scroll.
+ * `jobResponse` would answer for that slug.** This is not a history endpoint.
+ * Returning every job a registry still holds is unbounded in both count and
+ * payload for a robot that has been working all day, and the one thing this
+ * route exists to answer — *what is this robot doing* — would be the first
+ * line of a scroll. The durable history has its own routes.
  *
  * A settled job stays visible as its slug's current entry until something
  * else runs there, which is what makes a job that just failed still findable.
@@ -165,7 +161,7 @@ type DatapointValue = z.infer<typeof datapointValue>;
  * `jobResponse`.
  */
 /**
- * What a `rate_limited` refusal tells the caller (W6c).
+ * What a `rate_limited` refusal tells the caller.
  *
  * One number, and it is the only one that matters: **when to come back.** A
  * limit that says "too many" without saying "in 800 ms" produces a client that
@@ -189,7 +185,7 @@ declare const cameraDescriptor: z.ZodObject<{
 }, z.core.$strip>;
 type CameraDescriptor = z.infer<typeof cameraDescriptor>;
 /**
- * Raw samples. `timestamp_ms` is the **bridge's capture time** (§6.3) — the
+ * Raw samples. `timestamp_ms` is the **bridge's capture time** — the
  * same instant the live value carried, so a recorded point and a live one can
  * be placed on one axis without apology.
  *
@@ -217,9 +213,8 @@ type HistorySamplesResponse = z.infer<typeof historySamplesResponse>;
  * inspection.
  *
  * `sample_count` exists because an empty bucket and a bucket whose average is
- * zero are different facts. W5 established at some cost what happens when two
- * facts share one representation, and a chart is the easiest place in this
- * product to draw a gap as a line.
+ * zero are different facts. When two facts share one representation, a chart
+ * is the easiest place to draw a gap as a line.
  */
 declare const historyBucketsResponse: z.ZodObject<{
     slug: z.ZodString;
@@ -238,6 +233,7 @@ declare const historyBucketsResponse: z.ZodObject<{
 }, z.core.$strip>;
 type HistoryBucketsResponse = z.infer<typeof historyBucketsResponse>;
 
+
 /**
  * One datapoint sample pushed to a subscriber. The current value arrives
  * immediately on subscribe, then every change. `timestamp_ms` semantics as
@@ -252,8 +248,9 @@ declare const datapointEvent: z.ZodObject<{
 }, z.core.$strip>;
 type DatapointEvent = z.infer<typeof datapointEvent>;
 
+
 /**
- * Access plus refresh (spec §3.4). The access token is short-lived; the
+ * Access plus refresh. The access token is short-lived; the
  * refresh token rotates on every use, so a stolen one is detectable when the
  * original is presented again.
  *
@@ -267,10 +264,11 @@ declare const sessionTokens: z.ZodObject<{
 }, z.core.$strip>;
 type SessionTokens = z.infer<typeof sessionTokens>;
 
+
 /**
  * **Why a federated sign-in ended without a session, in a code the app can
  * branch on** — carried back to the app's own `redirect_uri` as `error`, not
- * rendered by Fleetless (D2). The only Fleetless-rendered page in this flow is
+ * rendered by Fleetless. The only Fleetless-rendered page in this flow is
  * the one for a state that can no longer be resolved to a redirect URI, because
  * then there is nowhere to send the answer.
  *
@@ -319,7 +317,7 @@ declare const clientOidcErrorCode: z.ZodEnum<{
 type ClientOidcErrorCode = z.infer<typeof clientOidcErrorCode>;
 /**
  * **A pending MCP authorization, as the app's own consent screen reads it**
- * (D7). Fleetless renders no page here either: `authorize` redirects to the
+ * Fleetless renders no page here either: `authorize` redirects to the
  * app's `mcp_login_url` with an interaction id, the app authenticates the user
  * with its normal UI, shows this, and approves or denies through the API.
  *
@@ -394,7 +392,7 @@ type McpConsentGrant = z.infer<typeof mcpConsentGrant>;
  * quietest way for a cut like this to go wrong.
  *
  * **`act` is gone.** It named the org admin behind an impersonation (the RFC
- * 8693 pattern). Impersonation is deleted with no successor (D1), so a field
+ * 8693 pattern). Impersonation is deleted with no successor, so a field
  * that could still arrive would describe a delegation nothing can mint — and a
  * client rendering "you are acting as …" from it would be showing a state the
  * platform cannot enter.
@@ -414,6 +412,7 @@ declare const clientIdentity: z.ZodObject<{
 }, z.core.$strip>;
 type ClientIdentity = z.infer<typeof clientIdentity>;
 
+
 declare const asset: z.ZodObject<{
     id: z.ZodUUID;
     robot_id: z.ZodUUID;
@@ -436,23 +435,18 @@ type Asset = z.infer<typeof asset>;
  *
  * `missing` carries **the reference, verbatim, that no asset answers** — for
  * a `package://` mesh the URI the bridge could not resolve in the workspace,
- * and since W7's security fix also the absolute paths and bare relative paths
- * a URDF may carry, which the extractor sees and the sync deliberately never
- * offers. The sentence used to say "the `package://` URIs" and the field
- * carried three kinds of string (Momus-W7); it is widened here rather than
- * narrowed, because a developer whose URDF names `/opt/meshes/arm.stl` is
- * entitled to be told that nothing will ever fetch it.
+ * and also the absolute paths and bare relative paths a URDF may carry, which
+ * the extractor sees and the sync deliberately never offers. A developer whose
+ * URDF names `/opt/meshes/arm.stl` is entitled to be told that nothing will
+ * ever fetch it.
  *
- * The spec's example is "2 Meshes fehlen" and that number alone is a dead
- * end: it tells a developer to go looking through a workspace by hand. The
- * references are what they can act on, so the references travel.
+ * A bare count of what is missing is a dead end: it tells a developer to go
+ * looking through a workspace by hand. The references are what they can act
+ * on, so the references travel.
  *
- * **Every entry must be actionable, and that is a constraint on the
- * producers, not on this field (W7a).** An entry a developer cannot make
- * disappear by fixing what it names is a defect in whoever put it there: for
- * a whole wave `<texture>` references were listed here and no sync would ever
- * offer them, so the honest instruction behind the list was "fix this, it
- * will not help".
+ * **Every entry must be actionable, and that is a constraint on the producers,
+ * not on this field.** An entry a developer cannot make disappear by fixing
+ * what it names is a defect in whoever put it there.
  */
 declare const urdfCompleteness: z.ZodObject<{
     present: z.ZodBoolean;
@@ -552,8 +546,9 @@ declare const assetListResponse: z.ZodObject<{
 }, z.core.$strip>;
 type AssetListResponse = z.infer<typeof assetListResponse>;
 
+
 /**
- * One violated §4.4 rule. `details` on the envelope stays `unknown` — codes
+ * One violated parameter rule. `details` on the envelope stays `unknown` — codes
  * are an open set, so their payloads cannot all be enumerated — but the
  * payload of `parameter_invalid` **is** pinned here, because otherwise every
  * consumer guesses: the cloud emits one shape, the SDK sniffs for two, the
@@ -586,7 +581,7 @@ declare const parameterInvalidDetails: z.ZodObject<{
 }, z.core.$strip>;
 type ParameterInvalidDetails = z.infer<typeof parameterInvalidDetails>;
 /**
- * The codes in use as of W2. The wire deliberately allows any string — this
+ * The codes in use today. The wire deliberately allows any string — this
  * list is the shared vocabulary, not a closed set, so a new refusal never
  * needs a contracts release before it can be reported honestly.
  */
@@ -1143,8 +1138,8 @@ interface AssetsApi {
      * in sync.
      *
      * **`urdf-loader` resolves `package://` itself, before any of this runs —
-     * a second resolution stage this method has to account for, measured in a
-     * real browser rather than read off the source.** `URDFLoader.parse()`'s own `resolvePath()`
+     * a second resolution stage this method has to account for.**
+     * `URDFLoader.parse()`'s own `resolvePath()`
      * rewrites `package://pkg/rel` using `this.packages` (default `''`) to
      * `/pkg/rel` — a root-relative URL — and *that* is what reaches
      * `loadMeshCb`/`ColladaLoader`/`manager.resolveURL()`, not the original
@@ -1361,8 +1356,8 @@ interface McpInteractionDecision {
     redirectTo: string;
 }
 /**
- * Who the caller is, reachable as `client.auth` — the whole client auth API of
- * spec §4, as JSON.
+ * Who the caller is, reachable as `client.auth` — the whole client
+ * authentication API, as JSON.
  *
  * **Fleetless serves an app user no page.** The developer's own UI owns every
  * screen: login, registration, verification, invitation acceptance, password
@@ -1933,8 +1928,8 @@ interface PublishersApi {
      * mean the SDK protects a caller who stops calling `publish` on purpose
      * without stopping cleanly (e.g. no repeated call at a safe rate): the
      * safety pattern for *how often* and *when* to publish belongs in the
-     * app, not here. See the README's "No teleop helpers" section before
-     * building a publisher-driven control loop.
+     * app, not here. See the README's "Publishers, and no teleop helpers"
+     * section before building a publisher-driven control loop.
      *
      * Rejects `publisher_busy` while a different user is publishing and has
      * not been quiet for its configured quiet timeout yet — whoever publishes

package/dist/index.d.ts

@@ -1,16 +1,18 @@
+// SPDX-License-Identifier: MIT
 import { z } from 'zod';
 
+
 /**
- * Jobs (spec §6.1, §11.3): one running unit of work on a robot — an action
+ * Jobs: one running unit of work on a robot — an action
  * goal or a service call — with an id both sides know, so bridge and cloud
  * stay in sync across a disconnect.
  *
  * Two rules shape everything here:
  *
- * 1. **State is observed by slug, not by id.** The id is informative (§11.3);
- *    a client watches `robot × slug` and sees whatever job is running there,
- *    which is also why every observer of a slug sees the same job.
- * 2. **`lost` is a real outcome and must be said out loud** (§6.1). Job state
+ * 1. **State is observed by slug, not by id.** The id is informative; a client
+ *    watches `robot × slug` and sees whatever job is running there, which is
+ *    also why every observer of a slug sees the same job.
+ * 2. **`lost` is a real outcome and must be said out loud.** Job state
  *    lives only in the bridge's memory; if it restarts mid-job, the results
  *    are gone. The cloud then marks the job `lost` — never leaves it reading
  *    "running" because nobody contradicted it. A system that reports a
@@ -50,8 +52,8 @@ type Job = z.infer<typeof job>;
 /**
  * One update about a job, pushed to subscribers of its slug.
  *
- * `timestamp_ms` is the bridge's capture time, exactly as for a datapoint
- * (§6.3 says action feedback carries it too) — so a client computes the age
+ * `timestamp_ms` is the bridge's capture time, exactly as for a datapoint —
+ * action feedback carries it too — so a client computes the age
  * of a progress report the same way it computes the age of a sensor value,
  * and a burst of late-delivered feedback after a reconnect is visibly late
  * rather than looking current.
@@ -87,9 +89,8 @@ declare const jobEvent: z.ZodObject<{
 }, z.core.$strip>;
 type JobEvent = z.infer<typeof jobEvent>;
 /**
- * What a busy refusal tells the caller (spec §11.3: "inkl. Information, was
- * läuft"). A refusal that only says "busy" forces the caller to guess whether
- * to wait or to give up.
+ * What a busy refusal tells the caller: what is already running. A refusal that
+ * only says "busy" forces the caller to guess whether to wait or to give up.
  */
 declare const busyDetails: z.ZodObject<{
     running: z.ZodObject<{
@@ -118,7 +119,7 @@ type BusyDetails = z.infer<typeof busyDetails>;
 
 /**
  * The REST read of one datapoint. For bridge-captured data `timestamp_ms`
- * is the capture time at the bridge (spec §6.3); for the cloud-observed
+ * is the capture time at the bridge; for the cloud-observed
  * built-in `bridge_state` it is the time the cloud observed the state.
  */
 declare const datapointValue: z.ZodObject<{
@@ -129,20 +130,18 @@ declare const datapointValue: z.ZodObject<{
 type DatapointValue = z.infer<typeof datapointValue>;
 /**
  * Every job the platform currently believes this robot has — `GET
- * /api/robots/:id/jobs` (W6b).
+ * /api/robots/:id/jobs`.
  *
  * `jobResponse` answers "what is on this slug", which requires knowing the
- * slug first. That was enough while a job could only exist on a slug the
- * published configuration named. W6b breaks that assumption twice: a
- * reconnecting bridge can name a job the cloud has **no row for** and the
- * cloud adopts it, and a configuration change can leave a job on a slug the
- * document no longer contains. Both are jobs nobody can ask about, because
- * asking requires already knowing what to ask for.
+ * slug first. Two kinds of job break that assumption: a reconnecting bridge
+ * can name a job the cloud has **no row for**, and the cloud adopts it; and a
+ * configuration change can leave a job on a slug the document no longer
+ * contains. Both are jobs nobody can ask about, because asking requires
+ * already knowing what to ask for.
  *
- * So this route exists to answer the question the per-slug route cannot: not
- * "is something running here", but "what is this robot doing". A restarted
- * cloud that has just reconciled a robot's `hello.active_jobs` has exactly
- * this list and, until now, no way to say it out loud.
+ * So this route answers the question the per-slug route cannot: not "is
+ * something running here", but "what is this robot doing". A cloud that has
+ * just reconciled a robot's `hello.active_jobs` has exactly this list.
  *
  * The array is ordered newest first and is **never null**: a robot doing
  * nothing answers `{ jobs: [] }`. "Nothing is running" and "we did not look"
@@ -150,14 +149,11 @@ type DatapointValue = z.infer<typeof datapointValue>;
  * distinction `robotDeletionSummary` was made all-required for.
  *
  * **At most one entry per slug: the current job there, exactly what
- * `jobResponse` would answer for that slug.** This is not a history endpoint
- * and must not become one. The first implementation returned every job the
- * registry still held — six rows and four complete Fibonacci results after a
- * few minutes of gate traffic, and unbounded in both count and payload for a
- * robot that has been working all day. The list would have grown until a
- * console page carried a robot's entire past, and the one thing it exists to
- * answer — *what is this robot doing* — would have been the first line of a
- * scroll.
+ * `jobResponse` would answer for that slug.** This is not a history endpoint.
+ * Returning every job a registry still holds is unbounded in both count and
+ * payload for a robot that has been working all day, and the one thing this
+ * route exists to answer — *what is this robot doing* — would be the first
+ * line of a scroll. The durable history has its own routes.
  *
  * A settled job stays visible as its slug's current entry until something
  * else runs there, which is what makes a job that just failed still findable.
@@ -165,7 +161,7 @@ type DatapointValue = z.infer<typeof datapointValue>;
  * `jobResponse`.
  */
 /**
- * What a `rate_limited` refusal tells the caller (W6c).
+ * What a `rate_limited` refusal tells the caller.
  *
  * One number, and it is the only one that matters: **when to come back.** A
  * limit that says "too many" without saying "in 800 ms" produces a client that
@@ -189,7 +185,7 @@ declare const cameraDescriptor: z.ZodObject<{
 }, z.core.$strip>;
 type CameraDescriptor = z.infer<typeof cameraDescriptor>;
 /**
- * Raw samples. `timestamp_ms` is the **bridge's capture time** (§6.3) — the
+ * Raw samples. `timestamp_ms` is the **bridge's capture time** — the
  * same instant the live value carried, so a recorded point and a live one can
  * be placed on one axis without apology.
  *
@@ -217,9 +213,8 @@ type HistorySamplesResponse = z.infer<typeof historySamplesResponse>;
  * inspection.
  *
  * `sample_count` exists because an empty bucket and a bucket whose average is
- * zero are different facts. W5 established at some cost what happens when two
- * facts share one representation, and a chart is the easiest place in this
- * product to draw a gap as a line.
+ * zero are different facts. When two facts share one representation, a chart
+ * is the easiest place to draw a gap as a line.
  */
 declare const historyBucketsResponse: z.ZodObject<{
     slug: z.ZodString;
@@ -238,6 +233,7 @@ declare const historyBucketsResponse: z.ZodObject<{
 }, z.core.$strip>;
 type HistoryBucketsResponse = z.infer<typeof historyBucketsResponse>;
 
+
 /**
  * One datapoint sample pushed to a subscriber. The current value arrives
  * immediately on subscribe, then every change. `timestamp_ms` semantics as
@@ -252,8 +248,9 @@ declare const datapointEvent: z.ZodObject<{
 }, z.core.$strip>;
 type DatapointEvent = z.infer<typeof datapointEvent>;
 
+
 /**
- * Access plus refresh (spec §3.4). The access token is short-lived; the
+ * Access plus refresh. The access token is short-lived; the
  * refresh token rotates on every use, so a stolen one is detectable when the
  * original is presented again.
  *
@@ -267,10 +264,11 @@ declare const sessionTokens: z.ZodObject<{
 }, z.core.$strip>;
 type SessionTokens = z.infer<typeof sessionTokens>;
 
+
 /**
  * **Why a federated sign-in ended without a session, in a code the app can
  * branch on** — carried back to the app's own `redirect_uri` as `error`, not
- * rendered by Fleetless (D2). The only Fleetless-rendered page in this flow is
+ * rendered by Fleetless. The only Fleetless-rendered page in this flow is
  * the one for a state that can no longer be resolved to a redirect URI, because
  * then there is nowhere to send the answer.
  *
@@ -319,7 +317,7 @@ declare const clientOidcErrorCode: z.ZodEnum<{
 type ClientOidcErrorCode = z.infer<typeof clientOidcErrorCode>;
 /**
  * **A pending MCP authorization, as the app's own consent screen reads it**
- * (D7). Fleetless renders no page here either: `authorize` redirects to the
+ * Fleetless renders no page here either: `authorize` redirects to the
  * app's `mcp_login_url` with an interaction id, the app authenticates the user
  * with its normal UI, shows this, and approves or denies through the API.
  *
@@ -394,7 +392,7 @@ type McpConsentGrant = z.infer<typeof mcpConsentGrant>;
  * quietest way for a cut like this to go wrong.
  *
  * **`act` is gone.** It named the org admin behind an impersonation (the RFC
- * 8693 pattern). Impersonation is deleted with no successor (D1), so a field
+ * 8693 pattern). Impersonation is deleted with no successor, so a field
  * that could still arrive would describe a delegation nothing can mint — and a
  * client rendering "you are acting as …" from it would be showing a state the
  * platform cannot enter.
@@ -414,6 +412,7 @@ declare const clientIdentity: z.ZodObject<{
 }, z.core.$strip>;
 type ClientIdentity = z.infer<typeof clientIdentity>;
 
+
 declare const asset: z.ZodObject<{
     id: z.ZodUUID;
     robot_id: z.ZodUUID;
@@ -436,23 +435,18 @@ type Asset = z.infer<typeof asset>;
  *
  * `missing` carries **the reference, verbatim, that no asset answers** — for
  * a `package://` mesh the URI the bridge could not resolve in the workspace,
- * and since W7's security fix also the absolute paths and bare relative paths
- * a URDF may carry, which the extractor sees and the sync deliberately never
- * offers. The sentence used to say "the `package://` URIs" and the field
- * carried three kinds of string (Momus-W7); it is widened here rather than
- * narrowed, because a developer whose URDF names `/opt/meshes/arm.stl` is
- * entitled to be told that nothing will ever fetch it.
+ * and also the absolute paths and bare relative paths a URDF may carry, which
+ * the extractor sees and the sync deliberately never offers. A developer whose
+ * URDF names `/opt/meshes/arm.stl` is entitled to be told that nothing will
+ * ever fetch it.
  *
- * The spec's example is "2 Meshes fehlen" and that number alone is a dead
- * end: it tells a developer to go looking through a workspace by hand. The
- * references are what they can act on, so the references travel.
+ * A bare count of what is missing is a dead end: it tells a developer to go
+ * looking through a workspace by hand. The references are what they can act
+ * on, so the references travel.
  *
- * **Every entry must be actionable, and that is a constraint on the
- * producers, not on this field (W7a).** An entry a developer cannot make
- * disappear by fixing what it names is a defect in whoever put it there: for
- * a whole wave `<texture>` references were listed here and no sync would ever
- * offer them, so the honest instruction behind the list was "fix this, it
- * will not help".
+ * **Every entry must be actionable, and that is a constraint on the producers,
+ * not on this field.** An entry a developer cannot make disappear by fixing
+ * what it names is a defect in whoever put it there.
  */
 declare const urdfCompleteness: z.ZodObject<{
     present: z.ZodBoolean;
@@ -552,8 +546,9 @@ declare const assetListResponse: z.ZodObject<{
 }, z.core.$strip>;
 type AssetListResponse = z.infer<typeof assetListResponse>;
 
+
 /**
- * One violated §4.4 rule. `details` on the envelope stays `unknown` — codes
+ * One violated parameter rule. `details` on the envelope stays `unknown` — codes
  * are an open set, so their payloads cannot all be enumerated — but the
  * payload of `parameter_invalid` **is** pinned here, because otherwise every
  * consumer guesses: the cloud emits one shape, the SDK sniffs for two, the
@@ -586,7 +581,7 @@ declare const parameterInvalidDetails: z.ZodObject<{
 }, z.core.$strip>;
 type ParameterInvalidDetails = z.infer<typeof parameterInvalidDetails>;
 /**
- * The codes in use as of W2. The wire deliberately allows any string — this
+ * The codes in use today. The wire deliberately allows any string — this
  * list is the shared vocabulary, not a closed set, so a new refusal never
  * needs a contracts release before it can be reported honestly.
  */
@@ -1143,8 +1138,8 @@ interface AssetsApi {
      * in sync.
      *
      * **`urdf-loader` resolves `package://` itself, before any of this runs —
-     * a second resolution stage this method has to account for, measured in a
-     * real browser rather than read off the source.** `URDFLoader.parse()`'s own `resolvePath()`
+     * a second resolution stage this method has to account for.**
+     * `URDFLoader.parse()`'s own `resolvePath()`
      * rewrites `package://pkg/rel` using `this.packages` (default `''`) to
      * `/pkg/rel` — a root-relative URL — and *that* is what reaches
      * `loadMeshCb`/`ColladaLoader`/`manager.resolveURL()`, not the original
@@ -1361,8 +1356,8 @@ interface McpInteractionDecision {
     redirectTo: string;
 }
 /**
- * Who the caller is, reachable as `client.auth` — the whole client auth API of
- * spec §4, as JSON.
+ * Who the caller is, reachable as `client.auth` — the whole client
+ * authentication API, as JSON.
  *
  * **Fleetless serves an app user no page.** The developer's own UI owns every
  * screen: login, registration, verification, invitation acceptance, password
@@ -1933,8 +1928,8 @@ interface PublishersApi {
      * mean the SDK protects a caller who stops calling `publish` on purpose
      * without stopping cleanly (e.g. no repeated call at a safe rate): the
      * safety pattern for *how often* and *when* to publish belongs in the
-     * app, not here. See the README's "No teleop helpers" section before
-     * building a publisher-driven control loop.
+     * app, not here. See the README's "Publishers, and no teleop helpers"
+     * section before building a publisher-driven control loop.
      *
      * Rejects `publisher_busy` while a different user is publishing and has
      * not been quiet for its configured quiet timeout yet — whoever publishes