l0ng-ai 3c495e03af fix(cli): say "1 pane", not "1 pane(s)", on the failure lines ...

Three lines still wrote `pane(s)`: the partial-close report, the
hang-up failure, and the orphan note. All three are reachable with a
count of one, and all three are what a reader meets when something has
already gone wrong — a poor moment to look unfinished.

`pane(s)` is the form a codebase uses when it has not decided, and this
one has: the GUI counts through `t_plural` with one/other branches, and
`pane close` narrates a batch only when there is a batch. These were
what was left.

I said in the doctor fix that "1 panes" was the last of these. It was
not — I had swept the success paths and the format strings that spell
the word out, and these spell it `pane(s)`, so the search missed them.

Checked against a live server: "closed 1 pane; 1 could not be closed"
for one, "closed 0 panes" and "2 could not be closed" for the rest.

2026-08-16 06:57:51 +08:00

..

src

fix(cli): say "1 pane", not "1 pane(s)", on the failure lines

2026-08-16 06:57:51 +08:00

tests

fix(cli): stamp panes with the workspace that holds them, not the client's name (#425)

2026-08-09 20:08:03 +08:00

Cargo.toml

fix(cli): submit send enter outside paste bursts (#322)

2026-08-03 16:55:48 +08:00