@lukoweb/apitogo 0.1.93 → 0.1.94

package/dist/cli/cli.js

@@ -9395,7 +9395,8 @@ var PLATFORM_PLAN_CATALOG = [
       "Paid end-user gateway plans (Stripe checkout for API subscribers)",
       "1 custom domain on the dev portal",
       "100k requests included; up to 1M requests / month",
-      "Stripe subscription billing with promotion codes at checkout"
+      "Stripe subscription billing with promotion codes at checkout",
+      "Standard support"
     ],
     limitations: [
       "Requires Stripe checkout to activate",
@@ -9415,7 +9416,8 @@ var PLATFORM_PLAN_CATALOG = [
       "3 custom domains",
       "1M requests included; up to 10M requests / month",
       "Advanced analytics and CDN for your API",
-      "Extended monitoring history and alerts"
+      "Extended monitoring history and alerts",
+      "Enterprise support"
     ],
     limitations: [
       "Requires Stripe checkout to activate",
@@ -9434,8 +9436,8 @@ function buildPlatformPlanSelectionAgentInstruction(quota) {
   const lines = [
     "Before calling ensure_platform_plan, explain the platform hosting tiers to the user using platformPlanCatalog from the bootstrap response or list_platform_plans.",
     "Free: $0/month, dev portal + API hub, no custom domain, free ($0) gateway/API plans only.",
-    "Starter: $99/month via Stripe, custom domain, paid gateway plans, production hosting.",
-    "Professional: $999/month via Stripe, higher limits, multiple domains, advanced analytics.",
+    "Starter: $99/month via Stripe, custom domain, paid gateway plans, production hosting, standard support.",
+    "Professional: $999/month via Stripe, higher limits, multiple domains, advanced analytics, enterprise support.",
     "This is separate from gateway/API plans (what end users pay for API access) configured in apitogo.config.json.",
     "If apitogo.config.json already has paid gateway plans (priceAmount > 0), warn before they pick Free: Free cannot publish paid API plans \u2014 they must choose Starter/Professional, or remove/zero those paid plans first. Never silently strip paid plans."
   ];
@@ -12533,7 +12535,7 @@ import {
 // package.json
 var package_default = {
   name: "@lukoweb/apitogo",
-  version: "0.1.93",
+  version: "0.1.94",
   type: "module",
   sideEffects: [
     "**/*.css",
@@ -18504,12 +18506,13 @@ function buildCreateApitogoCliArgs(invocationArgs, projectName, options) {
   const cliArgs = [
     ...invocationArgs,
     projectName,
-    "--yes",
+    "--typescript",
+    "--eslint",
     "--skip-install",
     "--use-npm"
   ];
   if (options?.withExamples) {
-    cliArgs.push("--with-examples");
+    cliArgs.push("--include-examples");
   }
   return cliArgs;
 }

package/docs/cli/commands.md

@@ -29,7 +29,8 @@ same commands so agents and humans get identical behavior.
 | `init [dir]` | Named folder; `--install` (default), `--overwrite`, `--json`, `--openapi-search` |
 | `config` | Interactive on TTY; flags: `--openapi`, `--page-*`, `--plan`, `--backend`, `--theme`, `--patch`, `--json` |
 
-`npm create @lukoweb/apitogo@latest` remains an interactive alternative for new folders.
+`npx @lukoweb/create-apitogo@latest` remains an interactive alternative for new folders.
+Pass `--typescript --eslint` to skip those prompts. See [Install the CLI](./setup.md#scaffold-options).
 
 See [Make config (CLI)](../configuration/make-config.mdx) for all `config` flags.
 

package/docs/cli/overview.md

@@ -13,7 +13,7 @@ local files, preview with `apitogo dev`, and publish to APItoGo hosting with `ap
 
 ## What you get
 
-- Scaffold a local portal site (`npm create @lukoweb/apitogo@latest` or `apitogo init`)
+- Scaffold a local portal site (`npx @lukoweb/create-apitogo@latest` or `apitogo init`)
 - Shape backend, OpenAPI, plans, and docs pages via `apitogo config` and file edits
 - Preview locally (`apitogo dev`)
 - Publish to APItoGo hosting (`apitogo apply`) with platform plans **Free**, **Starter**, or

package/docs/cli/setup.md

@@ -23,10 +23,10 @@ need a global install — scaffold commands add it to your project and `npm inst
 
 ### New project (recommended)
 
-`npm create` scaffolds the site **and** installs `@lukoweb/apitogo` locally:
+`npx @lukoweb/create-apitogo` scaffolds the site **and** installs `@lukoweb/apitogo` locally:
 
 ```bash
-npm create @lukoweb/apitogo@latest
+npx @lukoweb/create-apitogo@latest
 cd your-project-name
 npx apitogo config       # interactive: backend, OpenAPI, pages, plans
 npm run dev
@@ -35,14 +35,28 @@ npm run dev
 Also works with `pnpm create @lukoweb/apitogo`, `yarn create @lukoweb/apitogo`, or
 `bunx @lukoweb/create-apitogo`.
 
-Non-interactive example:
+Non-interactive:
 
 ```bash
-npm create @lukoweb/apitogo@latest my-portal -- --yes --typescript
+npx @lukoweb/create-apitogo@latest my-portal --typescript --eslint
 cd my-portal
 npx apitogo config
 ```
 
+#### Scaffold options
+
+| Flag | Effect |
+| ---- | ------ |
+| `--typescript` / `--ts` | TypeScript project |
+| `--javascript` / `--js` | JavaScript project |
+| `--eslint` | Add ESLint config |
+| `--no-eslint` | Skip ESLint |
+| `--include-examples` | Add starter docs and a sample OpenAPI spec (off unless passed) |
+
+Omit flags to be prompted for TypeScript and ESLint. Example files are never prompted.
+
+See `@lukoweb/create-apitogo --help` for package manager and install flags.
+
 ### Scaffold into an existing folder
 
 `apitogo init` writes `package.json` with `@lukoweb/apitogo` as a dependency. Run **`npm install`**
@@ -63,7 +77,7 @@ to preview, then `apitogo apply` when ready to go live.
 
 | Situation | Command |
 | --------- | ------- |
-| After `npm create` or `npm install` in the project | `npx apitogo <command>` (e.g. `npx apitogo config`) |
+| After `npx @lukoweb/create-apitogo` or `npm install` in the project | `npx apitogo <command>` (e.g. `npx apitogo config`) |
 | Same, if `node_modules/.bin` is on your PATH | `apitogo <command>` |
 | One-off, no project yet | `npx @lukoweb/apitogo <command>` |
 | Optional global install | `npm install -g @lukoweb/apitogo` then `apitogo <command>` anywhere |

package/docs/cli/shape.md

@@ -13,10 +13,10 @@ Requires the **`apitogo`** CLI (`@lukoweb/apitogo`). If you have not installed i
 
 ## Happy path
 
-`npm create` installs `@lukoweb/apitogo` into the new project. Then run config via `npx`:
+`npx @lukoweb/create-apitogo` installs `@lukoweb/apitogo` into the new project. Then run config via `npx`:
 
 ```bash
-npm create @lukoweb/apitogo@latest my-portal -- --yes
+npx @lukoweb/create-apitogo@latest my-portal --typescript --eslint
 cd my-portal
 npx apitogo config         # backend, OpenAPI, pages, plans (apply each immediately)
 npm run dev                # http://localhost:3000

package/docs/configuration/make-config.mdx

@@ -20,7 +20,7 @@ on new scaffolds. The command does **not** change `redirects`.
 
 Install the CLI first — see [Install the CLI](../cli/setup.md). In short:
 
-- **New site:** `npm create @lukoweb/apitogo@latest` (installs `@lukoweb/apitogo` into the project)
+- **New site:** `npx @lukoweb/create-apitogo@latest` (installs `@lukoweb/apitogo` into the project)
 - **Existing folder:** `npx @lukoweb/apitogo init .` then `npm install`
 
 Run config from the project root with `npx apitogo config` (or `apitogo config` if

package/package.json

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