wow-debuglisted

# Debug Wow Failures ## Scope gate Use only to diagnose a downstream application's failure; the Wow framework repository and its modules never qualify. Require the failing path to involve Wow, shown by scoped `me.ahoo.wow` imports, `wow-*` dependencies, or explicit failing Wow behavior. Checkout-wide markers, negated/comparative mentions, and generic DDD/CQRS vocabulary do not qualify. Otherwise state that this Skill does not apply and stop using it. Own the complete diagnosis or diagnose-and-fix task. Do not route to another Wow Skill. ## Contract - Keep diagnosis-only requests read-only. - Attempt the narrowest safe, non-mutating reproduction before explaining. If reproduction is unavailable, unsafe, or outside authorization, state that limit and use the strongest available evidence. - Prefer one falsifiable hypothesis over a list of speculative causes. - Compare with a working path in the same checkout. - Do not add retries, relax assertions, or change annotations before proving where the pipeline breaks. ## Diagnostic workflow 1. **Capture**: record the exact command, request, event, test, configuration, log, stack trace, timing, and expected behavior. 2. **Reproduce**: run the narrowest safe, non-mutating reproducer and preserve its exact result. If that is impossible or unauthorized, record the constraint and continue from logs, traces, source, tests, and configuration without inventing a reproducer. 3. **Locate**: use `references/pipeline-map.md` to identify the