Eric Traut c03eb20d8d Fix side conversation config inheritance (#22106) ...

Addresses #22101

## Why

Side conversations are ephemeral forks of the active thread, but `/side`
was building its fork config from the app-level config after refreshing
it from disk. If the parent thread had runtime settings that differed
from the current persisted defaults, such as a changed model, reasoning
effort, permissions, reviewer, or fast-mode selection, the side
conversation could start with different behavior than its parent.

## What changed

- Build side fork config from the active parent `ChatWidget` config,
then overlay the parent thread's effective model, reasoning effort,
service tier, and fast-mode opt-out state.
- Forward model reasoning summary, verbosity, personality, web search
mode, and service-tier overrides through TUI app-server
start/resume/fork lifecycle params.
- Add focused tests for parent runtime inheritance, side developer
guardrail preservation, and lifecycle param forwarding.

2026-05-11 09:47:51 -07:00

..

frames

Rename tui_app_server to tui (#16104)

2026-03-28 11:23:07 -06:00

src

Fix side conversation config inheritance (#22106)

2026-05-11 09:47:51 -07:00

tests

api: send hyphenated session and thread headers (#21757)

2026-05-08 17:11:19 +02:00

BUILD.bazel

bazel: use native rust test sharding (#18082)

2026-04-17 23:14:11 +00:00

Cargo.toml

Disable empty Cargo test targets (#21584)

2026-05-07 15:44:17 -07:00

prompt_for_init_command.md

Rename tui_app_server to tui (#16104)

2026-03-28 11:23:07 -06:00

styles.md

Rename tui_app_server to tui (#16104)

2026-03-28 11:23:07 -06:00

tooltips.txt

feat(tui): add configurable keymap support (#18593)

2026-04-28 12:52:25 -03:00