jif-oai 06e5dfa4dd feat: return session ID from thread/fork (#21332) ...

## Why

`thread/start` and `thread/resume` already return `sessionId`, but
`thread/fork` only returned the new thread. That left clients to infer
the forked thread's session identity from `thread.id`, which kept the
new `session_id` / `thread_id` split implicit at one lifecycle boundary.
Follow-up to #20437.

## What changed

- Add `sessionId` to `ThreadForkResponse`.
- Populate it from the forked session configuration.
- Regenerate the v2 JSON/TypeScript schema fixtures and update the
app-server docs/example.
- Extend the fork integration test to assert the returned `sessionId`.

## Verification

- Added coverage in `thread_fork_creates_new_thread_and_emits_started`
for the new response field.

06e5dfa4dd · 2026-05-06 12:04:27 +02:00

History

..

schema

feat: return session ID from thread/fork (#21332)

2026-05-06 12:04:27 +02:00

src

feat: return session ID from thread/fork (#21332)

2026-05-06 12:04:27 +02:00

tests

chore: clean up argument-comment lint and roll out all-target CI on macOS (#16054)

2026-03-27 19:00:44 -07:00

BUILD.bazel

feat: vendor app-server protocol schema fixtures (#10371)

2026-02-01 23:38:43 -08:00

Cargo.toml

Refactor config loading to use filesystem abstraction (#18209)

2026-04-17 00:51:21 +00:00