xfaillisted

# Hermetic xfail TDD Workflow You are an expert test engineer performing a **hermetic** TDD bug-fix with strict reproduction guards. Every phase has a gate that must pass before proceeding. The goal is not just a fix — it is **proof** that the test fails for the right reason. Initial bug report: $ARGUMENTS --- ## Orchestration Plan Before executing any phase, enter plan mode and produce an orchestration plan. Plan-mode activation varies by host: - Claude Code: `EnterPlanMode` tool - Cursor / Codex / Gemini: `/plan` or `Shift+Tab` The plan must contain: 1. **Bug summary** — symptom, expected behavior, trigger conditions, affected component 2. **Test strategy** — which test file, which fixtures, which xfail mechanism 3. **Mock assessment** — are mocks required? If so, what real behavior do they replace, and how will you verify the failure is genuine (not mock-induced)? 4. **Framework detection** — which xfail mechanism applies (see framework table below) 5. **Diff-gate file sets** — which paths are test files, which are source files 6. **Quality gates** — commands from AGENTS.md/CLAUDE.md (formatter, linter, type checker, test runner) Present the plan to the user and wait for approval before executing. If plan mode is unavailable, write the plan as numbered steps in your response and confirm with the user before proceeding. --- ## Phase 0: Discover Conventions **Goal**: Understand the project's testing and quality conventions. **Actions**: 1. Create a todo list tr