create-ailk 0.24.0 → 0.26.0

package/templates/README.md

@@ -33,7 +33,7 @@ pnpm preflight   # architecture + CLAUDE.md drift + types + lint + build
 pnpm build       # production build
 ```
 
-> Requires Node.js 20+ and `pnpm` — that is the whole prerequisite list. No database is needed to run or build this site (see [When you need a database](#when-you-need-a-database)), and no vendor API keys are required for first boot — Stripe, auth and email-provider integrations are opt-in. `pnpm install` generates the Prisma client for you; there is no generator step to remember.
+> Requires Node.js 20+ and `pnpm` — that is the whole prerequisite list. No database is needed to run or build this site (see [When you need a database](#when-you-need-a-database)), and no vendor API keys are required for first boot — Stripe, auth and email-provider integrations are opt-in. The Prisma client ships prebuilt in `@working-theory/database`; there is no generator step to remember.
 
 ## Content
 
@@ -131,7 +131,7 @@ Set `AILK_PUBLIC_DOMAIN` to your own domain. `STEALTH=true` keeps a fresh deploy
 
 ## When you need a database
 
-**A free marketing site needs no database at all.** `pnpm install`, `pnpm dev` and `pnpm build` all run green on an empty machine with no Postgres, no `DATABASE_URL` and no `.env` — the pages render from `content/*.mdx`, and the Prisma client is generated for you by `database`'s `postinstall` so the workspace type-checks and builds either way.
+**A free marketing site needs no database at all.** `pnpm install`, `pnpm dev` and `pnpm build` all run green on an empty machine with no Postgres, no `DATABASE_URL` and no `.env` — the pages render from `content/*.mdx`, and the Prisma client ships prebuilt in `@working-theory/database` so the workspace type-checks and builds either way.
 
 You need Postgres once you turn on one of these:
 
@@ -208,16 +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: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.        |
+| 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.                                 |
 
 <!-- generated:end -->
 
@@ -225,7 +226,7 @@ The AI Launch Kit skills come from the `ailk` Claude Code plugin; `.claude/setti
 
 This is your code — `{{PROJECT_NAME}}`, owned by {{COMPANY_NAME}} ({{COMPANY_DOMAIN}}). The root `package.json`'s `license` field ships set to `UNLICENSED` as a neutral placeholder; it's yours to change to whatever license suits your project (or to remove entirely if the repo is private).
 
-The `LICENSE` files under `apps/*/` and `database/` are the exception — they stay **Apache 2.0** because those directories are snapshots of `@working-theory/*` packages' own source, not code you authored.
+The `LICENSE` files under `apps/*/` are the exception — they stay **Apache 2.0** because those directories are snapshots of `@working-theory/*` packages' own source, not code you authored.
 
 The AI Launch Kit framework upstream is **Apache 2.0** — see <https://github.com/working-theory-labs/ai-launch-kit/blob/main/LICENSE>. Contributions are welcome at the upstream repo; start with the [contributing guide](https://github.com/working-theory-labs/ai-launch-kit/blob/main/CONTRIBUTING.md).
 

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

@@ -31,7 +31,7 @@ DATABASE_URL="postgresql://user:password@localhost:5432/customer_template"
 # =============================================================================
 # Stripe (Optional)
 # =============================================================================
-# Consumed by apps/api/src/lib/stripe.ts via @working-theory/stripe-client wrapper.
+# Consumed by packages/api/src/lib/stripe.ts via @working-theory/stripe-client wrapper.
 # Use sandbox keys only — live-mode keys are rejected at runtime, unless
 # STRIPE_MODE=live below admits a restricted live key (#8450).
 STRIPE_SECRET_KEY=sk_test_xxx
@@ -115,7 +115,7 @@ STRIPE_WEBHOOK_SECRET=whsec_xxx
 # ROTATION. Set STRIPE_CONNECTION_KEY_PREVIOUS to the old key and
 # STRIPE_CONNECTION_KEY to a new one, redeploy, run
 # `node dist/bin/stripe-connections-rekey.js` (dev:
-# `pnpm --filter @working-theory/api stripe-connections:rekey`) with the
+# `pnpm --filter @working-theory/app-api stripe-connections:rekey`) with the
 # production environment (VERCEL_ENV=production, or NODE_ENV=production off
 # Vercel) — anywhere else it prints `not_production` and touches nothing —
 # and unset _PREVIOUS once it prints `remaining=0`. A row it counts `unreadable`
@@ -125,6 +125,27 @@ STRIPE_WEBHOOK_SECRET=whsec_xxx
 # STRIPE_CONNECTION_KEY=
 # STRIPE_CONNECTION_KEY_PREVIOUS=
 #
+# An Organization's Slack connection (#9748) — the AES-256-GCM key each
+# Organization's Slack bot token and signing secret are encrypted under. The
+# same shape rule: exactly 32 random bytes in canonical standard base64
+# (`openssl rand -base64 32`), and never the same bytes as
+# SCHEDULING_CREDENTIAL_KEY, STRIPE_CONNECTION_KEY or
+# STRIPE_CONNECTION_KEY_PREVIOUS. Any other value stops the API at startup.
+# Unset means connect answers 503 credential_key_not_configured, every
+# connection reads as not connected, and disconnect still works.
+#
+# ROTATION. Set SLACK_CONNECTION_KEY_PREVIOUS to the old key and
+# SLACK_CONNECTION_KEY to a new one, and redeploy. Every connect writes under
+# the new key; a connection written under the old one reads as connected
+# while _PREVIOUS is set, and as not connected once it is unset, until its
+# owner reconnects. There is no rekey walk. A rotation made because the old
+# key LEAKED is not complete until each connected owner rotates the bot token
+# and signing secret in Slack and reconnects: the old key still opens every
+# row written under it. _PREVIOUS without a current key, or equal to it,
+# stops the API.
+# 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,