Ruslan Nigmatullin 1f54496c48 app-server: expose loaded thread status via read/list and notifications (#11786) ...

Motivation
- Today, a newly connected client has no direct way to determine the
current runtime status of threads from read/list responses alone.
- This forces clients to infer state from transient events, which can
lead to stale or inconsistent UI when reconnecting or attaching late.

Changes
- Add `status` to `thread/read` responses.
- Add `statuses` to `thread/list` responses.
- Emit `thread/status/changed` notifications with `threadId` and the new
status.
- Track runtime status for all loaded threads and default unknown
threads to `idle`.
- Update protocol/docs/tests/schema fixtures for the revised API.

Testing
- Validated protocol API changes with automated protocol tests and
regenerated schema/type fixtures.
- Validated app-server behavior with unit and integration test suites,
including status transitions and notifications.

1f54496c48 · 2026-02-18 15:20:03 -08:00

History

..

schema

app-server: expose loaded thread status via read/list and notifications (#11786)

2026-02-18 15:20:03 -08:00

src

app-server: expose loaded thread status via read/list and notifications (#11786)

2026-02-18 15:20:03 -08:00

tests

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

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

BUILD.bazel

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

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

Cargo.toml

feat(app-server): experimental flag to persist extended history (#11227)

2026-02-12 19:34:22 +00:00