From 4eaf0aae7312728baba0774859bf7fcc3316365e Mon Sep 17 00:00:00 2001 From: Kaoru0822 <208281322+kaoru0822-kitauji@users.noreply.github.com> Date: Sun, 25 Oct 2026 10:14:57 +0000 Subject: [PATCH] docs(browser): fence the dry-run plan example as output text Every JSON block in the scenario contract guide is admitted as a scenario by the product catalog test; the plan is output, not input. Co-Authored-By: Claude Opus 5.5 --- docs/browser-scenario-contract.md | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/docs/browser-scenario-contract.md b/docs/browser-scenario-contract.md index 6ad83a6c98..c78478f7c0 100644 --- a/docs/browser-scenario-contract.md +++ b/docs/browser-scenario-contract.md @@ -94,9 +94,10 @@ It also requires each declared secret's environment variable to be set, which is the rule a capture applies before acquiring a browser. Errors are the same `invalid_request` projection with field paths, under `"error": "Browser scenario validation failed"`. A valid scenario exits 0 -with a compact plan and creates no provider, profile, file or connection: +with a compact plan and creates no provider, profile, file or connection +(output shown for the minimal example above): -```json +```text { "operation": "capture_browser_scenario", "dry_run": true,