create-kywi-app 0.15.1 → 0.15.2

package/assets/agent-patterns.md

@@ -489,7 +489,10 @@ already answered.
 When consent is required and no page places the module, the API logs a one-time
 warning on its first request: nobody can grant consent, so every personalization
 cookie stays suppressed and audiences, A/B bucketing and UTM attribution serve
-default content to everyone.
+default content to everyone. A host that mounts the banner itself in app chrome
+instead of a page or blueprint layout (kywi-cms#193) is invisible to that scan,
+so set `theme.personalization.consentBanner: 'host'` to declare the placement
+and skip the check.
 
 ### Which do I reach for? (in order)
 

package/lib/templates.mjs

@@ -2662,7 +2662,11 @@ Audiences, experiments and the self-ID widget you configure in the admin resolve
   tooling instead, set \`personalization: { requireConsent: false }\` on your
   theme in \`kywi.config.ts\` **and** \`KYWI_REQUIRE_CONSENT=false\` in the
   environment (the edge middleware cannot read the config) — that hands
-  compliance to your tooling and restores the un-gated cookie behaviour.
+  compliance to your tooling and restores the un-gated cookie behaviour. If
+  you mount \`cookieConsent\` yourself in \`app/(site)/layout.tsx\` instead of
+  placing it through a page or blueprint layout, set
+  \`personalization: { consentBanner: 'host' }\` too, or the API's one-time
+  startup check will warn that nothing places it.
 - **Preview links** — an admin preview link sets \`kywi_preview_init\` and the page
   honours it, so you can preview an audience's experience.
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "create-kywi-app",
-  "version": "0.15.1",
+  "version": "0.15.2",
   "description": "Scaffold a new Kywi CMS project — npx create-kywi-app my-site",
   "type": "module",
   "homepage": "https://github.com/Kywi-Software/kywi-cms#readme",