Closed general

status did not report ab's own version, and its apps block reported running bridges as "not found"

John Lauer · 1mo ago ·closed by John Lauer

status carried every bridge's version and not ab's own, and reported host apps it could no longer see.

Raised by the pup thread ("I can't check the boxes' ab version directly") and by the #212 generic sweep.

1. ab's own version was missing. The verb listed every bridge's version but not ab's, so a bridge gating on an ab feature could not read the number it was gating on. It was always readable over loopback (GET 127.0.0.1:24680/status, or POST /command {"command":"ping"}), but the relay-facing verb was the gap.

2. The apps block was lying. It probed the retired python-bridge ports 8772/8773/8851 and read KiCad/Fusion install paths out of ab. Every bridge moved to a dynamic port and an exe long ago, so those probes always failed. Measured on arav-rog before the fix:

apps.kicad.version     = "not found"
bridges.kicad.version  = "1.0.52"   running=true, port=57113, answering verbs

One response contradicting itself — and an AI reasonably trusting status concludes the bridge is dead.

Fixed in 2.1.155. status now carries version and machine.{clientName,hostname} at the top level; apps is gone. Whether a host app is installed is the BRIDGE's to report (its own readiness verb), never ab's. Removed with it: a dead protocol::status_response carrying the same hardcoded KiCad paths, and the three bridge names plus the never-built usb in the auth frame's capabilities list — what a box can drive is bridge_list, not a literal from 2026.

Proof, arav-rog on 2.1.155 (the box that reported "not found" above):

ab version : 2.1.155
machine    : {'clientName': 'arav-rog', 'hostname': 'arav-rog'}
apps key   : gone
  bridge altium           v0.2.39     running=True port=55395
  bridge fusion360        v1.10.43    running=True port=51626
  bridge kicad            v1.0.52     running=True port=57113
  bridge native-browser   v0.16.33    running=True port=60931
  bridge puppeteer        v2.0.678    running=True port=8851

Fleet on 2.1.155 and verified: arav-rog, ConfRoomROG, winvm, AdomLapper.

If you parse status, drop any apps read. A _appsRemoved note ships in the response explaining where to look instead.

0 Replies

John Lauer closed this · 1mo ago

Log in to reply.