create-ailk 0.26.0 → 0.28.0

package/templates/README.md

@@ -77,7 +77,7 @@ A page marked `--shape organization-product` is in your site when you scaffolded
 
 To customize the home page, edit [`content/en/HomePage/home.mdx`](./content/en/HomePage/home.mdx). Save and reload the dev server. No build step.
 
-To add a new page, ask Claude Code to run the `/ailk:add-page` skill — it writes the page's content file and nav link in one confirm-before-write pass, and adds a missing route with `create-ailk add-route` first. See [Skills](#skills).
+To add a new page, ask Claude Code to run `/ailk:growth-ops page add` — it writes the page's content file and nav link in one confirm-before-write pass, and adds a missing route with `create-ailk add-route` first. See [Skills](#skills).
 
 > `content/_site.mdx` stays at the top level (not under `content/en/`) — site identity is locale-blind.
 
@@ -135,12 +135,12 @@ Set `AILK_PUBLIC_DOMAIN` to your own domain. `STEALTH=true` keeps a fresh deploy
 
 You need Postgres once you turn on one of these:
 
-| Surface                                                        | What it stores                                                                                                                                                                                                                                                                                                                                                                                                                  |
-| -------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| **Auth** — `/sign-in`, `/sign-up`, `/account`                  | users, sessions, accounts                                                                                                                                                                                                                                                                                                                                                                                                       |
-| **Lead inbox** — `/leads`                                      | submitted leads, for you to review signed in, and newsletter signups. Without a database, lead capture emails each contact-form message to you instead (`RESEND_API_KEY` + `AILK_LEAD_NOTIFICATION_TO` + `AILK_LEAD_NOTIFICATION_FROM` on the API); with neither in production, `/contact` shows your `_site.mdx` `contactEmail` instead of the form. The `setup-database` skill walks you from no database to a working inbox. |
-| **Checkout returns** — `/purchase/success`, `/purchase/cancel` | the paid checkouts the Stripe webhook records. These pages serve only on a site licensed for commerce.                                                                                                                                                                                                                                                                                                                          |
-| **`CONTENT_ADAPTER=database`**                                 | pages authored in the Artifact store rather than in `content/*.mdx`                                                                                                                                                                                                                                                                                                                                                             |
+| Surface                                                        | What it stores                                                                                                                                                                                                                                                                                                                                                                                                                   |
+| -------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| **Auth** — `/sign-in`, `/sign-up`, `/account`                  | users, sessions, accounts                                                                                                                                                                                                                                                                                                                                                                                                        |
+| **Lead inbox** — `/leads`                                      | submitted leads, for you to review signed in, and newsletter signups. Without a database, lead capture emails each contact-form message to you instead (`RESEND_API_KEY` + `AILK_LEAD_NOTIFICATION_TO` + `AILK_LEAD_NOTIFICATION_FROM` on the API); with neither in production, `/contact` shows your `_site.mdx` `contactEmail` instead of the form. `/ailk:growth-ops database` walks you from no database to a working inbox. |
+| **Checkout returns** — `/purchase/success`, `/purchase/cancel` | the paid checkouts the Stripe webhook records. These pages serve only on a site licensed for commerce.                                                                                                                                                                                                                                                                                                                           |
+| **`CONTENT_ADAPTER=database`**                                 | pages authored in the Artifact store rather than in `content/*.mdx`                                                                                                                                                                                                                                                                                                                                                              |
 
 ### One command to get one
 
@@ -165,7 +165,7 @@ That is the whole setup. `pnpm db:studio` opens a browser UI over the data, and
 
 ## Deploy
 
