@company-semantics/contracts 58.3.0 → 58.5.0

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@company-semantics/contracts",
-  "version": "58.3.0",
+  "version": "58.5.0",
   "private": false,
   "repository": {
     "type": "git",

package/src/execution/summary.ts

@@ -22,9 +22,12 @@ import type { ISO8601Timestamp } from "./types";
 
 /**
  * Target of an execution action.
- * Currently supports Slack integration; extensible for future integrations.
+ * Slack carries an optional workspace qualifier; BambooHR is addressed by
+ * connectionId alone (the org has at most one HRIS connection), so its
+ * target is bare (ADR-BE-610).
  */
-export type ExecutionTarget = { type: "slack"; workspaceId?: string };
+export type ExecutionTarget =
+  { type: "slack"; workspaceId?: string } | { type: "bamboohr" };
 
 // =============================================================================
 // Initiator

package/src/index.ts

@@ -687,6 +687,7 @@ export type { OrgDirectoryPerson, OrgDirectoryResponse } from "./org/index";
 // caller's own directory rather than supplied by the caller.
 export {
   BATCH_INVITE_PERSONS_MAX,
+  INVITE_EXPIRY_DAYS,
   BATCH_INVITE_SKIP_REASONS,
   BatchInviteSkipReasonSchema,
   BatchInviteRequestSchema,

package/src/integrations/README.md

@@ -20,6 +20,10 @@ alongside `Meetings`, `Comms`, and `Docs`.
   its enum mirrors the backend's `ConnectionRevokedReason` exactly — the app
   `parse`s this projection, so a value missing from the enum throws rather than
   degrades (ADR-CONTRACTS-138).
+- `credentialState: 'disconnected'` is a user-chosen stop, not a failure
+  (backend ADR-BE-610): imported data and sync history remain, `subdomain` and
+  `lastSyncAt` stay populated for the Reconnect flow, `connectionId` and
+  `revokedReason` are null, and `syncHealth` is null (nothing is broken).
 - `HrConnectInputSchema` carries only the customer's provider `subdomain`; no
   secrets or provider credentials live in contracts.
 - Pure vocabulary — `zod` is the only runtime import (vocabulary-guard).

package/src/integrations/schemas.ts

@@ -33,26 +33,37 @@ export const HrConnectionStatusSchema = z
         "whenever the integration cannot sync — read `credentialState` to " +
         "tell a never-connected integration from one whose grant died.",
     }),
-    credentialState: z.enum(["usable", "unusable", "absent"]).meta({
-      description:
-        "Why the integration is or is not working. 'usable' — a connection " +
-        "exists and its credential works (`connected` is true). 'unusable' " +
-        "— a connection exists but its credential cannot be used (expired " +
-        "or revoked grant); previously synced data remains, and the user " +
-        "must reconnect. 'absent' — no connection at all. Distinguishing " +
-        "'unusable' from 'absent' is the whole point: both leave " +
-        "`connected` false, but only one of them is the user's fault to fix " +
-        "by connecting for the first time.",
-    }),
+    credentialState: z
+      .enum(["usable", "unusable", "disconnected", "absent"])
+      .meta({
+        description:
+          "Why the integration is or is not working. 'usable' — a connection " +
+          "exists and its credential works (`connected` is true). 'unusable' " +
+          "— a connection exists but its credential cannot be used (expired " +
+          "or revoked grant); previously synced data remains, and the user " +
+          "must reconnect. 'disconnected' — the user chose to stop syncing " +
+          "(ADR-BE-610): credentials are gone by intent, imported data and " +
+          "sync history remain, and Reconnect resumes the same integration " +
+          "identity rather than starting over; nothing is broken, so it " +
+          "earns neutral treatment, not the needs-attention treatment " +
+          "'unusable' gets. 'absent' — no connection at all. The three " +
+          "not-connected states all leave `connected` false but ask " +
+          "different things of the reader: 'unusable' is 'fix me', " +
+          "'disconnected' is 'resume when ready', 'absent' is 'connect for " +
+          "the first time'.",
+      }),
     connectionId: z
       .string()
       .nullable()
       .meta({
         description:
           "Stable id of the connection row — the handle the app passes to " +
-          "`integration.disconnect`. Present whenever a connection exists, " +
-          "including when `credentialState` is 'unusable', so a dead " +
-          "integration can still be disconnected. Null only when 'absent'.",
+          "`integration.disconnect`. Present whenever there is something to " +
+          "disconnect, including when `credentialState` is 'unusable', so a " +
+          "dead integration can still be disconnected. Null when 'absent' " +
+          "and when 'disconnected' — a disconnected row is retained for " +
+          "history/identity (ADR-BE-610) but there is no credential left to " +
+          "disconnect, so no disconnect handle is offered.",
       }),
     subdomain: z
       .string()
