docs(ms-ai-architect): skriv inn DS-repoets svar - vendoring bestaar, source_commit er usann

playground-design-system svarte paa coord 20260826T125424Z-633311263 (deres
20260826T221726Z-1224320768). Alle fem baerende paastander er verifisert HER foer
de ble skrevet inn - en melding er premiss, ikke faktum:

1. c1b7bad LEVER i catalog-repoet (977 commits, pre-migrasjons-monorepohistorikk).
   Vaar egen slutning om at lineagen var kuttet var FEIL - den er kuttet fra vaart
   og deres repo, ikke fra catalog. Rettet.
2. Skriptet ligger i e84dffd^:scripts/sync-design-system.mjs - 225 linjer, og det
   tar allerede --source/--target/--check/--force. Restaurering, ikke nyutvikling.
3. source_commit c1b7bad er ikke bare unaabar, den er USANN: det vendorede treet
   inneholder components-tier4-project-view.css, som ikke fantes i den commiten.
   Kjent-positiv kontroll paa components-tier3.css i SAMME commit slaar opp fint,
   saa spoerringen kan finne. Syncen etikettmerket med marketplace-HEAD mens den
   kopierte et ukommittert arbeidstre.
4. 26 av 27 filer byte-identiske med DS-repoets naavaerende innhold. Merk: foerste
   maaling her ga 17/27 fordi generated-headeren ikke var trukket fra. Justert
   maaling matcher deres tall eksakt; kjent-positiv bekreftet at sammenligningen
   kan skille. Avviket er deres egen README.md.
5. 27/27 mot vaar egen MANIFEST - ingen lokal drift.

Skrevet inn: vendoring bestaar som anbefalt konsumentmodell, ingen avloesning.
Ingen kommando publisert ennaa - DS-repoet holder restaureringen til
kildeavgrensningen er valgt, fordi en naiv --source . over deres repo-rot ville
vendoret STATE.md og repo-apparatet inn hit. Vi rekonstruerer ingenting lokalt.
MANIFEST.json er LATT UROERT paa deres eksplisitte anbefaling: aa oversette stien
og beholde commiten ville gjort en aapenbart stale peker til en troverdig feil en.

Lagt til et punkt om hva en konsument kan sjekke uten skriptet, inkludert
header-fellen som ga min egen foerste maaling feil svar.

Verifisering: prosa, ingen test dekker den - hver erstatning er hel-linje-anker
med telt forekomst (alle unike). Diff-kontekst lest med -U4. Suite: 1070/1070.

README.md

@@ -472,7 +472,9 @@ The playground loads CSS from `playground/vendor/playground-design-system/` —
 
 - **Drift detection:** `MANIFEST.json` records SHA-256 per file, so local modification of a vendored file is detectable.
 - **Generated header:** Each vendored CSS file is prefixed with `/* Code generated by sync-design-system.mjs; DO NOT EDIT. */`. Never edit the vendored files directly.
-- **⚠️ Re-sync path under clarification — no command to run.** `MANIFEST.json` records this copy as synced from `shared/playground-design-system/` at the marketplace root via `scripts/sync-design-system.mjs`. Verified 2026-08-26: **neither that directory nor that script exists in the marketplace tree any more** — the marketplace is a polyrepo, and the design-system is its own sibling repository with the CSS files at its root. There is currently **no documented way to refresh this copy**, and this section deliberately names none rather than point at something that does not run. The question is with the design-system repository; this section will be updated when it is answered. The vendored copy is complete and the playground runs from it unchanged in the meantime.
+- **⚠️ No re-sync command yet — restoration pending upstream.** Vendoring **stands** as the recommended consumer model (design-system repository's decision, 2026-08-27; there is no replacement — a submodule or npm package would break its no-build / no-bundler / `file://` constraints). The sync script is **not lost**: it survives complete in the catalog repository's pre-migration history — `git -C <marketplace>/catalog show e84dffd^:scripts/sync-design-system.mjs` (225 lines, no npm dependencies, and it already accepts `--source`, `--target` and `--check`). Restoring it is the design-system repository's call, and they are deliberately holding it back until the source-scoping question is settled: their repo root holds the design-system **plus** repo apparatus, so a naive `--source .` would vendor `STATE.md`, `LICENSE` and `docs/` into consumers. They will publish a command once it is verified. Do not reconstruct one locally.
+- **🔴 Do not trust `source_commit` in `MANIFEST.json`.** It reads `c1b7bad`, which is not merely unreachable from this repo — it is **wrong**. The vendored tree contains `components-tier4-project-view.css`, and that file did not exist in `c1b7bad` (known-positive control: `components-tier3.css` in the same commit resolves fine). The sync labelled the copy with the marketplace HEAD while copying an uncommitted working tree. Leave the field alone: rewriting the path while keeping the commit would turn an obviously stale pointer into a credible false one. A future re-sync writes a true manifest.
+- **What you can check today, without the script:** re-hash the vendored tree against `MANIFEST.json`. Measured 2026-08-27 — **27/27 match**, so nothing here has been edited locally, and **26 of 27 files are byte-identical** with the design-system repository's current content, 3.5 months after the last sync. The sole difference is that repository's own `README.md`, which documents the system rather than being part of it. When comparing by hand, discount the first line of each vendored CSS file: the generated header is added by the sync, so a raw `diff` reports all nine CSS files as differing when none of them do.
 
 ---