fix: v2.5.11 — the commit box wraps only when the panel is narrow

The message keeps the row with the commit, Stage all and Unstage all
buttons while there is room (a 50/50 split, a full-width panel); in a
narrow panel the buttons wrap under it instead of squeezing the message
to a few characters. Client 1095/1095 on the committed tree.

docs/LANES.md

@@ -733,9 +733,10 @@ in every panel narrow enough to sit beside a console.
 **Per-file writes are the panel's, per-repo writes are the git bar's.** Staging
 one file means nothing unless a commit can take the index as it stands, so the
 overview grows a commit box the moment anything is staged — above the list and
-pinned while it scrolls, on ONE row with a **Stage all** that stages every listed file
-the index lacks in one call and an **Unstage all** that unstages every staged one — it sends
-`only: "staged"`, never `add -A`, and it is absent with a clean index because
+pinned while it scrolls: the message (and its suggest button), the commit button, a **Stage all** that stages every listed file
+the index lacks in one call and an **Unstage all** that unstages every staged one — one row when the
+panel has room, the buttons wrapping under the message when it is narrow. The commit sends
+`only: "staged"`, never `add -A`, and the box is absent with a clean index because
 there is nothing it could mean. A file you never want committed (a local note, a scratch folder) can be marked **Never stage** (its row's eye-off button, or right-click): **Stage all** and a folder's stage button then skip it, the row is struck through, and the file is drawn orange in the Files tree (`--kept`, apart from the amber of a modified file). The list is kept in this browser per workspace (`agenthub.changes.neverStage.<lane id>`) and git is never told — nothing is written to the repo, and the file's own Stage still works. It is the dashboard's ONLY commit: the git bar
 above it has none, so no click can sweep the rest of the tree in with `add -A`. **Discard** is the one
 irreversible action in the panel: it asks twice in the UI, and the server