Updates

Update applications from an immutable, reviewed Core tag or commit. Run the CLI plan first, inspect exact replacements, merge targets, new forward migrations and preserved developer paths, then apply the update.

supacharger coreupdate --plan --ref <tag-or-commit>
supacharger coreupdate --ref <tag-or-commit>

Do not edit exact managed files in a consumer. Put product routes under src/app/(project)/, composition in src/supacharger.adapters/, styling in src/styles/, and configuration in src/supacharger.config.ts.

After updating, review the Git diff and run every post-update check. Review the linked Supabase migration dry run separately; the CLI must not silently deploy hosted database changes. Advance the consumer Core lock only after hashes, tests and release checks pass.