Update Vercel Shop

Upgrade the working storefront from the vercel/shop release it is based on to a newer release, one release at a time. Release notes say what changed and when it applies; the template is a reference, not a replacement for downstream code. Base each decision on implemented behavior, not scaffold age.

Pick a mode

Infer the mode from the user's request:

• Audit — read-only comparison; report relevant differences and stop.
• Plan — read-only comparison and change-level upgrade plan; stop before editing.
• Apply — plan, confirm the selected changes, apply them, and validate. Use when the user asks to update or upgrade the shop.

Inspect the project

Read applicable AGENTS.md instructions, project structure, dependency versions, scripts, configuration, and relevant source. Inspect git status and staged/unstaged diffs, including untracked files, before proposing edits. Identify the storefront root; the upstream repository root maps to that root, which is not necessarily the downstream repository root.

Preserve dirty state, merchant design, custom features, integrations, and intentional departures from the template. Never overwrite custom code with template files or reset, stash, commit, or push without explicit permission. Stop if selected work cannot be separated safely from existing edits.

Keep each change within its owner: