create-cmp-cli 0.7.0 → 0.7.1

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "create-cmp-cli",
-  "version": "0.7.0",
+  "version": "0.7.1",
   "description": "Create production mobile apps (Android + iOS, one Kotlin codebase) with AI — the delivery harness for Compose Multiplatform, the current generation of cross-platform (Google-backed KMP, iOS stable since May 2025). A deterministic, non-interactive generator that scaffolds a green-building app in minutes, then holds AI-driven changes to a machine-enforced verify lane with a committed evidence receipt. Every app carries a device-free UI preview loop (real screens rendered headlessly on save; changed-screen attribution and compile-error surfacing for coding agents, a live gallery for humans) plus agent-first docs (CLAUDE.md + AGENTS.md). Installs the `create-cmp` command.",
   "type": "module",
   "bin": {

package/src/lib/tabs.mjs

@@ -378,8 +378,10 @@ ${imports.join("\n")}
  *
  * The \`@Preview\` analog for the create-cmp inspector: the registry makes "render screen
  * X" a closed, enumerable operation. The scaffolder regenerates the tab entries from the
- * configured \`tabs\`; when you add a screen by hand, add it here — the renderScreens
- * harness, the gallery, and golden baselines pick it up by id.
+ * configured \`tabs\`, and the feature stamper (\`qa/scaffold-feature.mjs\`, via the
+ * \`add-feature\`/\`add-screen\` skills) auto-appends a stamped screen at the
+ * \`// cmp:anchor preview-registry\` marker below; when you add a screen by hand, add it
+ * there too — the renderScreens harness, the gallery, and golden baselines pick it up by id.
  *
  * State variants (the Storybook "story" analog): a screen in a specific UI state is just
  * another entry with a derived id — e.g. \`ScreenPreview("home@empty", "Home — empty")\`
@@ -405,6 +407,7 @@ ${infos.map(previewTabArg).join("\n")}
     },
 ${infos.map(previewEntry).join("\n")}
     ScreenPreview("detail", "Detail (nav destination)") { DetailScreen(itemId = "1", onBack = {}) },
+    // cmp:anchor preview-registry
 )
 
 /**

package/template/CLAUDE.md

@@ -75,8 +75,10 @@ and tells you exactly what your edit changed.
 `composeApp/build/previews/<id>/{screen.png, tree.json}` (`-Pscreen=<id>` for one);
 `node qa/preview-gallery.mjs` builds a self-contained gallery page from the output.
 
-Screens come from `inspector/PreviewRegistry.kt` (desktopMain). **When you add a screen,
-register it there** — a forced-state variant is just another entry (`"home@empty"`).
+Screens come from `inspector/PreviewRegistry.kt` (desktopMain). The `add-feature`/`add-screen`
+stamper **auto-registers** a stamped screen there (at the `// cmp:anchor preview-registry`
+marker). **When you add a screen by hand, register it there** — a forced-state variant is just
+another entry (`"home@empty"`).
 Assert on the `tree.json` structure; never read PNG bytes (pixels are for humans).
 <!-- <<< cmp:feature inspector -->
 <!-- >>> cmp:feature dev-client -->

package/template/composeApp/src/desktopMain/kotlin/com/example/app/inspector/PreviewRegistry.kt

@@ -18,8 +18,10 @@ import __PACKAGE__.presentation.profile.ProfileScreen
  *
  * The `@Preview` analog for the create-cmp inspector: the registry makes "render screen
  * X" a closed, enumerable operation. The scaffolder regenerates the tab entries from the
- * configured `tabs`; when you add a screen by hand, add it here — the renderScreens
- * harness, the gallery, and golden baselines pick it up by id.
+ * configured `tabs`, and the feature stamper (`qa/scaffold-feature.mjs`, via the
+ * `add-feature`/`add-screen` skills) auto-appends a stamped screen at the
+ * `// cmp:anchor preview-registry` marker below; when you add a screen by hand, add it
+ * there too — the renderScreens harness, the gallery, and golden baselines pick it up by id.
  *
  * State variants (the Storybook "story" analog): a screen in a specific UI state is just
  * another entry with a derived id — e.g. `ScreenPreview("home@empty", "Home — empty")`
