version 0.2.0 replaces fromer version!

BOOTSTRAP.md

@@ -1,6 +1,6 @@
 # Bootstrap: prime `whynot-design` from this seed
 
-You're holding a zip — `whynot-design-seed.zip` — that contains a complete first commit for the `whynot-design` repository.
+You're holding a zip — `whynot-design-seed.zip` — that contains a complete first commit for the `whynot-design` repository at **v0.2.0**.
 
 ## Step-by-step
 
@@ -13,22 +13,32 @@ rmdir whynot-design-seed
 
 # 2. Sanity-check the tree.
 ls -la
-# Expect: README.md  DesignSystemIntroduction.md  SKILL.md  CONTRIBUTING.md
-#         CHANGELOG.md  package.json  src/  tokens/  assets/  examples/
+# Expect: README.md  DesignSystemIntroduction.md  MultiFrameworkSupport.md
+#         SKILL.md  CONTRIBUTING.md  CHANGELOG.md  BOOTSTRAP.md
+#         package.json  src/  tokens/  assets/  adapters/  examples/
 #         .gitea/  .github/  scripts/  tests/
 
-# 3. First commit.
+# 3. Replace placeholder host names.
+#    Search-and-replace `gitea.example.com` with your actual Gitea host in:
+#      - package.json
+#      - .npmrc
+#      - .gitea/workflows/ci.yml  (and .github/ if you keep that)
+#      - README.md (one quick-start block)
+
+# 4. First commit.
 git add -A
-git commit -m "feat: seed whynot-design from atelier — v0.1.0"
-git tag v0.1.0
+git commit -m "feat: seed whynot-design at v0.2.0 — three-layer architecture, Lit web components"
+git tag v0.2.0
 git push origin main --tags
 
-# 4. Verify the example renders.
+# 5. Install + smoke-test.
 pnpm install
-pnpm example
-# Open http://localhost:3000 — should show the whynot-control kit.
+pnpm showcase
+# Visit http://localhost:4321/examples/showcase/
+# Every <wn-*> component should render. If Lit fails to load,
+# check that `lit` ^3.2.1 resolved in node_modules.
 
-# 5. (Optional) Generate Playwright baselines locally.
+# 6. Generate Playwright baselines locally.
 pnpm exec playwright install --with-deps chromium
 pnpm test:visual:update
 git add tests/visual/__screenshots__
@@ -36,17 +46,18 @@ git commit -m "test: add initial visual-regression baselines"
 git push
 ```
 
+## After bootstrap
+
+1. **Record the bootstrap as `DEC-004` in `whynot-control/DECISIONS.md`** — something like *"Established whynot-design as the implementation surface, three-layer architecture, Lit web components as the canonical component layer."*
+2. **Mention `whynot-design` in `whynot-control/SCOPE.md`** as a sibling repository.
+3. **Add `@whynot/design` as a dependency in your first consuming app** — Django, React, or both. Follow `MultiFrameworkSupport.md` for the per-framework wiring.
+
 ## Notes
 
 - The `git+ssh` URL in `package.json` (`gitea.example.com/whynot/whynot-design.git`) is a placeholder. Replace with your actual Gitea host.
 - The same goes for `.npmrc` and the registry URL in `.gitea/workflows/ci.yml` (commented out — uncomment when you stand up a Gitea Packages registry).
 - `.gitea/workflows/ci.yml` and `.github/workflows/ci.yml` are identical. Keep whichever your forge uses and delete the other.
-
-## After bootstrap
-
-1. Record the bootstrap as `DEC-004` in `whynot-control/DECISIONS.md`.
-2. Mention `whynot-design` in `whynot-control/SCOPE.md` as a sibling repository (out of scope for `whynot-control`, in scope for the org).
-3. Add `@whynot/design` as a dependency in your first consuming prototype to close the loop.
+- The `examples/showcase/index.html` page uses `importmap` to load Lit from esm.sh **for the standalone-no-build case**. When you have a bundler in the consuming app, the bundler resolves `lit` from `node_modules` and the importmap is irrelevant.
 
 ## You can delete this file after bootstrap