# Changelog: the Plynth robot kit

## 0.2.2, 2026-10-21

- The client waits out a 429 for you: it sends the call again after its `Retry-After`, up to `wait_429` seconds a
  call (10 by default; 0 raises at once), and a stream's connecting does the same. The conformance check waits up
  to 60, so a busy sandbox slows a run rather than failing it.

## 0.2.1, 2026-10-21

- `GatewayError.retry_after`: the seconds a 429 asks you to wait, from its `Retry-After`.
- No answer raises `URLError`, an `OSError`, never `GatewayError`: a timeout, a cut-off or garbled answer, or a 502,
  503 or 504 that isn't the gateway's own (a proxy's, the site's network's). Reconnect and send again, as the stream
  example does.
- `plynth.hello`'s next step keeps your `--env`.

## 0.2.0, 2026-10-21

- The kit is a package, `plynth`: `plynth.client`, `plynth.conformance` and `plynth.hello`. The old name, `gateway`,
  still works.
- A version, this changelog, a README and the Apache License 2.0. A wheel to `pip install`, and SHA-256 sums, on `/docs`.
- `plynth.hello` checks a key in one step.
- The conformance check reads `GATEWAY_URL`, `GATEWAY_ROBOT_ID` and `GATEWAY_ROBOT_SECRET`, or `--env` with the file
  your company's page gives you. Against the sandbox it uses the sandbox's door and elevator unless you name others.
- Its report records the kit's version, the gateway's release and the API version. It says when the kit answered a
  drill for your robot, and it skips a check your key may not run, saying why.
- The client signs the path it sends, a path in the gateway's address included.
- `plynth.grade`: the sandbox grades your own software on what it saw your robot do, and every check passed gives a
  certificate, sandbox-verified. The client's `test_run=` sends `X-Test-Run`, and the conformance check marks its
  own trips with it, so a building's record shows them as a test and the grade leaves them out.

## 0.1.0, 2026-10-15

- The reference client and the conformance check, as the sandbox's `/docs` first served them.