@@ -47,6 +49,7 @@ fun previewRegistry(): List<ScreenPreview> = listOf(
     ScreenPreview("home", "Home tab") { TabHost { HomeScreen(onItemClick = {}) } },
     ScreenPreview("profile", "Profile tab") { TabHost { ProfileScreen() } },
     ScreenPreview("detail", "Detail (nav destination)") { DetailScreen(itemId = "1", onBack = {}) },
+    // cmp:anchor preview-registry
 )
 
 /**

package/template/qa/scaffold-feature.mjs

@@ -446,6 +446,11 @@ const plan = {
 const APP_MODULE = path.join(SRC("commonMain"), "di/AppModule.kt");
 const SCREEN_KT = path.join(SRC("commonMain"), "presentation/navigation/Screen.kt");
 const APP_NAV_HOST = path.join(SRC("commonMain"), "presentation/navigation/AppNavHost.kt");
+// Optional (present only when the inspector feature is enabled): the preview
+// registry lives in desktopMain. A stamped pushed-destination screen is
+// registered here so `renderScreens`, the gallery, and golden baselines pick it
+// up with zero hand edits — the same reason we wire nav/DI automatically.
+const PREVIEW_REGISTRY = path.join(SRC("desktopMain"), "inspector/PreviewRegistry.kt");
 
 // Each step is tagged with the presets it belongs to, same mechanism as
 // FILES above: `repository` gets repo+usecase DI (+ imports) only; `screen`
@@ -478,14 +483,30 @@ const ALL_INJECTION_PLANS = [
       { presets: ["feature", "screen"], apply: (c) => injectAtAnchor(c, APP_NAV_HOST, "nav-destinations", `composable(Screen.${F}.route) { ${F}Screen(onItemClick = {}) }`) },
     ],
   },
+  {
+    // Optional: only wired when the inspector feature shipped PreviewRegistry.kt.
+    // Registers the stamped screen exactly as the NavHost hosts it (pushed
+    // destination → standalone, matching DetailScreen), so preview parity holds.
+    filePath: PREVIEW_REGISTRY,
+    optional: true,
+    steps: [
+      { presets: ["feature", "screen"], apply: (c) => injectImport(c, PREVIEW_REGISTRY, `import ${PACKAGE}.presentation.${f}.${F}Screen`) },
+      { presets: ["feature", "screen"], apply: (c) => injectAtAnchor(c, PREVIEW_REGISTRY, "preview-registry", `ScreenPreview("${f}", "${F} (nav destination)") { ${F}Screen(onItemClick = {}) },`) },
+    ],
+  },
 ];
 
 // Filter steps by active preset; drop any file plan left with zero steps
 // (e.g. Screen.kt / AppNavHost.kt entirely for `repository`).
 const fileInjectionPlans = ALL_INJECTION_PLANS.map((p) => ({
   filePath: p.filePath,
+  optional: p.optional === true,
   steps: p.steps.filter((s) => s.presets.includes(preset)).map((s) => s.apply),
-})).filter((p) => p.steps.length > 0);
+}))
+  .filter((p) => p.steps.length > 0)
+  // An optional shared file (PreviewRegistry.kt when the inspector is disabled)
+  // simply isn't wired — a required file that's missing still dies in applyInjectionSteps.
+  .filter((p) => !(p.optional && !fs.existsSync(p.filePath)));
 
 const fileResults = fileInjectionPlans.map((p) => applyInjectionSteps(p.filePath, p.steps));
 
@@ -520,6 +541,11 @@ if (dryRun) {
       `\n${F}Screen.kt is stamped wrapped in BaseScreen (SHELL-05 — pushed destinations wrap their own content).`,
     );
   }
+  if (fileInjectionPlans.some((p) => p.filePath === PREVIEW_REGISTRY)) {
+    console.log(
+      `\n${F}Screen is auto-registered in inspector/PreviewRegistry.kt (renderScreens + gallery + golden baseline pick it up).`,
+    );
+  }
   if (writesSpec) {
     console.log(`\nspecs/${f}.spec.md will be written with default clauses ${F_UPPER}-01..06.`);
   } else {