1097fa3507
A client-callback throw only becomes a JSON-RPC error RESPONSE to the agent's session/request_permission — runScenario itself kept going, so a tolerant agent could treat the error as a denial and the scenario would pass, or worse, record: the impossible click baked into fixture and golden, green on every replay. The mismatch is now captured as a harness error while the agent is answered plain cancelled (a well-defined path it cannot reinterpret), and the step loop rejects the run on it as soon as the in-flight step settles. The spec asserts the rejection instead of the agent-side error echo. |
||
|---|---|---|
| .. | ||
| 2026-06-11-property-based-testing.md | ||
| 2026-06-19-acp-snapshot-tests.md | ||
| 2026-06-19-real-api-e2e-ci.md | ||
| 2026-06-20-remove-redundant-snapshot-log-goldens.md | ||
| 2026-06-22-fork-child-replay-seed-boundary.md | ||
| 2026-06-22-fork-snapshot-scenarios.md | ||
| 2026-06-22-subagent-snapshot-replay.md | ||
| 2026-07-04-hook-snapshot-matrix.md | ||
| 2026-07-04-single-source-acp-replay-config.md | ||
| 2026-07-06-pin-request-header-content-in-one-scenario.md | ||
| 2026-07-08-shared-acp-snapshot-package.md | ||