@lukoweb/apitogo 0.1.110 → 0.1.111

package/dist/cli/cli.js

@@ -5801,7 +5801,7 @@ import {
 // package.json
 var package_default = {
   name: "@lukoweb/apitogo",
-  version: "0.1.110",
+  version: "0.1.111",
   type: "module",
   sideEffects: [
     "**/*.css",
@@ -11959,8 +11959,6 @@ function applyScaffoldManifestPolicy(manifest, options) {
   if (options.includeDefaultPlans) {
     result.plans = mergePlansBySku2(result.plans, DEFAULT_PLANS);
     result.pricing = { enabled: true };
-  } else {
-    delete result.plans;
   }
   return result;
 }
@@ -14341,7 +14339,7 @@ function buildCreateApitogoCliArgs(invocationArgs, projectName, options) {
     "--skip-install",
     "--use-npm"
   ];
-  if (options?.withExamples) {
+  if (options?.withExamples !== false) {
     cliArgs.push("--include-examples");
   }
   return cliArgs;

package/dist/declarations/cli/platform/helpers/dev-portal-manifest.d.ts

@@ -110,7 +110,7 @@ export declare const SCAFFOLD_OPENAPI_MISSING_NEXT_STEP: DevPortalSuggestedNextS
 export declare const SCAFFOLD_SUGGESTED_NEXT_STEPS: DevPortalSuggestedNextStep[];
 export declare function buildScaffoldJourneyPhases(steps?: DevPortalSuggestedNextStep[]): DevPortalJourneyPhase[];
 export declare const SCAFFOLD_JOURNEY_PHASES: DevPortalJourneyPhase[];
-export declare const SCAFFOLD_AGENT_INSTRUCTION = "Scaffold only \u2014 dependencies are installed but the dev server is not started. Tell the user the site is ready and to run npm run dev in outputDirectory. The home page lives in landing/LandingPage.tsx (starter hero + features). After npm run dev, ask if they want to customize the home page. When they do, always ask for their real content first (what the API does, key endpoints, audience, tone, desired sections) before editing \u2014 never invent placeholder copy unless they explicitly ask for placeholders \u2014 then edit that TSX file directly or call get_dev_portal_landing_guide for the component catalog. Do not write home page content to apitogo.config.json. Then ask what else they want (OpenAPI, plans, bootstrap API ToGo, or go live). Do not mention missing plans, null projectId, skipped bootstrap, publishPrerequisites, or other absent setup unless the user asks about publish or platform provisioning. One user intent \u2192 one MCP tool. When preview is running, shape-phase file edits hot-reload. Never pass restartPreview: true on update_dev_portal_manifest or set_dev_portal_theme (ignored; used to time out against npm run dev). For publish, the user saves OIDC (+ Stripe if paid) in .env using APITOGO_CONFIG_AUTHENTICATION__* keys \u2014 never collect secrets in chat. Call check_dev_portal_publish_readiness after they confirm, then publish_dev_portal. Do not call sync_gateway_plans_from_manifest before publish.";
+export declare const SCAFFOLD_AGENT_INSTRUCTION = "Scaffold only \u2014 dependencies are installed but the dev server is not started. Tell the user the site is ready and to run npm run dev in outputDirectory. The home page lives in landing/LandingPage.tsx (default sample sections including plans). After npm run dev, ask if they want to customize the home page. When they do, always ask for their real content first (what the API does, key endpoints, audience, tone, desired sections) before editing \u2014 never invent placeholder copy unless they explicitly ask for placeholders \u2014 then edit that TSX file directly or call get_dev_portal_landing_guide for the component catalog. Do not write home page content to apitogo.config.json. Then ask what else they want (OpenAPI, plans, bootstrap API ToGo, or go live). Do not mention missing plans, null projectId, skipped bootstrap, publishPrerequisites, or other absent setup unless the user asks about publish or platform provisioning. One user intent \u2192 one MCP tool. When preview is running, shape-phase file edits hot-reload. Never pass restartPreview: true on update_dev_portal_manifest or set_dev_portal_theme (ignored; used to time out against npm run dev). For publish, the user saves OIDC (+ Stripe if paid) in .env using APITOGO_CONFIG_AUTHENTICATION__* keys \u2014 never collect secrets in chat. Call check_dev_portal_publish_readiness after they confirm, then publish_dev_portal. Do not call sync_gateway_plans_from_manifest before publish.";
 export declare function manifestRequiresStripe(plans: ManifestPlanInput[] | undefined): boolean;
 export declare function isNativeAuthEnabledInManifest(manifest: DevPortalLocalManifest): boolean;
 export declare function readManifestAuthProviders(manifest: DevPortalLocalManifest): NonNullable<DevPortalLocalManifest["authentication"]>["providers"];

package/docs/mcp/shape.md

@@ -27,7 +27,7 @@ chat.
 
 ## Scaffold only
 
-If you only want an empty site:
+If you only want a local site:
 
 > Create a dev portal in `./dev-portal-site`.
 

package/docs/quickstart.md

@@ -39,8 +39,8 @@ Build an API product (developer portal, plans, gateway, backend) with an AI agen
    > Create a portal in `./dev-portal` for my API in `./api` with Free (100/min) and Pro (1000/min);
    > make `/health` public.
 
-   The agent should call `apply_product_intent` with `mode: "shape"` (or `create_dev_portal` for an
-   empty scaffold). See [Shape](./mcp/shape.md).
+   The agent should call `apply_product_intent` with `mode: "shape"` (or `create_dev_portal` for a
+   default scaffold). See [Shape](./mcp/shape.md).
 
 1. **Preview locally**
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@lukoweb/apitogo",
-  "version": "0.1.110",
+  "version": "0.1.111",
   "type": "module",
   "sideEffects": [
     "**/*.css",