@fleetless/sdk 3.0.0 → 3.0.2

package/CHANGELOG.md

@@ -4,6 +4,149 @@ All notable changes to `@fleetless/sdk`. The format follows Keep a Changelog; th
 
 ## [Unreleased]
 
+## [3.0.2] — 2026-09-07
+
+No API change, and one documentation example that now compiles. The guard
+that was supposed to prove 3.0.1 clean was **green over four internal
+references still inside the published bundle**, so it was rebuilt around the
+question rather than around three directory names.
+
+### Fixed
+
+- **Four internal references in the published 3.0.1 bundle**, which the guard
+  could not see: an internal decision label in `dist/index.js` and
+  `dist/index.cjs`, and a sentence in both about how a defect class had been
+  found. Measured against the registry rather than against this tree — 3.0.1
+  scores 4, 3.0.2 scores 0, and 3.0.0 scores 423.
+- **The README's error-handling example did not compile.** `details` is
+  `unknown` on `FleetlessError`, deliberately, and the block read fields off
+  it directly — two `TS2339`s in a TypeScript SDK's own README, in the block a
+  reader copies first. It now narrows before reading, and it is opted in to
+  the documentation type check so it cannot drift again.
+- **`Node 20 or newer` was listed as a runtime for the whole SDK.** Node 20
+  has no global `WebSocket` — it is behind a flag there — so anything realtime
+  fails on it with the SDK's own `no_websocket`. The README names Node 22, and
+  says what to pass on Node 20 instead.
+- **Everything published pointed at a public repository that does not exist
+  yet.** `repository`, `bugs.url`, the README, `CONTRIBUTING.md` and
+  `RELEASING.md` all named it, and its four relative links resolved to 404s on
+  the npm page. They point at the maintainer address until the repository is
+  opened.
+- **`CONTRIBUTING.md` linked `RELEASING.md`, which the tarball did not
+  carry.** `RELEASING.md` ships now, and every relative link in every shipped
+  document is checked against the tarball's own entries.
+- **Each published file declares exactly one licence.** The bundler inlines
+  `@fleetless/contracts`, which is Apache-2.0, and the declaration files
+  carried six of its SPDX identifiers below this package's MIT one. A licence
+  scan over `node_modules` reported Apache obligations for a package that
+  ships no Apache text. The inherited identifiers are stripped at build time.
+- **A CI comment sent whoever was reading a red publish job to a README
+  section that does not exist**, and `RELEASING.md` told a maintainer the
+  suite runs against a fake `fetch` — which `CONTRIBUTING.md` devotes a
+  section to denying, and which is untrue of three of the nineteen suites.
+
+### Changed
+
+- **The guard scans what becomes public, computed rather than named.** The
+  union of what `npm pack` reports, what `git ls-files` reports and a walk of
+  every directory in `files`. Ten tracked files were outside the previous
+  shape, two of them published bytes; one of those two had already carried an
+  internal host to the registry inside `devDependencies`.
+- **Only the German scan strips anything**, and only URLs and single-token
+  code spans. Stripping links and backticks before every class made the six
+  shipped documents blind to an internal hostname inside a markdown link.
+- **Eighteen detectors, each carrying its own two fixtures**, with a floor
+  over the count. Seven of the previous fifteen had no fixture proving they
+  could fire, and two could be deleted with the whole suite green.
+- **The tarball guard asserts absence as well as presence**: nothing outside
+  `files`, no sourcemaps, no source. It reads every dependency section rather
+  than the runtime one alone, and runs the marker detectors over the packed
+  manifest.
+
+### Added
+
+- **`test/readme-pointers.test.ts`**: every pointer from the code into the
+  README resolves to a heading that is there. That was the defect 3.0.1 fixed
+  and left unguarded, one of them inside a runtime error message.
+- **`scripts/verify-commit-messages.mjs`**, wired into the verify job. A
+  commit message is public the moment it is pushed.
+
+## [3.0.1] — 2026-09-07
+
+No API change. This release exists because **3.0.0 published internal material
+to the registry**, and the only way to withdraw it is to publish a version
+without it.
+
+### Fixed
+
+- **The published bundle no longer carries internal text.** `tsup` inlines
+  `@fleetless/contracts` into `dist/index.js` and `dist/index.cjs` with its doc
+  comments intact, and it writes the path each inlined module came from as a
+  comment beside it. In 3.0.0 those paths encoded a `git+ssh://` dependency
+  specifier, so an internal hostname appeared **48 times** across the two
+  bundles; the inlined comments carried German paragraphs and internal defect
+  ids with them.
+
+  The table this entry first carried cited "the same seventeen detectors",
+  while the entry below it said the guard had fifteen classes and the guard
+  itself asserted fifteen. No seventeen-detector artefact ever existed, so
+  the numbers could not be reproduced from anything shipped. They are
+  replaced here by a measurement of the two **published tarballs** with the
+  guard as rebuilt in 3.0.2, which is a thing a reader can run:
+
+  | class | 3.0.0 | 3.0.1 |
+  |---|---:|---:|
+  | terse schedule label | 134 | 0 |
+  | German prose | 58 | 0 |
+  | internal host or workspace name | 49 | 0 |
+  | internal decision label | 44 | **2** |
+  | a reference to this package rather than the reader's | 30 | 0 |
+  | internal review codename | 28 | 0 |
+  | a reference to a document the reader does not have | 26 | 0 |
+  | longer schedule label | 16 | 0 |
+  | how the behaviour was found | 16 | **2** |
+  | internal defect id | 14 | 0 |
+  | internal feature id | 4 | 0 |
+  | the reference robot by name | 4 | 0 |
+  | **total** | **423** | **4** |
+
+  The four remaining in 3.0.1 are the subject of 3.0.2 below. They are here
+  rather than in that entry because this is the entry that claimed zero.
+
+  None of it appeared in this repository's own source, which is why no sweep of
+  the source had found it. The fix is the contracts pin — `@fleetless/contracts`
+  is a public npm package at an exact version now — plus a sweep of this
+  repository's own comments.
+
+- **`publishers.publish`, `commands.cancel`, `cameras.live` and the error
+  re-exports pointed at README sections that did not exist.** One of them
+  (`cancel`'s upgrade message) is a **runtime error** telling a developer to
+  read "the README's Actions section" of a README whose sections were named
+  something else. The README now has *Actions*, *Errors*, and *Publishers, and
+  no teleop helpers*, and every pointer resolves.
+
+### Added
+
+- **`SECURITY.md`, `CONTRIBUTING.md` and `CODE_OF_CONDUCT.md`**, and all three
+  ship inside the tarball, so the README's links resolve from `node_modules` and
+  from the npm page. `SECURITY.md` says what is in scope here — how this package
+  handles tokens, the PKCE verifier and the `state` value — and that the cloud
+  is not in this repository. Security reports go to **security@fleetless.dev**,
+  which the README now states literally rather than only by link.
+- **`repository` and `bugs.url`** in `package.json`, pointing at
+  <https://github.com/fleetless/sdk>.
+- **An `Errors` section in the README**, documenting the `FleetlessError` `code`
+  you branch on, that `rate_limited` is surfaced with its `retry_after_ms` and
+  never retried, and that `token_expired` is the one retry the SDK performs.
+- **The SPDX header `// SPDX-License-Identifier: MIT`** on every source file and
+  on all four published `dist/` files. `test/license-headers.test.ts` asserts it
+  over the repository; `pnpm run test:pack` asserts it over the tarball's own
+  bytes, which is the only place that can tell a stamped build from a stamped
+  publish.
+- **`test/published-prose.test.ts`**, which is what stops the top item here from
+  happening again: fifteen detector classes over `dist/`, `src/`, `test/`,
+  `scripts/` and the shipped markdown, with fixtures in both directions.
+
 ## [3.0.0] — 2026-09-06
 
 Fleetless shows an app user **no page**. The developer's own UI owns every

package/CODE_OF_CONDUCT.md

@@ -0,0 +1,83 @@
+# Contributor Covenant Code of Conduct
+
+## Our Pledge
+
+We as members, contributors, and leaders pledge to make participation in our community a harassment-free experience for everyone, regardless of age, body size, visible or invisible disability, ethnicity, sex characteristics, gender identity and expression, level of experience, education, socio-economic status, nationality, personal appearance, race, caste, color, religion, or sexual identity and orientation.
+
+We pledge to act and interact in ways that contribute to an open, welcoming, diverse, inclusive, and healthy community.
+
+## Our Standards
+
+Examples of behavior that contributes to a positive environment for our community include:
+
+* Demonstrating empathy and kindness toward other people
+* Being respectful of differing opinions, viewpoints, and experiences
+* Giving and gracefully accepting constructive feedback
+* Accepting responsibility and apologizing to those affected by our mistakes, and learning from the experience
+* Focusing on what is best not just for us as individuals, but for the overall community
+
+Examples of unacceptable behavior include:
+
+* The use of sexualized language or imagery, and sexual attention or advances of any kind
+* Trolling, insulting or derogatory comments, and personal or political attacks
+* Public or private harassment
+* Publishing others' private information, such as a physical or email address, without their explicit permission
+* Other conduct which could reasonably be considered inappropriate in a professional setting
+
+## Enforcement Responsibilities
+
+Community leaders are responsible for clarifying and enforcing our standards of acceptable behavior and will take appropriate and fair corrective action in response to any behavior that they deem inappropriate, threatening, offensive, or harmful.
+
+Community leaders have the right and responsibility to remove, edit, or reject comments, commits, code, wiki edits, issues, and other contributions that are not aligned to this Code of Conduct, and will communicate reasons for moderation decisions when appropriate.
+
+## Scope
+
+This Code of Conduct applies within all community spaces, and also applies when an individual is officially representing the community in public spaces. Examples of representing our community include using an official e-mail address, posting via an official social media account, or acting as an appointed representative at an online or offline event.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be reported to the community leaders responsible for enforcement at hello@fleetless.dev. All complaints will be reviewed and investigated promptly and fairly.
+
+All community leaders are obligated to respect the privacy and security of the reporter of any incident.
+
+## Enforcement Guidelines
+
+Community leaders will follow these Community Impact Guidelines in determining the consequences for any action they deem in violation of this Code of Conduct:
+
+### 1. Correction
+
+**Community Impact**: Use of inappropriate language or other behavior deemed unprofessional or unwelcome in the community.
+
+**Consequence**: A private, written warning from community leaders, providing clarity around the nature of the violation and an explanation of why the behavior was inappropriate. A public apology may be requested.
+
+### 2. Warning
+
+**Community Impact**: A violation through a single incident or series of actions.
+
+**Consequence**: A warning with consequences for continued behavior. No interaction with the people involved, including unsolicited interaction with those enforcing the Code of Conduct, for a specified period of time. This includes avoiding interactions in community spaces as well as external channels like social media. Violating these terms may lead to a temporary or permanent ban.
+
+### 3. Temporary Ban
+
+**Community Impact**: A serious violation of community standards, including sustained inappropriate behavior.
+
+**Consequence**: A temporary ban from any sort of interaction or public communication with the community for a specified period of time. No public or private interaction with the people involved, including unsolicited interaction with those enforcing the Code of Conduct, is allowed during this period. Violating these terms may lead to a permanent ban.
+
+### 4. Permanent Ban
+
+**Community Impact**: Demonstrating a pattern of violation of community standards, including sustained inappropriate behavior, harassment of an individual, or aggression toward or disparagement of classes of individuals.
+
+**Consequence**: A permanent ban from any sort of public interaction within the community.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 2.1, available at [https://www.contributor-covenant.org/version/2/1/code_of_conduct.html][v2.1].
+
+Community Impact Guidelines were inspired by [Mozilla's code of conduct enforcement ladder][Mozilla CoC].
+
+For answers to common questions about this code of conduct, see the FAQ at [https://www.contributor-covenant.org/faq][FAQ]. Translations are available at [https://www.contributor-covenant.org/translations][translations].
+
+[homepage]: https://www.contributor-covenant.org
+[v2.1]: https://www.contributor-covenant.org/version/2/1/code_of_conduct.html
+[Mozilla CoC]: https://github.com/mozilla/diversity
+[FAQ]: https://www.contributor-covenant.org/faq
+[translations]: https://www.contributor-covenant.org/translations

package/CONTRIBUTING.md

@@ -0,0 +1,131 @@
+# Contributing to `@fleetless/sdk`
+
+This package is the TypeScript client for the Fleetless API. It is what a
+developer's own application calls, so a change here reaches every app built on
+it, and a change to what a method *sends* reaches the platform as well.
+
+## Setup
+
+Node 22 and pnpm (through corepack):
+
+```sh
+nvm use 22
+corepack enable
+pnpm install
+```
+
+There are no private dependencies. `pnpm install` works from a clean checkout
+with nothing but a network connection to the npm registry — the wire schemas
+come from `@fleetless/contracts`, which is a public package.
+
+`pnpm install` runs `prepare`, which builds `dist/`. Some of the checks below
+read the built bundle, so a fresh checkout is ready for them.
+
+## The checks
+
+| Command | What it does |
+|---|---|
+| `pnpm typecheck` | `tsc --noEmit` over the whole project. |
+| `pnpm test` | The vitest suite. No network beyond loopback. |
+| `pnpm build` | `tsup` into `dist/` — ESM, CJS, and a declaration file for each. |
+| `pnpm run test:pack` | Packs the tarball, asserts what is and is not inside it, then installs it into a scratch project and both typechecks and runs real code against it. |
+
+To run one test file, use `pnpm vitest run test/<name>.test.ts`.
+
+## The rule this repository is most serious about: a real server, not a mocked `fetch`
+
+**The auth suites drive the SDK's own default `fetch` against a real
+`node:http` server** (`test/local-api.ts`), and no `fetch` option is passed to
+`createClient` in them.
+
+That is not ceremony. A suite that passes its own `fetch` never enters the code
+that actually ships: `client.ts` resolves `globalThis.fetch.bind(globalThis)`,
+and every assertion about "what the SDK sends" becomes an assertion about what
+a `vi.fn()` was asked to pretend to send. The two most expensive defects this
+package has had were both invisible to a mocked `fetch` and both obvious to a
+socket:
+
+- `createClient` defaulted to a **detached** `globalThis.fetch`. A real
+  browser's `fetch` is a Web IDL method that throws "Illegal invocation" unless
+  its receiver is the global object. Node's undici does not enforce that check,
+  so every test passed and every browser failed on the first call.
+- A path segment shaped like `../../../admin` reached a real server as a
+  traversal, because the encoding was asserted against a double that never
+  parsed the URL.
+
+So: **if your change is about what leaves the process, test it against
+`test/local-api.ts`.** A double is fine for testing branching, refcounting,
+timers and error mapping, and most of the suite uses one for exactly that.
+
+`test/client.test.ts` carries a test named for this property on its own, so
+that removing it is visible in a diff rather than silent.
+
+## Licence headers
+
+Every source file carries the SPDX header `// SPDX-License-Identifier: MIT` as
+its first line — a `#!` shebang is the only thing allowed above it.
+`test/license-headers.test.ts` asserts this over the whole set, and it takes
+that set from `git ls-files` rather than from a list of directories, so a file
+added anywhere in the repository is swept the day it exists.
+
+## Nothing internal reaches the published bytes
+
+`tsup` bundles `@fleetless/contracts` **into** `dist/index.js` and
+`dist/index.cjs`, doc comments and all, and it writes the path each inlined
+module came from as a comment beside it. A comment written for the people who
+build this is therefore a comment an editor shows to somebody who installed it —
+and for four published versions that included German paragraphs, internal
+defect ids and an internal hostname, none of which appeared anywhere in this
+repository's source.
+
+Write a comment as what the code does for a caller. Never as how the behaviour
+was found, on which machine, under which internal ticket, or in which language
+the team happened to be thinking that day.
+
+`test/published-prose.test.ts` enforces it over `dist/`, `src/`, `test/`,
+`scripts/` and the shipped markdown, and it will tell you which class of thing
+came back and on which line.
+
+## Pull requests
+
+**The public repository is not open yet.** It will be, and this section
+describes how it will work then. Until it exists, send patches and questions to
+<hello@fleetless.dev>. Either way, raise anything that changes an existing
+method signature or what a method sends before you write it, so we can say what
+else has to move with it.
+
+**CI runs on GitLab.** This repository is mirrored from an internal GitLab
+instance, which is where the pipeline that verifies and publishes it lives. You
+will not see a check run on your GitHub pull request; a maintainer runs the
+same checks, and the result comes back as a review comment. Run
+`pnpm typecheck && pnpm test && pnpm run test:pack` yourself before you open the
+pull request and you will have seen everything CI would tell you.
+
+## The CLA
+
+The first pull request you open will ask you to sign a Contributor Licence
+Agreement. It grants Dehne Robotik GmbH the right to license your contribution
+under terms other than MIT in future — that is the whole of what it is for, and
+it is why the project can relicense its own code later without having to find
+every past contributor. It does not take your copyright away and it does not
+stop you from using your own contribution however you like.
+
+## Commit messages
+
+[Conventional Commits](https://www.conventionalcommits.org/en/v1.0.0/):
+`feat:`, `fix:`, `docs:`, `chore:`, `ci:`, `refactor:`, `test:`. A change that
+alters an existing method's signature or what it sends is a breaking change;
+say so with a `!` and a `BREAKING CHANGE:` footer, because it decides the next
+version number.
+
+Everything in this repository is written in **English** — code, comments,
+commit messages, documentation.
+
+## Code of conduct
+
+By participating you agree to the [Code of Conduct](CODE_OF_CONDUCT.md).
+
+## Releasing (maintainers)
+
+See [RELEASING.md](RELEASING.md). The pipeline publishes; `npm publish` from a
+working tree is not how a version gets to the registry.

package/README.md

@@ -12,8 +12,27 @@ behind roles. The SDK covers all of it: datapoints (read, subscribe, recorded
 history), actions, services, publishers, cameras, jobs, assets and URDF, and
 the whole client auth API your own sign-in UI calls. It is framework-agnostic,
 ships ESM and CJS with its own types, and runs wherever a `fetch` and a
-`WebSocket` exist — a browser, a mobile webview, Node 20 or newer, and
-server-side with a server key instead of a user session.
+`WebSocket` exist — a browser, a mobile webview, Node 22 or newer, and
+server-side with a server key instead of a user session. On Node 20 the REST
+half works as it stands, but there is no global `WebSocket` (it is behind
+`--experimental-websocket` there), so anything realtime needs one supplied:
+`createClient({ …, WebSocket: (await import('ws')).WebSocket })`, or the flag.
+Without it, `subscribe` calls `onError` with `no_websocket`.
+
+**The mental model in one paragraph.** A robot runs the Fleetless bridge, a
+ROS 2 node. In the [Fleetless Console](https://console.fleetless.dev) a
+developer picks which topics, services and actions that robot exposes and gives
+each one a stable `snake_case` slug and a role that may reach it. The cloud
+turns those into REST and realtime endpoints. This package is the client for
+those endpoints: you address a robot by its id and a capability by its slug,
+you sign your own users in against your own app's user directory, and you never
+see a ROS name, a topic type or a message definition. Renaming a node on the
+robot is invisible to your app; changing a slug is not.
+
+New here? The [getting-started guide](https://docs.fleetless.dev/getting-started/)
+goes from a robot that has never connected to a value on a page, and the
+[app-auth recipe](https://docs.fleetless.dev/recipes/app-auth/) is the
+walkthrough for every sign-in screen.
 
 ## Why
 
@@ -202,7 +221,7 @@ const grants = await client.auth.listMcpGrants()
 await client.auth.revokeMcpGrant(grants[0].client_id)
 ```
 
-### Running a job
+### Actions
 
 An action is a job with a lifecycle. `invoke` resolves as soon as the job
 exists; feedback, progress and the result arrive over `subscribe`.
@@ -230,6 +249,35 @@ sub.unsubscribe()
 `error.details.running`. A service is the same machinery with a plain result:
 `await client.services.call(robotId, 'set_mode', { mode: 'autonomous' })`.
 
+### Publishers, and no teleop helpers
+
+`publishers.publish` sends **one** message. There is no `startPublishing`, no
+rate helper, no joystick binding and no "hold this value" call, and that is a
+decision rather than a gap.
+
+The safety primitive lives on the robot. A publisher is configured with a
+`timeout_ms` and a failsafe message; if messages stop arriving — including
+because your process crashed, your tab closed, or the network went away — the
+bridge publishes the failsafe itself. Nothing in your event loop has to survive
+for that to happen.
+
+A helper here would move the appearance of that guarantee into a browser, where
+it is not true. So *how often* and *when* to publish is your application's
+decision, made where it can see the user's intent:
+
+```ts
+// A control loop is yours to write, and yours to stop. `speed` is your app's.
+const timer = setInterval(() => {
+  void client.publishers.publish(robotId, 'cmd_vel', { 'linear.x': speed })
+}, 100)
+
+// Stop publishing and let the robot's own failsafe take over.
+clearInterval(timer)
+```
+
+`publish` rejects `publisher_busy` while a different user holds the publisher
+and has not been quiet for its configured timeout.
+
 ### Cameras
 
 ```ts
@@ -250,6 +298,65 @@ await room.disconnect()
 await session.release()
 ```
 
+## Errors
+
+Every refusal arrives as a `FleetlessError` with a stable `code`. Branch on the
+code; never parse the message, which is written for a developer reading a
+console and may change.
+
+`error.details` is typed `unknown`, deliberately: it is whatever the server
+sent, and the SDK does not pretend to have validated it. Narrow it before you
+read a field. `BusyDetails` and `RateLimitDetails` are exported as types, and
+`parameterInvalidDetails` as a runtime schema you can `parse`.
+
+```ts checked
+import { createClient, FleetlessError } from '@fleetless/sdk'
+import type { BusyDetails, RateLimitDetails } from '@fleetless/sdk'
+
+declare function showRunning(job: BusyDetails['running'] | undefined): void
+declare function showOffline(): void
+declare function showNotAllowed(): void
+declare function showRetryLater(ms: number | undefined): void
+declare function showUnexpected(error: FleetlessError): void
+
+const client = createClient({ apiUrl: 'https://api.fleetless.dev', appIdentifier: 'warehouse_dash' })
+const robotId = '4f2c1a90-7b3e-4d51-9c86-0a1b2c3d4e5f'
+
+/** `details` is server-shaped: check the field is there before reading it. */
+const field = <T,>(details: unknown, key: string): T | undefined =>
+  typeof details === 'object' && details !== null && key in details
+    ? ((details as Record<string, unknown>)[key] as T)
+    : undefined
+
+try {
+  await client.actions.invoke(robotId, 'dock', {})
+} catch (error) {
+  if (!(error instanceof FleetlessError)) throw error
+  switch (error.code) {
+    case 'busy':          showRunning(field<BusyDetails['running']>(error.details, 'running')); break
+    case 'robot_offline': showOffline(); break
+    case 'forbidden':     showNotAllowed(); break
+    case 'rate_limited':  showRetryLater(field<RateLimitDetails['retry_after_ms']>(error.details, 'retry_after_ms')); break
+    default:              showUnexpected(error); break
+  }
+}
+```
+
+- **`rate_limited` is surfaced, never retried behind your back.** The SDK does
+  not sleep and re-send. `details.retry_after_ms` carries the wait the platform
+  asked for, when it sent one — read it defensively, since a refusal from an
+  intermediary may carry no `details` at all.
+- **The one retry the SDK does perform is `token_expired`**, and only once: it
+  refreshes the session and re-sends the same request. That refresh is
+  single-flight, so ten concurrent calls meeting an expired token share one.
+- **`command_outcome_unknown` is an honest answer, not a failure.** It means
+  the realtime connection cycled while a command was in flight and the SDK
+  cannot say whether the robot got it. Read the job back by slug through
+  `actions.subscribe` to find out.
+- Some codes never reach the network at all — `invalid_option`,
+  `state_mismatch`, `no_session`, `untrusted_absolute_url`. They are the SDK
+  refusing to send something rather than the platform refusing to accept it.
+
 ## Documentation and help
 
 - **[SDK reference](https://docs.fleetless.dev/reference/sdk/)** — every method,
@@ -270,10 +377,27 @@ await session.release()
 Fleetless is in closed beta. The waiting list is at
 <https://fleetless.dev/#waiting-list>.
 
+## Reporting a security issue
+
+Email **security@fleetless.dev**. Please do not open a public issue for a
+security report. [SECURITY.md](SECURITY.md) says what is in scope here — how
+this package handles tokens, the PKCE verifier and the `state` value — and what
+belongs to the platform instead.
+
+## Contributing
+
+The public repository is not open yet. Until it is, send patches and questions
+to <hello@fleetless.dev>. Read
+[CONTRIBUTING.md](CONTRIBUTING.md) first: it covers the setup, the checks, the
+Contributor Licence Agreement, and the one rule this repository is strict about
+— the auth suites drive the SDK's own `fetch` against a real `node:http`
+server rather than a double, because a mocked `fetch` cannot see the bugs that
+have actually shipped.
+
+By participating you agree to the [Code of Conduct](CODE_OF_CONDUCT.md).
+
 ## Maintainers
 
-Maintained by [Dehne Robotik GmbH](https://dehne-robotik.de). The source
-repository is private and takes no outside contributions; questions and bug
-reports go to hello@fleetless.dev.
+Maintained by [Dehne Robotik GmbH](https://dehne-robotik.de).
 
 MIT licensed — see [LICENSE](LICENSE).