l0ng-ai ed29cdce47 docs: a restored pane is a resized pane, as far as capture is concerned ...

`--scrollback`'s help said the flag makes no difference "for a
never-resized pane", and the reference said the same. Both are wrong for
the panes where the difference matters most.

I killed a daemon under a running GUI, watched it come back, and captured
a pane that had `RESTORE-MARKER-7788` in it. Plain `capture` answered with
two lines — the restore banner and a prompt — while `--scrollback` had the
marker and everything around it. Nothing had been resized.

`ReplayRing::seeded` ends with `resize(size)`, deliberately: the restored
screen is replayed at the size it was recorded at, and the new shell
writes at the size the pane came back as. When those differ the restored
screen is sealed into an earlier segment, and the default capture cannot
see it.

That is the agent-facing primitive answering "almost nothing" for a pane
that kept its screen, with the help explaining that this only happens
after a resize. Both now say restores count, and say what a plain capture
looks like when it does.

`resize` returns early on an unchanged size, so a pane that comes back the
same shape really does keep one segment — the test covers both sides of
that, which is the part the wording turns on.

2026-08-16 11:05:39 +08:00

..

src

docs: a restored pane is a resized pane, as far as capture is concerned

2026-08-16 11:05:39 +08:00

tests

test(e2e): pin the tree and the registry agreeing under a race

2026-08-16 07:55:15 +08:00

Cargo.toml

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

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