jif 851d9e95f1 Bind Guardian reviews to the action's target environment (#47630) ...

## Why

Actions targeting a secondary environment could be reviewed with the primary environment's denied-read restrictions. Each review needs the permission context of the environment that owns the action, including when a Guardian session is reused across environments.

## What changed

- Carry `environment_id` through environment-scoped approval requests and their planned-action JSON.
- Select and label permission context using the target environment, explicitly stating when it has no denied-read paths or globs.
- Reject reviews for unavailable target environments and reject environment IDs longer than 256 bytes before Guardian inference, while preserving manual approval routing for oversized IDs.

## Testing

Add coverage for `exec_command`, `apply_patch`, and `request_permissions` reviews switching environments while preserving the existing review prefix. Extend tests for environment-specific restrictions, unavailable environments, action serialization, and the 256-byte ID boundary.

GitOrigin-RevId: ad3292edddb1c6f5b180142c6857cba6f1308328

2026-09-23 19:03:12 +00:00

..

src

Bind Guardian reviews to the action's target environment (#47630)

2026-09-23 19:03:12 +00:00

tests

Preserve Guardian's reusable history prefix across approval requests (#46279)

2026-09-17 18:56:26 +00:00

BUILD.bazel

Add shared Guardian context primitives (#41392)

2026-08-28 19:02:26 +00:00

Cargo.toml

Move trusted tool metadata into shared Guardian context (#43597)

2026-09-07 21:29:31 +00:00