@cosmoops/connect-sdk 0.25.0 → 0.27.0

package/dist/theme.css

@@ -106,6 +106,34 @@
   --overlay: oklch(21% 0.002 145.67);
 }
 
+/* ---------------------------------------------------------------------------
+ * Radius, as one number.
+ *
+ * HeroUI derives its whole radius scale from `--radius`: `rounded-sm` is
+ * `--radius * 0.5`, `rounded-lg` is `--radius * 1`, and `rounded-3xl` - what
+ * `.button` resolves to - is `--radius * 3`. The scale is a set of *ratios*,
+ * so this token is the only magnitude in it and one value decides every
+ * corner in every component.
+ *
+ * The stock pair is `--radius: 0.5rem` with `--field-radius` derived at
+ * `calc(var(--radius) * 1.5)`. Connect's own app has always run at `0.25rem`,
+ * but the shared theme carried neither token - so every partner platform
+ * silently inherited HeroUI's stock values and drew its cards and inputs at
+ * twice Connect's radius. That was the one place platforms sharing this
+ * palette visibly disagreed. Stating it here is what makes "the same theme"
+ * mean the same shapes as well as the same colours.
+ *
+ * `--field-radius` is set rather than derived, deliberately: at 1.5x an input
+ * rounds harder than the card holding it, which inverts the nesting the
+ * radius scale exists to express.
+ *
+ * Radius does not vary by theme, so this sits outside the light/dark blocks.
+ * ------------------------------------------------------------------------ */
+:root {
+  --radius: 0.25rem;
+  --field-radius: 0.25rem;
+}
+
 body {
   background: var(--background);
   color: var(--foreground);
@@ -197,3 +225,28 @@ body {
     animation: none;
   }
 }
+
+/* ---------------------------------------------------------------------------
+ * A hand-rolled button still looks pressable.
+ *
+ * Tailwind v4's Preflight sets `cursor: default` on `button`, reversing v3 -
+ * and HeroUI restores the pointer only on its *own* classes, through
+ * `--cursor-interactive` on `.button`, `.chip` triggers and friends. So a
+ * plain `<button>` - which every app writes: a menu row, a filter chip, a
+ * calendar day, a card that is really a press target - renders with an arrow
+ * and reads as text.
+ *
+ * That is not a per-button oversight to fix per button. It is the default
+ * being wrong for this codebase, so it is corrected once, here, where every
+ * application platform importing this theme picks it up.
+ *
+ * `:where()` keeps the specificity at zero, so any component rule - including
+ * HeroUI's own disabled handling, which swaps in `--cursor-disabled` - still
+ * wins outright. The `:not()`s are belt and braces for the un-classed case,
+ * where there is no component rule to defer to.
+ * ------------------------------------------------------------------------ */
+@layer base {
+  :where(button, [role="button"]):not(:disabled):not([aria-disabled="true"]):not([data-disabled="true"]) {
+    cursor: pointer;
+  }
+}

package/dist/types/client/components/access-gate.d.ts

@@ -56,7 +56,16 @@ export interface ConnectAccessGateProps {
     children: ReactNode;
     /** Replaces the default card for every hard-block state (`suspended`/`no_subscription`/`onboarding_pending`/`blocked`) uniformly. For a different card per state, call `useConnectAccessGate()` directly instead. */
     fallback?: ReactNode;
-    /** Shown while the first read is in flight. */
+    /**
+     * Shown while the first read is in flight, **in place of** `children`.
+     *
+     * Opt-in, and rarely what you want. The default is to render `children`
+     * during that window - see the component's doc comment on why a blanket
+     * placeholder over a whole application is worse than the flash it avoids.
+     * Pass this only for a gate wrapped around one small region whose blocked
+     * and unblocked states differ enough that showing the unblocked one first
+     * would mislead.
+     */
     loading?: ReactNode;
     className?: string;
 }
