Andrei Eternal fe15bd38de Report the local command working directory in PreToolUse hooks (#57198) ...

## Why

`PreToolUse` hooks receive the host working directory even when a local
`exec_command` call specifies a different `workdir`. This prevents hooks from
seeing the directory in which the command will execute.

## What changed

- Share working-directory resolution between command execution and hook input,
  using the selected environment and the command's `workdir`.
- Report the resolved local directory in the hook input's `cwd`. Keep hook
  processes in the host directory and retain the host `cwd` for remote commands.
- Reject invalid environment selections or paths before running hooks and record
  failures in tool-result telemetry.

## Testing

Add unit and integration coverage for default, empty, relative, and absolute
working directories; Windows path conventions; remote commands; hook denial and
input rewriting; and invalid arguments that fail without running hooks.

GitOrigin-RevId: 97f71f6d3e21a5d95a7abf5384f06f4993241797

2026-10-26 19:11:28 +00:00

..

schema/generated

Add observation-only model request lifecycle hooks (#55144)

2026-10-18 22:43:56 +00:00

src

Report the local command working directory in PreToolUse hooks (#57198)

2026-10-26 19:11:28 +00:00

BUILD.bazel

build: run buildifier from just fmt (#28125)

2026-06-13 21:43:39 -07:00

Cargo.toml

Bind plugin hook approval to plugin contents (#54619)

2026-10-16 14:38:19 +00:00