It is a big challenge for us to keep up with changes in Pathways content and program usage requirements.
The challenge of keeping everything in sync is one of the concerns I had when I implemented the FreeToastHost Pathways support. Given that Pathways "Basecamp" is built on top of a commercial "learning management system" (LMS) that TM HQ is likely paying a good bit for, there are likely a lot of intricacies in that system including logic for who can do what projects... There is only so much that we can realistically replicate in terms of that logic in our code without basically replicating the underlying system (which is not something I want to do). Additionally, the Pathways Basecamp code has access to which TM members have paid for which paths... that is another example of something that we cannot realistically address in FreeToastHost.
Because of that, we do rely on users such as yourself for helping to keep us aware of changes in Pathways as they occur. (thank you for that) Even then, there may be some changes that we cannot fully reflect in FreeToastHost because of the above mentioned challenges. We will do the best we can to support Pathways in FreeToastHost, but it will likely always be a bit imperfect.