@@ -85,9 +94,31 @@ export interface ConnectAccessGateProps {
  * entire app must not hide a public landing page behind an empty gate. Your
  * own sign-in flow decides what a signed-out visitor sees.
  *
+ * **While the verdict is unknown, `children` render.** The two reads behind
+ * this gate are client-side round trips that happen on *every* page load, and
+ * this component is mounted around an entire application - so blocking on
+ * them replaced every partner's whole page with one placeholder until both
+ * came back. Anything the host had streamed underneath was discarded: per-
+ * section skeletons never painted, and a page built as a static shell with
+ * suspended regions arrived all at once anyway. That is the common path, paid
+ * by every workspace on every navigation.
+ *
+ * Rendering `children` instead makes the loading case agree with the two
+ * cases either side of it. A *failed* read already falls through to `clear`
+ * ("fail open rather than hard-block the whole app on a network hiccup", in
+ * `useConnectAccessGate`), and a signed-out visitor already renders
+ * `children` too - "we do not know yet" was the one unknown treated as a
+ * refusal.
+ *
+ * What it costs is honest and small: a genuinely blocked workspace sees its
+ * app for the length of one round trip before the block card replaces it.
+ * That is the rare path, it is self-correcting, and it is the same exposure
+ * the failed-read branch has always accepted. Pass `loading` to opt back into
+ * a placeholder for a gate around one small region.
+ *
  * **This is a UX gate, not a security boundary** - same caveat as every
- * other gate in this package. The authoritative check is
- * `client.entitlements.getReadiness` on your server, before you do the
- * thing.
+ * other gate in this package, and the reason the trade above is available at
+ * all. The authoritative check is `client.entitlements.getReadiness` on your
+ * server, before you do the thing.
  */
 export declare function ConnectAccessGate({ children, fallback, loading, className }: ConnectAccessGateProps): import("react").JSX.Element;

package/dist/types/client/components/cursor-pagination.d.ts

@@ -8,6 +8,11 @@ export interface ConnectCursorPaginationProps {
     onNext: (cursor: string) => void;
     onPrevious: () => void;
     isPending?: boolean;
+    /**
+     * Merged onto the root, so a utility here replaces the conflicting default
+     * rather than sitting beside it. See `cn`.
+     */
+    className?: string;
     /** Singular/plural noun for the count, e.g. `["contact", "contacts"]`. */
     noun?: readonly [string, string];
 }
@@ -24,4 +29,4 @@ export interface ConnectCursorPaginationProps {
  * filtering or paging changed the result set. Without it the table silently
  * swaps its contents.
  */
-export declare function ConnectCursorPagination({ shown, nextCursor, hasPrevious, onNext, onPrevious, isPending, noun, }: Readonly<ConnectCursorPaginationProps>): import("react").JSX.Element;
+export declare function ConnectCursorPagination({ shown, nextCursor, hasPrevious, onNext, onPrevious, isPending, noun, className, }: Readonly<ConnectCursorPaginationProps>): import("react").JSX.Element;

package/dist/types/client/components/filter-tabs.d.ts

@@ -8,6 +8,11 @@ export interface ConnectFilterTabsProps<TValue extends string> {
     options: ReadonlyArray<ConnectFilterTabsOption<TValue>>;
     value: TValue | null;
     onChange: (value: TValue | null) => void;
+    /**
+     * Merged onto the root, so a utility here replaces the conflicting default
+     * rather than sitting beside it. See `cn`.
+     */
+    className?: string;
     /** Names the group for assistive technology - "Filter contacts by lifecycle". */
     label: string;
 }
@@ -20,7 +25,8 @@ export interface ConnectFilterTabsProps<TValue extends string> {
  * selected one should be announced as selected. A group of `<button>`s gets
  * neither, and that is the usual hand-rolled shape.
  *
- * Scrolls horizontally rather than wrapping on a narrow viewport - a filter
- * strip that wraps to three lines pushes the list itself off the screen.
+ * Wraps rather than scrolling on a narrow viewport. See the note on the
+ * container below: a horizontal scroller nested in a vertically scrolling
+ * page hides its overflow rather than deferring it.
  */
-export declare function ConnectFilterTabs<TValue extends string>({ options, value, onChange, label, }: Readonly<ConnectFilterTabsProps<TValue>>): import("react").JSX.Element;
+export declare function ConnectFilterTabs<TValue extends string>({ options, value, onChange, label, className, }: Readonly<ConnectFilterTabsProps<TValue>>): import("react").JSX.Element;

package/dist/types/cn.d.ts

@@ -0,0 +1,48 @@
+/**
+ * Merge class names so a caller's Tailwind utility actually wins.
+ *
+ * Every component in this package carries default utilities, and a partner
+ * styling one reaches for `className`. Concatenating the two does not do what
+ * it looks like it does:
+ *
+ * ```tsx
+ * // ConnectBookingCalendar with className="gap-8"
+ * <div className={`flex flex-col gap-4 ${className}`} />
+ * //  -> class="flex flex-col gap-4 gap-8"
+ * ```
+ *
+ * Both rules are now in the stylesheet and both match, so the winner is
+ * decided by **source order in the generated CSS**, not by the order they
+ * appear in the attribute. Tailwind sorts its output by its own internal
+ * ordering, so whether `gap-8` beats `gap-4` depends on which utility Tailwind
+ * happens to emit later - `p-8` over `px-3 py-2` lands one way, `gap-8` over
+ * `gap-4` the other. An override that works on one prop and silently does
+ * nothing on the next is worse than one that never works, because nobody
+ * suspects the mechanism.
+ *
+ * `cn` resolves it by *removing* the conflicting default rather than adding to
+ * it - `cn("flex flex-col gap-4", "gap-8")` is `"flex flex-col gap-8"`, and
+ * `cn("px-3 py-2", "p-8")` is `"p-8"`. That is a real understanding of
+ * Tailwind's shorthand groups, which is why it is `tailwind-merge` and not a
+ * `join(" ")`.
+ *
+ * Re-exported rather than reimplemented. The implementation is
+ * `tailwind-variants`' `cn`, which `@heroui/react` re-exports and which every
+ * HeroUI component uses internally through `tv` - so a partner's override is
+ * resolved by exactly the same rules whether it lands on one of these
+ * components or on a HeroUI one. It is reached through `@heroui/react` rather
+ * than `tailwind-variants` directly because HeroUI is already a declared peer
+ * of both UI entry points, and importing a package this manifest does not name
+ * would be relying on someone else's transitive tree.
+ *
+ * Safe in the server-rendered `./ui` entry: the `@heroui/react` barrel carries
+ * no top-level `"use client"` (only its individual components do), so `cn`
+ * arrives as a real function rather than a client-reference proxy. That
+ * distinction matters for a *function* in a way it does not for a component -
+ * `ui/section.tsx` has always imported `Card` from the same barrel.
+ *
+ * Not exported from the root entry, which is isomorphic and React-free. It is
+ * public from `./ui`, because a partner composing on top of these primitives
+ * needs the same merge the primitives use.
+ */
+export { cn } from "@heroui/react";

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.25.0";
+export declare const SDK_VERSION = "0.27.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/store.d.ts

@@ -82,6 +82,12 @@ export interface StoreIndexField {
  *
  * Throws for a query Firestore cannot serve at all - two `array-contains`
  * filters, ranges over two fields, or a range ordered by a different field.
+ *
+ * A **range bounded on both sides** over one field needs no declaration: two
+ * filters, one field, and the automatic single-field index serves it. Ask this
+ * function with the filters you actually send rather than with one of the two
+ * bounds - the answer is the same, and modelling the range as a single `>=`
+ * is how a schema comes to declare a shape its own runtime does not make.
  */
 export declare function storeIndexFor(query: {
     filters?: readonly StoreQueryFilter[];

package/dist/types/types.d.ts

@@ -1283,6 +1283,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/dist/types/ui/index.d.ts

@@ -38,3 +38,9 @@ export { ConnectSettingRow } from "./setting-row.js";
 export type { ConnectSettingRowProps } from "./setting-row.js";
 export { ConnectStatusChip } from "./status-chip.js";
 export type { ConnectStatusTone, ConnectStatusPresentation } from "./status-chip.js";
+/**
+ * Merge class names the way these components do internally, so a utility you
+ * pass wins over a conflicting default instead of racing it in the stylesheet.
+ * Use it when composing your own components on top of these.
+ */
+export { cn } from "../cn.js";

package/dist/types/ui/page-shell.d.ts

@@ -7,6 +7,12 @@ export interface ConnectPageShellProps {
     clamp?: boolean;
     /** Rendered above the header - a breadcrumb trail, a back link, a banner. */
     above?: ReactNode;
+    /**
+     * Merged onto the page root, so a utility here beats the default rather than
+     * sitting beside it - `className="space-y-8"` really does widen the page gap.
+     * See `cn`.
+     */
+    className?: string;
     children?: ReactNode;
 }
 /**
@@ -28,7 +34,7 @@ export interface ConnectPageShellProps {
  *
  * `space-y-5` is the page gap, owned here so it has exactly one definition.
  */
-export declare function ConnectPageShell({ title, description, action, clamp, above, children, }: Readonly<ConnectPageShellProps>): import("react").JSX.Element;
+export declare function ConnectPageShell({ title, description, action, clamp, above, children, className, }: Readonly<ConnectPageShellProps>): import("react").JSX.Element;
 export declare namespace ConnectPageShell {
     var Header: typeof ConnectPageHeader;
     var Async: ({ fallback, children, }: Readonly<{

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@cosmoops/connect-sdk",
-  "version": "0.25.0",
+  "version": "0.27.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",