This made me think hard about how to avoid my usual slow brute-force frontal assault. I got oh-so-close with a few different approaches, and then finally shocked myself with a one-liner. That never happens! Thanks for the fun challenge!

Thanks for the fun kata. Brings back memories of looking at hex dumps of RPG programs and wondering what in the world they meant.

The description isn't clear. I needed to study the example pretty carefully to figure out what needed to be done. For one thing, it should be clarified that the prime divisor is never added to the element at index 0, despite the fact that 0 % [prime] equals 0.

Here's an example of input whose expected output does not follow the "one vowel per line" rule:
"oGweQFMoJNk KnJLHOtimUtRTu GirCkKZBLIzXtOfTfNvfI h"

If the test conformed to the description, the last line of expected output would be "fTfNvfI h". But the expected output instead puts a newline after the I and leaves h on the last line by itself.

In testing and modifying my code to handle cases like this, I found that it was the space following the I that was triggering the newline. If that space were not there, the last line of the expected output would be "fTfNvfIh". This is not explained in the description.

You should really not mark issues as "Resolved" until they have been resolved. I think you first need to reach a clear understanding in your own mind about the rules for the expected output. Then these rules will be easier to express accurately in the description.

OK, but I saw at least one case where the test did require a new line after the final vowel if there was a space after that final vowel. That should be explained.

Danke gleichfalls!

The description states: "The final result should have exactly one vowel per line." This is clearly not the case in the expected results for many of the tests.

Tip: Read the notes in the "Modulo check confirmation example" very carefully. There is a bit of important information there that occurs nowhere else in the description.

Approved at 7 kyu based on the consensus, but some will have to think a little harder than usual for a 7 kyu. I especially liked the extra information provided as a reward for solving it.

I couldn't get it out of my head

Not gonna lie, I was hoping that this kata had something to do with the Electric Light Orchestra. But I enjoyed it anyway!

What I really like about this kata is the two-part challenge. First you need a winning strategy, then you need to code it accurately. My first two attempts failed for faulty strategy. Thanks for the fun!

As I recall, you click that option to edit and then click on Rank (which is separate from Average Rank). I don't believe it requires any actual editing changes. But as I say, I rarely approve katas, so others will be more familiar with the process.

Thanks, both of you, for the feedback. I generally avoid being the one to approve a kata, because I sometimes miss issues or lesser problems that others catch. But this one seemed definitely ready for approval.

I was actually thinking about a 4 kyu ranking (definitely not 6), but went with 5 for the reason mentioned above and the fact that a 4 would have been out of line with other votes.