@mccaskie-labs/workbench-config 0.3.0 → 0.3.2

package/dist/capabilities.gen.js

@@ -1,6 +1,6 @@
 // Generated by `npm run capabilities:build` from capabilities/*.json. Do not edit.
 // check:capabilities fails in Checks when this file is stale.
-export const MANIFEST_VERSION = "de365af27674";
+export const MANIFEST_VERSION = "4a52a6ba9520";
 export const capabilities = {
     "ai": {
         "$schema": "./schema.json",
@@ -25,7 +25,9 @@ export const capabilities = {
                 "checkWriting",
                 "writingStops",
                 "writingNotes",
-                "writingFixNote"
+                "writingFixNote",
+                "Ai.reply",
+                "checkGuide"
             ]
         },
         "config": [
@@ -197,6 +199,13 @@ export const capabilities = {
                 "text": "Name a Workbench voice and spelling with the voice and spelling options, so the Gateway adds the text, or bring the app's own voice. Never paste Workbench's voice text into a prompt.",
                 "enforced_by": "gateway",
                 "probe": "ai.voice"
+            },
+            {
+                "id": "ai.reply-facts-from-code",
+                "kind": "must",
+                "text": "Draft replies with ai.reply from facts worked out by code (prices and dates from quote(), never from the AI), and show the draft in renderReplyBox for a person to check and copy. Never send a draft automatically, and never let a draft with needs_human_check go out unread.",
+                "enforced_by": "review",
+                "probe": "ai.reply"
             }
         ],
         "examples": [
@@ -213,6 +222,13 @@ export const capabilities = {
                 "lang": "ts",
                 "code": "const r = await ai.text({ model: 'claude-default', job: 'article.write', voice: 'conversational', spelling: 'en-AU', prompt })\nconst issues = checkWriting(r.text, { voice: 'conversational' })\nif (writingStops(issues).length > 0) await retryWith(prompt + writingFixNote(issues))",
                 "probe": "ai.voice"
+            },
+            {
+                "id": "ai.example.reply",
+                "title": "Draft a reply to an enquiry",
+                "lang": "ts",
+                "code": "import { REPLY_GUIDES } from './replies.generated'\nconst ai = createAi({ key: env.WORKBENCH_GATEWAY_KEY, env: workbenchEnv(env), url: env.WORKBENCH_GATEWAY_URL, replyGuides: REPLY_GUIDES })\nconst q = quote(settings, ask)\nconst draft = await ai.reply({\n  guide: 'venue-quote',\n  facts: { venue_name: venue.name, date: ask.date, available: q.available, packages: q.options.map((o) => ({ name: o.package, price: o.total.amount })), alternatives: q.alternatives.map((a) => a.date) },\n  incoming: { text, intake: read },\n  language: account.reply_language,\n})\nreturn html(renderReplyBox(draft, { againAction: `/enquiries/${id}/reply` }))",
+                "probe": "ai.reply"
             }
         ],
         "probes": [
@@ -292,20 +308,26 @@ export const capabilities = {
                 "half": "runtime",
                 "expect": "pass",
                 "cost_hint_usd": 0.008
+            },
+            {
+                "id": "ai.reply",
+                "half": "runtime",
+                "expect": "pass",
+                "cost_hint_usd": 0.005
             }
         ],
         "offer": {
             "pattern": "feature_or_content",
-            "when": "The client wants the app to write, summarise, sort, answer questions or pull details out of text with AI, as a feature visitors use, or wants wording for the site written once.",
+            "when": "The client wants the app to write, summarise, sort, answer questions or pull details out of text with AI, as a feature visitors use, or wants wording for the site written once, or wants ready-to-paste replies to the messages the business gets (quote requests, booking questions).",
             "say": "I'll do this with Workbench AI, which uses Claude through Workbench, so the app holds no AI key and spending has a monthly cap.",
             "answers_file": "workbench/ai/<name>.json",
             "per": "feature or piece of wording",
-            "answers_format": "For a feature: `{ \"format\": 1, \"route\": \"feature\", \"name\", \"about\" (the client's words), \"who\", \"cap_usd\", \"keep\", \"job\" }`, where `job` is the `X-Workbench-Job` the feature's calls send (`<name>` with dots, such as `quotes.estimate`), so its spending shows on its own line in Control. Write it, then build the feature with the package. For wording made once: `npx workbench-ai pick <name> <round>-<draft>` writes it from the draft the client picked, with the round's request ids and cost; never write one from nothing. Then put the wording into the strings catalogue (the workbench-strings skill), keyed for where it is shown. Drafts and their previews stay in `workbench/ai/drafts/`, which isn't committed.",
+            "answers_format": "For a feature: `{ \"format\": 1, \"route\": \"feature\", \"name\", \"about\" (the client's words), \"who\", \"cap_usd\", \"keep\", \"job\" }`, where `job` is the `X-Workbench-Job` the feature's calls send (`<name>` with dots, such as `quotes.estimate`), so its spending shows on its own line in Control. Write it, then build the feature with the package. For wording made once: `npx workbench-ai pick <name> <round>-<draft>` writes it from the draft the client picked, with the round's request ids and cost; never write one from nothing. Then put the wording into the strings catalogue (the workbench-strings skill), keyed for where it is shown. Drafts and their previews stay in `workbench/ai/drafts/`, which isn't committed. For replies: write the guide itself to `workbench/replies/<name>.json` (format 1: `name`, `version`, `voice`, `spelling`, `max_words`, `max_questions`, `facts` as a small JSON Schema with `x-money` on amounts and `format: date` on dates, `ask_order`, `guide` lines, `examples`, `never`), then run `npx workbench-ai replies generate`, which checks it and writes `src/replies.generated.ts`; never edit that file. Offer samples with `npx workbench-ai replies drafts <name> --languages <the client's languages>` (two to four, with the development key; tell the client the cost it prints) and keep the one the client picks with `npx workbench-ai replies pick <name> <round>-<draft>`, which makes it the guide's first example.",
             "questions": [
                 {
                     "id": "ai.route",
                     "sets": "route",
-                    "ask": "Is this something visitors use on the site, or something made once for the site?",
+                    "ask": "Is this something visitors use on the site, something made once for the site, or replies to the messages you get?",
                     "style": "cards",
                     "answers": [
                         {
@@ -317,10 +339,15 @@ export const capabilities = {
                             "label": "Made once for the site",
                             "value": "content",
                             "means": "Wording for a page, written once and kept: an About page, a welcome, product descriptions."
+                        },
+                        {
+                            "label": "Replies to messages",
+                            "value": "reply",
+                            "means": "A ready-to-paste reply to a customer's message, with your prices and dates filled in from your own details. A person checks it and copies it; nothing is sent by itself."
                         }
                     ],
                     "must_ask": true,
-                    "note": "Ask it even when the client's words seem to say, as a quick check: the two routes are built and paid for differently."
+                    "note": "Ask it even when the client's words seem to say, as a quick check: the two routes are built and paid for differently. Replies are their own route: the facts (prices, dates) come from the app's own code, so ask where those facts come from before anything else."
                 },
                 {
                     "id": "ai.who",
@@ -453,6 +480,196 @@ export const capabilities = {
                         ]
                     },
                     "note": "Name the piece after where it goes (about_us, home_blurb): lower case and underscores. The client's own words, with any facts they give (when they started, where they are), go in --about, because the drafts never invent facts and leave [gaps] for the owner instead."
+                },
+                {
+                    "id": "ai.reply.purpose",
+                    "sets": "reply.purpose",
+                    "ask": "What are these replies answering?",
+                    "style": "cards",
+                    "answers": [
+                        {
+                            "label": "Quote and price requests",
+                            "value": "quote",
+                            "means": "\"How much for Dec 12, 15 pax?\": the reply gives the price and asks only for what's missing."
+                        },
+                        {
+                            "label": "Availability questions",
+                            "value": "availability",
+                            "means": "\"Available pa po ba sa Sabado?\": the reply says yes or offers other dates."
+                        },
+                        {
+                            "label": "Booking or appointment requests",
+                            "value": "booking",
+                            "means": "\"May slot po ba bukas?\": the reply lists the free times and asks which one."
+                        }
+                    ],
+                    "other": {
+                        "kind": "text",
+                        "min": 3,
+                        "max": 200,
+                        "description": "What the messages are, in a few words."
+                    },
+                    "must_ask": true,
+                    "when": {
+                        "id": "ai.route",
+                        "is": [
+                            "reply"
+                        ]
+                    },
+                    "note": "Name the guide after it (venue-quote, appointment-slots): lower case and dashes. Say that prices and dates always come from the app's own details (workbench-availability's quote() where it's a booking), never from the AI."
+                },
+                {
+                    "id": "ai.reply.facts",
+                    "sets": "reply.facts",
+                    "ask": "Here are the details a reply can use. Keep, change or add?",
+                    "style": "table",
+                    "must_ask": true,
+                    "when": {
+                        "id": "ai.route",
+                        "is": [
+                            "reply"
+                        ]
+                    },
+                    "note": "Propose one row per fact from the client's words and what the app already holds: its name, what it is, where the app gets it, and whether it is money (x-money with the currency) or a date. Only these can appear in a reply; a fact the app doesn't have can't be quoted. Then ask which details a reply may ask the customer for, most important first (ask_order); intake's missing fields are asked from that list only."
+                },
+                {
+                    "id": "ai.reply.language",
+                    "sets": "reply.language",
+                    "ask": "Which language should replies use?",
+                    "style": "cards",
+                    "answers": [
+                        {
+                            "label": "Match the message",
+                            "value": "match",
+                            "means": "English gets English, Taglish gets Taglish, Tagalog gets Tagalog. When it can't tell, it uses your fallback and asks you to check."
+                        },
+                        {
+                            "label": "Always Taglish",
+                            "value": "taglish"
+                        },
+                        {
+                            "label": "Always English",
+                            "value": "en"
+                        },
+                        {
+                            "label": "Always Tagalog",
+                            "value": "tl"
+                        }
+                    ],
+                    "when": {
+                        "id": "ai.route",
+                        "is": [
+                            "reply"
+                        ]
+                    },
+                    "note": "This is the default. Where the app has accounts (a venue each), make it each account's own setting in its portal, defaulting to this, and pass it to ai.reply as language; with match, pass the account's fallback as fallbackLanguage."
+                },
+                {
+                    "id": "ai.reply.voice",
+                    "sets": "reply.voice",
+                    "ask": "Which tone?",
+                    "style": "cards",
+                    "answers": [
+                        {
+                            "label": "Conversational",
+                            "value": "conversational",
+                            "means": "Warm and natural, like a helpful person at the front desk."
+                        },
+                        {
+                            "label": "Casual",
+                            "value": "casual",
+                            "means": "Relaxed and friendly, like chatting with a regular."
+                        },
+                        {
+                            "label": "Plain",
+                            "value": "plain",
+                            "means": "Short and clear, nothing extra."
+                        },
+                        {
+                            "label": "Formal",
+                            "value": "formal",
+                            "means": "Polite and proper, for a business that keeps a formal tone."
+                        }
+                    ],
+                    "when": {
+                        "id": "ai.route",
+                        "is": [
+                            "reply"
+                        ]
+                    }
+                },
+                {
+                    "id": "ai.reply.length",
+                    "sets": "reply.max_words",
+                    "ask": "How long can a reply be, at most?",
+                    "style": "cards",
+                    "answers": [
+                        {
+                            "label": "About 90 words",
+                            "value": 90,
+                            "means": "Room for a price or two and one question."
+                        },
+                        {
+                            "label": "About 50 words",
+                            "value": 50,
+                            "means": "A quick chat reply."
+                        },
+                        {
+                            "label": "About 150 words",
+                            "value": 150,
+                            "means": "Room for several packages or options."
+                        }
+                    ],
+                    "other": {
+                        "kind": "whole",
+                        "min": 20,
+                        "max": 300,
+                        "description": "Words, from 20 to 300."
+                    },
+                    "when": {
+                        "id": "ai.route",
+                        "is": [
+                            "reply"
+                        ]
+                    },
+                    "note": "A reply up to a quarter over passes quietly; one over twice as long is sent back to be written again, then flagged for a person to check."
+                },
+                {
+                    "id": "ai.reply.never",
+                    "sets": "reply.never",
+                    "ask": "Is there anything a reply must never say?",
+                    "style": "cards",
+                    "answers": [
+                        {
+                            "label": "The usual three",
+                            "value": "usual",
+                            "means": "Never promise a discount, confirm a booking, or ask for payment details. Code checks these as well as telling the AI."
+                        },
+                        {
+                            "label": "The usual three, and more",
+                            "value": "usual_and_more",
+                            "means": "Those three plus things of your own (type them in Other)."
+                        },
+                        {
+                            "label": "Nothing",
+                            "value": "none",
+                            "means": "No rules beyond Workbench's own content rules."
+                        }
+                    ],
+                    "other": {
+                        "kind": "list",
+                        "min": 1,
+                        "max": 10,
+                        "description": "Each thing a reply must never do, in a few words (give medical advice, mention the pool)."
+                    },
+                    "must_ask": true,
+                    "when": {
+                        "id": "ai.route",
+                        "is": [
+                            "reply"
+                        ]
+                    },
+                    "note": "Write each as a never line in the guide. Lines about payment details, discounts and confirming bookings are also checked by code; others go into the prompt only, so say so if the client's line matters a lot."
                 }
             ],
             "not_asked": [
@@ -475,6 +692,9 @@ export const capabilities = {
                 "command": "npx workbench-ai drafts text <name> --about \"<what it is for, with the client's facts>\""
             }
         },
+        "styles": {
+            "prefix": "wb-reply-"
+        },
         "delivery": {
             "choice": "built_in",
             "intro": "Writing, summarising and answering questions with Claude, with a monthly spending cap."
@@ -627,6 +847,271 @@ export const capabilities = {
             "intro": "Counting page views and the things visitors do on the site."
         }
     },
+    "availability": {
+        "$schema": "./schema.json",
+        "format": 1,
+        "component": "availability",
+        "title": "Availability and pricing",
+        "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.",
+        "status": "built",
+        "surfaces": {
+            "package": [
+                "quote",
+                "createAvailability",
+                "availabilityMigration",
+                "calendarAction",
+                "checkSettings",
+                "stayClaims",
+                "staysClash",
+                "todayIn",
+                "AvailabilityError"
+            ]
+        },
+        "rules": [
+            {
+                "id": "availability.quote-is-fact",
+                "kind": "must",
+                "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.",
+                "enforced_by": "review",
+                "probe": "availability.quote"
+            },
+            {
+                "id": "availability.book-through-block",
+                "kind": "must",
+                "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.",
+                "enforced_by": "database",
+                "probe": "availability.store"
+            },
+            {
+                "id": "availability.calendar-days",
+                "kind": "must",
+                "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.",
+                "enforced_by": "types",
+                "probe": "availability.quote"
+            },
+            {
+                "id": "availability.no-names-in-notes",
+                "kind": "must_not",
+                "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.",
+                "enforced_by": "review",
+                "probe": "availability.store"
+            },
+            {
+                "id": "availability.public-gets-the-quote",
+                "kind": "must_not",
+                "text": "Let a public page or the anonymous key read availability_blocks: public pages get the finished quote from the server.",
+                "enforced_by": "database",
+                "probe": "availability.store"
+            },
+            {
+                "id": "availability.daily-cleanup",
+                "kind": "must",
+                "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.",
+                "enforced_by": "review",
+                "probe": "availability.store"
+            },
+            {
+                "id": "availability.calendar-as-shipped",
+                "kind": "must",
+                "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.",
+                "enforced_by": "review",
+                "probe": "availability.calendar"
+            }
+        ],
+        "examples": [
+            {
+                "id": "availability.example.quote",
+                "title": "Answer \"is 12 Dec free, and how much?\"",
+                "lang": "ts",
+                "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)', ...]",
+                "probe": "availability.quote"
+            },
+            {
+                "id": "availability.example.calendar",
+                "title": "The owner's tap-to-block calendar",
+                "lang": "ts",
+                "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 })",
+                "probe": "availability.calendar"
+            }
+        ],
+        "probes": [
+            {
+                "id": "availability.quote",
+                "half": "runtime",
+                "expect": "pass",
+                "smoke": true,
+                "cost_hint_usd": 0,
+                "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"
+            },
+            {
+                "id": "availability.store",
+                "half": "runtime",
+                "expect": "pass",
+                "cost_hint_usd": 0,
+                "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"
+            },
+            {
+                "id": "availability.calendar",
+                "half": "runtime",
+                "expect": "pass",
+                "cost_hint_usd": 0,
+                "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"
+            }
+        ],
+        "offer": {
+            "pattern": "settings",
+            "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.",
+            "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.",
+            "answers_file": "workbench/availability.json",
+            "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.",
+            "questions": [
+                {
+                    "id": "availability.what",
+                    "sets": "availability.what",
+                    "ask": "What do people book?",
+                    "style": "table",
+                    "other": {
+                        "kind": "text",
+                        "min": 3,
+                        "max": 200,
+                        "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\"."
+                    },
+                    "must_ask": true,
+                    "note": "Only the client knows. Their answer names the resources (one per thing booked separately) and suggests the stay types to propose next."
+                },
+                {
+                    "id": "availability.stays",
+                    "sets": "availability.stay_types",
+                    "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?",
+                    "style": "table",
+                    "other": {
+                        "kind": "list",
+                        "min": 1,
+                        "max": 10,
+                        "description": "Each way it's booked, with its start and end time and the others it can't share a date with."
+                    },
+                    "must_ask": true,
+                    "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."
+                },
+                {
+                    "id": "availability.events",
+                    "sets": "availability.event_types",
+                    "ask": "Should prices depend on the kind of event? Here is the usual list.",
+                    "style": "cards",
+                    "answers": [
+                        {
+                            "label": "Yes, use this list",
+                            "value": "list",
+                            "means": "Birthday, debut, wedding, baptism, reunion, team building, other: a rule can add a fee for some of them."
+                        },
+                        {
+                            "label": "No, same price for all",
+                            "value": "none",
+                            "means": "No event types; the quote never asks for one."
+                        },
+                        {
+                            "label": "Yes, with my own list",
+                            "value": "own",
+                            "means": "Type the kinds of event the business prices differently."
+                        }
+                    ],
+                    "other": {
+                        "kind": "list",
+                        "min": 1,
+                        "max": 20,
+                        "description": "The kinds of event, each a short name."
+                    },
+                    "note": "Recommend the usual list for venues and resorts; \"none\" for most other businesses. Write ids in lower case with underscores (team_building)."
+                },
+                {
+                    "id": "availability.holidays",
+                    "sets": "availability.holidays",
+                    "ask": "Should holidays be priced like weekends?",
+                    "style": "cards",
+                    "answers": [
+                        {
+                            "label": "Yes, like a weekend",
+                            "value": "weekend",
+                            "means": "A regular holiday or special non-working day on a weekday costs the weekend price."
+                        },
+                        {
+                            "label": "No, by the day of the week",
+                            "value": "weekday",
+                            "means": "Holidays cost what their day of the week costs."
+                        },
+                        {
+                            "label": "Set holiday prices separately",
+                            "value": "separate",
+                            "means": "Holidays get their own price rules, entered on the owner's pages."
+                        }
+                    ],
+                    "other": {
+                        "kind": "text",
+                        "min": 3,
+                        "max": 200,
+                        "description": "How holidays should be priced, in the client's words."
+                    },
+                    "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."
+                },
+                {
+                    "id": "availability.holds",
+                    "sets": "availability.hold_days",
+                    "ask": "How long is a date held while waiting for a deposit?",
+                    "style": "cards",
+                    "answers": [
+                        {
+                            "label": "3 days",
+                            "value": 3,
+                            "means": "The date shows as held (H) for 3 days, then is free again unless marked booked."
+                        },
+                        {
+                            "label": "1 day",
+                            "value": 1
+                        },
+                        {
+                            "label": "7 days",
+                            "value": 7
+                        },
+                        {
+                            "label": "No holds",
+                            "value": 0,
+                            "means": "A date is free until it is booked; nothing is held."
+                        }
+                    ],
+                    "other": {
+                        "kind": "whole",
+                        "min": 0,
+                        "max": 60,
+                        "description": "Days, 0 to 60."
+                    }
+                }
+            ],
+            "not_asked": [
+                {
+                    "sets": "availability.prices",
+                    "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."
+                },
+                {
+                    "sets": "availability.alternatives",
+                    "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."
+                },
+                {
+                    "sets": "availability.currency",
+                    "why": "It is the country's own, from workbench/country.json."
+                }
+            ],
+            "needs": [
+                "country"
+            ]
+        },
+        "styles": {
+            "prefix": "wb-cal-"
+        },
+        "delivery": {
+            "choice": "optional",
+            "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."
+        }
+    },
     "config": {
         "$schema": "./schema.json",
         "format": 1,
@@ -781,7 +1266,11 @@ export const capabilities = {
                 "currencySymbol",
                 "currencySymbolFrom",
                 "WORLDWIDE",
-                "isWorldwide"
+                "isWorldwide",
+                "HOLIDAYS",
+                "holidaysFor",
+                "holidayOn",
+                "checkHolidays"
             ]
         },
         "rules": [
@@ -806,6 +1295,13 @@ export const capabilities = {
                 "enforced_by": "types",
                 "probe": "country.packs"
             },
+            {
+                "id": "country.holidays-from-proclamation",
+                "kind": "must",
+                "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.",
+                "enforced_by": "review",
+                "probe": "country.holidays"
+            },
             {
                 "id": "country.spelling-from-pack",
                 "kind": "must",
@@ -838,6 +1334,14 @@ export const capabilities = {
                 "expect": "pass",
                 "cost_hint_usd": 0,
                 "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"
+            },
+            {
+                "id": "country.holidays",
+                "half": "runtime",
+                "expect": "pass",
+                "smoke": true,
+                "cost_hint_usd": 0,
+                "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"
             }
         ],
         "offer": {

package/dist/capability-schema.d.ts

@@ -1,5 +1,5 @@
 import { z } from "zod";
-export declare const COMPONENTS: readonly ["gateway", "ai", "images", "image-search", "config", "email", "email-inbound", "email-sending", "database", "workers", "domains", "dns", "analytics", "country", "pdf", "access", "r2", "kv", "github", "strings", "ui", "forms", "sign-in"];
+export declare const COMPONENTS: readonly ["gateway", "ai", "images", "image-search", "config", "email", "email-inbound", "email-sending", "database", "workers", "domains", "dns", "analytics", "country", "pdf", "access", "r2", "kv", "github", "strings", "ui", "forms", "sign-in", "availability"];
 export type Component = (typeof COMPONENTS)[number];
 export declare const allowedSchemas: {
     gateway: z.ZodObject<{
@@ -163,6 +163,7 @@ export declare const capabilitySchema: z.ZodObject<{
         access: "access";
         ai: "ai";
         analytics: "analytics";
+        availability: "availability";
         config: "config";
         country: "country";
         database: "database";
@@ -294,6 +295,7 @@ export declare const capabilitySchema: z.ZodObject<{
         access: "access";
         ai: "ai";
         analytics: "analytics";
+        availability: "availability";
         config: "config";
         country: "country";
         database: "database";

package/dist/capability-schema.js

@@ -26,6 +26,7 @@ export const COMPONENTS = [
     "ui",
     "forms",
     "sign-in",
+    "availability",
 ];
 const id = z.string().regex(/^[a-z0-9][a-z0-9.-]*$/, "lower case, digits, dots and hyphens");
 const code = z.string().regex(/^[a-z][a-z0-9_]*$/, "a snake_case error code");