-Ask Claude Code to run the `setup-deploy` skill. It writes a Vercel deploy configuration at the project root — `vercel.json`, an `.env.example` covering the variables production needs, and a `RUNBOOK.md` with the steps — and asks before overwriting any file you already have. Vercel is the one platform it supports today. `apps/api` already ships its own `vercel.json`.
+Ask Claude Code to run `/ailk:growth-ops deploy`. It writes a Vercel deploy configuration at the project root — `vercel.json`, an `.env.example` covering the variables production needs, and a `RUNBOOK.md` with the steps — and asks before overwriting any file you already have. Vercel is the one platform it supports today. `apps/api` already ships its own `vercel.json`.
 
 The [deploy guide](https://ailaunchkit.ai/docs/guides/deploy-to-production) is where the full production walkthrough will live; until it is published, the skill's `RUNBOOK.md` is the checklist. Remember to set `STEALTH=false` on the hosting platform when you launch.
 
@@ -208,17 +208,17 @@ The AI Launch Kit skills come from the `ailk` Claude Code plugin; `.claude/setti
 
 <!-- generated:begin skills -->
 
-| Skill                  | What it does                                                                                                                                                     |
-| ---------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| `/ailk:add-auth`       | Activate the site's sign-in providers (email-and-password, Google OAuth, GitHub OAuth) and write the env vars for the ones you pick.                             |
-| `/ailk:add-page`       | Add a new page — its content file, its structured data and its nav link — in one confirm-before-write pass.                                                      |
-| `/ailk:check-site`     | Run `ailk-audit` on the site and explain the score and findings in plain language. It never edits files.                                                         |
-| `/ailk:extend-site`    | Explain the five ways this site may be extended, walk you to the right one, and record a site-authored file in `customizations.yaml` with its build-in decision. |
-| `/ailk:fill-page`      | Fill one existing page's section content from a category profile: labelled sample content, or your own first draft from a short intake.                          |
-| `/ailk:setup-database` | Take the site from no database to a working lead inbox, and prove it with one test message that must appear in the inbox.                                        |
-| `/ailk:setup-deploy`   | Emit deploy configuration — `vercel.json` and `RUNBOOK.md`, plus an env checklist read from the site's own `.env.example`.                                       |
-| `/ailk:update-page`    | Rename a page — its URL, its title, or both — in one plan-then-confirm pass, with a permanent redirect from the old URL.                                         |
-| `/ailk:upgrade-plan`   | Explain the AI Launch Kit options side by side, recommend one option for this site, and link the public pricing page for prices.                                 |
+| Command                        | What it does                                                                                                                                                     |
+| ------------------------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `/ailk:growth-ops page add`    | Add a new page — its content file, its structured data and its nav link — in one confirm-before-write pass.                                                      |
+| `/ailk:growth-ops page rename` | Rename a page — its URL, its title, or both — in one plan-then-confirm pass, with a permanent redirect from the old URL.                                         |
+| `/ailk:growth-ops page fill`   | Fill one existing page's section content from a category profile: labelled sample content, or your own first draft from a short intake.                          |
+| `/ailk:growth-ops audit`       | Run `ailk-audit` on the site and explain the score and findings in plain language. It never edits files.                                                         |
+| `/ailk:growth-ops extend`      | Explain the five ways this site may be extended, walk you to the right one, and record a site-authored file in `customizations.yaml` with its build-in decision. |
+| `/ailk:growth-ops auth`        | Activate the site's sign-in providers (email-and-password, Google OAuth, GitHub OAuth) and write the env vars for the ones you pick.                             |
+| `/ailk:growth-ops database`    | Take the site from no database to a working lead inbox, and prove it with one test message that must appear in the inbox.                                        |
+| `/ailk:growth-ops deploy`      | Emit deploy configuration — `vercel.json` and `RUNBOOK.md`, plus an env checklist read from the site's own `.env.example`.                                       |
+| `/ailk:growth-ops plan`        | Explain the AI Launch Kit options side by side, recommend one option for this site, and link the public pricing page for prices.                                 |
 
 <!-- generated:end -->
 

package/templates/apps/api/.env.example

@@ -146,11 +146,15 @@ STRIPE_WEBHOOK_SECRET=whsec_xxx
 # SLACK_CONNECTION_KEY=
 # SLACK_CONNECTION_KEY_PREVIOUS=
 #
-# The Organization that owns STRIPE_SECRET_KEY (#9285). On a deployment with
-# the multi-tenant module, only the Organization whose id is named here sees
-# that key as its Stripe connection and sells its Offerings through it; unset,
-# blank or naming no Organization, nobody owns it. Without the multi-tenant
-# module the deployment's single Organization owns it and this is not read.
+# The Organization that owns STRIPE_SECRET_KEY (#9285). On a deployment whose
+# AILK_ENABLED_MODULES selects the multi-tenant module, only the Organization
+# whose id is named here sees that key as its Stripe connection and sells its
+# Offerings through it; unset, blank or naming no Organization, nobody owns it.
+# The selection decides, not the licence (#9968): a deployment that selects
+# multi-tenant must set this for any Organization to own the key, including a
+# downgraded one whose licence no longer claims the module. Without the
+# multi-tenant module selected the deployment's single Organization owns it
+# and this is not read.
 # STRIPE_ENV_ORGANIZATION_ID=
 #
 # The booking webhook receiver (#6085) — a SEPARATE credential from the
@@ -170,6 +174,13 @@ STRIPE_WEBHOOK_SECRET=whsec_xxx
 # equals the caller's own workspace id: the receiver writes under
 # AILK_SITE_ID, the read scopes to the tenant's workspace, and a mismatch
 # fails EMPTY, never wide.
+# The prospect-channel archive cron's secret (#9855). Vercel Cron sends it as
+# `Authorization: Bearer <CRON_SECRET>` to GET /v1/cron/prospect-channel-archive
+# (the scheduling module; the scaffold's apps/api/vercel.json schedules it
+# daily). Generate it with `openssl rand -hex 32`. Unset, or shorter than 32
+# characters, makes the route answer 503 and archive nothing. The bin
+# (`prospect-channel-archive:sweep`) needs no secret.
+# CRON_SECRET=
 
 # =============================================================================
 # Paid modules (D-44, #5368)