create-ailk 0.7.0 → 0.9.0

package/site-templates/minimalism-site/flows/referral.flow.json

@@ -1,71 +0,0 @@
-{
-  "slug": "referral",
-  "defaultLocale": "en",
-  "steps": [
-    {
-      "key": "introduction",
-      "type": "field",
-      "copy": {
-        "title": {
-          "en": "Who should we meet?"
-        }
-      },
-      "fields": [
-        {
-          "name": "referrer_name",
-          "inputType": "text",
-          "required": true,
-          "mapsTo": "name",
-          "copy": {
-            "label": {
-              "en": "Your name"
-            },
-            "help": {
-              "en": "So we can tell them who sent us."
-            }
-          }
-        },
-        {
-          "name": "referrer_email",
-          "inputType": "email",
-          "required": true,
-          "mapsTo": "email",
-          "copy": {
-            "label": {
-              "en": "Your email"
-            },
-            "help": {
-              "en": "Where we tell you how it went."
-            }
-          }
-        },
-        {
-          "name": "referral_details",
-          "inputType": "textarea",
-          "required": true,
-          "minLength": 20,
-          "copy": {
-            "label": {
-              "en": "Who are they, and why them?"
-            },
-            "placeholder": {
-              "en": "Their name, a way to reach them, and one line on why you thought of them."
-            }
-          }
-        }
-      ]
-    },
-    {
-      "key": "sent",
-      "type": "message",
-      "copy": {
-        "title": {
-          "en": "Thank you — the introduction is in"
-        },
-        "body": {
-          "en": "We will reach out within a few days and let you know either way. Placeholder copy: replace it with what you actually do."
-        }
-      }
-    }
-  ]
-}

package/site-templates/minimalism-site/provenance.json

@@ -1,4 +0,0 @@
-{
-  "template": "minimalism-site",
-  "requires": ["marketing", "scheduling", "signal-collectors"]
-}

package/site-templates/simple-service/DESIGN.md

