6.0.0

• dw-swift-migrate-site replaces dw-swift-migrate-content as the master site migration. One flow moves any
  website or webshop into a Swift 2 site: content pages, and when in scope the product catalog as a PIM data model
  with imported products. It opens with an intake that asks, in one message, only what the request leaves open
  (source URL, new or existing website, content and/or catalog, language, currency and VAT, permission to copy, and
  for a catalog where the API key file is), takes the connected solution, a subset-first scope and six review rounds
  as stated defaults, and starts the survey at once when the request answered everything. Then seven steps, each
  ending at a checkpoint of one of two kinds: a decision the agent waits on (the scope, the data model, the website
  proposal) or a report it posts and continues past, unless the report shows a problem or the user asked to review
  every step: survey, scrape, data model, Data Integration import, content rebuild, catalog tuning,
  and a screenshot-scored critic review loop, with RUN-STATE.md so a run resumes in a new session. The content
  rebuild of the retired skill (extract_site_content, the per-page layout plan, build_pages) lives on as
  references/content-rebuild.md, with two safety rules: the site extraction and media import run only when the
  source's owner accepts their load (both read 6 requests at a time and skip robots.txt), and a product import
  first checks that no existing product shares a source product number, because the Ecom provider would update it.
  Group membership is imported through the product file's Groups/PrimaryGroup columns.
  dw-swift-migrate-site is dynamo: false (it needs a shell, the dw CLI and a browser), so the manifest no longer carries a site migration skill. The skill is self-contained: it links to no
  other skill, carries the page create order, the dw CLI upload rules, the Data Integration activity rules and the
  facet field rule itself, and describes steps in plain language, naming MCP tools only where a call has a trap
  (the restricted migration tool family and the page create order). Registered in dynamicweb-frontend and
  dynamicweb-commerce; routing in dw-swift-migrate-v1, dw-swift-page-design, dw-swift-building,
  dw-demo-swift and dw-demo-base now points at it.