frontpage-host 0.3.24 → 0.3.25

package/AGENTS.md

@@ -320,6 +320,8 @@ remain errors; they do not become original-file fallback successes.
 
 ## Native Booking
 
+Appointment types support `startIntervalMinutes:null` (match current appointment length) or 5/10/15/20/30/45/60 through the existing JSON type save. Read BOOKING.md for clock alignment and current-rule rescheduling. Use exact returned availability; do not invent starts.
+
 Read [BOOKING.md](./BOOKING.md) before using `frontpage modules booking`. Use native settings, types/forms, members/spaces, availability, reservations and recurring blocks. Do not send new bookings through the old generic module collector. Every write requires a stable request key; updates require the current revision. Consent and private calendar-link entry stay with the human in Workspace → Connections. Ordinary owned connection management and self-hours share the workspace actions; setup requests appear in the editor status bar and overview.
 
 ## Page screenshots

package/BOOKING.md

@@ -83,3 +83,15 @@ Only consent/private-link entry uses the secure human handoff. Never pass OAuth
 Only the booking type chooses instant confirmation or manual acceptance of customer requests; connecting a calendar never changes that choice. Successful imports revalidate every 15 minutes even when the source advertises a longer cache lifetime. Connection summaries include safe `health` with `status`, `label`, `message` and `usable`. Fresh last-good busy times still apply during refresh or a temporary failure; missing, revoked, disconnected, stale (30 minutes) or uncovered imports keep dependent availability unavailable. Retries keep existing backoff and Retry-After. Imported event titles and private feed URLs never appear in these summaries.
 
 Repeated Connect for your existing Google/Microsoft account returns its current calendar choices without replacing its grant or selections. Use Reconnect on the existing account to renew permissions.
+
+## Appointment start times
+
+Set `startIntervalMinutes` in the existing `types save --file type.json` value. Use `null` for Automatic, which follows the current `durationMinutes`, or `5`, `10`, `15`, `20`, `30`, `45`, `60` for a fixed interval. Omit the field when updating to keep the saved choice; new types default to Automatic.
+
+For a 60-minute appointment that can start on the hour or half hour, keep `durationMinutes:60` and set `startIntervalMinutes:30`. To return to hourly Automatic, send `startIntervalMinutes:null`. Send the complete booking-type value with the current revision and a stable request key:
+
+```bash
+frontpage modules booking types save --id TYPE_ID --revision REVISION --file type.json --request-key UNIQUE_KEY --site SITE --json
+```
+
+Starts align to midnight in the business time zone. Thirty-minute intervals offer :00/:30, even if working hours begin at 9:10. Buffers and calendar conflicts remove starts without moving the grid. New bookings and rescheduling follow the type's current interval; there is no historical 15-minute fallback. Stays keep their existing arrival/departure rules. Read `availability` and use an exact returned slot; direct off-grid requests fail with `slot_unavailable`. The website's design remains fully controlled by its author.

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "frontpage-host",
-  "version": "0.3.24",
-  "description": "Frontpage CLI \u2014 manage your site from the terminal",
+  "version": "0.3.25",
+  "description": "Frontpage CLI — manage your site from the terminal",
   "type": "module",
   "bin": {
     "frontpage": "dist/bin.js"