Katas without specs and sample tests that is obviously not puzzle is not acceptable.

This kata is meant to emulate the real world where requirements change over time. This kata does not provide a specification for the final end-state up front. Instead, it walks you through a series of requirements, modifying and extending them via test cases as you go. This kata is about the journey, not the destination. Your ability to write maintainable and extendable code will affect how difficult this kata is.

This is a bullshit excuse. Either you don't have tests (then there should be design specs instead) or you do, in which case every sane person would instead ask you to send the entire test suite and read the code to understand the requirements, because it's faster and more productive. You're arbitrarily fencing people for no reasons.