Allow SDK version pinning for live/published apps

The Problem:

Base44 apps load the SDK dynamically at runtime. This means that when Base44 pushes an SDK update, all live apps are immediately affected — even apps that haven't been modified in weeks or months.

As a result, a production app can break without any action from the app owner. This is especially problematic for:

• Users on vacation or unavailable

• Business-critical apps that require high uptime

• Apps that have been stable and tested but are suddenly impacted by a platform change

The Request:

Introduce one or more of the following mechanisms:

1. SDK version pinning — Allow app owners to lock their live app to a specific SDK version

2. Opt-in SDK updates — Notify app owners of available SDK updates and let them apply the update on their own schedule

3. Staged rollout with a grace period — When a breaking SDK change is released, give app owners a defined window (e.g., 2 weeks) before the update is enforced on live apps

Why it matters:

Users on paid plans (especially Elite) are running real production apps with real users. Platform-level changes that silently break live apps undermine trust and reliability. This feature would bring Base44 closer to the stability expectations of a production-grade platform.