jif 6c4fa86838 Add an in-memory launcher for the message-board MCP server (#58909) ...

## What changed

Expose `launch_in_memory()` and `LocalServer` to run a loopback HTTP endpoint with generated bearer credentials. Runners register a shared in-memory board per session through `add_board(session_id, host)`, using `MessageBoardHost` for membership, clocks, and notifications without a SQLite registry.

The handle exposes the endpoint and authorization header for MCP configuration, including plugin endpoint overrides. Dropping it cancels HTTP and MCP sessions; `shutdown().await` also waits for completion.

## Testing

Extend the parent/child HTTP integration scenario to cover the in-memory launcher, plugin endpoint overrides, host-provided timestamps, authentication and invalid identity rejection, and operation without creating a SQLite board database.

GitOrigin-RevId: e1cae295724a35f4eded290ba8a4e19926b98c13

2026-11-02 15:29:45 +00:00

..

common

Add an in-memory launcher for the message-board MCP server (#58909)

2026-11-02 15:29:45 +00:00

local_board

Add an MCP adapter for message-board tools (#58341)

2026-10-30 13:33:02 +00:00

local_board.rs

Add an in-memory launcher for the message-board MCP server (#58909)

2026-11-02 15:29:45 +00:00