diff --git a/docs/design-plans/2026-04-26-test-oauth-client-interactive.md b/docs/design-plans/2026-04-26-test-oauth-client-interactive.md
index 3798faf..be332b9 100644
--- a/docs/design-plans/2026-04-26-test-oauth-client-interactive.md
+++ b/docs/design-plans/2026-04-26-test-oauth-client-interactive.md
@@ -159,7 +159,7 @@ observable from operator mode.
 ### test-oauth-client-interactive.AC9: TTY discipline, tracing isolation, flag wiring
 - **test-oauth-client-interactive.AC9.1 Failure:** When stdout or stdin is not a TTY, `RealOperator::run_starting` emits the documented error message ("interactive mode requires a TTY …") and exits non-zero before scenario 1 starts.
 - **test-oauth-client-interactive.AC9.2 Success:** All `tracing-subscriber` output goes to stderr; stdout contains only operator prompts, observation lines, and the final report.
-- **test-oauth-client-interactive.AC9.3 Success:** `--scenario-timeout <DURATION>` overrides the 5-minute default; `--negative-trigger-timeout <DURATION>` overrides the 30-second default.
+- **test-oauth-client-interactive.AC9.3 Success:** `--scenario-timeout <DURATION>` and `--negative-trigger-timeout <DURATION>` actually shape orchestrator behaviour. A `FakeOperator`-driven integration test invoked with `--scenario-timeout 1s` observes a positive-trigger scenario record `Errored` within ~1s of the prompt (not at the 5-minute default); a separate test with `--negative-trigger-timeout 1s` against an absence-trigger scenario observes the auto-continue fire within ~1s (not at the 30-second default). A stub that hard-codes the defaults fails both tests.
 - **test-oauth-client-interactive.AC9.4 Failure:** Invalid duration values produce a clap parse error before any pipeline execution.
 
 ## Glossary