1. Is there a way to synchronize the TH1 scripts that define the ticket UI?
2. If not, should there be?
3. If not, is there documentation that describes unambiguously what you do and do not get locally when you do fossil sync vs fossil sync --verily vs fossil clone?
4. If not, should there be?

Context:

I was surprised when neither fossil sync nor fossil sync --verily pulled down changes I had made on the remote to the ticket UI TH1 scripts. When I do a sync operation on a DVCS, I expect to have everything I need locally to be productive while offline. In this case, that expectation was not met because I was missing the needed configuration to create tickets that conform to the remote's ticket format.

After the above surprise, I tried making a fresh clone, and that new clone did indeed have the updated ticket UI. I searched through the forums and documentation to see if there is any way to sync the ticket UI settings without cloning. I found nothing. I realized it would be very helpful for me to have a document that lists exactly what can and cannot be synced, and how.

Or perhaps this documentation already exists, and I merely failed to find it.

Yes fossil configuration pull ticket was exactly the thing I was missing. Since configuration is not versioned, it makes sense that it doesn't get synced with fossil sync. I was just unfamiliar with the configuration command (I think I had it mixed up with the settings command).

Thanks for the help!