docs(changelog): record thread-owned terminals (CW-7669) [skip ci]

Fold the desktop-contracts session's lines for 9805a009e8 into 0.10.3:
the Changed entry (called out as breaking for Runtime API clients, since
`/v1/terminal/{name}/*` now answers 410 and `/v1/runtime/info` replaces the
four `terminal_*` flags with `thread_scoped_terminals`) and the terminal
lifetime known limit. Other sessions' uncommitted CHANGELOG text and a
staged skill rename in the shared index are left untouched (committed from
a private index).

Verified: scripts/sync-changelog.sh --check up to date on the committed
pair.

Co-Authored-By: Claude Opus 5.5 <[email protected]>

CHANGELOG.md

@@ -26,6 +26,7 @@ until the matching tag, packages, checksums, and release assets exist.
 
 ### Work in progress and known limits
 
+- **Terminal lifetime:** deleting a conversation does not end its terminal shells; they run until the Engine exits. Scrollback beyond the 512 KiB ring is not recoverable, and an Engine restart loses live shells (reported as a new terminal `instance`).
 - **Codex App Server compatibility:** Codewhale is working toward full Codex
   wire parity on the existing Engine. The current HTTP/SSE Runtime remains
   available; full-tool turns, subscriptions, bidirectional interactions, durable
@@ -190,6 +191,7 @@ until the matching tag, packages, checksums, and release assets exist.
 
 ### Changed
 
+- **Thread-owned terminals (Runtime API, breaking):** Engine terminal shells now belong to the conversation that started them, so two conversations using `term-1` in one folder get separate shells instead of sharing cwd, running command and output. Clients list a thread's shells at `GET /v1/threads/{id}/terminals` and drive one at `/v1/threads/{id}/terminals/{terminal_id}/output|input|resize|kill`; a reset shell, another thread's or workspace's shell, or one from before an Engine restart answers 404 instead of attaching to a same-named shell. The name-addressed `/v1/terminal/{name}/*` routes now answer 410, and `/v1/runtime/info` advertises `thread_scoped_terminals` in place of the four `terminal_*` flags. Client input meets the thread's shell consent and sandbox-reuse guard, and a lone Ctrl-C uses the dock's confirmed interrupt. In the TUI, a new conversation starts its own `term-1` rather than reusing the previous conversation's shell, which the dock still lists.
 - **Brighter terminal working states:** the Ocean palette has stronger accents,
   and active work uses a restrained left-to-right text sweep. Quiet and
   reduced-motion settings keep stable working indicators. The shared

crates/tui/CHANGELOG.md

@@ -26,6 +26,7 @@ until the matching tag, packages, checksums, and release assets exist.
 
 ### Work in progress and known limits
 
+- **Terminal lifetime:** deleting a conversation does not end its terminal shells; they run until the Engine exits. Scrollback beyond the 512 KiB ring is not recoverable, and an Engine restart loses live shells (reported as a new terminal `instance`).
 - **Codex App Server compatibility:** Codewhale is working toward full Codex
   wire parity on the existing Engine. The current HTTP/SSE Runtime remains
   available; full-tool turns, subscriptions, bidirectional interactions, durable
@@ -190,6 +191,7 @@ until the matching tag, packages, checksums, and release assets exist.
 
 ### Changed
 
+- **Thread-owned terminals (Runtime API, breaking):** Engine terminal shells now belong to the conversation that started them, so two conversations using `term-1` in one folder get separate shells instead of sharing cwd, running command and output. Clients list a thread's shells at `GET /v1/threads/{id}/terminals` and drive one at `/v1/threads/{id}/terminals/{terminal_id}/output|input|resize|kill`; a reset shell, another thread's or workspace's shell, or one from before an Engine restart answers 404 instead of attaching to a same-named shell. The name-addressed `/v1/terminal/{name}/*` routes now answer 410, and `/v1/runtime/info` advertises `thread_scoped_terminals` in place of the four `terminal_*` flags. Client input meets the thread's shell consent and sandbox-reuse guard, and a lone Ctrl-C uses the dock's confirmed interrupt. In the TUI, a new conversation starts its own `term-1` rather than reusing the previous conversation's shell, which the dock still lists.
 - **Brighter terminal working states:** the Ocean palette has stronger accents,
   and active work uses a restrained left-to-right text sweep. Quiet and
   reduced-motion settings keep stable working indicators. The shared