… compiles the package after it writes (#3035)

#3033 stopped the sync writing unresolvable import paths. It did not make
`--update-all` safe to run: the other failure mode is overwriting local
edits, and I was wrong about how that shows up. I expected a loud type
error. It is silent.

`command.tsx` is the worked example. It carries local additions upstream
has never had — a `sr-only` `DialogTitle`/`DialogDescription` on
`CommandDialog` (Radix requires an accessible name) and `contentProps`,
which is the ADR-0054 C4 testability contract letting callers attach a
stable locator to the dialog element. Syncing it deletes 38 lines,
removes both, and **type-checks clean**, because upstream drops each
addition together with its usages. Nothing downstream notices.

So two layers, not one:

**Refuse before writing.** Any line the local file has that the incoming
version does not is reported, and the write is skipped. Comments count —
a comment explaining why we diverged is exactly what must not evaporate.
`--force` overrides. Measured across all 46 registry entries this
discriminates rather than crying wolf: 29 have no local-only lines and
sync cleanly, 17 are protected. `--update-all` now reports skipped
separately from failed.

**Compile after writing.** `--update` and `--update-all` then run
`pnpm --filter @object-ui/components type-check` and say plainly whether
the package still builds, with the rollback command on failure.
`--no-verify` skips it. This is the backstop for whatever the first layer
does not model — it would not have caught `command`, which is precisely
why the first layer exists.

Reporting only; neither layer rolls back for you. Auto-reverting would
throw away a sync someone may want to fix by hand.

Verified end to end: `--update command` refuses and lists the ADR-0054
lines; `--force` overrides it; `--update button` (0 local-only lines)
syncs and leaves the tree byte-identical; the #3033 unmapped-path guard
and the `resizable` reclassification both still hold. Tree restored — no
component file changes here.

Co-authored-by: Jack Zhuang <277994282+os-zhuang@users.noreply.github.com>
Co-authored-by: Claude Opus 5 <noreply@anthropic.com>

…46 components "modified" (#3049)

The heuristic was `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 of them: `--check` reported the entire tracked set as "modified",
every time, which is the same as reporting nothing.

#3035 added `localOnlyLines` for the pre-write guard. It is directional —
lines in the first argument the second lacks — so calling it both ways
answers the two questions that actually decide whether to sync: what
would a sync DESTROY, and what would it GAIN. That replaces the
heuristic, and splits the old "modified" bucket in two:

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

Each line now carries counts, and the summary names the components in
each bucket so the next step is obvious without running --diff 46 times.

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 invisible before.

The per-component counts line up with the guard that enforces them
(`command` 35, `select` 32, `sidebar` 24, `table` 17 …), because both
sides call the same function.

`--check` stays exit 0: it is a status report, and 17 locally-modified
components is the steady state here, not a failure.

Verified against the live registry. The `outdated` bucket is the one real
traffic never exercises, so it was tested 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
command. Restored after. `--list`, `--diff`, `--update` and both #3033 /
#3035 guards regression-checked; no component file changes.

Co-authored-by: Jack Zhuang <277994282+os-zhuang@users.noreply.github.com>
Co-authored-by: Claude Opus 5 <noreply@anthropic.com>