I really liked the original -- mapping to JSON.parse was the clever part.
Using reduceRight eliminated the need to reverse.
Nice! :)

If you're asking this question, you probably have issues with the larger numbers in the submission tests.
Without seeing your code, it's impossible to know.
If you're timing out, it's hard to say whether your approach needs a simple tweak or a complete overhaul.

Quick -- pretend like you're the computer running your algorithm and answer the following:

What's the next smaller number from 90000001 with the same digits?

Do you sense that you're doing unncessary work? Is there a simplification you can do?

If that's no problem,try the same with the following: 912345678?

If these are hard for you to attempt doing by hand using the algorithm you coded -- you should rethink your algorithm.
If that's too much you might try a similar experiment in a debugger, stepping line-by-line and noting where your code is spending its time. Is there any unnecessary/pointless work being done?
If that doesn't help, read the troubleshooting guide available in the codewars docs.

Good luck! IMO it's the challenge of this exercise that makes it worth figuring out.

Excellent points -- I would reinstate the list and the "if q" guard on the append. Particularly after finding this reaffirmation: https://stackoverflow.com/a/2414916

I love this solution; it is among the few for this kata that use functional programming at all. IMO, the lambda syntax in Python as compared to other languages where it is shorter makes it less desirable. I'm no language designer, I believe alternatives were weighed and there's good reason for it being this way.

Among other qualities I appreciate, I like the limited abbreviations. Most solutions (including mine) use single letter variable names; this one uses: KEYBOARD, digit, sequence. It does use "q" and "r" -- for "quotient" and "remainder" -- which I can still appreciate over more generic: i,j,k,m,n,w,x,y,z or names that echo the type like 'str' (ooh, that's the argument to our method.)

I will attempt a kumite/fork to explore a couple ideas. Well-done! 👍

In this latter case with the it works! in the list-comprehension, we have a ternary expression instead of a filter. In the original comprehension, the 'if' at the end is a filter expression that indicates which elements to include.

It took me a moment to think about this -- this was updated to reflect the removal of reduce as a built-in. Now it's in functools.

Thanks. It's really not a big deal, I overengineer sometimes too. I think the wording in Kata prompt certain approaches -- like the graph approach. I try to find novel approaches and this one struck me when I was thinking about properties of triplets.