Manifest version consistency between Teams Toolkit and Teams App Studio

Goal: keep the Teams app manifest synchronized between local development with the Teams Toolkit extension and the web‑based Teams App Studio so that a repeatable environment uses a single source of truth.

Constraint: the Toolkit creates and watches a local manifest.json but does not ingest changes made in App Studio; App Studio can import the local file via its Import button yet any edits performed there are not pushed back to the workspace, and the Toolkit’s packaged zip must be manually extracted before it can be imported into App Studio, while differences in schema previews can trigger validation errors.

Questions: How can edits made in App Studio be persisted automatically to the local manifest without manual export? Is there a way to configure the Toolkit to accept upstream updates from App Studio during the development loop? What versioning strategy prevents schema drift when both tools are used concurrently?