the preloaded section emits warnings to STDERR:

Note: src/main/java/ClassHelper.java uses unchecked or unsafe operations.

This seems to be caused by this line:

class SpecialFileManager extends ForwardingJavaFileManager {

ForwardingJavaFileManager is a generic class:

Class ForwardingJavaFileManager<M extends JavaFileManager>

so the subclass SpecialFileManager is a raw type, hence the warnings. It should either be parameterized itself, or should extend a parameterized version of ForwardingJavaFileManager.

Ruby version kumited, please check and comment or approve.

Missing random tests in Java.

Missing random tests in C#.

typo in the 'Instruction set' section:

Instructions for same ...

should be:

Instructions for Sam ...

I honestly think it's quite an "odd" idea to move this kata to Kotlin (and other languages too) as it completely relies on Java functionality. This is not a Kotlin kata.

TypeScript translation pending, feel free to leave feedback (if there is anything I can do better) or approve if you think it's ready.

I understand almost nothing from the description of this Kata and the examples given just can't make up for the 75% missing explanation. Can someone please explain me what I even have to do for this Kata?

in python, C# and Java, you'll have to manage null/None input too

This is not true for Python. IMO, this requirement should be removed from other languages if it's actually present there.

Ruby 3.0 should be enabled.

"Connecting linked lists" does not feel quite right. To me, that sounds like solver has to connect two linked lists.

Would you consider "Find shared node in linked lists" or something like that?

Python version is broken.

Cases:
'snakecase' should equal 'snake_case'
'urlrouter' should equal 'url_router'
'impl0test' should equal 'impl0_test'
'copyonwritearraylist' should equal 'copy_on_write_array_list'
'impl0test1inst0' should equal 'impl0_test1_inst0'

How is it possible to implement an algorithm for these?

In addition to that, these tests are not specified in the specs.

The error output string should be changed. I was recieving a lot of these types of errors when submitting tokens with integer (rather than the expected string) values:

[Token(chars='12345', type='integer')] should equal [Token(chars='12345', type='integer')]

This made it much more difficult to debug than it needed to be for what I think are obvious reasons.

Cheers