loop2-stress-test

You can orchestrate Loop 2 stress testing by invoking the tester, evaluating exit checks, and branching execution based on pass or fail outcomes. It coordinates context propagation and manages cumulative history across rounds.

When an adversarial evaluation fails during a stress test, the system guides retreat decisions by clearly presenting options and required actions to the user. It applies to re-tests after Loop 1 retreats, managing reports under the stress test directory.

Idea pressure testing enforces a hard cap of 3 rounds for tracking round progression. It maintains a cumulative history of tester outputs across these rounds to support re-tests and end-to-end orchestration.

Stress test reports and adversarial literature outputs are saved as markdown files under the phase_0_ideation/stress_test/ directory. You run a new round by invoking the idea-pressure-tester and saving the result with a numbered tester report naming convention.

No external dependencies are required to coordinate end-to-end stress testing. The system internally manages context propagation, tester invocation, and user-facing continue or retreat decisions across all rounds without external modules.

You should use a stress test orchestrator when you need reliable coordination of multiple testing rounds, cumulative output tracking, and structured retreat decisions. It ensures end-to-end context propagation that manual testing cannot easily maintain.