kaafil-react-uikit 0.4.2 → 0.6.0

package/CHANGELOG.md

@@ -6,6 +6,34 @@ The format follows [Keep a Changelog](https://keepachangelog.com/en/1.1.0/),
 and this package uses [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
 While on `0.x` a minor bump may carry a breaking change; the entry will say so.
 
+## [0.6.0] — 2026-09-14
+
+### Added
+
+- **Create a booking group.** `families/admin/06-parties.md §PartyEditor`
+  specifies create *and* edit ("`partyId` … presence switches the composite
+  from create to edit"), but only the edit half was ever built: a desk could
+  edit a group the engine had derived and had no way to make one, even though
+  `useDirectories.createParty` and the wire both supported it. `New group`
+  now sits in the manifest toolbar, appearing once there are two travellers to
+  group, and `EditPartyDialog` takes `group` as optional — omitted is create.
+
+## [0.5.0] — 2026-09-14
+
+Requires `kaafil-js@^0.5.0` and an engine carrying the matching wire change.
+
+### Fixed
+
+- **"Add traveller" failed with "Couldn't add them. Nothing changed — try
+  again", and never made a request at all.** `addTraveller` sent
+  `useServerTime().now()` as the manifest entry's `sourceUpdatedAt`. That hook
+  throws until a `snapshot.updated` event carrying `serverTime` has landed,
+  and that event comes from the offline lane, which the desk's direct reads
+  never drive — so on the desk it threw before the request was built. The
+  field is now optional on the wire and omitted here; the server stamps the
+  write, exactly as `assignManager` already did. This is the add-traveller
+  failure from the QA report, whose real cause was a clock, not the write.
+
 ## [0.4.2] — 2026-09-14
 
 All four found by driving the real UI with a browser rather than reading the