Are there plans to support our code mirroring back to a Git repository?

[pbiggar]

A user says:

Here are some things I wanted to ask:
Git: given tools like Git are still used for all non-backend parts of a Darklang application, are there plans to support our code mirroring back to a Git repository? I would like my Darklang "current state" mirrored to a folder in my repo. How updates are merged to the rest of the codebases main branch would be an issue so I imagine a separate branch for this mirror and engineers can merge into their mainline branch as they feel is necessary (though it wouldn't serve a function other than a history of changes that happened within dark).

Frontend Versioning: with feature flags controlling breaking changes in the backend, what strategies are recommended for versioning our application frontends? How do we ensure we can deprecate a feature on the backend and ensure all clients are updated? Are there metrics/logging to show the usage of paths through our feature flags?

Logging: Are there any long-term plans to create a logging dashboard showing traces through the system? Or should we start looking for patterns and permanent solutions in this space now?

Trace Masking: developing with live production traces through the system is truly revolutionary, though I can't help but see this becoming a regulatory issue. Can you share plans for support for field masking/encryption of production data, or rather, shielding information from developers while in the REPL/Canvas?