@cosmoops/connect-sdk 0.26.0 → 0.28.0

package/CHANGELOG.md

@@ -3,6 +3,127 @@
 `@cosmoops/connect-sdk` follows semver, with the 0.x convention that **minor
 versions may carry breaking changes** and patch versions never do.
 
+## 0.28.0
+
+Connect's webhook bus carried four events, all of them about billing and
+deletion. It now carries the seven a system of record is actually built on —
+calls, appointments and contacts — so the work your customers do inside
+Connect can reach the product they do the rest of their work in.
+
+### Added
+
+- Seven webhook event types, with their payloads fully typed on
+  `ConnectWebhookEventMap`: `call.completed`, `call.missed`,
+  `booking.confirmed`, `booking.cancelled`, `booking.rescheduled`,
+  `contact.created` and `contact.updated`. Register handlers for them on
+  `createConnectWebhookHandler` exactly as you do the existing four.
+- `ConnectCallDirection` and `ConnectContactSource`, the two unions those
+  payloads carry.
+
+  These are **activity** events rather than lifecycle ones, and the difference
+  decides who receives them: they are delivered only to applications the
+  workspace is actually subscribed to, so a lapsed customer stops emitting on
+  the same boundary that stops their access.
+
+  Three conventions are worth reading before you write a handler, each
+  documented on the types themselves. Phone numbers are E.164. A call event
+  identifies its party by `contactPhone` and deliberately carries no
+  `contactId` — Connect resolves a caller *by* the number and at the moment a
+  call ends it often has not, so the field would be `null` on most deliveries.
+  And `booking.rescheduled` carries `previousBookingId` as well as `bookingId`,
+  because Connect retires the old booking and writes a new one: reconcile on
+  the previous id or you will end up holding two appointments.
+
+### Fixed
+
+- `Booking` fixtures in the bundled tests compile again — the type gained a
+  required `hostMemberIds` in 0.27.0 and one fixture was missed. No runtime
+  change.
+
+### A note on exhaustiveness
+
+`ConnectWebhookEventType` is a union that grows, and this release grows it.
+`createConnectWebhookHandler` is unaffected — its `on` map is partial and it
+answers 200 to anything you have not registered. A hand-written `switch` with
+an exhaustive `never` check on that union will now fail to compile until you
+add the new members; that is the documented contract of this union rather than
+a break, and it is the reason the handler exists.
+
+## 0.27.0
+
+A minor rather than a patch because `Booking` gains a required field, so a
+hand-written object satisfying the old interface no longer type-checks. Nothing
+you *read* from the API breaks.
+
+0.26.1 was never published; its note below ships as part of this release, so the
+registry goes 0.26.0 → 0.27.0.
+
+### Added
+
+- **`connect.scheduling.getBooking()`** - one appointment, by the id you
+  stored.
+
+  ```ts
+  const booking = await connect.scheduling.getBooking({
+    workspaceId,
+    bookingId, // the id you kept on your own record
+  });
+  ```
+
+  This is the read to make when a record of yours - a meeting on a deal, an
+  appointment on a case - holds a booking id. **`listBookings` cannot serve
+  it.** That is a window over `startAt`, and the `startAt` you cached is
+  exactly what is wrong once somebody has moved the appointment on the
+  workspace's own calendar, so the window you build from it comes back without
+  the row - in the one case worth re-reading for.
+
+  A retired booking still resolves, deliberately. `status: "rescheduled"`
+  answers with `rescheduledToId`, so an id stored months ago leads to the
+  appointment that exists today; follow the pointer. `cancelled` answers with
+  its reason. `not_found` means this workspace never had that booking, which is
+  a different fact from "it moved".
+
+  `GET /scheduling/booking?bookingId=` is the matching browser bridge route -
+  singular, and the id in the query string, because the bridge's route table is
+  matched by exact string. Same reason `reschedule` and `cancel` take theirs in
+  the body.
+
+- **`Booking.hostMemberIds`** - the workspace members committed to an
+  appointment, so an integration can render who it belongs to.
+
+  These are the `WorkspaceMember.id` values `workspaces.listMembers` returns,
+  so an owner column is a lookup against a roster you already hold rather than
+  another round trip. They were withheld as "Connect internals", which
+  `listBookings` had already contradicted by *filtering* on `hostMemberId` - a
+  partner could narrow a diary by a value it was never allowed to read back.
+
+  Resolved when the slot was held and frozen there: a round-robin event type
+  picks one host, a collective one commits the whole group, and re-pointing the
+  event type afterwards does not move an appointment already made.
+
+  **This is the breaking half.** The field is required, so code constructing a
+  `Booking` literal - a test fixture, a mock, a storybook arg - needs
+  `hostMemberIds: []` added. Code that only reads bookings from the API is
+  unaffected.
+
+## 0.26.1
+
+### Added
+
+- **`<ConnectAppShell>` renders a skip link.** The rail is the shell's first
+  content, so a keyboard or switch user tabbed every navigation row, the app
+  launcher and the account menu again on **every** route change before reaching
+  the page they came for - WCAG 2.4.1, and the one bypass a single-rail layout
+  cannot do without, because there is no second landmark to jump between. The
+  link is the first focusable element in the document, visually hidden until it
+  takes focus, and `<main>` now carries `id="connect-main-content"` and
+  `tabIndex={-1}` so focus genuinely lands there. Without that `tabIndex` a
+  browser scrolls to the anchor and leaves focus where it was, so the next Tab
+  returns to the top of the rail and the link appears to do nothing.
+
+  Nothing to adopt: it is on for every platform. The only visible change is a
+  "Skip to content" button that appears at the top-left on the first Tab.
+
 ## 0.26.0
 
 A minor rather than a patch because two of these change how existing screens

