Figure out inliner/extractor proxy

[terabyte]

Our tenative solution to some of QBT's "UI learning curve" is to use the extractor/inliner to make available a bidirectional mono-repo view of a QBT manifest. This means some users could commit to the manifest history as usual, and push pins, while others might instead choose to clone the monorepo view and treat the entire thing like a big git repo. Git commit, log, and diff would all work normally, and new commits pushed would be automatically extracted back to the normal manifest history.

Inliner/extractor are written, but we need a plan for how to keep these different "views" (branches) in sync, solve races, etc.