Charlie Marsh 1f0290c607 Broadcast thread section changes to connected clients (#58380) ...

## Why

Clients need to refresh section membership and ordering when another client moves a thread.

## What changed

Broadcast `thread/section/changed` after a successful `thread/section/move`, including moves within the same section. Send the response before the notification, and include `threadId` and the destination `sectionId`, using `null` for removal. Failed moves do not emit the notification.

Add the notification to the protocol schemas, TypeScript exports, and Python SDK models and registry, and document its behavior.

## Testing

Add a WebSocket integration test with separate writer and observer clients covering section insertion, reordering, removal, and a failed move.

GitOrigin-RevId: 128ba7eddc9aae8e3bac766f47e4a2c55c64a6a5

2026-10-30 16:09:46 +00:00

..

schema

Broadcast thread section changes to connected clients (#58380)

2026-10-30 16:09:46 +00:00

scripts

Generate Python SDK types from repository app-server schemas (#44032)

2026-09-09 03:27:31 +00:00

src

Broadcast thread section changes to connected clients (#58380)

2026-10-30 16:09:46 +00:00

BUILD.bazel

Use a dedicated binary for Bazel schema generation (#58083)

2026-10-29 13:37:06 +00:00

Cargo.toml

Keep credentials out of app-server logs (#39993)

2026-08-21 19:04:32 +00:00

schema_generator.rs

Use a dedicated binary for Bazel schema generation (#58083)

2026-10-29 13:37:06 +00:00