@mccaskie-labs/workbench-config 0.2.5 → 0.3.1

package/dist/capabilities.gen.d.ts

@@ -1,4 +1,4 @@
-export declare const MANIFEST_VERSION: "b74fc43c59b7";
+export declare const MANIFEST_VERSION: "9aae488ad117";
 export declare const capabilities: {
     readonly ai: {
         readonly $schema: "./schema.json";
@@ -454,6 +454,221 @@ export declare const capabilities: {
             readonly intro: "Counting page views and the things visitors do on the site.";
         };
     };
+    readonly availability: {
+        readonly $schema: "./schema.json";
+        readonly format: 1;
+        readonly component: "availability";
+        readonly title: "Availability and pricing";
+        readonly summary: "workbench-availability answers \"is this date free, and what does it cost?\" for a bookable thing (a venue, a room, a photographer's day) from its calendar and its price rules, with the same answer every time and one plain line per rule applied. A store over the app's own database stops two bookings landing on one date, and a tap-to-block calendar lets the owner close dates from a phone. It runs in the app itself, with no Gateway call, no AI and no cost.";
+        readonly status: "built";
+        readonly surfaces: {
+            readonly package: readonly ["quote", "createAvailability", "availabilityMigration", "calendarAction", "checkSettings", "stayClaims", "staysClash", "todayIn", "AvailabilityError"];
+        };
+        readonly rules: readonly [{
+            readonly id: "availability.quote-is-fact";
+            readonly kind: "must";
+            readonly text: "Take every availability answer and price the app shows or sends from quote() (or createAvailability's quote), and pass its lines and explain on as facts. Never let AI work out a price or a free date, and never write a price into a page or prompt by hand.";
+            readonly enforced_by: "review";
+            readonly probe: "availability.quote";
+        }, {
+            readonly id: "availability.book-through-block";
+            readonly kind: "must";
+            readonly text: "Book, hold and block dates only through createAvailability's block(), which runs availability_block() in one transaction: never insert into availability_blocks directly, so the exclusion constraint and the hold expiry always apply.";
+            readonly enforced_by: "database";
+            readonly probe: "availability.store";
+        }, {
+            readonly id: "availability.calendar-days";
+            readonly kind: "must";
+            readonly text: "Treat dates as calendar days (YYYY-MM-DD) in the account's time zone: pass todayIn(timeZone) as today, never new Date() in UTC.";
+            readonly enforced_by: "types";
+            readonly probe: "availability.quote";
+        }, {
+            readonly id: "availability.no-names-in-notes";
+            readonly kind: "must_not";
+            readonly text: "Write a guest's name or phone number into a block's note: link the app's own booking in subject instead. The .ics feed carries neither.";
+            readonly enforced_by: "review";
+            readonly probe: "availability.store";
+        }, {
+            readonly id: "availability.public-gets-the-quote";
+            readonly kind: "must_not";
+            readonly text: "Let a public page or the anonymous key read availability_blocks: public pages get the finished quote from the server.";
+            readonly enforced_by: "database";
+            readonly probe: "availability.store";
+        }, {
+            readonly id: "availability.daily-cleanup";
+            readonly kind: "must";
+            readonly text: "Run createAvailability's cleanup() once a day from the app's cron with the service client, so lapsed holds show as expired and old blocks are deleted on time.";
+            readonly enforced_by: "review";
+            readonly probe: "availability.store";
+        }, {
+            readonly id: "availability.calendar-as-shipped";
+            readonly kind: "must";
+            readonly text: "Draw the owner's calendar with renderCalendar and CALENDAR_SCRIPT (under the page's nonce), and hand the posted body to calendarAction behind the owner's sign-in. Never hand-write the calendar's markup or script.";
+            readonly enforced_by: "review";
+            readonly probe: "availability.calendar";
+        }];
+        readonly examples: readonly [{
+            readonly id: "availability.example.quote";
+            readonly title: "Answer \"is 12 Dec free, and how much?\"";
+            readonly lang: "ts";
+            readonly code: "import { createAvailability } from '@mccaskie-labs/workbench-availability'\nimport settings from '../workbench/availability.json'\n\nconst av = createAvailability({ db: serviceClient, account: venue.id, settings, country: 'PH', timeZone: 'Asia/Manila' })\nconst q = await av.quote({ resource: 'villa-sol-pool', date: '2026-12-12', stay: 'day_use', guests: { min: 15, max: 15 }, eventType: 'birthday' })\n// q.available 'yes'; q.options[0].total { amount: '9500.00', currency: 'PHP' }; q.explain ['Weekend day use: ₱9,500 (rule r-weekend)', ...]";
+            readonly probe: "availability.quote";
+        }, {
+            readonly id: "availability.example.calendar";
+            readonly title: "The owner's tap-to-block calendar";
+            readonly lang: "ts";
+            readonly code: "import { calendarAction } from '@mccaskie-labs/workbench-availability'\nimport { CALENDAR_SCRIPT, renderCalendar } from '@mccaskie-labs/workbench-availability/calendar'\n\nconst days = await av.month('villa-sol-pool', '2026-12')\nconst html = renderCalendar(days, t, { resource: 'villa-sol-pool', month: '2026-12', endpoint: '/owner/calendar', stays: [{ id: 'day_use', label: t('ui.stay.day_use')! }] })\n// The page adds <script nonce=...>${CALENDAR_SCRIPT}</script>; POST /owner/calendar (owner signed in):\nconst r = await calendarAction(av, await request.json())\nreturn Response.json(r.body, { status: r.status })";
+            readonly probe: "availability.calendar";
+        }];
+        readonly probes: readonly [{
+            readonly id: "availability.quote";
+            readonly half: "runtime";
+            readonly expect: "pass";
+            readonly smoke: true;
+            readonly cost_hint_usd: 0;
+            readonly note: "In the Worker itself: quote() on the spec's HmPo example (Sat 12 Dec ₱9,500, Sat 19 Dec ₱10,925 with peak, 25 guests ₱10,250 over capacity, no guests a from price) and the alternatives when 19 Dec is booked; no database, no Gateway call";
+        }, {
+            readonly id: "availability.store";
+            readonly half: "runtime";
+            readonly expect: "pass";
+            readonly cost_hint_usd: 0;
+            readonly note: "Against the probe app's own database: two block(booked) calls for one night at once (one lands, one refused as clash), a lapsed hold quoted free and marked expired by cleanup(), another account's resource unreachable, then every probe block removed";
+        }, {
+            readonly id: "availability.calendar";
+            readonly half: "runtime";
+            readonly expect: "pass";
+            readonly cost_hint_usd: 0;
+            readonly note: "The probe page draws a month with renderCalendar and CALENDAR_SCRIPT: tap, Block day, Undo leaves no block; a change made offline shows \"1 change waiting\" and is sent on reconnect";
+        }];
+        readonly offer: {
+            readonly pattern: "settings";
+            readonly when: "The client takes bookings for something with dates: a venue, a room, a resort day pass, a photographer's or hire business's days, or wants prices that depend on the day, season, holiday, number of guests or kind of event, or wants a calendar to block dates.";
+            readonly say: "I'll set this up with Workbench availability, so every price and free date comes out the same way each time, explained line by line, and you get a calendar to block dates from your phone. Here's how a business like yours usually books; tell me what to change.";
+            readonly answers_file: "workbench/availability.json";
+            readonly answers_format: "`{ \"format\": 1, \"status\": \"draft\" | \"done\", \"what\": \"<the client's words>\", \"stay_types\": [{ \"id\", \"start\", \"end\", \"clashes\" }], \"event_types\": [...], \"currency\": \"PHP\", \"alternatives\": { \"count\": 3, \"within_days\": 21 }, \"hold_days\": 3, \"holidays\": \"weekend\" | \"weekday\" | \"separate\" }`. Every stay type clashes with itself; list each pair that can't share a date on both sides. Take `currency` from workbench/country.json. checkSettings() reads this file at startup and names every problem. Each account's resources, packages and price rules are data in the app's database (availability_resources, availability_packages, availability_price_rules), entered on the owner's pages, never in this file. Copy availabilityMigration into supabase/migrations with its down file, and CALENDAR_WORDS into the strings catalogue.";
+            readonly questions: readonly [{
+                readonly id: "availability.what";
+                readonly sets: "availability.what";
+                readonly ask: "What do people book?";
+                readonly style: "table";
+                readonly other: {
+                    readonly kind: "text";
+                    readonly min: 3;
+                    readonly max: 200;
+                    readonly description: "In the client's words, such as \"a resort's pool and function hall\" or \"me, as a photographer, by the half or full day\".";
+                };
+                readonly must_ask: true;
+                readonly note: "Only the client knows. Their answer names the resources (one per thing booked separately) and suggests the stay types to propose next.";
+            }, {
+                readonly id: "availability.stays";
+                readonly sets: "availability.stay_types";
+                readonly ask: "Here are the usual ways it's booked in a day, with their hours and which can't share a date. Accept them, change some, or add or remove?";
+                readonly style: "table";
+                readonly other: {
+                    readonly kind: "list";
+                    readonly min: 1;
+                    readonly max: 10;
+                    readonly description: "Each way it's booked, with its start and end time and the others it can't share a date with.";
+                };
+                readonly must_ask: true;
+                readonly note: "Propose from the client's answer to availability.what. A resort or venue: day use 08:00 to 17:00, night use 19:00 to 07:00, overnight 14:00 to 12:00 the next day (overnight clashes with both; day and night use don't clash with each other). A photographer or hire business: half day and full day, clashing with each other. One room or slot a day: a single stay type.";
+            }, {
+                readonly id: "availability.events";
+                readonly sets: "availability.event_types";
+                readonly ask: "Should prices depend on the kind of event? Here is the usual list.";
+                readonly style: "cards";
+                readonly answers: readonly [{
+                    readonly label: "Yes, use this list";
+                    readonly value: "list";
+                    readonly means: "Birthday, debut, wedding, baptism, reunion, team building, other: a rule can add a fee for some of them.";
+                }, {
+                    readonly label: "No, same price for all";
+                    readonly value: "none";
+                    readonly means: "No event types; the quote never asks for one.";
+                }, {
+                    readonly label: "Yes, with my own list";
+                    readonly value: "own";
+                    readonly means: "Type the kinds of event the business prices differently.";
+                }];
+                readonly other: {
+                    readonly kind: "list";
+                    readonly min: 1;
+                    readonly max: 20;
+                    readonly description: "The kinds of event, each a short name.";
+                };
+                readonly note: "Recommend the usual list for venues and resorts; \"none\" for most other businesses. Write ids in lower case with underscores (team_building).";
+            }, {
+                readonly id: "availability.holidays";
+                readonly sets: "availability.holidays";
+                readonly ask: "Should holidays be priced like weekends?";
+                readonly style: "cards";
+                readonly answers: readonly [{
+                    readonly label: "Yes, like a weekend";
+                    readonly value: "weekend";
+                    readonly means: "A regular holiday or special non-working day on a weekday costs the weekend price.";
+                }, {
+                    readonly label: "No, by the day of the week";
+                    readonly value: "weekday";
+                    readonly means: "Holidays cost what their day of the week costs.";
+                }, {
+                    readonly label: "Set holiday prices separately";
+                    readonly value: "separate";
+                    readonly means: "Holidays get their own price rules, entered on the owner's pages.";
+                }];
+                readonly other: {
+                    readonly kind: "text";
+                    readonly min: 3;
+                    readonly max: 200;
+                    readonly description: "How holidays should be priced, in the client's words.";
+                };
+                readonly note: "Holidays come from workbench-country's yearly list (the Philippines' proclamation each year); a local fiesta goes in the availability_holidays table. Special working days (the EDSA anniversary) are never priced as holidays.";
+            }, {
+                readonly id: "availability.holds";
+                readonly sets: "availability.hold_days";
+                readonly ask: "How long is a date held while waiting for a deposit?";
+                readonly style: "cards";
+                readonly answers: readonly [{
+                    readonly label: "3 days";
+                    readonly value: 3;
+                    readonly means: "The date shows as held (H) for 3 days, then is free again unless marked booked.";
+                }, {
+                    readonly label: "1 day";
+                    readonly value: 1;
+                }, {
+                    readonly label: "7 days";
+                    readonly value: 7;
+                }, {
+                    readonly label: "No holds";
+                    readonly value: 0;
+                    readonly means: "A date is free until it is booked; nothing is held.";
+                }];
+                readonly other: {
+                    readonly kind: "whole";
+                    readonly min: 0;
+                    readonly max: 60;
+                    readonly description: "Days, 0 to 60.";
+                };
+            }];
+            readonly not_asked: readonly [{
+                readonly sets: "availability.prices";
+                readonly why: "Each account's prices, packages and rules change often, so they are data the owner enters on their own pages (or that onboarding reads from their rate card), not project settings.";
+            }, {
+                readonly sets: "availability.alternatives";
+                readonly why: "Up to 3 nearest free dates within 21 days, same weekday first, suits every business so far; change it in the answers file if a client asks.";
+            }, {
+                readonly sets: "availability.currency";
+                readonly why: "It is the country's own, from workbench/country.json.";
+            }];
+            readonly needs: readonly ["country"];
+        };
+        readonly styles: {
+            readonly prefix: "wb-cal-";
+        };
+        readonly delivery: {
+            readonly choice: "optional";
+            readonly intro: "Which dates are free and what each costs, worked out the same way every time, with a calendar the owner taps to block dates.";
+        };
+    };
     readonly config: {
         readonly $schema: "./schema.json";
         readonly format: 1;
@@ -552,7 +767,7 @@ export declare const capabilities: {
         readonly summary: "workbench-country writes dates, times, numbers and money the way readers in the Philippines, Australia, the UK and the US expect, from one pack per country, and gives each pack's spelling for the Gateway. It runs in the app itself, with no Gateway call and no cost.";
         readonly status: "built";
         readonly surfaces: {
-            readonly package: readonly ["COUNTRY_PACKS", "countryPackFor", "audiencePack", "checkPack", "CountryPackError", "formatDate", "formatDateTime", "calendarDayIn", "formatNumber", "formatMoney", "formattingLocale", "currencySymbol", "currencySymbolFrom", "WORLDWIDE", "isWorldwide"];
+            readonly package: readonly ["COUNTRY_PACKS", "countryPackFor", "audiencePack", "checkPack", "CountryPackError", "formatDate", "formatDateTime", "calendarDayIn", "formatNumber", "formatMoney", "formattingLocale", "currencySymbol", "currencySymbolFrom", "WORLDWIDE", "isWorldwide", "HOLIDAYS", "holidaysFor", "holidayOn", "checkHolidays"];
         };
         readonly rules: readonly [{
             readonly id: "country.one-formatter";
@@ -572,6 +787,12 @@ export declare const capabilities: {
             readonly text: "Write an amount with a bare \"$\": Australian dollars are A$ and US dollars US$.";
             readonly enforced_by: "types";
             readonly probe: "country.packs";
+        }, {
+            readonly id: "country.holidays-from-proclamation";
+            readonly kind: "must";
+            readonly text: "Take public holidays from holidaysFor or holidayOn, never worked out or guessed: a year with no list returns undefined, and checkHolidays fails from 1 December until next year's list is in.";
+            readonly enforced_by: "review";
+            readonly probe: "country.holidays";
         }, {
             readonly id: "country.spelling-from-pack";
             readonly kind: "must";
@@ -599,6 +820,13 @@ export declare const capabilities: {
             readonly expect: "pass";
             readonly cost_hint_usd: 0;
             readonly note: "Every pack's spelling is one the Gateway accepts (en-PH, en-AU, en-GB, en-US), checked against the ai manifest's spellings; no Gateway call";
+        }, {
+            readonly id: "country.holidays";
+            readonly half: "runtime";
+            readonly expect: "pass";
+            readonly smoke: true;
+            readonly cost_hint_usd: 0;
+            readonly note: "The December probe: checkHolidays for every country with a built-in list, on today in that country's time zone. Fails when this year's list is missing, and from 1 December when next year's is, so the list is added from the proclamation before January's prices need it";
         }];
         readonly offer: {
             readonly pattern: "project";
@@ -909,10 +1137,33 @@ export declare const capabilities: {
             readonly cost_hint_usd: 0;
             readonly note: "On a project's staging: cf_turnstile_widget_create and the turnstile_sitekey and turnstile_secret sources; the sign-in page shows the check, /auth/code without a passed token sends no code, and with one it does";
         }];
+        readonly offer: {
+            readonly pattern: "settings";
+            readonly when: "The app needs to store or read data, or the client asks for a change to what is stored: a new table, column, rule or migration.";
+            readonly say: "The app's data goes in its own Workbench database, one for testing and one for the live site. I'll propose what to store and who can see it, and change it with a migration you can undo.";
+            readonly answers_file: "workbench/database.json";
+            readonly answers_format: "`{ \"format\": 1, \"status\": \"draft\", \"tables\": [{ \"name\": \"orders\", \"row\": \"one order\", \"columns\": [{ \"name\": \"total\", \"kind\": \"money\", \"required\": true }], \"read\": \"own\", \"change\": \"own\" }] }`. Then write one migration (`supabase/migrations/<14 digits>_<name>.sql`) with its down file, turning on row-level security with one policy per answer, apply it on staging with Workbench Control (`sb_migration_apply`), and refresh `supabase/staging-columns.json`.";
+            readonly questions: readonly [{
+                readonly id: "database.tables";
+                readonly sets: "tables";
+                readonly ask: "What should the app store, and who can see and change it?";
+                readonly style: "table";
+                readonly note: "Propose the tables the request needs, each with what one row is, its columns (name, kind such as text, number, money, date, yes/no, a link to another table; and whether it is required), and who may read and who may change its rows: `own` (the person who made the row), `admins`, `signed_in` (anyone signed in) or `public` (anyone, read only). Recommend `own` for anything about a person. Show money as whole cents, never a fraction. The client accepts, removes or adds tables and columns.";
+            }];
+            readonly not_asked: readonly [{
+                readonly sets: "keys";
+                readonly why: "The app reaches the database as the signed-in person (`dbAs`), so row-level security decides what each person sees; the template holds no secret key.";
+            }, {
+                readonly sets: "hosting";
+                readonly why: "Each project has its own staging and production databases, made by Workbench Control in the region set for the install.";
+            }, {
+                readonly sets: "sign_in_settings";
+                readonly why: "The database's sign-in settings follow the Workbench baseline (the workbench-sign-in skill).";
+            }];
+        };
         readonly delivery: {
             readonly choice: "built_in";
             readonly intro: "The app's own database, one for testing and one for the live site.";
-            readonly when: "The app needs to store or read data, or the client asks for a change to what is stored: a new table, column, rule or migration.";
         };
     };
     readonly email: {
@@ -1157,13 +1408,67 @@ export declare const capabilities: {
             readonly cost_hint_usd: 0;
             readonly note: "GET brand.json's logo.url from outside with no sign-in answers 200 with an image content type";
         }];
+        readonly offer: {
+            readonly pattern: "settings";
+            readonly when: "The app needs to send an email: a confirmation, receipt, notification, invitation or sign-in code.";
+            readonly say: "I'll send these with Workbench email, which sends from the app's own address in your brand, with no email key in the app. The sign-in codes are already there; I'll add yours beside them.";
+            readonly answers_file: "workbench/email.json";
+            readonly answers_format: "`{ \"format\": 1, \"status\": \"draft\", \"reply_to\": null, \"emails\": [{ \"id\": \"order_confirmed\", \"when\": \"a customer sends an order\", \"to\": \"the customer\", \"parts\": [\"heading\", \"paragraph\", \"button\"], \"link_changes_something\": false }] }`. Declare each email in `src/lib/emails.ts` with `defineEmails` (stream `transactional`, shell `account`, `decidedBy` naming this answers file), put its words in the strings under `email.<id>.<key>`, and send it with `mailerFor(env)` and an `idempotencyKey` whenever a retry could repeat it.";
+            readonly questions: readonly [{
+                readonly id: "email.emails";
+                readonly sets: "emails";
+                readonly ask: "Which emails should the app send?";
+                readonly style: "table";
+                readonly note: "Propose the emails the request needs, each with an id (snake_case: `order_confirmed`), when it is sent, who gets it, its parts in order (heading, paragraphs, a button and its link, small print) and whether its link changes something (then the link lands on a confirmation page first). Only emails a person's own action or account causes: receipts, confirmations, notices. The client accepts, removes or adds. The wording is drafted afterwards, one email at a time.";
+            }, {
+                readonly id: "email.reply-to";
+                readonly sets: "reply_to";
+                readonly ask: "Where should a reply to these emails go?";
+                readonly style: "cards";
+                readonly answers: readonly [{
+                    readonly label: "Nowhere";
+                    readonly value: null;
+                    readonly means: "The emails come from an address that isn't read. Say so in the small print, with where to get help instead.";
+                }, {
+                    readonly label: "To the app";
+                    readonly value: "app";
+                    readonly means: "Replies go to an address the app reads itself (Workbench inbound email).";
+                }];
+                readonly other: {
+                    readonly kind: "text";
+                    readonly min: 6;
+                    readonly max: 254;
+                    readonly description: "An email address someone at the business reads.";
+                };
+                readonly must_ask: true;
+                readonly note: "A typed address goes in each send as `replyTo`; check it looks like an email address. With the app, the workbench-email-inbound skill sets up the address.";
+            }];
+            readonly not_asked: readonly [{
+                readonly sets: "sender";
+                readonly why: "Emails come from the project's own sending address (`FROM` in `src/lib/email.ts`) on its own domain, which Workbench Control sets up.";
+            }, {
+                readonly sets: "marketing";
+                readonly why: "Only transactional email exists: newsletters and other bulk mail are refused until Workbench has a sender for them, so offer none.";
+            }, {
+                readonly sets: "look";
+                readonly why: "Emails take the brand's name, colour and logo, and the project's `project.css` (see Restyling).";
+            }];
+            readonly drafts: {
+                readonly of: "wording for one email";
+                readonly surface: "ai";
+                readonly alias: "claude-default";
+                readonly count: 3;
+                readonly max_rounds: 3;
+                readonly job: "ai.drafts";
+                readonly command: "npx workbench-ai drafts text email_<id> --about \"<what the email is for, who gets it and its parts>\"";
+            };
+        };
         readonly styles: {
             readonly prefix: "wb-email-";
         };
         readonly delivery: {
             readonly choice: "built_in";
             readonly intro: "The emails the app sends, such as confirmations, receipts and sign-in codes.";
-            readonly when: "The app needs to send an email: a confirmation, receipt, notification, invitation or sign-in code.";
         };
     };
     readonly "email-inbound": {
@@ -1266,10 +1571,45 @@ export declare const capabilities: {
             readonly two_step: true;
             readonly note: "cf_email_routing_rule_delete returns a confirmation and changes nothing until Robert approves";
         }];
+        readonly offer: {
+            readonly pattern: "switch_on";
+            readonly when: "The client wants the app to receive email: replies to its messages, or an address such as hello@ that the app handles.";
+            readonly say: "The project can already receive email with Workbench inbound email: each address goes straight to the app, which decides what to do with every message. I'll switch on the addresses you want.";
+            readonly answers_file: "workbench/email-inbound.json";
+            readonly answers_format: "`{ \"format\": 1, \"addresses\": [{ \"name\": \"hello\", \"does\": \"saves it as a message the admins see\" }] }`. Then set `INBOUND_EMAIL` to `\"on\"` in `wrangler.jsonc`, write `handleEmail` in `src/app.ts` to do what each address `does`, and make the addresses with Workbench Control: `cf_email_routing_enable`, then `cf_email_routing_rule_create` for each address on staging first (the capabilities guide below has the steps).";
+            readonly questions: readonly [{
+                readonly id: "email-inbound.addresses";
+                readonly sets: "addresses";
+                readonly ask: "Which addresses should the app receive, and what should it do with each message?";
+                readonly style: "table";
+                readonly note: "Propose the addresses the request needs, each with its name (the part before @, lower case: `hello`, `bookings`) and what the app does with a message, in the client's words: save it for the admins to read, add it to a booking, answer it automatically. One address, one job. Say plainly that the app reads the mail itself: nothing is forwarded to anyone's inbox.";
+            }, {
+                readonly id: "email-inbound.attachments";
+                readonly sets: "attachments";
+                readonly ask: "What should happen to files attached to these emails?";
+                readonly style: "cards";
+                readonly answers: readonly [{
+                    readonly label: "Leave them out";
+                    readonly value: "drop";
+                    readonly means: "The app keeps the words of each email, not its files. Nothing extra to store or check.";
+                }, {
+                    readonly label: "Keep them";
+                    readonly value: "keep";
+                    readonly means: "The app stores each file for the admins. Files can be large or unsafe, so keep only the types the job needs.";
+                }];
+                readonly note: "With keep, ask which types (photos, PDFs) and store them outside the Worker, in file storage the app already has, or ask the owner before adding some; refuse other types with `reject`.";
+            }];
+            readonly not_asked: readonly [{
+                readonly sets: "domain";
+                readonly why: "Addresses are on the project's own email domain: its staging name first, and the client's own domain once it is attached for production (`cf_zone_attach`).";
+            }, {
+                readonly sets: "forwarding";
+                readonly why: "Workbench never forwards mail outside the project or catches every address: each literal address goes to the app.";
+            }];
+        };
         readonly delivery: {
             readonly choice: "optional";
             readonly intro: "Receiving email at the project's own addresses, for the app to act on.";
-            readonly when: "The client wants the app to receive email: replies to its messages, or an address such as hello@ that the app handles.";
         };
     };
     readonly "email-sending": {
@@ -2729,10 +3069,45 @@ export declare const capabilities: {
             readonly cost_hint_usd: 0;
             readonly note: "The app's own checkStrings run passes in its tests, and npx workbench-strings check passes in CI";
         }];
+        readonly offer: {
+            readonly pattern: "project";
+            readonly when: "The client wants to add or change wording on a page or in an email, or asks about showing the app in another language.";
+            readonly say: "Every word the app shows is kept in one place with Workbench strings, so changing wording never means hunting through code, and other languages can be added later.";
+            readonly answers_file: "workbench/strings.json";
+            readonly answers_format: "`{ \"format\": 1, \"languages\": [\"en-AU\"], \"later\": [\"fil\"] }`: the language the site is written in first, and any the client wants later. New wording goes into `strings/strings.<base>.json` with one key per sentence, and `npm run check:strings` checks it.";
+            readonly questions: readonly [{
+                readonly id: "strings.languages";
+                readonly sets: "languages";
+                readonly ask: "Does the site need to be in any language besides English?";
+                readonly style: "cards";
+                readonly answers: readonly [{
+                    readonly label: "English only";
+                    readonly value: "none";
+                    readonly means: "Every page and email is in English.";
+                }, {
+                    readonly label: "Another language later";
+                    readonly value: "later";
+                    readonly means: "English now. The words are kept so a translation can be added, checked by a native speaker, without changing the code.";
+                }];
+                readonly other: {
+                    readonly kind: "text";
+                    readonly min: 2;
+                    readonly max: 120;
+                    readonly description: "The languages, such as Filipino or Spanish.";
+                };
+                readonly note: "Translations come with a Workbench tool that isn't built yet: record the languages under `later`, keep every word in the catalogue, and tell the client a translation goes live only once a named native speaker has checked it.";
+            }];
+            readonly not_asked: readonly [{
+                readonly sets: "base";
+                readonly why: "The site is written first in English, in the readers' spelling from the country answers, so it isn't asked again.";
+            }, {
+                readonly sets: "wording";
+                readonly why: "Wording is content, not a setting: the client says what they want in their own words, or asks for drafts (the workbench-ai skill), and it goes into the catalogue.";
+            }];
+        };
         readonly delivery: {
             readonly choice: "built_in";
             readonly intro: "The words on the app's screens and in its emails, kept in one place for each language.";
-            readonly when: "The client wants to add or change wording on a page or in an email, or asks about showing the app in another language.";
         };
     };
     readonly ui: {