Hello
While developing a custom Freshdesk app using the latest Fresh works CLI (v9+); we encountered an issue where context.client appears to be undefined inside a modal launched from the main app interface. 
This happens despite the modal being declared correctly in manifest.json & the parent-to-modal communication setup working as expected in older CLI versions. 
We’re using client.interface.trigger('showModal', {...}) and passing relevant context, but once inside the modal, attempts to call context.client.data.get('ticket') / even simple interface triggers fail with an undefined error. We’ve double-checked our locations, permissions, & whitelisted-domains, and everything seems to be configured correctly.
Checked Freshworks Developer Docs | Use interface methods documentation guide for reference.
Has anyone else run into this issue with context.client scope in modals using the Freshworks CLI v9 or later? As we align our development approach with what is devops in practice rapid iterations; tight feedback loops facing such CLI inconsistencies disrupts the expected efficiency of our deployment cycle. 
Could there be a breaking change / missing compatibility step in the newer CLI version? Any guidance or known workaround would be greatly appreciated.
Thank you !!