It's safe to assume that CV inputs would be used in every patch you see. What may not be so obvious is that you're not working with inputs directly. Instead of that OWL patches use parameters, which can be mapped to an actual ADC input or set by MIDI. This allows running patches on different hardware that has different number of inputs/outputs.
So in a typical patch you'll see something like
registerParameter(PARAMETER_A); in patch constructor. Then in processAudio callback current value would be read like
This is the software side of OWL patches, you can use it to build them without the web patcher.
Parameters order depend on device where patch runs, i.e. on Lich A-D are inputs, F & G are outputs. This is for compatibility with original OWL pedal that had parameter E as expression pedal input. Some devices (Magus) have parameters that can be set as inputs or outputs in software, because it's using an external chip that supports this kind of direction remapping. "LFO>" has ">" as a shortcut for setting parameter on output. It doesn't matter on Lich as parameters directions are fixed there.
If you want to have a look at code that manages UI specifically for Lich, it's in firmware side of OWL here . But you don't really need to understand that to write patches, because your code would only interact with things from OwlProgram repo.
Hope that helps!