Expose publish_base44_app + get_app_publish_status via the MCP

The Base44 MCP today lets my orchestrator edit apps autonomously via edit_base44_app, but every change lands in preview and requires a manual Publish click in the editor UI. At 135 apps across my portfolio, that single click is the largest bottleneck standing between me and fully-autonomous operation.

Requested primitives:

• publish_base44_app({ appId }) — promote the current preview build to production

• get_app_publish_status({ appId }) — returns states such as building, ready, error, with a link to any failing deployment logs

This is low-scope, low-risk, and it directly grows platform usage by removing the last manual gate between orchestrators and live deployments. If only one MCP primitive could ship in the next sprint, it would be this one.

Context: I run ~135 Base44 apps
driven by Claude in Anthropic's Cowork product. Thank you for considering.