What problem does it solve? Running the Insight deployed-stand test suite requires correctly bringing up a seeded compose environment, aiming pytest at the right stand, and distinguishing environment failures from real product defects — mistakes in any of these produce misleading failures that look like product bugs. ## Core Features & Use Cases - Stand lifecycle management: Bring the stand up with ./dev-compose.sh test-stand up, re-seed it, and tear it down with volume removal as the only reset mechanism. - Run targeting: Aim a test run at a local or remote stand via --base-url and --stand-manifest, including the localhost/TLS constraint that prevents silent session-cookie loss and login loops. - Failure triage: Diagnose stand-versus-product failures using the symptom table covering manifest errors, capability skips, scratch-row leaks, and gateway preflight aborts. - Use Case: When test-stand up fails or the suite aborts with UsageError: stand manifest unusable, use this Skill to identify whether the stand was seeded incorrectly and re-seed it before re-running. ## Quick Start Ask the assistant to bring the Insight test stand up, seed it, and run the stand test suite, then triage any failures.