Antithesis Setup

Purpose and Goal

Scaffold the antithesis/ harness needed to bring the system up in Antithesis in a mostly idle, ready state.

Success means:

• antithesis/config/docker-compose.yaml exists and required SUT images are referenced with build: directives
• snouty validate on antithesis/config/ succeeds
• the SUT dependency graph includes the relevant Antithesis SDK where assertions or lifecycle hooks will run
• at least one minimal bootstrap property exists in a simple SUT path and is expected to show up in the first Antithesis run
• The harness is ready for the antithesis-workload skill to add or iterate on test templates, assertions, and workload code
• If the user asks to submit or launch a run, use the antithesis-launch skill — do not run snouty run directly

Prerequisites

• Research artifacts required. Before proceeding, check whether antithesis/scratchbook/ exists and contains research output (at minimum sut-analysis.md and deployment-topology.md). If the scratchbook is missing or empty, stop and warn the user: