From 31201f4a96f4306328a1e8d57ddda88cbe5c6cb6 Mon Sep 17 00:00:00 2001 From: Dotta Date: Wed, 30 Sep 2026 15:46:28 -0500 Subject: [PATCH] docs(runner-e2e): correct trusted board caller identity Co-Authored-By: Paperclip --- tests/runner-e2e/FIXTURES.md | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/tests/runner-e2e/FIXTURES.md b/tests/runner-e2e/FIXTURES.md index 675a56b5df0..756d35ceb21 100644 --- a/tests/runner-e2e/FIXTURES.md +++ b/tests/runner-e2e/FIXTURES.md @@ -382,8 +382,9 @@ The server reserves it under the run-row lock before dispatch, uses an earlier or different caller intent, an earlier uncorrelated Stop, or a terminal run without that same reserved intent. Malformed UUIDs return HTTP400. Repeating the same UUID from the same board actor is idempotent. A different -actor receives HTTP409; local trusted board uses an explicit null user ID. Default clients may omit the field; they -preserve and join an existing reserved intent rather than overwrite it. +actor receives HTTP409; local trusted board uses the `local-board` user ID. +Default clients may omit the field; they preserve and join an existing reserved +intent rather than overwrite it. The denial fixture generates its UUID before observation, retains it in `paperclip.e2e.copilot-pre-stop-observation.v2`, and requires the same intent in