aibdd-red-execute

Mapping BDD Scenario steps to step definitions requires loading project arguments and runtime refs, matching each Given/When/Then to boundary handlers, rendering definitions, and executing the acceptance runner to verify a behavior-driven failure.

A legal red in acceptance testing is a failure driven by genuine behavior gaps, not a broken test harness. It enforces red→green→refactor discipline by proving acceptance boundaries are concretely exercised before implementation code is written.

Executing BDD acceptance tests for the red phase involves running the test runner against generated step definitions, classifying failures by legal-red rules, and emitting a behavior test report plus a red handoff for the green phase.

Yes, python3 is required to execute BDD red green refactor workflows. The runner uses python3 to load runtime refs, map DSL steps to boundary handlers, and execute acceptance tests that produce the red handoff.

The BDD test runner stops early when required feature or BDD configuration is absent, or when the active boundary cannot be bound. This guardrail prevents writing step definitions before acceptance boundaries are concretely exercised.

The best way to hand off a failing BDD test to the green phase is to emit a structured red handoff following required schemas, ensuring the failure is classified as a legal, behavior-driven red that green can implement upon.