Repository navigation
Menu, composer and panel fixes from Milo stress run 3 - #159
Merged
Merged
Conversation
…ate to update Milo 0.15.18 runs zcp v9.200.3, whose data console has no /api/summary: its "/" serves the console's page, so the summary read came back 200 text/html, the broker failed it as an unreadable response (internal), and the panel matched the generic "Something went wrong." against its no-reason sentence and told the up-to-date Mate to update, repeating the failure under the list. The broker now reads a 2xx text/html answer as unsupported. The panel leaves an unoffered summary quiet (no error, no retry), says "update the Mate" only for a no-reason failure on a server older than 0.15.13 (the summary's first release), and keeps the summary's failure out of the list's error line.
…s signed in Milo, signed in to Claude, sat under "Sign in inside this Zerops Control Plane" with a full Codex sign-in row beside it (stress run 3): the card read as a sign-in request. The panel now knows the conversation's agent; signed in, the card says "<agent> is signed in", and another agent that only offers a sign-in shrinks to one quiet line with its link. An agent with a sign-in running or further logins keeps its row.
The composer hands its editor one text at a time, the draft or the open question's answer, with the handler that keeps it. The editor wrote the new text in a layout effect but took the new handler in a passive one, so a keystroke between the two (a throttled machine: stress run 3 A +12:45) went to the previous text's keeper: the draft handed back after a question became that question's answer, and a keystroke on a just-opened question replaced the draft. The handler now changes in the same commit, before the text is written.
With ten tabs open the panel's strip cut the left ones off ("…ff", "…les")
with only a fade and a sideways scroll to reach them (stress run 3). The
strip now measures which tabs its edges cut, as it scrolls or resizes, and a
chevron beside it lists them; choosing one opens it, and the strip scrolls it
into view. The vault harness takes ?tabs=many to show ten tabs.
The row's last line held 18 px while the Mate worked and grew to 24 px when it showed "Needs an answer": the marker sat in an inline box on the menu's taller line, so Milo's row went 76 -> 82 px and moved every row under it (stress run 3, +0:31 and +2:27). The status line now holds the other lines' 18 px.
… to the open Mate Stress run 3's reload (+16:58.9) painted every project as its "Review" row alone, then the Mates' menu, then slid down to Milo: - the tree let a project's open changes bypass its unread gate, so with no Mate row yet it drew change-only sections the Mates' menu then replaced. A project's changes alone now draw only once the listing is complete. - the open Mate is found from the listing, which a reload reads after the menu drew; the tree took the late-found Mate for one opened afterwards and scrolled it into view. The Sidebar now says when the route's Mate is still being found, and the Mate a reload opened on is never revealed (openMateReveal).
fxck
added a commit
that referenced
this pull request
Oct 9, 2026
- #159 Menu, composer and panel fixes from Milo stress run 3
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Defects from the recorded live run on Milo (0.15.18), segment B (and A for the composer).
/api/summary; its/answers 200text/html, the broker called it an unreadable response, and the panel told the up-to-date Mate to update and repeated "Something went wrong." under the list. The broker now reads a 2xx HTML answer asunsupported. The panel stays quiet for a summary the console doesn't offer, says "update the Mate" only for a no-reason failure on a server older than 0.15.13, and keeps the summary failure out of the list's error line.Not changed: the "Draft:" flash on send. The rig pastes, waits 300 ms, then presses Enter (
tools/say.mjs). The draft is cleared in Enter's own task.Gates:
node scripts/gate-changed.tsgreen (web 6848, server 337 related cases); web/server/client-runtime typecheck clean.🤖 Generated with Claude Code