"Setup needed" badge and locked blocks in the picker

Two safety chips help you avoid publishing blocks that won't render anything for visitors.

"Setup needed" amber chip:
A block ships with a "Setup needed" badge in its header when one of its required fields is still empty. Hover the chip to see exactly which field is missing. Click the block to open the inspector and fill it in.

Examples:
• A Cinema Hero block needs a channelSlug — without one it has no video to feature.
• A Pledge Progress block needs a campaignId — without one it has no goal to track.
• A Live Product Stock block needs a productId.
• A Booking block needs a profileId.

Locked blocks in the picker:
When you open the "+ Add block" picker, blocks that depend on a module the org hasn't turned on show as locked tiles with a dashed border, a lock icon, and a small label like "Turn on Lodging". Click the locked tile to open Settings → Modules in a new tab. Once the module is on, the block becomes available immediately.

This pattern means the picker doubles as a discovery surface — you can see every block the platform offers, even ones outside your active modules, and one click takes you to the on-switch.

Existing pages keep rendering:
If a module is turned OFF after a page already uses one of its blocks, the public site keeps rendering as-is. Gating only affects discovery in the picker, not in-place rendering of existing pages.