@@ -106,8 +117,9 @@ export const HrConnectionStatusSchema = z
           "restored there. The distinction matters because the four cases " +
           "ask different things of the reader: three are 'click Reconnect' " +
           "and one is 'go fix it in the provider first'. Null whenever " +
-          "`credentialState` is not 'unusable', and null on a connection " +
-          "revoked before this field existed.",
+          "`credentialState` is not 'unusable' (including 'disconnected', " +
+          "which is chosen, not suffered), and null on a connection revoked " +
+          "before this field existed.",
       }),
   })
   .meta({

package/src/org/README.md

@@ -163,6 +163,7 @@ Shared type vocabulary for organization ownership, type classification, and tran
 - `INVITE_BATCH_ITEM_REASONS` — Why an item is not `sent`.
 - `INVITE_BATCH_ITEM_STATUSES` — Per-recipient outcome within a batch. - `eligible` — will be invited when the batch is sent. - `excluded` —…
 - `INVITE_BATCH_STATUSES` — Batch lifecycle. - `draft` — created, membership not yet evaluated.
+- `INVITE_EXPIRY_DAYS` — How many days an invitation link stays redeemable.
 - `IdentityTrustLevel` _(type)_ — Identity Trust Level — org's identity posture
 - `IntegrationRequest` _(type)_ — Advisory integration request created by a member.
 - `IntegrationRequestStatus` _(type)_ — Status of an integration request from a member.

package/src/org/index.ts

@@ -412,6 +412,7 @@ export {
   OrgDirectoryPersonSchema,
   OrgDirectoryResponseSchema,
   BATCH_INVITE_PERSONS_MAX,
+  INVITE_EXPIRY_DAYS,
   BATCH_INVITE_SKIP_REASONS,
   BatchInviteSkipReasonSchema,
   BatchInviteRequestSchema,

package/src/org/schemas.ts

@@ -854,6 +854,20 @@ export type OrgDirectoryResponse = z.infer<typeof OrgDirectoryResponseSchema>;
  */
 export const BATCH_INVITE_PERSONS_MAX = 100;
 
+/**
+ * How many days an invitation link stays redeemable.
+ *
+ * Shared vocabulary, not prose: the backend stamps `expires_at` from this when
+ * it mints an invite, and the review surface states the same window to the
+ * person about to send one. It lived in both places as a literal and drifted —
+ * the copy still promised seven days after the policy moved.
+ *
+ * A SECURITY parameter as much as a UX one: it bounds how long a leaked invite
+ * link stays usable, so widening it is a deliberate trust-model change rather
+ * than a copy edit.
+ */
+export const INVITE_EXPIRY_DAYS = 30;
+
 /** @deprecated Use {@link CreateInviteBatchRequestSchema}. Removed in 58.0.0. */
 export const BatchInviteRequestSchema = z.object({
   personIds: z.array(z.string().uuid()).min(1).max(BATCH_INVITE_PERSONS_MAX),