fix(scripts): --check reports real divergence instead of calling all 46 components "modified"

[os-zhuang]

--check was structurally incapable of telling you anything. The heuristic:

const isDifferent = lineDiff > 10 || localContent.includes('ObjectUI') || localContent.includes('data-slot');

Every synced file carries the ObjectUI header this script prepends, so the second clause was true for all 46 tracked components. --check reported the entire set as "modified", every run. That is the same as reporting nothing.

Using the primitive #3035 already built

localOnlyLines is directional — lines in the first argument the second lacks. Calling it both ways answers the two questions that actually decide whether to sync:

• what would a sync destroy? → localOnlyLines(local, upstream)
• what would it gain? → localOnlyLines(upstream, local)

That replaces the heuristic and splits the old "modified" bucket into the two states that need different actions:

	meaning	action
↑ outdated	upstream moved, no local edits	safe to sync
⚠ modified	local edits present	--update refuses

Because --check and the write guard now call the same function, the counts --check shows are exactly the counts that will stop a write.

What it says about this repo right now

✓ Identical: 29    ↑ Outdated: 0    ⚠ Modified: 17    ● Custom: 2

Zero outdated is the headline. Every component where upstream has moved also carries local edits — so there is currently no component --update-all could touch without deleting something. It has no safe work to do at all. That was completely invisible under the old output.

The summary also names the components per bucket with their counts, so triage doesn't need 46 --diff runs:

These carry local edits a sync would delete:
  badge(4), calendar(7), chart(11), command(35), context-menu(2), dropdown-menu(2),
  form(1), hover-card(1), menubar(2), popover(1), select(32), sheet(4), sidebar(24),
  slider(4), sonner(2), table(17), tooltip(1)

Verification

Against the live registry:

• Counts reconcile: 46 tracked = 29 identical + 17 modified; +2 untracked files on disk = 48 local components
• Per-component numbers match the fix(scripts): shadcn-sync refuses to silently delete local edits, and compiles the package after it writes #3035 guard that enforces them (command 35, select 32, sidebar 24 …) — same function, both sides
• The outdated bucket is the one real traffic never exercises (it's 0), so I tested it by deleting a line from an identical component (separator). It flips to ↑ 1 upstream line(s) to pick up — safe to sync and the summary offers the exact --update separator command. Restored after.
• lineDiff had no consumers outside the function that produced it
• --list, --diff, --update, and both the fix(scripts): shadcn-sync rewrites the registry paths Shadcn actually serves, and refuses to write a file when it cannot #3033 unmapped-path guard and fix(scripts): shadcn-sync refuses to silently delete local edits, and compiles the package after it writes #3035 local-edit guard regression-checked
• --check stays exit 0 — it's a status report, and 17 locally-modified components is the steady state here, not a failure
• eslint clean; no component file changes

No changeset — tooling only.

🤖 Generated with Claude Code

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

1 Skipped Deployment

Project	Deployment	Actions	Updated (UTC)
objectui	Ignored		Jul 30, 2026 1:54pm