The current workflow is described here: https://github.com/ricardoquesada/creator_to_cocos2d
but we are working on polishing it. the idea is that it will be built-in in Cocos Creator. Kind of "Export -> cpp" and wiill generate all the needed files.
Not sure. I will need more info.
I'm not doing anything special in my example:
mmm... wait. I think you are exporting the assets with this:
$ ./convert_fire_to_json.py --cocospath creator/assets --creatorassets creator_project/temp creator_project/assets/*.fire
so, all the assets generated by the script have the "full path" embedded in them.
If you add your own assets in that directory, they won't be found automatically.