@fleetless/sdk 3.1.1 → 4.1.0

package/CHANGELOG.md

@@ -1,9 +1,39 @@
 # Changelog
 
-All notable changes to `@fleetless/sdk`. The format follows Keep a Changelog; the versions follow semver.
+All notable changes to `@fleetless/sdk`. The format follows Keep a Changelog; the versions follow semver. A pull request that changes what a consumer sees adds its entry under `## [Unreleased]`; the release renames that heading to the version.
 
 ## [Unreleased]
 
+## [4.1.0] — 2026-09-30
+
+Built against `@fleetless/contracts` 5.0.0. Two changes to `Job` a consumer's code sees, so the next release is a major.
+
+### Added
+
+- **`JobOrigin`** is re-exported: the type of `Job.origin`.
+
+### Changed
+
+- **`Job.origin` is required**: `fleetless` for a job the cloud minted from an invocation, `external` for a goal the bridge found running on a published action without having sent it — started by anything else on the robot's ROS graph, or its own goal after the bridge lost the mapping. An external job has no parameters and no starter, and never appears in `jobs.history`. A hand-built `Job` (a test fixture, a mock) now needs the field.
+- **`actions.cancel` is answered by the robot's action server.** It resolves once the server accepted the cancel, with the job usually still `running` — the end arrives as the job's own update. It rejects `cancel_rejected` when the server refused (`ERROR_REJECTED`), with `error.details.goals` listing each goal the cancel reached as `{ job_id, goal_id, return_code }` (`0`–`3`, or `null` when that goal's server did not answer); `bridge_timeout` when the bridge did not answer in time; and with the bridge's own code (e.g. `action_server_lost`) when it could not ask at all. Code that treated a resolved cancel as a stopped goal, or every rejection as "nothing was cancelled", needs to read these apart. Cancelling an `unknown` job cancels every `external` goal on its action.
+- **`JobState` gains `unknown`**: the cloud cannot currently say whether the job is still running — the robot went offline, or its bridge did not report in time. Not terminal: only the robot's bridge moves the job on, to `running` or to how it ended. `lost` is now final. An exhaustive `switch` over `JobState` needs the new case; `services.call` keeps waiting through `unknown`, and `jobs.history` takes `state: 'unknown'`.
+
+## [4.0.0] — 2026-09-22
+
+### Added
+
+- **`createClient({ credentials })`** — hand the client a bearer it does not own. `CredentialSource` is two methods: `token()` answers the current raw bearer or `null`, and `handleExpired()` says whether a `token_expired` is worth retrying. Mutually exclusive with `tokenStore` and `serverKey`, and `auth.login`/`auth.logout` refuse on it for the reason they refuse on a server key: there is no session here to start or end. For an embedder that already holds a session and refreshes it itself — without this it had to impersonate a token store, and a cloud-side `token_expired` arriving while its own clock still read live posted one empty refresh.
+
+### Changed
+
+- **`BridgeState` gains `low_bandwidth`** (bridge protocol 3): whether the robot's bridge is in its low-bandwidth mode. Required, not optional.
+- **`AssetListResponse` gains `store` (`bytes`, `used_bytes`) and `joint_state_slug`.**
+- **`AssetListResponse.active_sync.failed[].details` changed shape**: `{ limit_bytes, size_bytes }` is now `{ store_bytes, used_bytes, size_bytes }`.
+
+### Removed
+
+- **`AssetKind` `other` and the asset failure kind `too_large`.** A robot has one gigabyte of asset storage; there is no per-file limit. This is a major.
+
 ## [3.1.1] — 2026-09-17
 
 ### Fixed

package/CONTRIBUTING.md

@@ -93,8 +93,9 @@ tell you what else has to move with it.
 
 **CI runs on GitHub Actions**, in this repository
 (`.github/workflows/verify.yml`) — the suite, on every push and every pull
-request. `release.yml` publishes on a release tag and calls that same file
-first, so a release is never checked by a different pipeline than a push.
+request. `release.yml` (the **Release** button) calls that same file on the
+commit it publishes, so a release is never checked by a different pipeline
+than a push.
 
 **Your pull request is verified, a fork's included** — the same suite, the
 same file. GitHub holds a first-time contributor's first run until a

package/README.md

@@ -95,10 +95,10 @@ Everything past this point lives at **[docs.fleetless.dev](https://docs.fleetles
   method, every option, and what each one deliberately does not do.
 - **[Getting started](https://docs.fleetless.dev/getting-started/)** — from a
   robot that has never connected to a value in your app.
-- **[Your own login UI](https://docs.fleetless.dev/recipes/app-auth/)** — the
-  walkthrough for every sign-in screen.
-- **[Identity](https://docs.fleetless.dev/reference/identity/)** — the two
-  identity spaces, and what a refusal licenses your UI to claim.
+- **[App Starter](https://docs.fleetless.dev/recipes/app-starter/)** — every
+  sign-in screen, already built, on this SDK.
+- **[Manage users and roles](https://docs.fleetless.dev/concepts/manage-users-and-roles/)** —
+  the two identity spaces, and what a refusal licenses your UI to claim.
 - **[REST and realtime API](https://docs.fleetless.dev/reference/api/)** —
   the wire underneath this package.
 - **[CHANGELOG.md](CHANGELOG.md)** — what changed in each version.