package/README.md

@@ -345,7 +345,7 @@ try {
 | `contacts` | `lookupByPhone` · `get` |
 | `channels` | `list` · `get` · `claim` · `setRouting` · `clearRouting` |
 | `calls` | `list` · `get` |
-| `scheduling` | `listEventTypes` · `findSlots` · `listBookings` · `createBooking` · `rescheduleBooking` · `cancelBooking` |
+| `scheduling` | `listEventTypes` · `findSlots` · `listBookings` · `getBooking` · `createBooking` · `rescheduleBooking` · `cancelBooking` |
 | `ai` | `chat` · `extract` |
 | `otp` | `send` · `verify` |
 | `logs` | `write` |
@@ -404,6 +404,26 @@ try {
 `timezone` is the **business's** zone, not your user's - render the wall time in
 it, or you will offer an hour they are not open.
 
+Keeping the booking id on a record of your own - a meeting on a deal, an
+appointment on a case - is how you get back to it later:
+
+```ts
+const booking = await client.scheduling.getBooking({ workspaceId, bookingId });
+
+// Someone moved it on the workspace's own calendar. Follow the pointer.
+if (booking.status === "rescheduled") {
+  const current = await client.scheduling.getBooking({
+    workspaceId,
+    bookingId: booking.rescheduledToId!,
+  });
+}
+```
+
+Use `getBooking`, not `listBookings`, for that. The list is a window over
+`startAt`, and the `startAt` you cached is exactly what is wrong once the
+appointment has moved - so the window you build from it comes back without the
+row, in the one case worth re-reading for.
+
 ### Attributing a log to a user
 
 ```ts

package/dist/cjs/client/components/app-shell.js

@@ -23,6 +23,15 @@ const use_active_path_js_1 = require("../use-active-path.js");
 const cn_js_1 = require("../../cn.js");
 const COLLAPSED_KEY = "connect_sidenav_collapsed";
 const COLLAPSED_EVENT = "connect:sidenav-collapsed";
+/**
+ * The `<main>` element's id, and the skip link's target.
+ *
+ * Module-local rather than a prop: both ends of the pair live in this file, so
+ * there is nothing for a caller to keep in step - and a partner supplying
+ * their own id could only get it wrong. Namespaced because it lands in a
+ * document the partner also writes.
+ */
+const CONTENT_ID = "connect-main-content";
 /**
  * The stored rail preference, or `null` when there isn't one (or when reading
  * it is not allowed).
@@ -189,5 +198,5 @@ function AppShell({ name, icon, homeHref = "/", nav, secondaryNav, activePath, r
     }), [renderLink, activePath, closeMobile]);
     const accountRow = signedOut ? (showAuthButtons && ((0, jsx_runtime_1.jsxs)("div", { className: "flex flex-col gap-2", children: [(0, jsx_runtime_1.jsx)(auth_buttons_js_1.ConnectLoginButton, { size: "sm", fullWidth: true }), (0, jsx_runtime_1.jsx)(auth_buttons_js_1.ConnectRegisterButton, { size: "sm", fullWidth: true })] }))) : ((0, jsx_runtime_1.jsx)(user_menu_js_1.ConnectUserButton, { variant: "row", theme: theme, onThemeChange: onThemeChange }));
     const railContent = ((0, jsx_runtime_1.jsxs)(jsx_runtime_1.Fragment, { children: [(0, jsx_runtime_1.jsx)(sidebar_js_1.ConnectSidebarHeader, { name: name, icon: icon, homeHref: homeHref }), workspaceSwitcher !== false && ((0, jsx_runtime_1.jsx)("div", { className: "shrink-0 px-3 pb-1", children: (0, jsx_runtime_1.jsx)(workspace_switcher_js_1.ConnectWorkspaceSwitcher, {}) })), (0, jsx_runtime_1.jsx)(sidebar_js_1.ConnectSidebarBody, { children: (0, jsx_runtime_1.jsx)(side_nav_js_1.ConnectSidebarNav, { nav: visibleNav }) }), (visibleSecondaryNav || sidebarFooter || showAppsGrid) && ((0, jsx_runtime_1.jsxs)(sidebar_js_1.ConnectSidebarFooter, { separated: false, children: [visibleSecondaryNav && (0, jsx_runtime_1.jsx)(side_nav_js_1.ConnectSidebarNav, { nav: visibleSecondaryNav }), sidebarFooter, showAppsGrid && (0, jsx_runtime_1.jsx)(apps_grid_js_1.ConnectAppsGrid, { variant: "row" })] })), accountRow && (0, jsx_runtime_1.jsx)(sidebar_js_1.ConnectSidebarFooter, { children: accountRow })] }));
-    return ((0, jsx_runtime_1.jsx)(motion_js_1.MotionProvider, { children: (0, jsx_runtime_1.jsxs)("div", { className: (0, cn_js_1.cn)("flex h-screen bg-background", className), children: [(0, jsx_runtime_1.jsx)(shell_context_js_1.ConnectShellProvider, { value: railShell, children: (0, jsx_runtime_1.jsx)(sidebar_js_1.ConnectSidebar, { children: railContent }) }), (0, jsx_runtime_1.jsx)(react_2.Drawer.Backdrop, { isOpen: mobileOpen, onOpenChange: setMobileOpen, children: (0, jsx_runtime_1.jsx)(react_2.Drawer.Content, { placement: "left", className: "w-[min(20rem,85vw)]", children: (0, jsx_runtime_1.jsx)(react_2.Drawer.Dialog, { "aria-label": "Navigation menu", className: "p-0", children: (0, jsx_runtime_1.jsx)(shell_context_js_1.ConnectShellProvider, { value: drawerShell, children: (0, jsx_runtime_1.jsx)("div", { className: "flex h-full flex-col", children: railContent }) }) }) }) }), (0, jsx_runtime_1.jsxs)("div", { className: "flex min-w-0 flex-1 flex-col", children: [(0, jsx_runtime_1.jsxs)("header", { className: "flex h-14 shrink-0 items-center gap-2 border-b border-border bg-surface px-3 md:hidden", children: [(0, jsx_runtime_1.jsx)(react_2.Button, { isIconOnly: true, variant: "tertiary", size: "sm", "aria-label": "Open navigation menu", onPress: () => setMobileOpen(true), children: (0, jsx_runtime_1.jsx)(lucide_react_1.Menu, { className: "size-5" }) }), (0, jsx_runtime_1.jsx)(logo_js_1.ConnectLogo, { name: name, icon: icon })] }), (0, jsx_runtime_1.jsx)("main", { className: "flex-1 overflow-y-auto", children: (0, jsx_runtime_1.jsxs)("div", { className: contentClassName ?? "w-full px-4 py-5 md:px-6 md:py-6", children: [gated ? (0, jsx_runtime_1.jsx)(access_gate_js_1.ConnectAccessGate, { children: children }) : children, footer] }) })] }), askAi && (0, jsx_runtime_1.jsx)(ask_ai_js_1.ConnectAskAi, { ...(askAi === true ? {} : askAi) })] }) }));
+    return ((0, jsx_runtime_1.jsx)(motion_js_1.MotionProvider, { children: (0, jsx_runtime_1.jsxs)("div", { className: (0, cn_js_1.cn)("flex h-dvh bg-background", className), children: [(0, jsx_runtime_1.jsx)("a", { href: `#${CONTENT_ID}`, className: "sr-only focus:not-sr-only focus:absolute focus:start-3 focus:top-3 focus:z-50 focus:rounded-lg focus:bg-surface focus:px-3 focus:py-2 focus:text-sm focus:font-medium focus:text-foreground focus:shadow-lg focus:outline-2 focus:outline-offset-2 focus:outline-focus", children: "Skip to content" }), (0, jsx_runtime_1.jsx)(shell_context_js_1.ConnectShellProvider, { value: railShell, children: (0, jsx_runtime_1.jsx)(sidebar_js_1.ConnectSidebar, { children: railContent }) }), (0, jsx_runtime_1.jsx)(react_2.Drawer.Backdrop, { isOpen: mobileOpen, onOpenChange: setMobileOpen, children: (0, jsx_runtime_1.jsx)(react_2.Drawer.Content, { placement: "left", className: "w-[min(20rem,85vw)]", children: (0, jsx_runtime_1.jsxs)(react_2.Drawer.Dialog, { "aria-label": "Navigation menu", className: "p-0 pt-[env(safe-area-inset-top)] pb-[env(safe-area-inset-bottom)]", children: [(0, jsx_runtime_1.jsx)(react_2.Drawer.CloseTrigger, { className: "end-3 top-[calc(--spacing(3)+env(safe-area-inset-top))]" }), (0, jsx_runtime_1.jsx)(shell_context_js_1.ConnectShellProvider, { value: drawerShell, children: (0, jsx_runtime_1.jsx)("div", { className: "flex h-full flex-col [&>:first-child]:pe-10", children: railContent }) })] }) }) }), (0, jsx_runtime_1.jsxs)("div", { className: "flex min-w-0 flex-1 flex-col", children: [(0, jsx_runtime_1.jsxs)("header", { className: "flex h-14 shrink-0 items-center gap-2 border-b border-border bg-surface px-3 md:hidden", children: [(0, jsx_runtime_1.jsx)(react_2.Button, { isIconOnly: true, variant: "tertiary", size: "sm", "aria-label": "Open navigation menu", onPress: () => setMobileOpen(true), children: (0, jsx_runtime_1.jsx)(lucide_react_1.Menu, { className: "size-5" }) }), (0, jsx_runtime_1.jsx)(logo_js_1.ConnectLogo, { name: name, icon: icon })] }), (0, jsx_runtime_1.jsx)("main", { id: CONTENT_ID, tabIndex: -1, className: "flex-1 overflow-y-auto outline-none", children: (0, jsx_runtime_1.jsxs)("div", { className: contentClassName ?? "w-full px-4 py-5 md:px-6 md:py-6", children: [gated ? (0, jsx_runtime_1.jsx)(access_gate_js_1.ConnectAccessGate, { children: children }) : children, footer] }) })] }), askAi && (0, jsx_runtime_1.jsx)(ask_ai_js_1.ConnectAskAi, { ...(askAi === true ? {} : askAi) })] }) }));
 }

package/dist/cjs/client/components/sidebar.js

@@ -100,7 +100,23 @@ function ConnectSidebarHeader({ name, icon, homeHref = "/" }) {
  * the sidebar is `shrink-0`, so this is the only part that ever gives way.
  */
 function ConnectSidebarBody({ children }) {
-    return ((0, jsx_runtime_1.jsx)("div", { className: "flex min-h-0 flex-1 flex-col gap-1 overflow-y-auto overflow-x-hidden px-3 py-2", children: children }));
+    return (
+    // `touch-pan-y touch-pinch-zoom` is what lets this scroll under a finger
+    // inside the mobile drawer. `Drawer.Dialog` carries an inline
+    // `touch-action: none` whenever it is dismissable - HeroUI sets it so its
+    // own pointer-driven drag-to-dismiss is not fighting the browser's pan -
+    // and the declaration meant to hand the scroll back to the scrollable
+    // region is missing from the shipped stylesheet: `@heroui/styles`'
+    // `drawer.css` carries the comment ("touch-action: pan-y allows vertical
+    // scrolling while the dialog captures drag gestures") on a `.drawer__body`
+    // rule that never sets the property. A nav longer than the panel was
+    // therefore frozen on a phone while scrolling normally under a wheel.
+    //
+    // `pinch-zoom` alongside `pan-y` rather than `pan-y` on its own: taking
+    // zoom away over a region of text is a WCAG 1.4.4 failure, and nothing
+    // here needs it suppressed. On the desktop rail, where no ancestor
+    // restricts anything, the pair is equivalent to the default.
+    (0, jsx_runtime_1.jsx)("div", { className: "flex min-h-0 flex-1 touch-pan-y touch-pinch-zoom flex-col gap-1 overflow-y-auto overflow-x-hidden px-3 py-2", children: children }));
 }
 /**
  * A pinned region at the foot of the rail - the secondary nav, the launcher,

package/dist/cjs/server/client.js

@@ -161,4 +161,4 @@ class ConnectClient {
 }
 exports.ConnectClient = ConnectClient;
 /** Kept in step with `package.json` by `sdk.test.ts`. */
-exports.SDK_VERSION = "0.26.0";
+exports.SDK_VERSION = "0.28.0";

package/dist/cjs/server/handler.js

@@ -511,6 +511,21 @@ function createConnectHandler(options) {
                 asUser,
             }));
         },
