Matching, sharedstreets-api, and sharestreets-js

[ian-r-rose]

Somewhat related to #41. I'm reading through some of the sharedstreets org codebase, and trying to wrap my head around the division of responsibilities. This is a bit of a cross-cutting question, so apologies if this is not the right place to ask. In particular, I'm trying to understand the relationship between the sharedstreets-api repo and this CLI tool, as well as that provided by sharedstreets-python:

• Is this library+CLI meant to be complementary to the REST API, an alternative, or something else?
• More specifically, this library seems to provide its own matching implementation. How does that relate to the match API endpoint? Under what circumstances will they give the same results, and when might they be different? If they are different, is there a recommendation for how to choose?
• This is may be more appropriate to ask in sharedstreets-python, but I see that has not had much activity recently: how does that tool relate to this one? The naming of the two libraries suggests that they are simple client libraries, but both seem to have some implementation logic as well.

Any thoughts or pointers towards documentation would be greatly appreciated. Thanks for the hard work!