migration-planninglisted

# SpielOS Migration Planning Preserve the owner's useful system while translating and improving it for the current SpielOS schema. A source may be an older SpielOS home or any collection of repositories, files, workflows, prompts, templates, galleries, applications, integrations, and assets. ## Preserve scope and authority Separate three authorities: 1. read-only discovery; 2. writing a migration plan; 3. executing transformations, copying secrets, installing, deploying, or calling external services. Authorization for one does not imply the next. If the owner asks only for a plan, inspect read-only and write only the requested plan artifact. Do not copy, move, rename, rewrite, delete, install, activate, publish, deploy, or test live connections. Treat source projects as protected unless the owner explicitly authorizes mutation. Do not assume a named source exists. Resolve its exact path or URL first. When it cannot be found, state that plainly and make source resolution the first gate; never fabricate an inventory. ## Suggest migration without hijacking onboarding When company state has no active Goal, make a short optional suggestion: if the owner already has useful work elsewhere, it can be inventoried and migrated. Then return to the owner's intent. Do not turn every fresh-home conversation into a questionnaire or create a Goal merely to discuss migration. Recognize ordinary owner language such as “my workflow is here,” “the templates are in that folder,” or “o