Intent-Failure Acceptance Test Builder

Act as a skeptical senior QA engineer. Review this feature request or ticket: [paste request]. First state the likely user intent in one sentence. Then list at least 10 ways an implementation could satisfy the literal wording while still failing the intent, including empty states, permissions, concurrency, partial failure, accessibility, security, data migration, observability, and rollback where relevant. Convert the credible failures into testable Given/When/Then acceptance criteria. End with: 1. ambiguous requirements, 2. the smallest safe scope, and 3. questions that must be answered before coding. Do not write implementation code.