docs(ms-ai-architect): fjern de doede design-system-instruksjonene fra egen dokumentasjon
Dokumentasjonen instruerte lesere om a kjore `node scripts/sync-design-system.mjs ms-ai-architect` fra marketplace-roten, og om a legge DS-endringer i `shared/playground-design-system/`. Malt 2026-08-26 mot ground truth: `find` over marketplace-treet (maxdepth 4) finner ikke skriptet noe sted, og `shared/`-katalogen finnes ikke. Marketplace er polyrepo; designsystemet er et eget soesterrepo med CSS-filene i rot. En dokumentasjon som peker pa et skript som ikke finnes er usann. Rettet, 9 linjer i 2 filer: - README.md 471, 473-475 (+ 474 som beskrev `--force`-oppforselen til samme skript) - docs/playground.md 55, 59, 61-62, 64 Erstatningsteksten oppgir bevisst INGEN ny kommando. Den riktige re-sync-veien er ukjent: spoersmalet er sendt til `playground-design-system` (coord 20260826T125424Z-633311263) og er ubesvart. Teksten sier na hva som er malt, at veien er under avklaring, og at den vendored kopien er komplett og fungerer som den er. "Under avklaring" er sant; en peker til et fravaerende skript er det ikke. IKKE roert - historiske oppforinger der stien var sann da den ble skrevet: CHANGELOG.md 203/291/336/399/412/452, README.md 409/420, docs/playground.md 41, playground/A11Y-RAPPORT.md 86. Heller ikke playground/vendor/** (upstreams filer) eller MANIFEST.json sitt source-felt (spurt om, ikke besvart). Verifisering: ingen test dekker prosa, sa grep ER sjekken. Hver av de 9 linjene ble lest med `sed -n Np` og telt med `grep -Fxc -e` foer erstatning (alle unike, 1 forekomst); en kjent-negativ ga 0/rc=1, sa telleren kan skille "ingen treff" fra "broedt kall". Diff-kontekst lest med -U6 foer commit. Suite over sporede testfiler: 1070/1070.
This commit is contained in:
parent
31d2b62aed
commit
66eda40cb4
2 changed files with 9 additions and 9 deletions
|
|
@ -468,11 +468,11 @@ Regenerate via `cd tests/screenshot && npm install && npx playwright install chr
|
|||
|
||||
### Vendored design-system
|
||||
|
||||
The playground loads CSS from `playground/vendor/playground-design-system/` — a vendored copy of the marketplace-root `shared/playground-design-system/`. This keeps the plugin **standalone**: copy the plugin folder anywhere and the playground still works.
|
||||
The playground loads CSS from `playground/vendor/playground-design-system/` — a vendored copy of the shared playground design-system (27 files + `MANIFEST.json`). This keeps the plugin **standalone**: copy the plugin folder anywhere and the playground still works.
|
||||
|
||||
- **Sync:** `node scripts/sync-design-system.mjs ms-ai-architect` (run from marketplace root)
|
||||
- **Drift detection:** `MANIFEST.json` records SHA-256 per file. Re-sync refuses to overwrite files modified locally — pass `--force` to override.
|
||||
- **Generated header:** Each vendored CSS file is prefixed with `/* Code generated by sync-design-system.mjs; DO NOT EDIT. */`. Edit `shared/`, then re-sync.
|
||||
- **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.
|
||||
|
||||
---
|
||||
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue