Preserve Runnable Customization

Headless panel startup may scaffold missing files but must preserve existing runnable-owned declarations, components, and styles. Repeated startup must not overwrite customization or recreate obsolete declaration copies. Keep root declarations separate from rendering components and add explicit mappings when new scaffold files are needed.

Philosophy

Starting a runnable must not undo its design or application composition.

Fix

Create only missing scaffold files, preserve existing content, and test repeated startup against customized files.