`status.update` carries two spellings for the same phase: auto-compaction
emits `compacting`/`compacted`, while manual `/compress` pins `compressing`
for the whole run and always clears it with `ready` from a `finally`
(tui_gateway/methods_session.py:1859-1861).
The desktop dispatcher matched only the auto-compaction pair, so
`$compactingSessions` was never set for `/compress`: no composer busy flag,
no steer guard, no COMPACTION_LABEL hint. Nothing at all is shown while a
multi-minute compress runs, and there is no way to tell whether it finished.
The Ink TUI has matched both spellings since
ui-tui/src/app/createGatewayEventHandler.ts:904; this brings the desktop in
line. Routing `ready` into the `compacted` branch also gives manual compress
the post-compress `hydrateFromStoredSession` refresh added for #97948.
`_status_update(sid, "ready")` occurs in exactly three places server-wide
(compute_host_bridge.py:327, methods_session.py:1861 and :1880), all
compress-related, so it is not a generic high-frequency status.
a59d15a0c8