create-avocado-site 0.21.0 → 0.22.0

package/NOTICE

@@ -0,0 +1,8 @@
+Avocado Studio
+Copyright 2026 Avocado Studio Contributors
+
+This product includes software developed by the Avocado Studio
+Contributors (https://www.avocadostudio.dev).
+
+Licensed under the Apache License, Version 2.0. See LICENSE for the
+full license text.

package/dist/templates/demo-app.js

@@ -690,21 +690,13 @@ export default function RootLayout({ children }: { children: ReactNode }) {
       <body style={{ background: "var(--bg-0, #12170f)" }}>
         {children}
         {/*
-          Two controls, one state — see the note in \`theme-toggle.tsx\`.
-
-          The header copy is portalled into the nav the SiteHeader block
+          One control, in the header's top-right corner — see the note in
+          \`theme-toggle.tsx\`. It is portalled into the nav the SiteHeader block
           renders, because that markup belongs to the blocks package rather
           than to this app; as a real child of that flex row it inherits the
           sticky positioning instead of guessing at the header's height.
-
-          The footer copy needs no portal. \`children\` is the whole page
-          including the footer, so a sibling after it lands exactly where the
-          demo puts it: on the footer's own ground, below the last link.
         */}
         <SiteThemeToggle portalTo=".site-top-nav-inner" />
-        <div className="site-theme-bar">
-          <SiteThemeToggle />
-        </div>
       </body>
     </html>
   )

package/dist/versions.d.ts

@@ -17,7 +17,7 @@
  * `@avocadostudio-ai/orchestrator-core`, already pinned there; naming it again
  * here is how a project ends up with two.
  */
-export declare const AVOCADO = "0.21.0";
+export declare const AVOCADO = "0.22.0";
 /**
  * Next 15.5.25 rather than 16, because that is the version every example app
  * and the demo site in this repository build and test against. The SDK

package/dist/versions.js

@@ -17,7 +17,7 @@
  * `@avocadostudio-ai/orchestrator-core`, already pinned there; naming it again
  * here is how a project ends up with two.
  */
-export const AVOCADO = "0.21.0";
+export const AVOCADO = "0.22.0";
 /**
  * Next 15.5.25 rather than 16, because that is the version every example app
  * and the demo site in this repository build and test against. The SDK

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "create-avocado-site",
-  "version": "0.21.0",
+  "version": "0.22.0",
   "description": "Bootstrap a runnable Avocado Studio demo site, or wire Avocado into an existing Next.js project",
   "type": "module",
   "bin": {
@@ -11,7 +11,8 @@
     "assets",
     "theme",
     "README.md",
-    "LICENSE"
+    "LICENSE",
+    "NOTICE"
   ],
   "keywords": [
     "avocado",
@@ -30,14 +31,14 @@
   },
   "dependencies": {
     "@clack/prompts": "^0.9.1",
-    "@avocadostudio-ai/skills": "^0.21.0"
+    "@avocadostudio-ai/skills": "^0.22.0"
   },
   "devDependencies": {
     "@types/node": "^22.13.10",
     "tsx": "^4.19.0",
     "typescript": "^5.7.3",
-    "@avocadostudio-ai/shared": "0.21.0",
-    "@avocadostudio-ai/site-sdk": "0.21.0"
+    "@avocadostudio-ai/site-sdk": "0.22.0",
+    "@avocadostudio-ai/shared": "0.22.0"
   },
   "license": "Apache-2.0",
   "homepage": "https://docs.avocadostudio.dev",

package/theme/theme-toggle.css

@@ -19,19 +19,12 @@
  */
 
 /*
- * The theme control, in the footer.
+ * The theme control lives in one place: the top-right corner of the header.
  *
- * It was styled as a 38x36 icon square for a header slot it was never
- * actually placed in. In the footer it can afford a label, which removes the
- * guess a lone sun-or-moon glyph always asks of the reader: does the icon
- * show the theme I am in, or the one I would get?
+ * It also sat in the footer, and the editor's preview only ever mounted that
+ * copy, so on the public demo the one control a visitor could find was below
+ * the last link of a long page.
  */
-.site-theme-bar {
-  display: flex;
-  justify-content: center;
-  padding: 0 var(--section-pad-x) var(--section-pad-y-tight);
-  background: var(--footer-bg);
-}
 
 /*
  * Icon only, and square.
@@ -77,15 +70,6 @@
   color: var(--accent-ink);
 }
 
-/* On the footer's own ground, which is a different surface from the page. */
-.site-theme-bar .site-theme-toggle {
-  color: var(--footer-link);
-}
-
-.site-theme-bar .site-theme-toggle:hover {
-  color: var(--footer-link-hover);
-}
-
 /* Portalled into the header's inner flex row; `auto` pushes it to the far
    right without the row needing to know it is there. */
 .site-top-nav-inner > .site-theme-toggle {

package/theme/theme-toggle.tsx

@@ -36,9 +36,9 @@ const LABEL: Record<Choice, string> = { system: "System", light: "Light", dark:
 /*
  * Both copies of the control answer to one state.
  *
- * There are two on the page — one in the header, one in the footer — and two
- * React instances do not share a `useState`. Without this, clicking the header
- * button changed the theme and left the footer button still reporting the old
+ * There is one on the page now, in the header's top-right corner, but a host
+ * can mount more, and two React instances do not share a `useState`. Without
+ * this, clicking one changed the theme and left the other reporting the old
  * one, which is the kind of thing that looks like a caching bug.
  */
 const THEME_EVENT = "site-theme-change"