@odla-ai/chapter 0.57.0 → 0.58.0

package/README.md

@@ -1850,6 +1850,17 @@ These bite silently — a smoke test won't catch them:
   named and whether that person joined without folding the seat status machine
   itself; `NamedSeatRecipientLine` renders it.
 
+  **Availability saves keep what the editor does not show (0.58.0).**
+  `PUT /api/admin/scheduling` now merges the fields it receives onto the
+  stored config before validating, so an editor that sends only hours, days,
+  slot length, timezone, notice and window no longer resets the branded
+  `summaryTemplate` to the generic default. A stored config the rules reject
+  answers `409` on `GET` with the field errors (the next save repairs it), and a
+  failed database write answers `503` with `code: "scheduling_write_failed"`
+  and the database's own code as `cause`, never a bare 500. The default
+  booking window is now 21 days (three weeks of offered times); a group row
+  that already stores `windowDays` keeps it.
+
   **Decisions after the conversation (0.57.0).** Four operations close the
   gaps a chapter hits once applicants are real people (BNF bugs fa96b11c,
   f7bc92ee, 38000934, c3c1d338, 79590edc):

package/dist/index.cjs

@@ -1379,7 +1379,7 @@ var DEFAULT_SCHEDULING = {
   endHour: 17,
   timezone: "America/Los_Angeles",
   minNoticeHours: 24,
-  windowDays: 14
+  windowDays: 21
 };
 function defaultEmailTemplates(name) {
   const sign = `
@@ -9157,7 +9157,7 @@ var SCHEDULING_DEFAULTS = {
   endHour: 17,
   timezone: "America/Los_Angeles",
   minNoticeHours: 24,
-  windowDays: 14,
+  windowDays: 21,
   summaryTemplate: "Introduction call with {{firstName}} {{lastName}}"
 };
 function isValidTimeZone(tz) {