Loading…
Reference in a new issue
No description provided.
Delete branch "claude/backend-cells"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Two console changes the owner asked for together: #391 and #392.
What changes
The Braid box (#391). One still dot for the Braid server and nothing else: mint green on time, yellow for a late or unexpected answer, stopped live updates or a problem with itself, and red for no answer. It no longer says
Backend down, since a run's backend is not Braid's status. This reverses #387, whose reason was a green dot beside that word.The run bar (#391).
vLLM qwen3.8-27b, for any run, live or finished, with the same dot for how that server answers now and an info hover. A finished run used to lose its Backend and Model cells, because/api/backendslists only live runs.Backend Planning Repair, or have a cell of their own when they use another server or model.GET /api/runs/{id}/backendsis new. A server is degraded when it answers late or wrongly, or does not list the run's model.Capitals (#392). Labels read as they are written, in the console's one label style. The
BRAIDwordmark, the tab title and the top bar's Braid cell keep their capitals, as the owner ruled.Verification
./tools/test.shpasses on the combined tip: 444 backend, 100 UI unit, 38 browser.openspec validate --all --strictpasses. The smoke sims passed on #391 before #392 joined it; #392 has no Python in it.Not proved here
🤖 Generated with Claude Code
Backend downis not Braid's status: a dot for the server, and backend cells that outlive the run #391.eyebrowand five others #392