Adom Bridge

Verified on ConfRoomROG with ab 2.1.79: a plain notify_user now lands in Hydrogen (ab log: TOAST-MIRROR: plain toast id=toast-probe-279 shown in ah, and John's screenshot of the ralph level=error toast rendered red in ah). Two notes for the record.

1. The remaining gap was Hydrogen's, not ab's. The /ui/toast route documents detail, but ah's hd-toast listener only ever read message, so ab's headline/detail split rendered as a headline with no body. Fixed in Hydrogen 1.0.287 (hydrogen-desktop f379ddc): toastStore carries detail, ToastContainer renders it as a second line, and the listener passes it through. Building now; the preprod runner gains a toast phase (t1: /ui/toast with detail shows both lines; t2: a real ab notify_user shows its body in the page).

2. Level mapping is right: level=error painted the red error toast in ah, which is what the ralph test asked for. It reads at first glance like ah throwing an error, so a plain-toast mirror at level=error will always look alarming; that is the caller's choice, not a defect.

From Hydrogen's side #167/#169 close when 1.0.287 shows the body on a box you can see.

Shipped as 2.1.79 (insiders), commit c5a3344d. Fleet: AdomLapper, arav-rog (boot smoke), ConfRoomROG and winvm (both taken by ah's own update handshake, not by me). Public manifest untouched at 2.1.29.

Proof — ah's DOM, not ab's log

Each leg fires a real notify_user, then asks Hydrogen's own document (POST /eval) what its toastStore rendered:

So: the route is right, the level mapping is right, and a cross-box toast leads with its origin box. test-via-gallia: 62 checks clean on the 2.1.79 relay (its three smoke notifies also rendered, gallia_t65..67).

What this proof is not

Not a pixel. Hydrogen's window was minimized on the test box for the whole run (desktop_find_window puts it at −32000,−32000 — the Windows minimized placeholder), so every hd_screenshot / CDP viewport came back blank. The DOM read is Hydrogen's own truth about what it painted, which is a level above the TOAST-MIRROR log line that fooled #167 — but the human-eyes check is still owed. Leaving this open until John sees one on screen.

Found on the way, filed separately

• #171: after the 2.1.79 apply on AdomLapper the mesh came back without its relay, and settings_set of an unrelated key bounces the mesh.
• The Windows CLI hands a targeted call to the local ab's egress and returns its target_not_found payload as the result instead of falling back to the relay path (cli/src/relay.rs direct_call_target → Ok(v) on any 200). Root of the "directed notify_user says target_not_found while update_status answers" confusion from the #167 close. Noted in #171 as well.

Hydrogen 1.0.287 is shipped (wiki release + insiders manifest) and installed on ConfRoomROG and AdomLapper. Verified through the real path, not the log line: adom-bridge notify_user {title, body} on each box, then a DOM read of Hydrogen's .toast 2.5 s later:

ConfRoomROG: {found:true, hasDetail:true, text:"1.0.287 toast t2 4139 ab body 4139 should show under the headline"} AdomLapper: {found:true, hasDetail:true, text:"1.0.287 toast t2 4142 ab body 4142 should show under the headline"}

So with ab 2.1.79 and ah 1.0.287 a plain toast renders in Hydrogen with both its lines. The preprod runner now has a toast phase that fails the gate if either half regresses (t1 /ui/toast with detail, t2 a real notify_user). Nothing further owed by Hydrogen on #167/#169.

Closing. Re-verified live today on 2.1.114 rather than on the old report, because this issue was once closed on a false log line and that is worth not repeating.

Sent notify_user {title, body} with no buttons to AdomLapper, then read Hydrogen's own DOM back through hd_api POST /eval:

["toast-container svelte-uhnbpr|AL\nPlain toast re-verify\nreverify167-21229",
 "toast toast-info svelte-uhnbpr|AL\nPlain toast re-verify\nreverify167-21229"]

toast toast-info with the probe body, in the receiver's DOM. The evidence is what Hydrogen rendered, not what ab logged.

Two notes from doing it:

• The toast auto-dismisses quickly. My first read was ~3 s later and found an empty toast-container, which on a worse day would have read as "still broken". Poll immediately, or you will retract a working fix.
• The AL prefix on that toast is AdomLapper's identity monogram from #180 stage 2, so that path is confirmed rendering in ah as a side effect.