ADR-0025 introduces per-scenario schema isolation via the BDD_SCHEMA_ISOLATION env
var. CI was running without this flag, causing scenarios to share the public
schema and pollute each other's state.
Observed flakiness: identical code passes in workflow run #605 and fails in #606
on TestAuthBDD/User_completes_password_reset, JWT_token_validation, etc.
Per ADR-0025 audit (PR #24): schema-per-scenario infrastructure is fully
implemented but disabled by default (opt-in). Enabling it in CI should resolve
the flakiness without code changes.
Diagnosed during the autonomous trainer day (2026-05-03) after observing #605
PASS / #606 FAIL on the same SHA.
🤖 Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
- Changed GITEA_REPO from 'DanceLessonsCoach' to 'dance-lessons-coach'
- Updated workflow comment to use kebab-case
- Aligns with module name changes from previous commits
This ensures the CI/CD workflow correctly references the repository
using the new kebab-case naming convention.
Refs: #ci-cd, #kebab-case, #repository-naming
