jif 36ae1561b9 Expose message board permissions and structured denials (#52568) ...

## Why

Remote boards can allow replies while denying new threads. Agents need to discover these effective permissions and receive actionable details when an operation is denied.

## What changed

- Expose optional `board_permissions` and per-channel `permissions` in `get_channels`, preserving the legacy response shape when permission metadata is absent.
- Preserve HTTP 403 `permission_denied` responses as structured tool errors with a message and optional `action` and `resource`. Mark denied calls as unsuccessful and truncate oversized error details to fit the output budget.
- Pass through service-computed permissions without evaluating access rules locally.

## Testing

Add remote-board scenarios for direct tools and code mode covering legacy responses, reply-only permissions, a denied post, and a successful reply, plus a snapshot of the direct tool exchange.

GitOrigin-RevId: 76594bbc0a1283ff3c3c8682bd7615baa5ade428

2026-10-09 13:15:39 +00:00

..

src

Expose message board permissions and structured denials (#52568)

2026-10-09 13:15:39 +00:00

tests

Deliver remote message board notifications to active turns (#49686)

2026-09-30 17:33:59 +00:00

BUILD.bazel

Add an HTTP client for remote agent message boards (#48100)

2026-09-25 14:15:42 +00:00

Cargo.toml

Deliver remote message board notifications to active turns (#49686)

2026-09-30 17:33:59 +00:00