The problem is that there isn't really any git branch for the CVP Jocly games. Originally I created these games by directly hacking the library. I have started to backport all that to source code, and the source code for that fork you can find in the jocly hgm branch of the git repository at http://hgm.nubati.net/cgi-bin/gitweb.cgi . But it is far from complete, and in particular it doesn't contain a subdirectory .../res/fairy/wolf. But the library does. For some unfathomable reason the piece that looks like a somewhat demagnified archbishop has become known under the name wolf, and a grep on fr-wolf in the chessbase directory of the library shows that it is used in several of the CVP games under that name. Amongst which Spartan Chess.
I guess that when I did the backporting (as Spartan Chess is one of the games that is already backported) I chose a more sensible name, as the spartan-chess-model.js refers to the 'aspect' of that same piece as fr-proper-cardinal. So there is no collission at the (backported) source level with your wolf piece. I will just have to fix the collision in the library. (But since there seem to be no games that use your new wolf now that you changed Wilde Mirza, there is no hurry for that.)
The Crowned Rook is another problem, though. The master branch of Jocly at github already included a fairy/crowned-rook when I cloned it to create my own branch on top of it. You now made a new one, and the crowned-rook.js file collides with the existing one. By coincidence the *map.jpg files don't. Only Gigachess II seems to use this new crowned-rook, though. So I guess I will just let it use the 'official' one, and make duplicats of the corresponding *map.jpg files with an extra hyphen to let your code use the maps that belong to that shape. If you want to keep your design I recommend you pick another name for it, so that your fork can be merged with the master branch without collisions.
The problem is that there isn't really any git branch for the CVP Jocly games. Originally I created these games by directly hacking the library. I have started to backport all that to source code, and the source code for that fork you can find in the jocly hgm branch of the git repository at http://hgm.nubati.net/cgi-bin/gitweb.cgi . But it is far from complete, and in particular it doesn't contain a subdirectory .../res/fairy/wolf. But the library does. For some unfathomable reason the piece that looks like a somewhat demagnified archbishop has become known under the name wolf, and a grep on fr-wolf in the chessbase directory of the library shows that it is used in several of the CVP games under that name. Amongst which Spartan Chess.
I guess that when I did the backporting (as Spartan Chess is one of the games that is already backported) I chose a more sensible name, as the spartan-chess-model.js refers to the 'aspect' of that same piece as fr-proper-cardinal. So there is no collission at the (backported) source level with your wolf piece. I will just have to fix the collision in the library. (But since there seem to be no games that use your new wolf now that you changed Wilde Mirza, there is no hurry for that.)
The Crowned Rook is another problem, though. The master branch of Jocly at github already included a fairy/crowned-rook when I cloned it to create my own branch on top of it. You now made a new one, and the crowned-rook.js file collides with the existing one. By coincidence the *map.jpg files don't. Only Gigachess II seems to use this new crowned-rook, though. So I guess I will just let it use the 'official' one, and make duplicats of the corresponding *map.jpg files with an extra hyphen to let your code use the maps that belong to that shape. If you want to keep your design I recommend you pick another name for it, so that your fork can be merged with the master branch without collisions.