The importer's automatic CSS cascade isolation rewrote selectors the
source never contained (body.instatic-import-scope-* prefixes, silent
btn-2 suffix renames). That machinery is gone; control moves to the user.

Each top-level linked stylesheet now imports in one of two modes, picked
in the Review step (default 'convert'):

- convert: parsed into editable style rules, merging CSS-natively into
  the one global cascade. When two page cascades define the same class
  differently, that is an explicit "Stylesheets disagree" conflict row
  (rename with suffix / keep first / overwrite) — applied scoped to the
  affected cascades, never silently. Repeated class fragments demote to
  ambient rules so the registry keeps one bindable rule per name.
- file: the CSS imports verbatim as a SiteFile (type 'style') with a
  site.runtime.styles entry scoped to exactly the linking pages — page
  isolation via runtime scope instead of generated classes. @import
  graphs flatten in cascade order, Google-font imports still install as
  self-hosted fonts, url() assets still upload and rewrite. Node class
  tokens survive through the existing bare-class linking step.

scopeClasses.ts is deleted; classCascades.ts (conflict detection +
resolution + bindable normalization) and stylesheetPlan.ts (mode
partition + flattening) replace it. The near-identical script/stylesheet
SiteFile committers are deduplicated into importedSiteFiles.ts.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

Two losses found by comparing an imported template against its source:

- The framework color engine only parsed hex and hsl/hsla. Imported
  tokens authored as rgba() (--rule, --ink-2, ...) silently emitted NO
  CSS variable, so every `var(--rule)` reference lost its declaration —
  user-visibly, all borders on the demo template vanished. parseColor
  now handles rgb()/rgba() (comma and space syntax, % alpha), and an
  unparseable BASE value (oklch(), color-mix(), named) emits verbatim
  instead of dropping — emission stays injection-safe because
  formatCssVariableBlock sanitises every value. Derived shade/tint/
  transparent variants still skip what they can't model.

- The Site Import modal is a global surface (Spotlight, any workspace),
  but static-site analysis resolves HTML through the module registry,
  which only the site editor's chunk populated. Importing from the Data
  workspace failed with "Module base.container is not registered". The
  modal now registers @modules/base itself, riding its own lazy chunk.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>