Studio
Plugin HTTP surface
The four endpoints the plugin actually calls.
All under this origin:
•POST /api/studio/pair — exchange a short-lived code for a hashed, scoped token
•GET /api/studio/status — connection + current revision
•GET /api/studio/pull — download the latest revision tree
•POST /api/studio/push — upload Studio-side edits
•POST /api/studio/errors — report script errors from playtest
Tokens are per-project. There is no master key. Pairing codes expire. If you share a code, treat the project as compromised and revoke the connection.