Skip to content

The ultimate harness for coding agents and beyond. All your agents. All your machines. One command center. Start with code, then follow your curiosity and build across disciplines: CAD, circuits, robots, games and music.

Device add-ons docs: a device ignores unknown event kinds; a propose with no answer is always OUTCOME_UNKNOWN (#1488)

daniel-auto1ede52277d16
diff --git a/docs/autonomous-device-addons.md b/docs/autonomous-device-addons.md
index 4a4570706..69063b3ae 100644
--- a/docs/autonomous-device-addons.md
+++ b/docs/autonomous-device-addons.md
@@ -150,14 +150,15 @@ device (`BACKPRESSURE`). A proposal not decided within `holdsMs` becomes `expire
stay readable ten minutes; at most 256 are kept, and a proposal still inside the rate window is never
dropped to make room: a new one is refused `BACKPRESSURE` instead.
-**No answer in time.** The CLI waits 5 seconds for the Wi-Fi device service. A `propose` with no answer
-in time is `OUTCOME_UNKNOWN` (504): it may have been sent. Retry with the same `--key` and it is sent at
-most once. A read with no answer is `UNAVAILABLE` (503).
+**No answer in time.** The CLI waits 5 seconds for the Wi-Fi device service, and cannot tell a service
+that is down from one that answered late. So a `propose` with no answer is always `OUTCOME_UNKNOWN`
+(504), even when the service turns out to be down: it may have been sent, and retrying with the same
+`--key` sends it at most once. Only a read (`state`, `proposal`) with no answer is `UNAVAILABLE` (503).
**Errors** (HTTP status): `INVALID_REQUEST` 400, `PAYLOAD_TOO_LARGE` 413, `DEVICE_NOT_FOUND` 404,
`PROPOSAL_UNKNOWN` 404, `MISSING_TARGET` 409, `DEVICE_OFFLINE` 409, `IDEMPOTENCY_CONFLICT` 409,
-`RATE_LIMITED` 429, `BACKPRESSURE` 429, `UNAVAILABLE` 503 when the Wi-Fi device service is not running,
-`OUTCOME_UNKNOWN` 504 for a propose with no answer in time.
+`RATE_LIMITED` 429, `BACKPRESSURE` 429, `UNAVAILABLE` 503 for a read the Wi-Fi device service did not
+answer, `OUTCOME_UNKNOWN` 504 for a propose it did not answer (down or late).
## A device that is a Harness machine
diff --git a/docs/autonomous-device-integration.md b/docs/autonomous-device-integration.md
index 813e5a26e..1183e45c7 100644
--- a/docs/autonomous-device-integration.md
+++ b/docs/autonomous-device-integration.md
@@ -213,7 +213,10 @@ Events are encrypted full objects:
```
Kinds include `receipt.updated`, `turn.started`, `turn.done`, `turn.error`, `turn.summary`,
-`turn.tool`, `agent.error`, `question.open`, `question.close`.
+`turn.tool`, `agent.error`, `question.open`, `question.close`, and with the add-on capabilities
+`addon.proposal` and `addon.republish` ([device add-ons](autonomous-device-addons.md)).
+**A device ignores an event `kind` it does not know**: newer computers add kinds, and an older device
+must keep working beside them.
For an enriched `turn.summary` with resultId/correlation, use that event's fullText exclusively;
never fetch latest recap to identify its result. The [summary contract](autonomous-device-result-correlation.md)