reshaped-v3-v4

name	reshaped-v3-v4
description	Migrates apps from Reshaped v3 to v4 breaking API changes. Use when the user asks to upgrade to v4, fix breaking changes, or migrate deprecated Reshaped APIs.

Reshaped v3 to v4 Migration

Apply documented and safe migrations from Reshaped v3 to v4 with minimal edits and explicit reporting.

Scope and inputs

• Canonical migration recipes live in changes/*.md in this skill directory.
• Each file in changes/*.md represents one breaking-change topic.
• Follow documented migration paths from those files first; if there is no automated migration path available and you don't have a high confidence solution – don't edit the code and add this case to the migration report.
• Prefer deterministic, low-risk edits over broad refactors.

Operating rules

1. Confirm migration scope

   • Identify which package(s), app(s), or folders should be migrated.
   • If scope is unclear, ask a focused clarifying question before editing.

2. Build an ordered migration checklist

   • List all available files in changes/*.md.
   • Process them one by one in a stable order (for example: alphabetical by filename).
   • For each change file, determine whether it applies to the target scope.

3. Apply migrations conservatively

   • Use exact symbol/prop matching when possible.
   • Keep behavior unchanged unless the migration doc requires behavior changes.
   • Avoid unrelated cleanup while migrating.
   • Preserve user-authored custom logic and styling intent.

4. Validate after batches of edits

   • Run local checks relevant to the repo (typecheck, lint, tests, build, or targeted checks).
   • If a migration introduces uncertainty, stop and verify before continuing.