Wanted to convey a msg to author/contributors and/or reviewers tbh

But I never meant that

I believe this comment could have focused more on conciseness, especially when conveying a clear message to future solvers.

Okay, i think it must be crystal clear that after every mistake Alex has to redo the failed kata solution .. Thus, consumes more 6 minutes for next trial! Hence, only after successful submission of each kata we can mark it solved and subtract calculated time for this particular kata from the total time provided!
Shouldn't the description be that clear?

Guys, the kata is marked as FUNDAMENTALS and Ranked as 7 KYU. Isn't it?

Being tricky by hiding important info for solving the challenge is different from making the challenge more complex by racking up complexity & difficulty like utilizing different data-structures and/or algorithms for the sake of solving the problem and being really trained on PROGRAMMING.

Brevity is different from conciseness.

Maybe it can be a fit for PUZZLES. But IMHO making the description clear is the way to go!
Think of it as a task handed/provided to you in a day-to-day job/work on a task management tool like Jira for instance, would you like to get your tasks described that way?
People are here to practice programming I swear, Ain't they?!
At least this is the fundamental and principal and main and master and ultimate goal. Then, whoever wants puzzling should visit the relevant space/tag/criteria on-purpose and expect this kind of tricks and be on their own, shouldn't they?

Please review this and LMK your thoughts =)

Kind Regards,

BTW, the kata is great. Fun, well-designed, well-solved, and well tested. I liked it so much! Just like it to be perfect and help future folks avoid questioning themselves and think that tests are written in a wrong manner or mistakenly!

Once again convinced that regex patterns are powerful instrument

Approved

python new test framework

Nice Kata, worth the time I spent on it. Thanks to everyone who contributed.

added

if doing a kata wrong counts as doing a kata then yes, you're right.

I think that could be more clear in the description.

Pleasantly tricky. Nice kata!

maybe i'm not understanding the kata right.
I don't get how 6 katas in 60 minutes can afford 2 mistakes as is seen in one of the tests in rust.

text output floated in tests (Golang):

With numberOfKatas = %!k(int=11), timeLimit = 120

I don't why but i think this kata should be at least 6 kuy, it took me longer than others 7 kuy's.