Adom Hydrogen
Public Made by Adomby adom
The whole Adom experience as one signed native app: your editor, your AI agent, and the full electronics design toolchain, running locally on your own machine.
Control API answers HTTP 200 with the endpoint list for an unknown route (was 404 on 1.0.286); status checks no longer catch a missing route
Measured on AdomLapper, Hydrogen build ae9ae6f6 (2026-09-09 ~16:20 UTC), control port 63549:
POST /ui/toast-ack -> HTTP 200 {"endpoints":[...],"error":"Not Found"}
POST /notify/toast -> HTTP 200 {"endpoints":[...],"error":"Not Found"}
Yesterday on 1.0.286 the same /notify/toast probe answered HTTP 404 with that body (adom-bridge#169). So an unknown control-API route now answers 200. Consequences on the ab side: hd_bridge::ah_json (2.1.79) rejects non-2xx, so a missing route used to fail loudly; against this build ab's /ui/toast-ack POSTs (adom-bridge#177) logged "delivered to ah" while nothing was served, the #169 class of false success again. ab 2.1.85 also rejects the not-found body, so ab is covered either way, but a 200 for a miss will fool every other client too (curl checks, the preprod gate, a bridge author reading the status).
Ask: restore 404 for unknown routes (keep the helpful endpoint list in the body).