+        /*
+         * Singular, and the id is a query param rather than a path segment - the
+         * table above is matched by exact string, which is the same reason
+         * reschedule and cancel take theirs in the body. Keying it as
+         * `/scheduling/bookings/{id}` would simply never match.
+         */
+        "GET /scheduling/booking": async (request) => {
+            const { workspaceId } = await requireWorkspace(request);
+            const asUser = await requireToken(request);
+            const bookingId = new URL(request.url).searchParams.get("bookingId");
+            if (!bookingId) {
+                return json({ error: { code: "validation_error", message: "bookingId is required" } }, 400);
+            }
+            return json(await client.scheduling.getBooking({ workspaceId, bookingId, asUser }));
+        },
         "GET /scheduling/bookings": async (request) => {
             const { workspaceId } = await requireWorkspace(request);
             const asUser = await requireToken(request);

package/dist/cjs/server/resources/scheduling.js

@@ -61,6 +61,29 @@ class SchedulingResource {
             headers: (0, acting_as_js_1.actingAs)(input.asUser),
         });
     }
+    /**
+     * One appointment, by the id you stored.
+     *
+     * **This is the read to make when you kept a booking id on a record of your
+     * own** - a meeting on a deal, an appointment on a case. `listBookings`
+     * cannot serve it: that is a window over `startAt`, and the `startAt` you
+     * cached is exactly what is wrong once someone has moved the appointment on
+     * the workspace's own calendar, so the window you build from it comes back
+     * without the row.
+     *
+     * A retired booking still resolves. `status: "rescheduled"` answers with
+     * `rescheduledToId`, so an id stored months ago leads to the appointment
+     * that exists today; `cancelled` answers with its reason. `not_found` means
+     * this workspace never had that booking.
+     */
+    getBooking(input) {
+        return (0, http_js_1.request)(this.transport, {
+            method: "GET",
+            path: `/scheduling/bookings/${encodeURIComponent(input.bookingId)}`,
+            query: { workspaceId: input.workspaceId },
+            headers: (0, acting_as_js_1.actingAs)(input.asUser),
+        });
+    }
     /** One page of the workspace's diary. */
     listBookings(input) {
         return (0, http_js_1.request)(this.transport, {

package/dist/esm/client/components/app-shell.js

@@ -20,6 +20,15 @@ import { useActivePath } from "../use-active-path.js";
 import { cn } from "../../cn.js";
 const COLLAPSED_KEY = "connect_sidenav_collapsed";
 const COLLAPSED_EVENT = "connect:sidenav-collapsed";
+/**
+ * The `<main>` element's id, and the skip link's target.
+ *
+ * Module-local rather than a prop: both ends of the pair live in this file, so
+ * there is nothing for a caller to keep in step - and a partner supplying
+ * their own id could only get it wrong. Namespaced because it lands in a
+ * document the partner also writes.
+ */
+const CONTENT_ID = "connect-main-content";
 /**
  * The stored rail preference, or `null` when there isn't one (or when reading
  * it is not allowed).
@@ -186,5 +195,5 @@ export function AppShell({ name, icon, homeHref = "/", nav, secondaryNav, active
     }), [renderLink, activePath, closeMobile]);
     const accountRow = signedOut ? (showAuthButtons && (_jsxs("div", { className: "flex flex-col gap-2", children: [_jsx(ConnectLoginButton, { size: "sm", fullWidth: true }), _jsx(ConnectRegisterButton, { size: "sm", fullWidth: true })] }))) : (_jsx(ConnectUserButton, { variant: "row", theme: theme, onThemeChange: onThemeChange }));
     const railContent = (_jsxs(_Fragment, { children: [_jsx(ConnectSidebarHeader, { name: name, icon: icon, homeHref: homeHref }), workspaceSwitcher !== false && (_jsx("div", { className: "shrink-0 px-3 pb-1", children: _jsx(ConnectWorkspaceSwitcher, {}) })), _jsx(ConnectSidebarBody, { children: _jsx(ConnectSidebarNav, { nav: visibleNav }) }), (visibleSecondaryNav || sidebarFooter || showAppsGrid) && (_jsxs(ConnectSidebarFooter, { separated: false, children: [visibleSecondaryNav && _jsx(ConnectSidebarNav, { nav: visibleSecondaryNav }), sidebarFooter, showAppsGrid && _jsx(ConnectAppsGrid, { variant: "row" })] })), accountRow && _jsx(ConnectSidebarFooter, { children: accountRow })] }));
-    return (_jsx(MotionProvider, { children: _jsxs("div", { className: cn("flex h-screen bg-background", className), children: [_jsx(ConnectShellProvider, { value: railShell, children: _jsx(ConnectSidebar, { children: railContent }) }), _jsx(Drawer.Backdrop, { isOpen: mobileOpen, onOpenChange: setMobileOpen, children: _jsx(Drawer.Content, { placement: "left", className: "w-[min(20rem,85vw)]", children: _jsx(Drawer.Dialog, { "aria-label": "Navigation menu", className: "p-0", children: _jsx(ConnectShellProvider, { value: drawerShell, children: _jsx("div", { className: "flex h-full flex-col", children: railContent }) }) }) }) }), _jsxs("div", { className: "flex min-w-0 flex-1 flex-col", children: [_jsxs("header", { className: "flex h-14 shrink-0 items-center gap-2 border-b border-border bg-surface px-3 md:hidden", children: [_jsx(Button, { isIconOnly: true, variant: "tertiary", size: "sm", "aria-label": "Open navigation menu", onPress: () => setMobileOpen(true), children: _jsx(Menu, { className: "size-5" }) }), _jsx(ConnectLogo, { name: name, icon: icon })] }), _jsx("main", { className: "flex-1 overflow-y-auto", children: _jsxs("div", { className: contentClassName ?? "w-full px-4 py-5 md:px-6 md:py-6", children: [gated ? _jsx(ConnectAccessGate, { children: children }) : children, footer] }) })] }), askAi && _jsx(ConnectAskAi, { ...(askAi === true ? {} : askAi) })] }) }));
+    return (_jsx(MotionProvider, { children: _jsxs("div", { className: cn("flex h-dvh bg-background", className), children: [_jsx("a", { href: `#${CONTENT_ID}`, className: "sr-only focus:not-sr-only focus:absolute focus:start-3 focus:top-3 focus:z-50 focus:rounded-lg focus:bg-surface focus:px-3 focus:py-2 focus:text-sm focus:font-medium focus:text-foreground focus:shadow-lg focus:outline-2 focus:outline-offset-2 focus:outline-focus", children: "Skip to content" }), _jsx(ConnectShellProvider, { value: railShell, children: _jsx(ConnectSidebar, { children: railContent }) }), _jsx(Drawer.Backdrop, { isOpen: mobileOpen, onOpenChange: setMobileOpen, children: _jsx(Drawer.Content, { placement: "left", className: "w-[min(20rem,85vw)]", children: _jsxs(Drawer.Dialog, { "aria-label": "Navigation menu", className: "p-0 pt-[env(safe-area-inset-top)] pb-[env(safe-area-inset-bottom)]", children: [_jsx(Drawer.CloseTrigger, { className: "end-3 top-[calc(--spacing(3)+env(safe-area-inset-top))]" }), _jsx(ConnectShellProvider, { value: drawerShell, children: _jsx("div", { className: "flex h-full flex-col [&>:first-child]:pe-10", children: railContent }) })] }) }) }), _jsxs("div", { className: "flex min-w-0 flex-1 flex-col", children: [_jsxs("header", { className: "flex h-14 shrink-0 items-center gap-2 border-b border-border bg-surface px-3 md:hidden", children: [_jsx(Button, { isIconOnly: true, variant: "tertiary", size: "sm", "aria-label": "Open navigation menu", onPress: () => setMobileOpen(true), children: _jsx(Menu, { className: "size-5" }) }), _jsx(ConnectLogo, { name: name, icon: icon })] }), _jsx("main", { id: CONTENT_ID, tabIndex: -1, className: "flex-1 overflow-y-auto outline-none", children: _jsxs("div", { className: contentClassName ?? "w-full px-4 py-5 md:px-6 md:py-6", children: [gated ? _jsx(ConnectAccessGate, { children: children }) : children, footer] }) })] }), askAi && _jsx(ConnectAskAi, { ...(askAi === true ? {} : askAi) })] }) }));
 }

package/dist/esm/client/components/sidebar.js

@@ -93,7 +93,23 @@ export function ConnectSidebarHeader({ name, icon, homeHref = "/" }) {
  * the sidebar is `shrink-0`, so this is the only part that ever gives way.
  */
 export function ConnectSidebarBody({ children }) {
-    return (_jsx("div", { className: "flex min-h-0 flex-1 flex-col gap-1 overflow-y-auto overflow-x-hidden px-3 py-2", children: children }));
+    return (
+    // `touch-pan-y touch-pinch-zoom` is what lets this scroll under a finger
+    // inside the mobile drawer. `Drawer.Dialog` carries an inline
+    // `touch-action: none` whenever it is dismissable - HeroUI sets it so its
+    // own pointer-driven drag-to-dismiss is not fighting the browser's pan -
+    // and the declaration meant to hand the scroll back to the scrollable
+    // region is missing from the shipped stylesheet: `@heroui/styles`'
+    // `drawer.css` carries the comment ("touch-action: pan-y allows vertical
+    // scrolling while the dialog captures drag gestures") on a `.drawer__body`
+    // rule that never sets the property. A nav longer than the panel was
+    // therefore frozen on a phone while scrolling normally under a wheel.
+    //
+    // `pinch-zoom` alongside `pan-y` rather than `pan-y` on its own: taking
+    // zoom away over a region of text is a WCAG 1.4.4 failure, and nothing
+    // here needs it suppressed. On the desktop rail, where no ancestor
+    // restricts anything, the pair is equivalent to the default.
+    _jsx("div", { className: "flex min-h-0 flex-1 touch-pan-y touch-pinch-zoom flex-col gap-1 overflow-y-auto overflow-x-hidden px-3 py-2", children: children }));
 }
 /**
  * A pinned region at the foot of the rail - the secondary nav, the launcher,

package/dist/esm/server/client.js

@@ -157,4 +157,4 @@ export class ConnectClient {
     }
 }
 /** Kept in step with `package.json` by `sdk.test.ts`. */
-export const SDK_VERSION = "0.26.0";
+export const SDK_VERSION = "0.28.0";

package/dist/esm/server/handler.js

@@ -508,6 +508,21 @@ export function createConnectHandler(options) {
                 asUser,
             }));
         },
