Neil 9927edd631 fix(ssh): let the host say whether it armed the ready marker (#18802) ...

#18796 made every SSH Codex background launch wait for the shell-ready marker,
but the client cannot see the remote shell. On a host that never publishes one --
fish, sh, Windows, or a relay predating #18796 -- no marker arrives and delivery
falls back at 1.5s where it used to write at 50ms.

The relay already computes whether it armed the marker; publish that as an
optional `shellReadyArmed` on the spawn reply and let the client skip a wait it
now knows is pointless. Absent stays UNKNOWN and keeps the client's own guess, so
an older host behaves exactly as before; false is only ever an answer a host gave.
It rides every reply, false included, or absent would stop meaning "old host".

A host that did not arm the marker did not arm bracketed paste either, so the
released path still submits raw.

2026-09-05 01:34:38 -07:00

..

cli

Shorten orchestration skill description under the Agent Skills 1024-char limit (#18683)

2026-09-04 14:27:07 -04:00

main

fix(ssh): let the host say whether it armed the ready marker (#18802)

2026-09-05 01:34:38 -07:00

preload

fix(ssh): let the host say whether it armed the ready marker (#18802)

2026-09-05 01:34:38 -07:00

relay

fix(ssh): let the host say whether it armed the ready marker (#18802)

2026-09-05 01:34:38 -07:00

renderer

fix(ssh): let the host say whether it armed the ready marker (#18802)

2026-09-05 01:34:38 -07:00

shared

perf(terminal): cheap-tier process inspection for anchored local agent panes (#18780)

2026-09-05 00:57:02 -07:00

types

…