manual_tests.run_not_fire_tests

To verify safety rules do not fire when conditions are met, you can run parallel non-fire tests using sub-agents. This approach executes six dedicated tests concurrently to confirm that no blocking hooks fire and the rules queue remains empty.

Parallel non-fire testing is a validation process that executes six dedicated tests concurrently across sub-agents. It confirms that automatic rule evaluations occur correctly without manual interventions, ensuring a clean baseline before firing tests.

You can test DeepWork safety rules across Trigger, Set Mode, Pair Mode, Multi Safety, and Created Mode scenarios by running orchestrated manual tests. These tests use Haiku sub-agents to validate rule behavior across all specified conditions.

Yes, running non-fire tests requires configuring Haiku sub-agents with a maximum of five turns. This specific sub-agent setup ensures proper isolation and validation of automatic rule evaluations without manual interventions.

Checking the rules queue after running safety tests ensures no entries are created when appropriate. This post-run verification confirms that the orchestrated reset flow worked and the rules queue remains empty during non-fire conditions.

Limitations of parallel sub-agent safety testing include strict file edit constraints and a hard limit of five turns per Haiku sub-agent. The tests strictly validate non-fire conditions without performing actual file edits.