feat(docsync): docsync-get: CLI to get docsyncs

[robinanterior]

Example:

$ docsync-get typescript/src | jq
{
  "Call": "A full brrr request payload. This is a low-level brrr primitive. The memo key must be generated by the instantiator of this class, and it must be deterministic: the \"same\" args and kwargs must always encode to the same memo key. Using the same memo key, we store the task and its argv here so we can retrieve them in workers.",
  "PendingReturns": "Set of parents waiting for a child call to complete. When the child call is scheduled, a timestamp is added to this record to indicate it doesn't need to be rescheduled. If the record exists but with a null scheduled timestamp, you cannot be sure this child has ever actually been scheduled, so it should be rescheduled. This record is used in highly race sensitive context and is the point of a lot of CASing."
}

[the9000]

I'm approving this, assuming that you will explain the purpose and use of this code better.
For instance, it could work for pure Python modules in Python stdlib:

docsync-get $(python -c "import base64; print(base64.__file__)") b64encode

[robinanterior]

I'm approving this, assuming that you will explain the purpose and use of this code better. For instance, it could work for pure Python modules in Python stdlib:

docsync-get $(python -c "import base64; print(base64.__file__)") b64encode

discussed offline: misunderstanding arose from my use of the implementation filename in the example docstring. Changed, to avoid this happening again. Ftr it doesn't take code as input, only source files.

---

sorry this was a different quote--the misunderstanding here was the purpose of the tool , operating only on explicitly defined comment tags, not generic code.