Fixed dropped responses in the Integrations API
A proxy bug could drop or corrupt Integrations API responses; that's fixed, and Playbook automation tools now load content in one step.
If your team connects to SharpOS through the Integrations API, some requests were coming back empty or with corrupted bodies because of how the proxy forwarded compressed responses. That's fixed: responses now pass through cleanly every time.
We also cleaned up how automated writing and audit tools load an organization's Playbook. Instead of several separate calls, they now pull the whole document, its subpages, and the page tree in one step, which makes AI-generated content and audits more consistent.