l0ng-ai 91c2cac80d fix(cli): say where a workspace id nobody typed came from ...

`tty7 tab new` in a shell whose workspace has been removed answered:

    no workspace with id 65b90fd4-421f-4cfb-9848-d263c9a80959 on this machine

Nothing in what was typed contains a uuid. `workspace_or_context` falls
back to `$TTY7_WS`, so the id came from the shell — and bare like that it
reads as an internal error rather than something to act on. Every sibling
message in this file carries a hint; this one had none.

Found by running the CLI against a daemon that was not the one my shell
belonged to, which is the same shape as the two cases the comment above
`run --keep` already names: a workspace since removed, or a shell opened
against another machine. That insight was in the source and never reached
the reader.

The id stays whole rather than shortened the way an ambiguity is — it is
the exact string to compare against `echo $TTY7_WS`.

2026-08-16 10:42:03 +08:00

..

tty7-cli

fix(cli): say where a workspace id nobody typed came from

2026-08-16 10:42:03 +08:00

tty7-core

test: keep every setting on the configuration page

2026-08-16 10:32:05 +08:00

tty7-server

fix(resize): defer the reflow to the daemon's Size echo on remote routes too (#632)

2026-08-14 16:02:04 +08:00