@commonpub/layer 0.23.2 → 0.23.3

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@commonpub/layer",
-  "version": "0.23.2",
+  "version": "0.23.3",
   "type": "module",
   "main": "./nuxt.config.ts",
   "files": [
@@ -51,16 +51,16 @@
     "vue": "^3.4.0",
     "vue-router": "^4.3.0",
     "zod": "^4.3.6",
-    "@commonpub/auth": "0.6.0",
     "@commonpub/config": "0.15.0",
-    "@commonpub/editor": "0.7.11",
-    "@commonpub/explainer": "0.7.15",
     "@commonpub/docs": "0.6.3",
     "@commonpub/learning": "0.5.2",
+    "@commonpub/editor": "0.7.11",
     "@commonpub/protocol": "0.12.0",
     "@commonpub/schema": "0.17.0",
+    "@commonpub/server": "2.57.0",
     "@commonpub/ui": "0.9.0",
-    "@commonpub/server": "2.57.0"
+    "@commonpub/auth": "0.6.0",
+    "@commonpub/explainer": "0.7.15"
   },
   "devDependencies": {
     "@testing-library/jest-dom": "^6.9.1",

package/pages/index.vue

@@ -14,9 +14,22 @@ const sortedSections = computed(() =>
 );
 
 const { user: authUser } = useAuth();
-const { hubs: hubsEnabled, contests: contestsEnabled, learning: learningEnabled, video: videoEnabled, docs: docsEnabled, editorial: editorialEnabled, layoutEngine: layoutEngineEnabled } = useFeatures();
+const { hubs: hubsEnabled, contests: contestsEnabled, learning: learningEnabled, video: videoEnabled, docs: docsEnabled, editorial: editorialEnabled, layoutEngine: layoutEngineFlag } = useFeatures();
 const { enabledTypeMeta } = useContentTypes();
 
+// Layout engine path — only active when BOTH the flag is on AND a layout
+// actually exists in the DB for this route. Prevents the "operator enables
+// the flag without seeding a homepage layout → page goes blank" trap
+// (reported by user, session 158 follow-up). When the flag's on but
+// useLayout returns null (feature off OR no published layout for route),
+// we fall through to the configurable/legacy render paths so the user
+// still sees content. Admin can call POST /api/admin/layouts/seed-homepage
+// to populate a default and start using the layout engine for real.
+const { layout: homepageLayout } = useLayout('/');
+const layoutEngineActive = computed(
+  () => layoutEngineFlag.value && homepageLayout.value !== null,
+);
+
 const activeTab = ref(authUser.value ? 'foryou' : 'latest');
 const tabs = computed(() => [
   { value: 'foryou', label: 'For You', icon: 'fa-solid fa-sparkles' },
@@ -144,15 +157,16 @@ async function handleHubJoin(hubSlug: string): Promise<void> {
 <template>
   <div>
     <!-- ═══ LAYOUT ENGINE (Phase 1c — feature-flagged) ═══
-         When `features.layoutEngine` is ON, render the homepage via
-         <LayoutSlot> zones backed by the layouts table. Operators flip
-         this on AFTER running POST /api/admin/layouts/seed-homepage so
-         a default layout exists at scope ('route', '/'). If the flag is
-         on but no layout exists, LayoutSlot renders nothing and the
-         user sees an empty page — documented at
-         docs/reference/guides/layout-engine.md. Falls through to the
-         configurable section renderer when the flag is OFF (default). -->
-    <template v-if="layoutEngineEnabled">
+         Renders DB-driven layout via <LayoutSlot> zones ONLY when BOTH
+         (a) features.layoutEngine is ON AND (b) a layout actually exists
+         at scope ('route', '/'). Falls through to the configurable or
+         legacy renderer otherwise — including when the flag's ON but
+         no layout has been seeded yet (the "blank page" trap reported
+         in session 158 follow-up).
+
+         To enable for real: POST /api/admin/layouts/seed-homepage,
+         then flip the flag. See docs/reference/guides/layout-engine.md. -->
+    <template v-if="layoutEngineActive">
       <LayoutSlot route="/" zone="full-width" />
       <div class="cpub-main-layout">
         <main class="cpub-feed-col">