I got the chance to investigate the constant schedule issue and it was a very subtle bug. I just pushed a fix for it:
… and verified that it works after it’s implemented:
Give it an hour or two for the change to percolate through all of our integration tests and then you should be able to get it on your end with the versioner component.
For the question about whether to use detailed objects in your standards library (eg. schedules embedded in the program definition) or use abridged objects (eg. schedules referenced by identifier in the schedules folder), it really depends on how extensive of a standards collection you are trying to build and how/if you want to distribute it.
If you just want to create a few programs that are easy to share individually with other people, you might as well embed everything in the program JSON so that there’s only one file to share and there’s no risk of people missing a referenced file. This is why this is the default.
However, if you are trying to build a whole collection of standards and you plan to re-use the same schedule across several programs, you might want to just define it once in your schedules folder and have all of the other programs reference it by identifier (using abridged programs). This makes it easier to change that one schedule later and have all of the referenced programs updated. One thing to be aware of along these lines is that, when schedules are embedded under a program, they become specific to that program. So schedules that are embedded like this will not show up as their own element within the schedule library (they only exist within the ProgramType object in the programs library and, if you want to grab that individual schedule and use it elsewhere, you have to deconstruct that ProgramType). So this may be another reason why you want to use abridged programs. But just bear in mind that abridged objects can make it difficult to share your standards so, if you want to share or distribute standards in an abridged format, you should probably zip your whole standards folder.