+        /*
+         * Singular, and the id is a query param rather than a path segment - the
+         * table above is matched by exact string, which is the same reason
+         * reschedule and cancel take theirs in the body. Keying it as
+         * `/scheduling/bookings/{id}` would simply never match.
+         */
+        "GET /scheduling/booking": async (request) => {
+            const { workspaceId } = await requireWorkspace(request);
+            const asUser = await requireToken(request);
+            const bookingId = new URL(request.url).searchParams.get("bookingId");
+            if (!bookingId) {
+                return json({ error: { code: "validation_error", message: "bookingId is required" } }, 400);
+            }
+            return json(await client.scheduling.getBooking({ workspaceId, bookingId, asUser }));
+        },
         "GET /scheduling/bookings": async (request) => {
             const { workspaceId } = await requireWorkspace(request);
             const asUser = await requireToken(request);

package/dist/esm/server/resources/scheduling.js

@@ -58,6 +58,29 @@ export class SchedulingResource {
             headers: actingAs(input.asUser),
         });
     }
+    /**
+     * One appointment, by the id you stored.
+     *
+     * **This is the read to make when you kept a booking id on a record of your
+     * own** - a meeting on a deal, an appointment on a case. `listBookings`
+     * cannot serve it: that is a window over `startAt`, and the `startAt` you
+     * cached is exactly what is wrong once someone has moved the appointment on
+     * the workspace's own calendar, so the window you build from it comes back
+     * without the row.
+     *
+     * A retired booking still resolves. `status: "rescheduled"` answers with
+     * `rescheduledToId`, so an id stored months ago leads to the appointment
+     * that exists today; `cancelled` answers with its reason. `not_found` means
+     * this workspace never had that booking.
+     */
+    getBooking(input) {
+        return request(this.transport, {
+            method: "GET",
+            path: `/scheduling/bookings/${encodeURIComponent(input.bookingId)}`,
+            query: { workspaceId: input.workspaceId },
+            headers: actingAs(input.asUser),
+        });
+    }
     /** One page of the workspace's diary. */
     listBookings(input) {
         return request(this.transport, {

package/dist/types/server/client.d.ts

@@ -123,4 +123,4 @@ export declare class ConnectClient {
     constructor(options: ConnectClientOptions);
 }
 /** Kept in step with `package.json` by `sdk.test.ts`. */
-export declare const SDK_VERSION = "0.26.0";
+export declare const SDK_VERSION = "0.28.0";

package/dist/types/server/resources/scheduling.d.ts

@@ -97,6 +97,25 @@ export declare class SchedulingResource {
      * days rather than an error.
      */
     findSlots(input: FindSlotsInput): Promise<BookingSlots>;
+    /**
+     * One appointment, by the id you stored.
+     *
+     * **This is the read to make when you kept a booking id on a record of your
+     * own** - a meeting on a deal, an appointment on a case. `listBookings`
+     * cannot serve it: that is a window over `startAt`, and the `startAt` you
+     * cached is exactly what is wrong once someone has moved the appointment on
+     * the workspace's own calendar, so the window you build from it comes back
+     * without the row.
+     *
+     * A retired booking still resolves. `status: "rescheduled"` answers with
+     * `rescheduledToId`, so an id stored months ago leads to the appointment
+     * that exists today; `cancelled` answers with its reason. `not_found` means
+     * this workspace never had that booking.
+     */
+    getBooking(input: ActingAsOption & {
+        workspaceId: string;
+        bookingId: string;
+    }): Promise<Booking>;
     /** One page of the workspace's diary. */
     listBookings(input: ListBookingsInput): Promise<ListBookingsPage>;
     /**

package/dist/types/types.d.ts

@@ -775,7 +775,7 @@ export interface EmitEventsResponse {
  * `createConnectWebhookHandler` simply ignores anything you have not
  * registered a handler for.
  */
-export type ConnectWebhookEventType = "workspace.deletion_scheduled" | "workspace.deletion_cancelled" | "workspace.deleted" | "subscription.cancelled";
+export type ConnectWebhookEventType = "workspace.deletion_scheduled" | "workspace.deletion_cancelled" | "workspace.deleted" | "subscription.cancelled" | "call.completed" | "call.missed" | "booking.confirmed" | "booking.cancelled" | "booking.rescheduled" | "contact.created" | "contact.updated";
 /**
  * A workspace's deletion has been confirmed and the grace window is running.
  *
@@ -815,12 +815,197 @@ export interface SubscriptionCancelledEvent {
     subscriptionId: string;
     applicationId: string;
 }
+/** Which way a call went. */
+export type ConnectCallDirection = "inbound" | "outbound";
+/**
+ * A call ended.
+ *
+ * The event an external system of record is built on: it is what turns a
+ * conversation that happened in Connect's telephony into a row in your own
+ * timeline with nobody retyping it. Fires for every completed call, whether an
+ * agent answered it or a person did.
+ */
+export interface CallCompletedEvent {
+    workspaceId: string;
+    callId: string;
+    channelId: string | null;
+    /**
+     * E.164, and the only identity a call event carries.
+     *
+     * There is deliberately no `contactId`: Connect resolves a caller to a
+     * contact by number, and at the moment a call ends it may not have done so
+     * at all - the field would be `null` on most deliveries, which is a field
+     * that silently does nothing. Match on this instead. It is the same
+     * canonical form `contacts.lookupByPhone` takes, so resolving it is one call
+     * if you want the contact.
+     */
+    contactPhone: string | null;
+    direction: ConnectCallDirection;
+    /** How it ended, as Connect's telephony reported it - `"completed"`, `"transferred"`, … */
+    outcome: string;
+    durationSeconds: number;
+    /**
+     * What the agent's skills captured during the conversation, keyed by the
+     * capture fields the agent declares.
+     *
+     * Shapeless on purpose - the keys and the value types are whatever that
+     * agent's `extractionSchema` declares, which Connect does not constrain.
+     * `{}` on most calls, since an unanswered or human-answered call extracts
+     * nothing, so treat every key as optional rather than checking the object
+     * for presence.
+     */
+    extraction: Record<string, unknown>;
+    /** ISO-8601. */
+    occurredAt: string;
+}
+/**
+ * A call reached a channel and nothing answered it.
+ *
+ * Its own event rather than an `outcome` on the one above, because the action
+ * differs in kind: a completed call is something to file, a missed one is
+ * somebody to ring back. Treating this as a lead is the right thing to do
+ * with it.
+ */
+export interface CallMissedEvent {
+    workspaceId: string;
+    callId: string;
+    channelId: string | null;
+    /** E.164, and the only identity this carries - see `CallCompletedEvent.contactPhone`. */
+    contactPhone: string | null;
+    direction: ConnectCallDirection;
+    /** ISO-8601. */
+    occurredAt: string;
+}
+/**
+ * An appointment was booked and is holding its slot.
+ *
+ * Raised however it was booked - the customer's portal, the public booking
+ * page, a voice agent mid-call, or your own API call - so you get one shape
+ * for all four and never have to reconcile "did we create this, or did they?".
+ * Dedupe on `bookingId`, not on the envelope alone.
+ */
+export interface BookingConfirmedEvent {
+    workspaceId: string;
+    bookingId: string;
+    eventTypeId: string;
+    eventTypeName: string;
+    /** ISO-8601, UTC. Render it in `timezone`, which is the workspace's, not the viewer's. */
+    startAt: string;
+    endAt: string;
+    /** IANA zone the appointment was booked in. */
+    timezone: string;
+    attendeeName: string;
+    attendeeEmail: string | null;
+    /** E.164. */
+    attendeePhone: string | null;
+    contactId: string | null;
+    /** Connect user ids of the hosts. */
+    hostMemberIds: string[];
+    /** ISO-8601. */
+    occurredAt: string;
+}
+/** An appointment was cancelled. The slot is free and any prep against it is void. */
+export interface BookingCancelledEvent {
+    workspaceId: string;
+    bookingId: string;
+    eventTypeId: string;
+    eventTypeName: string;
+    /** ISO-8601. The time it *was* going to happen. */
+    startAt: string;
+    attendeeName: string;
+    contactId: string | null;
+    /** ISO-8601. */
+    occurredAt: string;
+}
+/**
+ * An appointment moved.
+ *
+ * Connect retires the old booking and writes a new one rather than mutating
+ * it, so this carries **both ids**: `bookingId` is the row that now exists and
+ * `previousBookingId` is the one you are already holding. Reconcile on the
+ * previous id or you will end up with two appointments.
+ */
+export interface BookingRescheduledEvent {
+    workspaceId: string;
+    bookingId: string;
+    eventTypeId: string;
+    eventTypeName: string;
+    /** ISO-8601, the new time. */
+    startAt: string;
+    endAt: string;
+    previousBookingId: string;
+    /** ISO-8601, the time it was before. */
+    previousStartAt: string;
+    timezone: string;
+    attendeeName: string;
+    contactId: string | null;
+    /** ISO-8601. */
+    occurredAt: string;
+}
+/**
+ * How Connect came to know a contact.
+ *
+ * `extraction` is the interesting one: an agent's skill captured them from
+ * what was said, with nobody typing anything. `call` means the number was seen
+ * on a call. `manual` and `import` are the two a human stands behind, and
+ * Connect lets only those overwrite a field that already has a value.
+ */
+export type ConnectContactSource = "call" | "manual" | "import" | "api" | "extraction";
+/**
+ * Connect learned about a person.
+ *
+ * The event with no equivalent anywhere else in this API: most often an agent
+ * captured them mid-call through the `contact-capture` skill, so the contact
+ * exists in Connect and your product has never heard of them. Without this the
+ * capture is invisible where the customer actually works.
+ */
+export interface ContactCreatedEvent {
+    workspaceId: string;
+    contactId: string;
+    name: string | null;
+    /** E.164. */
+    phone: string | null;
+    email: string | null;
+    company: string | null;
+    source: ConnectContactSource;
+    /** ISO-8601. */
+    occurredAt: string;
+}
+/**
+ * A known contact's details changed.
+ *
+ * `changed` names the fields that actually moved, so you can apply a patch
+ * rather than overwriting fields your own users may have curated - a customer
+ * who corrected a company name in your product should not have it replaced by
+ * what an agent heard over a bad line.
+ */
+export interface ContactUpdatedEvent {
+    workspaceId: string;
+    contactId: string;
+    name: string | null;
+    /** E.164. */
+    phone: string | null;
+    email: string | null;
+    company: string | null;
+    /** The field names that changed on this update. */
+    changed: string[];
+    source: ConnectContactSource;
+    /** ISO-8601. */
+    occurredAt: string;
+}
 /** Maps each event type to the shape of its `data`. */
 export interface ConnectWebhookEventMap {
     "workspace.deletion_scheduled": WorkspaceDeletionScheduledEvent;
     "workspace.deletion_cancelled": WorkspaceDeletionCancelledEvent;
     "workspace.deleted": WorkspaceDeletedEvent;
     "subscription.cancelled": SubscriptionCancelledEvent;
+    "call.completed": CallCompletedEvent;
+    "call.missed": CallMissedEvent;
+    "booking.confirmed": BookingConfirmedEvent;
+    "booking.cancelled": BookingCancelledEvent;
+    "booking.rescheduled": BookingRescheduledEvent;
+    "contact.created": ContactCreatedEvent;
+    "contact.updated": ContactUpdatedEvent;
 }
 /** The envelope, as it arrives on the wire. */
 export interface ConnectWebhookEnvelope<T extends ConnectWebhookEventType = ConnectWebhookEventType> {
@@ -1283,6 +1468,18 @@ export type BookingSource = "agent-call" | "portal" | "api";
 export interface Booking {
     id: string;
     eventTypeId: string;
+    /**
+     * The workspace members committed to this appointment.
+     *
+     * These are `WorkspaceMember.id` values - the same ids `workspaces.listMembers`
+     * returns and `listBookings`' `hostMemberId` filter takes, so an owner column
+     * is a lookup against a roster you already have rather than another round trip.
+     *
+     * Resolved when the slot was held and frozen there: a round-robin event type
+     * picks one host, a collective one commits the whole group, and re-pointing
+     * the event type afterwards does not move an appointment already made.
+     */
+    hostMemberIds: string[];
     status: BookingStatus;
     /** ISO-8601 instants. */
     startAt: string;

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@cosmoops/connect-sdk",
-  "version": "0.26.0",
+  "version": "0.28.0",
   "description": "Official server-side SDK for the CosmoOps Connect platform API - Login with Connect, entitlements, billing and metering.",
   "license": "SEE LICENSE IN LICENSE",
   "type": "commonjs",