Thanks, that’s helpful regarding replies vs comments and Meet with Apple. Just to clarify, my concern is not a generic “will App Review like my app?” question. I’m trying to verify one specific distribution boundary before finalizing the onboarding flow: whether a sandboxed Mac App Store app may include its own pre-signed .mcpb Desktop Extension as a bundled resource and, after an explicit user action, open that resource using standard macOS APIs so Claude Desktop presents its own native installation and consent UI. The app would not silently install anything, modify Claude’s configuration, automate its UI, download executable code, or bypass user consent. I’ve already submitted the same narrow question to Apple Developer Support. I’m mainly trying to determine whether this pattern is something Apple has previously accepted or whether there is a specific guideline that would prohibit it.