@fleetless/sdk 3.0.3 → 3.1.0

package/CHANGELOG.md

@@ -4,6 +4,17 @@ All notable changes to `@fleetless/sdk`. The format follows Keep a Changelog; th
 
 ## [Unreleased]
 
+## [3.1.0] — 2026-09-17
+
+### Added
+
+- **`client.robots`** — `list()` answers the robots the caller reaches, with bridge state and published version; `describe(robotId)` answers the datasheet: every granted datapoint, action, service, publisher and camera with unit, decimals and parameter JSON Schema, plus the `action_history` and `assets` capabilities. The same rows and the same sheet the MCP tools `robots_list` and `robot_describe` answer, from the same server code. Needs a cloud that serves contracts 1.1.0.
+- **`client.jobs.history(robotId, options?)`** — the run history the reference described since 3.0.0 and the package never shipped. Filters `slug`, `state`, `kind`, `limit`, `beforeSeq`, `fromMs`, `toMs`; page until `next_cursor` is `null`.
+
+### Changed
+
+- Re-pinned to `@fleetless/contracts` 1.1.0. `ClientRobotListItem`, `McpRobotDatasheet`, `McpExposure`, `McpCapabilities`, `JobRun` and `JobRunListResponse` are re-exported.
+
 ## [3.0.3] — 2026-09-16
 
 - Published from GitHub Actions by npm trusted publishing: no publish token exists anywhere, and every version from this one on carries a provenance attestation linking it to the commit and the run that built it. `npm audit signatures` checks it.

package/README.md

@@ -24,6 +24,8 @@ Fleetless is in closed beta. The waiting list is at
 
 ## ✨ What you can do with it
 
+- **Find your robots** and read what your role lets you do on each — slugs,
+  units, parameter schemas — before you draw a screen.
 - **Read datapoints** once, subscribe to them live over one reconnecting
   WebSocket, or query their recorded history.
 - **Run actions and call services** by slug, with feedback, progress and