@@ -1,162 +0,0 @@
----
-name: Standard
-description: The standard design — the black-on-white foundation any shape wears by default: full navigation, a multi-column footer, the document-scroll home.
-colors:
-  bg: "#ffffff"
-  fg: "#000000"
-  surface: "#ffffff"
-  surface-secondary: "#ffffff"
-  border: "#000000"
-  text-muted: "#333333"
-  brand: "#000000"
-  fg-on-brand: "#ffffff"
-  accent: "#000000"
-  bg-dark: "#000000"
-  fg-dark: "#ffffff"
-  border-dark: "#ffffff"
-  brand-dark: "#ffffff"
-typography:
-  display:
-    fontFamily: "system-ui, -apple-system, Segoe UI, Roboto, Helvetica Neue, sans-serif"
-    fontSize: "3.5rem"
-    fontWeight: 700
-    lineHeight: 1.1
-    letterSpacing: "normal"
-  heading-section:
-    fontFamily: "system-ui, -apple-system, Segoe UI, Roboto, Helvetica Neue, sans-serif"
-    fontSize: "3rem"
-    fontWeight: 700
-    lineHeight: 1.1
-    letterSpacing: "normal"
-  heading-item:
-    fontSize: "2rem"
-    fontWeight: 700
-    lineHeight: 1.375
-    letterSpacing: "normal"
-  body:
-    fontFamily: "system-ui, -apple-system, Segoe UI, Roboto, Helvetica Neue, sans-serif"
-    fontSize: "1.125rem"
-    fontWeight: 400
-    lineHeight: 1.5
-  eyebrow:
-    fontSize: "0.875rem"
-    fontWeight: 600
-    lineHeight: 1.4
-    letterSpacing: "0.05em"
-rounded:
-  button: "0.5rem"
-  card: "0.75rem"
-spacing:
-  section: "7rem"
-  section-mobile: "4rem"
-  card: "1.5rem"
-  grid: "1.5rem"
-  container: "1280px"
-  measure: "36rem"
----
-
-<!--
-  Source template: simple-service
-  Design: standard
-  Version: create-ailk {{CREATE_AILK_VERSION}}
-
-  This is the `standard` design's DESIGN.md. Its one authored source is
-  create-ailk's site-templates/designs/standard/DESIGN.md; every template on
-  this design ships a copy of it that differs only in the "Source template"
-  line above, and a template installed with `--template <name>` replaces the
-  base scaffold's DESIGN.md with its own. The impeccable design skill reads
-  it at the start of every design session, so an agent building a new page
-  stays on-system.
-  Edit the canonical file, never a copy — a test holds every copy to it.
-
-  The tokens above describe what the site RENDERS today. Colours come from
-  content/_site.mdx (`theme.colors`); type, radius and spacing are platform
-  defaults a site cannot override yet — see "Where this is heading" below.
--->
-
-# Standard
-
-## Overview
-
-The foundation reads like a well-made wireframe: nothing on the page but the words, black on white, with rules where other sites use shadows and colour. It is the look of a site whose owner has not chosen a brand yet and does not pretend otherwise — every placeholder reads as a placeholder, and the structure of the argument is what the visitor sees. A brand is applied on top of it; it is not one.
-
-Every page is composed from the AI Launch Kit component library (`@working-theory/ui`). Nothing is hand-built: a page is a list of registered sections, each with a bounded set of variants. Each section is one full-width band with a lot of air around it.
-
-## Colors
-
-### Primary
-
-**Black** (`brand` `#000000`) fills the primary button; its label is white. The secondary button is white with a black hairline and black label.
-
-### Neutral
-
-Pure white ground (`bg` `#ffffff`), pure black ink for headings (`fg` `#000000`), and near-black `#333333` for body copy — well above AA on white. **Borders are black** (`#000000`): card outlines, the rule under the navigation, the rules between sections and the rule above the footer are all 1px black lines. Cards are white, not tinted (`surface-secondary` is white too). There is no accent colour — `accent` is black.
-
-Dark mode inverts: black ground, white ink, white rules, white primary button with black label.
-
-### Named Rules
-
-- **Rules, not fills.** A container is drawn with a black hairline on the white ground. Grey fills are reserved for image placeholders.
-
-## Typography
-
-System sans throughout; no web font.
-
-### Hierarchy
-
-| Role            | Size     | Weight | Notes                                                                                 |
-| --------------- | -------- | ------ | ------------------------------------------------------------------------------------- |
-| Hero headline   | 3.5rem   | 700    | Normal tracking, line-height 1.1; 2.5rem below 1024px                                 |
-| Section heading | 3rem     | 700    | Normal tracking, line-height 1.1; 2.25rem below 1024px, always under the hero         |
-| Item heading    | 2rem     | 700    | Card, feature and step titles; 1.5rem below 1024px                                    |
-| Body            | 1.125rem | 400    | `#333333`, line-height 1.5; section copy capped at 36rem (about 70 characters a line) |
-| Section label   | 0.875rem | 600    | Uppercase, +0.05em tracking today — the small label above a section heading           |
-
-Measured from the rendered scaffold (1440px and 390px wide), not transcribed from tokens. Bold headings at normal tracking follow the foundation's pinned direction (#6493).
-
-The small label above a section heading is **kept** as part of this foundation's voice (operator-disposed 2026-09-22) and is headed toward the treatment below.
-
-## Layout
-
-Full navigation; a multi-column footer; the default home. The home-only announcement banner is off by default (`layout.announcementBanner`). Every page this site carries is listed in its roster of record, `.ailk-site-manifest.json` at the site root. Shared foundation: a 1280px container, sections at 7rem (4rem below 1024px), card grids at 1.5rem, breakpoints 320 / 768 / 1024 / 1440.
-
-## Shapes
-
-Square corners everywhere (`theme.corners: square`) — buttons, cards, the auth card, image placeholders; the tokens above are the base foundation's defaults a site overrides.
-
-## Components
-
-### Buttons
-
-Primary: black fill, white label, 0.5rem corners. Secondary: transparent with a black 1px outline and black label. Both are the library `Button`.
-
-### Cards / Containers
-
-White panels with a black 1px outline, 0.75rem corners, `card` (1.5rem) padding. The one exception today: the "how it works" steps render as dark filled cards (see below).
-
-### Navigation
-
-Full navigation: wordmark left, page links, an outlined and a filled button at the far right. A black hairline separates it from the page. Page links are 16px at weight 400. The two buttons are 42px tall on a 44px touch target and keep the 0.5rem button radius; square corners arrive with the platform radius change below, not in the nav alone (#6508). The Product link opens, on hover or keyboard, a 640px two-column panel whose items each show an icon, a title and a one-line description.
-
-## Where this is heading
-
-The foundation's pinned direction is the pacing of a classic wireframe marketing kit — `standardissue.webflow.io` is the reference for rhythm, type scale, spacing density and section pacing only; no image, copy or code is taken from it. The four traits this section used to list as blocked now ship as settings, so the rendered site matches the reference:
-
-| Trait                                                  | How it is set                                                                                     |
-| ------------------------------------------------------ | ------------------------------------------------------------------------------------------------- |
-| Square corners on buttons, cards and inputs            | `theme.corners: square` in `_site.mdx`                                                            |
-| Section label in sentence case, bold, no tracking      | `theme.eyebrowCase: sentence`                                                                     |
-| Solid grey image placeholders, no outline              | `theme.placeholders: fill`                                                                        |
-| Bare check and cross marks, no circle badge            | `theme.checkmarks: plain`                                                                         |
-| Plain, uncarded feature and step items                 | per section: `itemStyle: plain`, and `variant: steps` for an image beside a numbered list         |
-| A left hero whose headline wraps at half the container | `measure: narrow` on the hero (pricing); `gapBelow: tight` where a list follows the hero directly |
-| A three-up post grid on the blog index                 | `blog-list` `variant: grid` (cover · date · read time · title · excerpt · Read more)              |
-| A plans section that leads its page                    | drop the hero; the pricing section owns the `<h1>` (`ownsPageTitle`)                              |
-
-## Do's and Don'ts
-
-- **Do** keep every page built from registered sections. If a section you need does not exist, request it rather than writing one-off markup.
-- **Do** change colours in `content/_site.mdx` `theme.colors`; they reach every section.
-- **Don't** add a colour accent. The foundation's one idea is black on white; a brand pass adds colour deliberately, through the theme.
-- **Don't** replace a black rule with a shadow or a grey fill.
-- **Don't** hard-code the "heading toward" values above into a page. They arrive through the platform, or not at all.

package/site-templates/simple-service/TEMPLATE-MANIFEST.md

@@ -1,333 +0,0 @@
-# Template manifest — `simple-service`
-
-> The T1 lawn-care template (#6087, Epic #5778) — the first site shape that composes `scheduling` and `commerce`: three priced services, a booker, a checkout return pair and a purchase policy (cancellation and refunds, #6646). Generated file: the regions between `<!-- generated:begin <id> -->` and `<!-- generated:end -->` are produced by `scripts/build-template-manifest.mjs --template simple-service` from the composed layer stack (this tree → its required modules → `_base` → the always-copied overlay), each roster row's MDX `sections[]`, and `component-catalog.json`. Everything outside the markers is written by hand.
-
-| Field                  | Value                                                                                                                     |
-| ---------------------- | ------------------------------------------------------------------------------------------------------------------------- |
-| Template               | `simple-service`                                                                                                          |
-| Level                  | Pro (derived from `requires` — `scheduling` and `commerce` are paid; never declared)                                      |
-| `requires`             | `[marketing, scheduling, commerce]` — the first template to take `commerce`                                               |
-| `extends`              | `_base` — lineage only, never level                                                                                       |
-| Delivery               | licence-checked module bundle (#5441); never in the Free tarball                                                          |
-| Sample content posture | every line of copy, and all three service prices, are **placeholders** — and the prices are PUBLISHED as JSON-LD `Offer`s |
-
-## 1. Chrome
-
-This template declares **no `layout` block**. The default marketing-site chrome is what a lawn-care site wants — a nav row a reader can reach `/services` from, the four-column footer, and the document-scroll home — and the issue's STOP boundary excludes layout knobs the spec does not name.
-
-### Layout knobs (#5612)
-
-The template's `layout` block — resolved with `resolveSiteChrome`, defaults filled.
-
-<!-- generated:begin layout -->
-
-| Knob                 | Value     |
-| -------------------- | --------- |
-| `nav`                | `full`    |
-| `footer`             | `columns` |
-| `announcementBanner` | `false`   |
-| `home`               | `default` |
-
-<!-- generated:end -->
-
-### Theme (locked)
-
-The template's `theme:` block as `_site.mdx` declares it — the shape knobs and the colour overlay. Generated, so a change to a locked template's look is a red `manifest:check`, not a silent drift (starter-template contract R3.5).
-
-<!-- generated:begin theme -->
-
-| Setting                  | Value      |
-| ------------------------ | ---------- |
-| `corners`                | `square`   |
-| `eyebrowCase`            | `sentence` |
-| `placeholders`           | `fill`     |
-| `checkmarks`             | `plain`    |
-| `colors.light.bg`        | `#ffffff`  |
-| `colors.light.bgMuted`   | `#ffffff`  |
-| `colors.light.surface`   | `#ffffff`  |
-| `colors.light.border`    | `#000000`  |
-| `colors.light.text`      | `#000000`  |
-| `colors.light.textMuted` | `#333333`  |
-| `colors.light.primary`   | `#000000`  |
-| `colors.light.primaryFg` | `#ffffff`  |
-| `colors.light.accent`    | `#000000`  |
-| `colors.dark.bg`         | `#000000`  |
-| `colors.dark.bgMuted`    | `#000000`  |
-| `colors.dark.surface`    | `#000000`  |
-| `colors.dark.border`     | `#ffffff`  |
-| `colors.dark.text`       | `#ffffff`  |
-| `colors.dark.textMuted`  | `#cccccc`  |
-| `colors.dark.primary`    | `#ffffff`  |
-| `colors.dark.primaryFg`  | `#000000`  |
-| `colors.dark.accent`     | `#ffffff`  |
-
-<!-- generated:end -->
-
-## 2. The money path
-
-The whole point of this template is the first roster that takes a booking **and** the payment for it:
-
-| Step      | Where it lives                                                                                                                                                                                           |
-| --------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| Discovery | `/services` and the three `/services/<slug>` pages. Each detail page's top-level `price` + `priceCurrency` + `provider` become one schema.org `Offer` in its JSON-LD (#5838) — the free discovery floor. |
-| Booking   | `/meet`, `/meet/<slug>`, `/meet/confirmed` — the `scheduling` module's own contributed rows; `/appointments` is the site owner's own list (#6086).                                                       |
-| Payment   | a provider-hosted page on the seller's own Stripe account. Nothing on this site renders a card form.                                                                                                     |
-| Return    | `/purchase/success` and `/purchase/cancel` — base tree under #6084 D12's shape-2 disposition, gated at request time on the `commerce` licence claim.                                                     |
-| Policies  | `/purchase-policy` (#6646) — cancellation and refunds sections, this template's service-shape override of the overlay's product-shape seed.                                                              |
-
-## 3. Pages
-
-One `page=<route>` region per roster row, generated from the seed file the composed layer stack lands for that route.
-
-`/`:
-
-<!-- generated:begin page=/ -->
-
-| #   | Section                                                    | Component | Copy (first line)                              |
-| --- | ---------------------------------------------------------- | --------- | ---------------------------------------------- |
-| 1   | `hero` (centered · eyebrow "{Your service area}" · 2 CTAs) | `Hero`    | {Lawn care that turns up when it says it will} |
-| 2   | `items` (columns=3 · items ×3)                             | `Items`   | What we do                                     |
-| 3   | `cta` (minimal · 2 CTAs)                                   | `CTA`     | Ready for a tidier yard?                       |
-
-<!-- generated:end -->
-
-`/services`:
-
-<!-- generated:begin page=/services -->
-
-| #   | Section                                | Component | Copy (first line)        |
-| --- | -------------------------------------- | --------- | ------------------------ |
-| 1   | `hero` (centered · eyebrow "Services") | `Hero`    | Three jobs, three prices |
-| 2   | `items` (columns=3 · items ×3)         | `Items`   | What we do               |
-| 3   | `cta` (minimal · 1 CTA)                | `CTA`     | Not sure which one?      |
-
-<!-- generated:end -->
-
-`/services/[slug]`:
-
-<!-- generated:begin page=/services/[slug] -->
-
-_Detail route over `content/en/Service/` — 3 seed pages: `landscape-design.mdx`, `lawn-maintenance.mdx`, `seasonal-cleanup.mdx`._
-<!-- generated:end -->
-
-`/about`:
-
-<!-- generated:begin page=/about -->
-
-| #   | Section                                    | Component      | Copy (first line)                          |
-| --- | ------------------------------------------ | -------------- | ------------------------------------------ |
-| 1   | `content-block` (narrow · eyebrow "About") | `ContentBlock` | {A small crew, the same yards, every week} |
-| 2   | `cta` (minimal · 2 CTAs)                   | `CTA`          | Want us to take a look?                    |
-
-<!-- generated:end -->
-
-`/contact`:
-
-<!-- generated:begin page=/contact -->
-
-| #   | Section                               | Component | Copy (first line)        |
-| --- | ------------------------------------- | --------- | ------------------------ |
-| 1   | `hero` (centered · eyebrow "Contact") | `Hero`    | Tell us about the yard   |
-| 2   | `cta` (minimal · 1 CTA)               | `CTA`     | Would a visit be faster? |
-
-<!-- generated:end -->
-
-`/faq`:
-
-<!-- generated:begin page=/faq -->
-
-| #   | Section                                                       | Component | Copy (first line)      |
-| --- | ------------------------------------------------------------- | --------- | ---------------------- |
-| 1   | `faq` (centered · items ×5 · supportLink · initialOpen first) | `FAQ`     | Questions              |
-| 2   | `cta` (minimal · 1 CTA)                                       | `CTA`     | Still have a question? |
-
-<!-- generated:end -->
-
-`/glossary`, `/newsletter` (base-layer seeds every starter carries, #6658 D5):
-
-<!-- generated:begin page=/glossary -->
-
-| #   | Section                             | Component       | Copy (first line)                            |
-| --- | ----------------------------------- | --------------- | -------------------------------------------- |
-| 1   | `hero` (eyebrow "Glossary" · 1 CTA) | `Hero`          | {Glossary: the terms your customers look up} |
-| 2   | `glossary-index` (columns)          | `GlossaryIndex` | {Terms, A to Z}                              |
-
-<!-- generated:end -->
-
-<!-- generated:begin page=/newsletter -->
-
-| #   | Section                               | Component    | Copy (first line)                                |
-| --- | ------------------------------------- | ------------ | ------------------------------------------------ |
-| 1   | `hero` (eyebrow "Newsletter" · 1 CTA) | `Hero`       | {Newsletter: what subscribers get and how often} |
-| 2   | `newsletter`                          | `Newsletter` | Subscribe                                        |
-| 3   | `faq` (expanded · items ×3)           | `FAQ`        | FAQs                                             |
-
-<!-- generated:end -->
-
-`/book-a-call` (this template's own override of the base seed — the call to action opens the `/meet` booker the scheduling module supplies, not `/contact`):
-
-<!-- generated:begin page=/book-a-call -->
-
-| #   | Section                                | Component | Copy (first line)                          |
-| --- | -------------------------------------- | --------- | ------------------------------------------ |
-| 1   | `hero` (eyebrow "Book a call" · 1 CTA) | `Hero`    | {Book a call: what a visitor gets from it} |
-| 2   | `items` (columns=3 · items ×3)         | `Items`   | What happens on the call?                  |
-
-<!-- generated:end -->
-
-`/purchase-policy`:
-
-<!-- generated:begin page=/purchase-policy -->
-
-| #   | Section                             | Component         | Copy (first line) |
-| --- | ----------------------------------- | ----------------- | ----------------- |
-| 1   | `document-chassis` (layout=article) | `DocumentChassis` | Purchase Policy   |
-
-<!-- generated:end -->
-
-`/privacy`:
-
-<!-- generated:begin page=/privacy -->
-
-| #   | Section                             | Component         | Copy (first line) |
-| --- | ----------------------------------- | ----------------- | ----------------- |
-| 1   | `document-chassis` (layout=article) | `DocumentChassis` | Privacy Policy    |
-
-<!-- generated:end -->
-
-`/terms`:
-
-<!-- generated:begin page=/terms -->
-
-| #   | Section                             | Component         | Copy (first line) |
-| --- | ----------------------------------- | ----------------- | ----------------- |
-| 1   | `document-chassis` (layout=article) | `DocumentChassis` | Terms of Service  |
-
-<!-- generated:end -->
-
-`/account`:
-
-<!-- generated:begin page=/account -->
-
-_Code route — no content, no sections._
-<!-- generated:end -->
-
-`/purchase/success`:
-
-<!-- generated:begin page=/purchase/success -->
-
-_Code route — no content, no sections._
-<!-- generated:end -->
-
-`/purchase/cancel`:
-
-<!-- generated:begin page=/purchase/cancel -->
-
-_Code route — no content, no sections._
-<!-- generated:end -->
-
-`/thanks/[slug]`:
-
-<!-- generated:begin page=/thanks/[slug] -->
-
-_Code route — no content, no sections._
-<!-- generated:end -->
-
-`/meet`:
-
-<!-- generated:begin page=/meet -->
-
-_Code route — no content, no sections._
-<!-- generated:end -->
-
-`/meet/[slug]`:
-
-<!-- generated:begin page=/meet/[slug] -->
-
-_Code route — no content, no sections._
-<!-- generated:end -->
-
-`/meet/confirmed`:
-
-<!-- generated:begin page=/meet/confirmed -->
-
-_Code route — no content, no sections._
-<!-- generated:end -->
-
-`/appointments`:
-
-<!-- generated:begin page=/appointments -->
-
-_Code route — no content, no sections._
-<!-- generated:end -->
-
-## 4. Roster, as the registry declares it
-
-`simple-service` is the second declared template that does not reuse `TEMPLATE_BASE_ROSTER`: a lawn-care site sells three named services from `/services`, not from a pricing table, so `/how-it-works`, the product page (`/software/product`) and `/pricing` are not pages this site has. The roster is what the template IS, so an unrostered page has neither a route directory nor its seed: `scaffold()` installs a `_base` or overlay seed only for a row that names it (#6646), so `content/en/Pricing/pricing.mdx` does not land. The merged roster, as the registry composes it:
-
-<!-- generated:begin roster -->
-
-```
-simple-service:
-  requires: [marketing, scheduling, commerce]
-  categories: [landscaping]
-  shape: local-business-service
-  design: standard
-  roster:
-    - { route: "/",                 kind: page, content: ["content/en/HomePage/home.mdx"] }
-    - { route: "/services",         kind: page, content: ["content/en/ServicesList/services.mdx"] }
-    - { route: "/services/[slug]",  kind: page, contentDir: "content/en/Service" }
-    - { route: "/about",            kind: page, content: ["content/en/AboutPage/about.mdx"] }
-    - { route: "/contact",          kind: page, content: ["content/en/ContactPage/contact.mdx"] }
-    - { route: "/faq",              kind: page, content: ["content/en/FAQPage/faq.mdx"] }
-    - { route: "/glossary",         kind: page, content: ["content/en/GlossaryList/glossary.mdx"] }
-    - { route: "/newsletter",       kind: page, content: ["content/en/NewsletterSignup/newsletter.mdx"] }
-    - { route: "/book-a-call",      kind: page, content: ["content/en/BookCall/book-call.mdx"] }
-    - { route: "/purchase-policy",  kind: page, content: ["content/en/PurchasePolicyPage/purchase-policy.mdx"] }
-    - { route: "/privacy",          kind: page, content: ["content/en/PrivacyPage/privacy.mdx"] }
-    - { route: "/terms",            kind: page, content: ["content/en/TermsPage/terms.mdx"] }
-    - { route: "/account",          kind: route }
-    - { route: "/purchase/success", kind: route }
-    - { route: "/purchase/cancel",  kind: route }
-    - { route: "/thanks/[slug]",    kind: route }
-    - { route: "/meet",             kind: route }
-    - { route: "/meet/[slug]",      kind: route }
-    - { route: "/meet/confirmed",   kind: route }
-    - { route: "/appointments",     kind: route }
-```
-
-<!-- generated:end -->
-
-By source:
-
-```
-template:    / · /services · /services/<slug> · /about · /contact · /faq
-             /purchase-policy · /privacy · /terms · /account
-             /purchase/success · /purchase/cancel · /thanks/<slug>
-scheduling:  /meet · /meet/<slug> · /meet/confirmed · /appointments
-```
-
-**Why the two `/purchase/*` rows are the TEMPLATE's and not the `commerce` module's.** #6084 landed the checkout return pair under the operator's shape-2 disposition (#6084 D12): `CORE_ROUTE_DIRS` carries `[locale]/purchase`, and neither `GATEABLE_SURFACES` nor `MODULE_SURFACES.commerce` gained an entry, so `MODULE_SLICES.commerce` contributes **no** `pageContributions` at all. Nothing else claims the two routes, so declaring them here trips no both-claimants refusal — and the issue's AC-1 requires the merged roster to carry them. The four scheduling rows, by contrast, **are** the module's, and declaring one here would make `mergeRoster` refuse this template outright.
-
-`/account` and `/purchase-policy` carry no `GATEABLE_SURFACES` entry and need none: `(authed)` ships unconditionally, and `/purchase-policy` has no gateable surface at all, so it is always copied. The six module-less surfaces this roster enables are `book-a-call`, `glossary`, `newsletter`, `privacy`, `services` and `terms`.
-
-## 5. Component inventory
-
-Every component the roster rows' seed content composes today (generated):
-
-<!-- generated:begin inventory -->
-
-| Tier     | Used by this template                                                                           |
-| -------- | ----------------------------------------------------------------------------------------------- |
-| Shell    | `MarketingShell`                                                                                |
-| Chrome   | `Nav`, `Footer`, `Banner` (+ `BannerConsentIsland`, `BannerDismissIsland`)                      |
-| Sections | `ContentBlock`, `CTA`, `DocumentChassis`, `FAQ`, `GlossaryIndex`, `Hero`, `Items`, `Newsletter` |
-
-<!-- generated:end -->
-
-## 6. Known gaps this manifest depends on
-
-| Gap                                                                                          | Issue |
-| -------------------------------------------------------------------------------------------- | ----- |
-| No routes-map row for `/account`, `/appointments` or `/purchase/*`, so those rows show blank | #5572 |
-| The Pro demo host `simple-service.ailaunchkit.ai` — provisioning is the runbook's act        | #5778 |

package/site-templates/simple-service/ailk-template.json

@@ -1,11 +0,0 @@
-{
-  "name": "simple-service",
-  "requires": ["marketing", "scheduling", "commerce"],
-  "extends": "_base",
-  "$comment": "The T1 lawn-care template (#6087, Epic #5778) — the first site shape that composes scheduling and commerce. Composed base -> modules -> template: /privacy and /terms arrive with the _base layer this extends (its unrostered /pricing seed does not install, #6646), and /purchase-policy is this tree's own service-shape override of the overlay's product-shape seed (#6646 — cancellation and refunds sections); /meet, /meet/<slug>, /meet/confirmed and /appointments with the scheduling bundle; /purchase/success and /purchase/cancel are BASE TREE (#6084 D12 shape 2 — CORE_ROUTE_DIRS carries [locale]/purchase and the commerce licence claim, not the scaffold, decides whether they serve); the Free about/contact/faq compositions with the overlay, which this template's own /about, /contact and /faq files then override; the overlay's other seeds (/use-cases, the /software/product page, the /blog teaser) are unrostered here and do not install (#6646). This tree holds ONLY its own compositions and its placeholder copy. It declares no layout block — the default marketing-site chrome is what this template renders with, and the code registry (TEMPLATE_MANIFESTS) is authoritative for a template create-ailk ships, so a duplicate block here would be a second authority for one fact. installMap: bundle-relative source -> scaffold-relative destination; the stager reads only installMap/postInstall/patches. Unmapped content/en/** lands at the scaffold root's content/, exactly as marketing-site-free's does.",
-  "installMap": {
-    "provenance.json": ".ailk-template.json",
-    "TEMPLATE-MANIFEST.json": ".ailk-site-manifest.json"
-  },
-  "postInstall": "Template simple-service installed. This is the lawn-care shape: three priced services at /services (content/en/Service/), a booker at /meet from the scheduling module, the site owner's own list at /appointments, and the checkout return pair at /purchase/success and /purchase/cancel. /privacy, /terms, /glossary and /newsletter came with the base layer, and /book-a-call is this template's own override of the base seed, its call to action opening the /meet booker. This template adds the home page, /services and its three detail pages, /about, /contact, /faq and /purchase-policy (cancellation and refunds). THE THREE PRICES ARE PLACEHOLDERS AND THEY ARE PUBLISHED: each service page's top-level price and priceCurrency become a schema.org Offer in that page's JSON-LD, which is what an agent reading your site quotes back to a buyer — replace all three, and the provider name with them, before you launch. Taking money needs the commerce licence claim and your own Stripe account: without the claim the return pages 404 by design. EVERY line of copy on this site is a placeholder too — replace it before you launch."
-}

package/site-templates/simple-service/content/en/BookCall/book-call.mdx

@@ -1,53 +0,0 @@
----
-type: "BookCall"
-slug: "book-call"
-title: "{Book a call: what a visitor gets from it}"
-description: "{One sentence on who the call is for and what they leave with}"
-placeholder: true
-schema:
-  mainEntity:
-    "@type": "Offer"
-    name: "{Your call name}"
-    price: 0
-    priceCurrency: "USD"
-sections:
-  [
-    {
-      "id": "hero",
-      "type": "hero",
-      "data":
-        {
-          "eyebrow": "Book a call",
-          "headline": "{Book a call: what a visitor gets from it}",
-          "subheadline": "{One sentence on who the call is for and what they leave with}",
-          "primaryCta": { "label": "Book a time", "href": "/meet" },
-        },
-    },
-    {
-      "id": "what-happens-on-the-call",
-      "type": "items",
-      "data":
-        {
-          "headline": "What happens on the call?",
-          "columns": 3,
-          "items":
-            [
-              {
-                "title": "{The first thing you cover}",
-                "description": "{One or two sentences on what the visitor learns or decides here}",
-              },
-              {
-                "title": "{The second thing you cover}",
-                "description": "{One or two sentences on what the visitor learns or decides here}",
-              },
-              {
-                "title": "{The next step you agree}",
-                "description": "{One or two sentences on what happens after the call}",
-              },
-            ],
-        },
-    },
-  ]
----
-
-{/* Rendered from frontmatter `sections[]` by the /book-a-call route. This template carries the scheduling module, so the call to action opens the /meet booker. It overrides the base layer's copy, which points at /contact. The `schema:` Offer is the page's JSON-LD main entity — a free call. Placeholder copy — replace every {brace} with your own words before you launch. */}