monitor-patterns

Wrap the test command with the Monitor primitive and a line-buffered filter, or call monitor_turbo_stream from the shared helper library. Each PASS/FAIL line arrives as a discrete event instead of one buffered stdout dump.

Use Monitor when you need to react to every occurrence of an event, such as each test result or deploy state change. Use run_in_background Bash when you only need a single completion signal with no per-event streaming.

jq is strict and errors on raw control characters embedded in API JSON, and a swallowed 2>/dev/null error leaves the gating variable empty so the terminal-state check never matches. Extract the gate scalar with grep or python json.loads(strict=False) instead.

Yes, the monitor_gh_ci helper polls a branch until CI reaches a terminal state, and monitor_gh_comments streams bot review comments on a PR as they post. Both are sourced from the shared monitor-helpers.sh library.

Avoid Monitor for one-shot lookups like playwright test --list, native blocking commands with clean exit codes like gh run watch --exit-status, non-streaming batch output, and parallel sub-agent coordination, where raw or background Bash is correct.