Kimi Code runs in a crystl shard with its own model selection, activity
visibility, and real approval cards for its tool calls. Crystl treats its
compatibility as partial because its hook surface can only deny, and because
transcript reading and resume by id are both still unwired.
The profile describes what crystl has tested; it never supplies a command,
hook script, or launch setting. Those remain local to the Crystl installation.